Prepare a consumer complaint file: transaction, defect, response and relief

Turn the complaint into a verifiable sequence

“The product was bad” tells a reader much less than a dated account supported by an invoice, photographs and correspondence. Begin with what was bought, who supplied it, what was paid and what was promised. Keep the listing or written specification as it appeared at the relevant time, if available. Clearly separate the promise from what you say actually happened.

Build four parts of the file

Transaction: identify the supplier and service provider accurately. Save the invoice, order confirmation, payment proof and contract or warranty terms. A marketplace, manufacturer and seller may have different roles; do not treat a brand name as a complete party description.

Problem: record the defect, shortfall or disputed conduct in concrete terms. Include dates, photographs, service reports and relevant use history. Keep original files where possible. If the problem needs technical testing, do not assume a photograph settles the question.

Response: preserve complaint numbers, emails, repair visits, proposed solutions and any refund or replacement already received. Add unanswered requests to the chronology with evidence of sending them. Avoid saying “no response” if there was a response you disagreed with.

Relief: explain what you are seeking and connect each amount to a document or a reasoned calculation. Distinguish the purchase price, other claimed loss and other relief. An unsupported large number can make the actual dispute harder to understand.

Use the Act to frame research questions

Section 35 of the Consumer Protection Act 2019 addresses how complaints may be made, including identified categories of complainants and electronic filing as prescribed. It does not mean that every complaint belongs before any chosen Commission. Eligibility, subject matter, territorial jurisdiction, current pecuniary rules and filing requirements need separate verification.

Section 38 describes procedures after admission and includes the role of documents and, where relevant, testing. Build a file that lets another reader trace each factual assertion back to evidence rather than relying on a long narrative alone.

Section 69 sets out a two-year limitation rule from the date the cause of action arose, with a provision for sufficient cause and recorded reasons for delay. Identifying the cause of action is a legal and factual question. Continuing correspondence should not be assumed to restart the period automatically. This guide does not calculate the last filing date.

Example: a repair history

Suppose an appliance was delivered, a fault was reported and two repair visits followed. Put the delivery, first report and each visit on separate lines. For each, attach the relevant invoice, ticket or report. If the last visit did not resolve the problem, explain what remained and how it is documented. The sequence helps identify questions; it does not establish liability by itself.

Before filing, verify the current official forum and procedure, fees, jurisdiction and limitation with appropriate advice. This guide prepares the research record; it does not submit a complaint, guarantee admission or decide the remedy.