Building an LGSCO evidence bundle

What this guide covers

A strong council case is usually built from records rather than adjectives. Keep the original report, complaint, acknowledgements, call notes, screenshots, photographs, policies, decision letters and a dated chronology. Where an account changes, set the competing statements side by side and ask the authority to reconcile them. FOI, EIR and subject access can sometimes add evidence, but each regime has a different purpose and exemptions.

Turn months of council correspondence into a usable Ombudsman submission with a chronology, issues schedule, evidence index and focused documents.

The points that usually decide the case

• Lead with a concise summary: what the council did wrong, the main injustice and the remedy sought. Do not force the investigator to discover the complaint by reading attachments.
• Use a dated chronology containing only material events and cite a document reference for each contested fact.
• Create separate headings for service failure and complaint-handling failure. They may produce different forms of injustice.
• Use an evidence index with document number, date, author/source and short relevance description.
• Where you allege contradiction, place the two statements in a comparison table and cite both sources.
• Do not overload the initial submission with repetitive correspondence. Preserve the full file and provide the key documents most capable of proving the issues.

Common situations

Create a single evidence spine

Use a chronology with date, event, source and significance. Give every important document a short label. This is far more useful than forwarding a mailbox full of emails. A later reviewer should be able to see what was promised, what changed and what remained unresolved without reconstructing the case from scratch.

Distinguish contradiction from development

Not every changed explanation is improper: new evidence can legitimately change a position. The question is whether the authority acknowledges the earlier account, explains the change and shows the evidence supporting the new conclusion. An unexplained shift is much more probative than a reasoned correction.

Ask precise disclosure questions

Information-rights requests work best when tied to a known issue. Seek the recorded information that would test a disputed proposition: a policy, inspection record, audit trail, call note, decision criterion or technical specification. Do not assume FOI gives access to personal complaint records or that a SAR entitles you to every internal document in unredacted form.

Prepare for an external reader

An Ombudsman or regulator needs an auditable record. Preserve final responses, appeal rights, dates, reference numbers and the version of any policy relied on. A short index explaining why each document matters is more persuasive than sheer volume.

Build around fault, injustice and remedy

An Ombudsman submission is easier to assess when every ground answers three questions: what was the fault, what injustice did it cause, and what remedy would address that injustice? A procedural mistake that made no practical difference may attract less attention than a smaller-looking error that caused months of delay, loss of a statutory opportunity or repeated avoidable effort.

Start with a one-page case map before the chronology. List the service issue, the complaint-handling issue, any separate appeal or information-rights issue, and the outcome sought. Then use the chronology to prove the sequence rather than to tell the entire story again.

Use an evidence index that explains relevance

Give each key item a stable label such as C01, C02 and C03. Record its date, author/source and a one-line statement of what it proves. Where two documents conflict, cite both in the same ground. Keep duplicate email chains, signatures and repeated footer material out of the core bundle unless they add something material. The objective is an auditable record, not the largest possible attachment.

Evidence to keep

Build the record as you go. The most useful evidence for this topic usually includes:

• chronology with source references
• original operational report and complaint
• call notes and follow-up confirmation emails
• portal screenshots/status changes
• relevant policy or technical disclosure
• evidence index identifying what each document proves

Keep originals and, where a document is later replaced online, retain the version that actually applied to your case. For calls, a contemporaneous note made immediately afterwards is far more useful than trying to reconstruct the conversation months later.

How to put the issue in writing

Use a short issue structure rather than one long narrative. Start with the decision, failure or service request and its reference number. Then number each complaint point. For each point identify the relevant date, the evidence, what you say was wrong, the practical effect and the outcome you want.

If the council has given different explanations, quote each material position with its date and ask it to reconcile them. If a response omits an issue, say “Issue 3 was not answered” and restate only that issue. This produces a record that can be audited at Stage 2 or by an external body without forcing the reader to infer what remains disputed.

When to escalate

Use the evidence to support the route that has power to decide the issue. For LGSCO, show fault and injustice. For ICO/FOI routes, frame the information-rights issue separately. Evidence gathering should not become a reason to miss an appeal deadline.

Escalation should not become an endless email chain. Once the authority has given a final response, or the relevant procedure is unreasonably stalled, preserve the final position and use the external route that has jurisdiction. Keep any legal limitation or statutory appeal deadline under separate review.

What this route cannot guarantee

A complaint can expose poor administration, require a reasoned response and support a remedy, but it does not guarantee the technical, enforcement or discretionary outcome you prefer. Where an authority has lawful discretion, the key question is usually whether it gathered the relevant evidence, applied the correct framework, gave intelligible reasons and acted without avoidable delay.

Likewise, an Ombudsman recommendation, statutory appeal, civil claim, data-protection complaint and information request perform different jobs. ConsumerWise links them where they overlap but keeps the legal tests separate.