Council maladministration: what it means

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.

A practical guide to administrative fault: delay, missing reasons, inconsistent accounts, procedural failures, poor records, ignored evidence and flawed decision-making.

The points that usually decide the case

• Maladministration is a broad public-administration concept rather than a single checklist offence. LGSCO looks at fault in what the authority did and the injustice caused.
• Examples can include unreasonable delay, failure to follow procedure, failure to take account of relevant evidence, inaccurate information, poor records, inadequate reasons and failure to implement decisions.
• A bad outcome does not necessarily prove maladministration. The focus is the quality and lawfulness of the process and service.
• Where a council exercises discretion, show the defect in the decision-making process rather than merely arguing that a different decision would have been better.
• Link every alleged fault to a personal injustice or relevant public-interest consequence and an achievable remedy.

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.

Fault is not enough on its own

LGSCO normally looks for both fault and resulting personal injustice. An inaccurate date, missed step or poor explanation can be fault, but the practical consequence matters when deciding whether investigation or a remedy is justified. Link each alleged administrative failure to what it actually caused: delay, avoidable effort, lost opportunity, financial loss, distress or an unreliable decision-making process.

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.