Begin with the customer's concern
A complaint file should help someone understand the issue without reconstructing it from disconnected messages. Begin with the customer's account and requested resolution, then establish the relevant chronology. The purpose is to make facts assessable, not to build a persuasive defence before the business has understood the concern. A coherent record supports fair internal review and clearer communication.
The Motor Ombudsman's complaint process identifies evidence such as correspondence, invoices and relevant reports. Its remit and eligibility must be checked for the particular situation. That reference supports an evidence-led approach, not an assumption that every automotive disagreement follows the same route. The dealership should organise its own records before discussing escalation or predicting an external outcome.
Build a factual chronology
Identify the original offer or booking, authorisations, completed work and later contacts. Use dates and source documents where available. Keep a distinction between recorded events and someone's later recollection. If there is a gap, identify it explicitly and seek clarification. Filling an incomplete record with a confident narrative can make the file appear stronger while reducing its reliability.
Connect technical notes to the question under review. A long diagnostic record may contain material irrelevant to the disputed promise. Explain which findings matter and why, using competent input. Preserve original documents alongside any summary so reviewers can examine the underlying evidence. A plain-language account should improve accessibility without changing the meaning or implying more certainty than the technical record supports.
Separate promises and performance
Establish what the customer was told, what they approved and what occurred. These may differ without proving why, so investigate the transition carefully. A repair can be technically successful while communication about timing or scope was inadequate. Treat those as distinct aspects of the concern. Otherwise the business may answer a workshop question while ignoring the customer experience actually being challenged.
Record relevant attempts to resolve the matter and the customer's response. Identify commitments that remain outstanding and who owns them. Multiple employees contacting the customer independently can create inconsistent explanations. A named case owner should coordinate the record and obtain appropriate decisions, while respecting the fact that specialist technical or legal questions may need other qualified input.
Turn the review into clear next steps
Explain findings in an accessible response that addresses the stated concern. Where evidence does not settle a point, identify the limitation and the proposed route to clarification. Avoid reproducing the whole file as though volume alone constitutes an answer. The customer needs the relevant reasoning and next action, with escalation information appropriate to the actual situation.
After the case, examine what the record reveals about process. Missing approval or contradictory updates may indicate a wider operational gap. Feed those findings into training or system changes without pretending one complaint establishes a universal pattern. A coherent file helps the dealership handle the present concern responsibly and makes any improvement traceable to evidence rather than speculation about who was at fault.
Sources & further reading
The Motor Ombudsman: Alternative Dispute Resolution for vehicles ↗
Reference for complaint evidence and checking scheme remit and business accreditation; no universal eligibility claim.
The Motor Ombudsman: Service and Repair Code ↗
Context for transparent service scope and agreed work; a voluntary code is not presented as legislation.
Prepared 2026-10-13. Source references retained from that edition. Corrections and feedback.
