Writing a clear complaint chronology

A complaint chronology lets someone unfamiliar with the purchase understand what went wrong. Official consumer guidance directs unresolved complaints to different advice and redress routes; a clear timeline helps whichever route applies. ^[1]

Give each event an evidence reference Use columns for date, event and supporting document. Begin with the advertisement or agreement, then payment, delivery, discovery of the problem and attempts to resolve it. Mark an approximate date as approximate.

Describe events neutrally. 'The engineer attended and replaced the valve' is more useful than 'another useless visit'. Put your explanation of why the repair failed in a separate issue note supported by the subsequent evidence.

Make the unresolved issue visible Finish with the latest response, the sum still disputed and the outcome requested. Separate refunds already received from the amount outstanding. If you missed an appointment or agreed an extension, include it rather than leaving a misleading gap.

Use a note of verbal promises where no written record exists. Before escalating, compare the chronology against the chosen redress route's requirements so the relevant events can be found without reading every attachment.

Define the question the timeline needs to explain Start by identifying the purchase and unresolved problem in a short introductory note. A chronology for a delayed refund may need the return, receipt and promised repayment dates; one about a recurring fault may need each repair attempt and subsequent failure. Include enough earlier context to understand the agreement without reproducing the customer's entire relationship with the trader. The chosen starting point should make the disputed sequence intelligible to a reader who has never seen the account or spoken to either party.

Set a clear cut-off date for the version being prepared. Record where later updates will be added and keep the previous version when a material change is made. This is particularly useful if the complaint is sent to different organisations over time. A document described simply as the final timeline can become misleading when another repair, refund or response arrives. Each recipient should be able to see the period covered and identify any event supplied after the version on which they were originally asked to act.

Distinguish the event date from the evidence date Record when an event happened separately from when a document about it was created or received. An inspection report issued on Friday may describe a visit on Tuesday; a bank refund may appear after the trader says it was authorised. Both dates can matter, but they answer different questions. Use a short note where the distinction affects the dispute. Do not place the event on the report's date merely because that is the most visible date on the supporting document.

Where timing is uncertain, state the best supported range and its basis. A customer may remember discovering a fault between delivery and a later message but not the exact day. Preserve that uncertainty rather than selecting an apparently convenient date. If messages involve different time zones, explain any conversion used and retain the original timestamp. The chronology should allow a reviewer to test the sequence against the evidence without mistaking an estimate or converted time for an original contemporaneous record.

Keep source references stable and observations factual Give each useful document a short, stable reference and use it consistently. If one email contains several relevant events, identify the appropriate passage or attachment without creating multiple incompatible names for the same record. Keep the source file unchanged and make any explanatory annotation separately. This avoids an accidental mismatch when an updated chronology is reviewed against an earlier set of attachments. The reference system should help the reader retrieve evidence rather than becoming a second complicated document to decipher.

Describe what happened in terms that the evidence can support. A missed promised call, an attendance, a replacement part and a payment are identifiable events. Whether a series of visits amounted to an adequate remedy belongs in the explanation of the issue, supported by those events. Include the trader's reason for a delay where known and mark disputed explanations as disputed. Do not write a conclusion such as deliberate avoidance into the event column when the records establish only that particular messages received no answer.

Check the sequence against the outstanding account Reconcile payment, refund and expenditure entries with a separate calculation of the amount still sought. A partial refund should appear on its actual date and reduce the relevant balance, even if other aspects of the complaint remain unresolved. Record concessions and agreed extensions as well as failures. Before submission, read the sequence once without attachments and then check each important entry against its source. This can reveal missing transitions, duplicated events or a statement that is stronger than the document supports.

Finish with the latest position and identify what response or action remains outstanding. If a scheme asks for particular dates, ensure those can be found without altering the underlying history. GOV.UK directs consumers to different advice and complaint routes, so a reliable timeline may support several later steps. Its purpose is to preserve a consistent factual account; it does not replace a scheme's form, a court document or advice about the significance of a particular deadline. ^[1]