A chronology turns a messy dispute into a sequence that can be checked against the documents.
A chronology is a dated list of events, not an argument. Its job is to show what happened and in what order: contract, payment, complaint, response, notice, reporting, escalation. Keep legal conclusions out of the event column unless they are clearly labelled as analysis.
The chronology becomes especially powerful when an organisation relies on the wrong date or describes events in an impossible order.
Key points
- Use exact dates where known and say “date unknown” rather than guessing.
- Link each important event to an evidence reference.
- Record what happened, not what you now think it meant.
- Maintain one master chronology and update it rather than creating conflicting versions.
A simple chronology format
| Date | Event |
|---|---|
| Source | Document or record that proves it |
| Issue | Which complaint issue it relates to |
| Notes | Short neutral context if required |
Why sequence can decide the issue
Contract acceptance before cancellation, notice before default reporting, complaint before final response and payment before arrears status are all sequence-sensitive. If the dates are wrong, the legal analysis built on them may also be wrong.
Use separate analytical notes
If you need to explain why a date matters, use a separate “significance” column or issue note. That preserves the chronology as an objective record.
In practice
- Start with the earliest transaction event and work forward.
- Use consistent date format such as 8 September 2026.
- Mark disputed events clearly: “Provider says X; consumer disputes - see E12/E13.”
What to do
A practical next-step plan
- Collect all dated documents.
- Enter major events in order.
- Add evidence references.
- Reconcile conflicting dates rather than silently choosing one.
- Check the chronology against the complaint and final response.
- Use a shortened version in submissions and keep the master version for reference.
Common traps
Things that often confuse the issue
- Do not fill gaps with assumptions.
- Do not include every routine contact if it makes the important sequence invisible.
- Do not change dates to match a later narrative; flag conflicts.
Evidence worth keeping
Keep one master chronology and derive shorter versions.
Practical method.
Maintain a full chronology for your own file. For an ombudsman or court submission, extract only the entries that matter to the live issues. This avoids burying a decision-maker in routine chasers while preserving the complete history if a date later becomes important.
Whenever a new material event occurs, add it immediately with the source document.
Use the chronology to expose gaps and changes in position.
A well-built timeline often reveals that a business changed its explanation, missed a deadline, recorded an event before it happened, or relied on a document created later. Mark those points, but keep the chronology itself neutral enough that a reviewer can trust it. Put argument in a separate issue note if necessary.
Link each important event to a document.
Use a reference column such as E1, E2 or page numbers once the evidence pack is stable. That turns the chronology into a navigation tool. If an event has no evidence, say so rather than inventing certainty: “telephone call, no recording available; contemporaneous note made same day” is transparent and still useful.
A useful chronology records legally or procedurally significant events, not every emotion in the dispute.
Start with the transaction, decision or event that created the problem. Then record complaints, responses, evidence requests, deadlines, promised actions, corrections and escalation points. Include the exact date where known and distinguish facts from later conclusions.
| Entry | Useful format |
|---|---|
| Contract/order | 12 Jan: order confirmation states £35 per month for 24 months. |
| Problem | 03 Feb: first incorrect £8 add-on appears on bill. |
| Complaint | 05 Feb: formal complaint submitted; ref ABC123. |
| Provider response | 12 Feb: provider says charge was “agreed during sales call”. |
| Evidence | 18 Feb: SAR disclosure contains no call recording but includes sales note. |
| Escalation | 20 Mar: six/eight-week or scheme deadline reached, as applicable. |