The method
A complaint is not just a story. It is a set of issues you are asking somebody to decide.
A useful complaint gives the reader a controlled route through the dispute. It identifies the scope, separates each issue, anchors important statements to evidence, exposes conflicts in the record, asks questions that can actually be answered and states the outcome you want.
This matters even more if the complaint may later go to an ombudsman, regulator, appeal body or court. A well-built complaint creates the record that the next decision-maker will inherit.
Before drafting
Decide what the complaint is actually about.
Many weak complaints start with a large chronology and never clearly define the dispute. Start the other way round. Write a short list headed Issues requiring a response. If you cannot state an issue in one or two sentences, it probably contains several issues that should be separated.
What happened in the transaction, service, decision or relationship?
Was the complaint itself delayed, mis-scoped, ignored or answered inconsistently?
Are records inaccurate, missing, contradictory or being relied on for a significant decision?
What financial, practical, credit, data, employment or other impact followed?
Those strands can arise from the same events but may require different findings, evidence and escalation routes. Keeping them separate prevents one broad answer from being treated as an answer to everything.
Issue drafting
Build each issue as: fact → conflict or failure → evidence → question → remedy.
This is the core ConsumerWise complaint method. It turns a general accusation into something capable of investigation.
The stronger version does not need inflammatory language. The documents create the problem. Your job is to identify the conflict precisely and require the organisation to resolve it.
Allegations and evidence
Describe the contradiction before accusing somebody of dishonesty.
“Your staff lied, covered this up and are now refusing to admit what happened.”
“Record A says X. Record B says Y. Both cannot describe the same event accurately without further explanation. Please reconcile the two records and identify the evidence supporting your final position.”
Sometimes dishonesty really is part of a dispute, but it is usually more effective to establish the objective inconsistency first. A complaint handler can dismiss rhetoric; it is harder to dismiss two documents that say materially different things.
Chronology
Use dates to prove sequence, not to bury the reader in history.
A chronology should answer: what happened, when, who was involved, what document records it, and why the event matters. Put the decisive events first. Background can sit in an appendix if it does not need to be in the main complaint.
| Date | Event | Evidence | Why it matters |
|---|---|---|---|
| 3 March | Customer receives written confirmation | Email A | Establishes the organisation's contemporaneous position |
| 10 March | Organisation gives a different explanation | Complaint response B | Creates a factual conflict requiring resolution |
| 14 March | Customer asks for the records supporting the new explanation | Email C | Shows that the contradiction was raised clearly |
A chronology is not a substitute for the complaint issues. It supports them.
Evidence
Tell the reader what each document proves.
Do not attach twenty documents and write “see evidence”. Use an evidence index. Give each important item a short identifier and explain its relevance.
| Ref | Document | Relevant issue | What it establishes |
|---|---|---|---|
| E1 | Order confirmation | Issue 1 | The wording given to the customer at the time |
| E2 | Later complaint response | Issue 1 / Issue 2 | The organisation's later and apparently different account |
| E3 | Account statement | Issue 3 | The financial consequence in dispute |
Where a document is long, give the page, paragraph, timestamp or section. Make the important evidence easy to find.
Questions
Ask questions that force the disputed point to be confronted.
A question should earn its place. Do not ask a long list of questions merely to make the complaint look forensic. Use questions where the answer will resolve an issue, identify the evidence relied on or expose that an important point has not been determined.
What is the organisation's final factual position on this issue?
Which document, system record or other evidence supports that position?
How does that evidence reconcile with the conflicting record identified above?
If the record is inaccurate, what will be corrected, by whom and by when?
If the complaint point is rejected, what is the reason for rejecting the evidence I have identified?
Findings
Ask for an answer issue by issue.
Number the issues and ask the final response to deal with each one. Where the organisation uses findings such as upheld, partly upheld or not upheld, ask it to state the finding, the evidence considered, the reasons and the remedy for each issue.
You cannot force every organisation to use your format. But a clear issue schedule creates a benchmark. If the final response later answers Issue 1 and Issue 4 but says nothing about Issues 2 and 3, the omission is visible.
Remedy
Separate what went wrong from what would put it right.
“I want this resolved” is too vague. Different failures require different remedies. Link the requested remedy to the issue and the consequence.
Amend an inaccurate record, bill, credit entry, decision or account status.
Give the missing reasons, evidence or factual account.
Put the consumer back into the position they should have been in where that is possible.
Refund, compensation or another financial remedy where appropriate to the issue and route.
If you ask for compensation, explain the impact rather than simply selecting a large number. Financial loss, time, inconvenience, distress and loss of opportunity are different things and may be treated differently by different schemes.
Scope control
Do not let a complex complaint become one giant allegation.
A dispute can involve the original service failure, inaccurate data, credit reporting, complaint handling and professional conduct at the same time. Keep a master issue list and decide which body is being asked to determine which issue.
This also protects against scope drift. If an organisation quietly reframes “why are these two records inconsistent?” as “the customer is unhappy with our service”, repeat the original question and identify that it remains unanswered.
Tone
Be firm, precise and difficult to misunderstand.
Professional does not mean passive. You can state clearly that an explanation is unsupported, that an answer does not address the question, or that two positions are irreconcilable on the evidence currently provided. Precision is stronger than outrage because it tells the reader exactly what must be dealt with.
Remove insults, speculation about motives and unnecessary adjectives. Keep strong conclusions where the evidence supports them, but show the route from evidence to conclusion.
Attachments
Make the complaint usable before you make it enormous.
For a larger dispute, use a short main complaint supported by a chronology and evidence index. Label attachments consistently. If the organisation already holds a document, it can still be useful to attach the decisive extract so the complaint handler cannot reasonably miss it.
- Main complaint with numbered issues.
- Chronology showing only material events.
- Evidence index explaining what each item proves.
- Key documents in the same reference order used in the complaint.
- Schedule of loss or impact where a quantified remedy is requested.
Final response
Ask the organisation to show its working.
A useful final response should leave you able to understand what the organisation decided and why. Ask it to identify the complaint scope, findings on each issue, material evidence considered, reasons, remedy and the next escalation route.
After the response
Audit the answer against the complaint you actually made.
Do not ask only whether the response sounds reasonable. Compare it with the issue list. Mark each issue as answered, partly answered, avoided, contradicted or unsupported. Record any new factual position or new evidence introduced by the organisation.
A response can be lengthy and still fail to answer the complaint. Equally, a short response can be adequate if it actually determines every material issue and explains the outcome.
Complaint blueprint
A reusable structure for a serious complaint.
- Opening and scope
State that this is a formal complaint, identify the relationship/account/service and define the matters you are asking the organisation to determine.
- Issues requiring findings
List the issues in numbered form before the detailed narrative.
- Relevant chronology
Give only the sequence needed to understand those issues.
- Issue analysis
For each issue: facts, evidence, conflict/failure, question and requested finding.
- Impact
Explain the practical or financial consequence and distinguish different heads of impact.
- Remedy
State what correction, action, explanation, refund or redress is sought and link it to the relevant issue.
- Evidence index
List attachments and explain what each one establishes.
- Final-response request
Ask for issue-by-issue findings, reasons, evidence relied on, remedy and escalation rights.
Final check
Before sending, test whether somebody unfamiliar with the dispute could decide it.
If not, separate or number them more clearly.
If not, add references, pages or an evidence index.
Anchor important conclusions to the record.
Remove rhetorical questions and ask for determinations.
State what should happen if the issue is upheld.
Your structure should make omissions obvious.
Build the record
Use ConsumerWise alongside the complaint.
Official sources and further reading
Complaint processes differ by sector. Use the method on this page to structure the case, then check the sector guide for the applicable procedure, time limit and external escalation route.