Using a subject access request in a council dispute

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.

Obtain your personal data from council case-management, call, complaint and contact systems without confusing a SAR with discovery or FOI.

The points that usually decide the case

• A SAR gives access to your personal data, not a guaranteed copy of every document that mentions the case. The council can redact third-party data and apply statutory exemptions where appropriate.
• Target known systems and data categories: complaint audit trails, call notes, contact logs, case status changes, emails about you, decision records containing your personal data and recordings if held.
• Ask early enough that disclosure may still assist the complaint, but do not assume the complaint or appeal deadline pauses while the SAR is processed.
• If data is missing, identify the category and why you reasonably believe it exists, rather than merely saying the response is incomplete.
• FOI/EIR may be better for non-personal policy, technical and statistical material. The routes can run concurrently.

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.

What a targeted council SAR can uncover

Useful categories can include complaint case notes, call logs, correspondence about you, status histories, audit trails, records of decisions concerning your case and personal data contained in contractor systems where the council is the relevant controller. Ask for categories of personal data rather than assuming Article 15 gives an unredacted copy of every internal document. Legal privilege, third-party data and other restrictions can affect disclosure.

If a particular call or system event matters, identify its date, approximate time, service area and reference number. That helps the authority locate the data and makes completeness easier to test. Preserve your own contemporaneous note even if you later request the council's version.

A SAR is evidence gathering, not a substitute complaint

Keep the complaint and data-rights tracks distinct. Missing personal data, an unjustified delay or an inadequate SAR search can be challenged through the data-protection route, but that does not decide whether the underlying highways, planning or Environmental Health decision was correct. Likewise, do not delay a statutory appeal while waiting for a SAR unless you have obtained specific advice about the deadline.

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.