Evidence for an ombudsman

Good ombudsman evidence shows what happened, when it happened, what rule or standard mattered and why the requested remedy follows.

An ombudsman does not need every document you possess. It needs enough reliable evidence to determine the disputed issues. The strongest bundles are indexed, chronological and issue-led.

Records made at the time - bills, contracts, confirmation emails, screenshots, call recordings, CRM notes and letters created at the time - often carry more weight than later recollections.

Key points

Start with a chronology and issue list.
Name documents consistently and explain why each one matters.
Separate factual evidence from argument.
Highlight contradictions without overstating what they prove.
Keep evidence of the impact and requested remedy, not just the underlying error.

Build an evidence map

Issue	The exact point the ombudsman must determine
Evidence	Documents/records supporting or contradicting it
Framework	Law, rule, code, policy or good-practice standard
Impact	What happened because of the issue
Remedy	What would put the position right

Use evidence created at the time first

A checkout confirmation created at the transaction time may be more useful than a later internal summary. A dated CRM note may help establish what a provider recorded. That does not make every internal note true; assess provenance, consistency and context.

Explain gaps and conflicts

If two records conflict, do not hide the conflict. Put both in the bundle and state the factual question the decision-maker needs to resolve. If a record is missing, explain why you reasonably expected it to exist and what attempts were made to obtain it.

In practice

A 20-page organised bundle can be stronger than 300 unexplained pages.
Quote short decisive extracts and give the full document reference.
Preserve original files where authenticity or metadata may matter.
Keep your remedy evidence - invoices, credit reports, loss calculations and correspondence about impact.

What to do

A practical next-step plan

List the issues.
Build a dated chronology.
Create an evidence index.
Link each key document to an issue.
Remove duplicates and irrelevant material.
Submit a short explanatory note identifying the decisive records.

Common traps

Things that often confuse the issue

Submitting screenshots without dates or context.
Treating an allegation as evidence because it appears in a complaint letter.
Overloading the case with irrelevant correspondence.
Failing to preserve the organisation’s own evidence bundle.

Evidence worth keeping

Original complaint and final response

A short chronology

An issue-by-issue evidence index

Only the documents needed to prove each important point

Relevant scheme rules or official guidance

Any investigator/decision correspondence once the case is open

Where to go next

If a decision does not engage with decisive evidence, identify the exact document, the issue it bears on and why it could have a significant effect on the outcome.

Give the reviewer a route through the evidence.

One-page case summary
Numbered issues
Short chronology
Evidence index
Loss/remedy schedule
Key documents only in the main bundle; secondary material clearly labelled

Test.

Could a reviewer locate the document proving each important sentence in your complaint in under 30 seconds? If not, improve the indexing before adding more documents.

Internal records can be powerful, but interpret them carefully.

SAR disclosures, case notes and audit logs can show what the organisation recorded at the time. They can also contain shorthand, errors or system-generated entries. Explain what the record proves and avoid claiming more than it says. A contradiction schedule is useful where an internal record conflicts with the later final response.

Use contemporaneous records and preserve context.

Keep complete emails, letters, account pages and screenshots where possible. If relying on a quotation, give the document/date/page so the reviewer can see the surrounding text. If a fact comes from a call, state whether there is a recording, transcript, contemporaneous note or only later recollection.

Ombudsman evidence should prove propositions, not demonstrate file size.

Start with an issue list. For each issue, write the proposition you need the decision-maker to accept and attach the best evidence for it. A 20-page indexed bundle can be stronger than 400 pages of unstructured correspondence.

Issue	Proposition	Best evidence
Sale/contract	The provider promised £X / term Y	Order confirmation, signed terms, recording.
Billing	The disputed balance is £X because entry Y is wrong	Bills, ledger, payments, calculation.
Complaint handling	Issue 3 was never answered	Complaint, final response, issue matrix.
Public body	Relevant evidence was not considered	Submitted document plus decision/reasons.
Loss	The failure caused £X expense	Receipt, bank entry, causation explanation.

Official sources

Check the rules behind this guide

These are official or primary sources for this topic. Rules, scheme terms and deadlines can change, so check the live source before relying on a formal time limit or procedure.