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.
How to prove, analyse and challenge shifting explanations without treating every changed position as misconduct.
The points that usually decide the case
- Put the statements side by side with date, author, forum and exact proposition. Separate true contradiction from a position that changed because new evidence emerged.
- Ask the council to identify which account is correct, why the earlier account changed and what evidence supports the final position.
- Contradictions matter most where they concern a material fact, reason for refusal, chronology, policy basis, technical proposition or remedy.
- Use targeted FOI or EIR where the disputed issue is institutional or technical recorded information; use SAR where the relevant records are personal data about your case.
- Do not overstate. One typo may be immaterial; a pattern of irreconcilable statements can undermine confidence in an investigation.
Common situations
| What happens | How to approach it |
|---|---|
| A phone call says 'budget'; the letter says 'technically impossible' | Ask for the recorded basis of both positions and a clear final reason. The explanations are different and should be reconciled. |
| Stage 1 and Stage 2 describe the same visit differently | Identify the common event and quote both descriptions. Ask which is accurate and what operational record supports it. |
| A later response quietly drops an earlier reason | Treat the omission as a question, not automatic proof of bad faith: ask whether the earlier reason was withdrawn and why. |
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.
Use a contradiction matrix
Put each material issue on one row. In the next columns record what the council said first, what it said later, the date/source of each statement, and the question the council now needs to answer. Typical examples include “no budget” versus “technically impossible”, “work completed” versus an open job record, or “no record held” versus a later disclosure showing one. This is far more persuasive than simply calling the authority inconsistent.
Not every changed explanation is maladministration. A position can properly change because an inspection took place, new evidence emerged or an earlier statement was corrected. The important questions are whether the authority acknowledged the earlier account, explained why it changed, and grounded the new conclusion in evidence. An unexplained shift on a central fact is much more significant than a transparent correction.
Ask for reconciliation, not confession
A useful question is: “Please reconcile statement A dated [date] with statement B dated [date], and identify the evidence relied on for the current position.” That formulation gives the council a fair opportunity to explain the discrepancy and creates a clean record for a later complaint reviewer or Ombudsman.
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.
Official sources
Check the rules behind this guide
These are official or primary sources for this topic. Council policies, local schemes and statutory deadlines can differ or change. Check the live decision notice and current local policy before relying on a deadline.