Quick answer
Keep one controlled file with six working tools: a matter sheet, source-linked chronology, scope-and-performance table, evidence index, complaint-and-remedy register, and route-and-deadline log. Store untouched originals separately from the copies you annotate or submit.
How to use this guide
Every entry should show its source, date, author or holder, status and next action. This prevents a service complaint from becoming a collection of repeated emails, revised accusations and unexplained attachments. A well-run file does not prove the provider was at fault, but it makes the real issues and gaps visible.
Create a matter sheet before sorting documents
Use one page to identify the consumer, the exact supplier entity, the service, transaction date, price, service location, current status, requested remedy and next fixed event. Include any platform, subcontractor, franchise or insurer, but describe its role rather than merging it with the supplier.
Add a coverage box. Record whether the transaction appears to have occurred in the ordinary course of the supplier's business, whether the consumer is an individual or juristic person, and whether a sector-specific scheme may apply. For a juristic person, note the records relevant to the prescribed R2 million asset-value or annual-turnover threshold at the transaction time.
Mark these as screening facts, not legal conclusions. The Consumer Protection Act contains exclusions and forum boundaries that may need professional or regulator assessment.
Separate originals from working copies
Create an “Originals received” archive that is read-only where possible. Keep original email files, attachments, photographs, videos, audio, job cards, quotations, signed terms, portal exports and technical logs with their native names and metadata.
Do not highlight, rename or compress the only copy. Make a working duplicate for pagination, redaction and notes. If you convert an audio message, spreadsheet or image into another format, keep the original and record the conversion.
Use a simple filename pattern for working copies: date, source, category and short description. The pattern should help retrieval without pretending that the filename proves the document's date or author.
Build a chronology that cites evidence
Use one row per material event with these fields:
- date and time;
- actor and entity;
- event or communication;
- source file and page;
- fact, allegation or inference;
- consequence; and
- next question.
Include the quote, acceptance, deposit, access dates, service stages, scope changes, promised completion, observed problem, first complaint, inspections, corrective attempts, final response and external referrals. Where dates conflict, record both versions and the source of each.
Avoid argumentative entries such as “supplier lied again”. Write “provider's email of 8 June gives completion as 4 June; access log records attendance on 6 June”. The difference can then be assessed without damaging the chronology's reliability.
Maintain a scope-and-performance table
Create a row for each promised task or deliverable. Add the specification, due date, approved variation, evidence of performance, consumer response, provider position and unresolved issue.
This table is essential because service disputes frequently expand beyond the original complaint. A late task, deficient workmanship, missing deliverable, disputed variation and defective supplied part should not be treated as one undefined “bad service” allegation.
Section 54 of the CPA deals with timely and quality service and, where applicable, provides for correction of the defect or a reasonable partial refund having regard to the extent of the failure. The table helps identify the affected portion; it does not automatically establish the statutory result.
Where goods were supplied during the service, create a linked product row with the item, serial or batch detail, installation date, alleged defect, custody and warranty response. Keep the goods and service analyses connected but distinct.
Use an evidence index with status controls
Give each record a stable exhibit number and record its date, source, description, issue, format, location, integrity note and submission history. Use defined statuses:
- original retained;
- working copy created;
- requested;
- partly supplied;
- source disputed;
- missing; or
- not applicable.
Do not delete duplicates until their identity is confirmed. The same photograph sent through two messaging platforms may have different compression and metadata. Note the relationship rather than assuming one is the original.
If another contractor, technician or assessor examines the work, record the mandate, qualifications, inspection date, methods, materials reviewed and changes made after inspection. A corrective-work quote and a causal report perform different functions and should be indexed separately.
Track every complaint as a distinct communication
The complaint register should show the recipient, channel, date, delivery proof, reference, issue raised, remedy requested, response due, answer received and follow-up. Link each entry to the exact letter or message.
Use one consolidated complaint before sending repeated fragments. The NCC's complaints page asks for transaction and dispute dates, proof of purchase, supplier-resolution steps and communications. Its service standards explain that missing supporting information can delay or close a ticket. A controlled register makes those items easy to supply and prevents a new submission from contradicting an earlier one.
The CGSO process also uses a reference number, supplier response and additional information requests. Record the stage without writing “won” or “lost” when the body has only acknowledged or assessed the complaint.
Keep a remedy tracker separate from the allegations
List each remedy proposed by either party, its date, conditions, amount or work scope, implementation steps, expiry and status. Preserve drafts of settlement or “full and final” wording.
If corrective service is proposed, record who will do it, access, parts, method, target date, quality check and what happens to removed material. If a refund is offered, separate the original price, partial amount, credits, deductions and claimed additional loss.
Do not silently change the desired remedy in successive complaints. A change may be reasonable after new evidence or a failed repair, but record why it changed.
Create a route-and-timing dashboard
Use a table for the provider's process, industry ombud, NCC, provincial body, regulator, tribunal or court. For each route, record current jurisdiction evidence, supplier-first requirement, documents needed, submission date, reference, formal decision and next step.
Do not open every route at once. The CGSO warns that it may not assist where the same event is or was before another court, tribunal, regulator or ombud. The NCC may refer matters to an ADR body, another regulator or a provincial consumer office. A route dashboard shows what is active and why.
Add a date column for every formal notice and possible limitation issue. The NCC describes a three-year section 116 screening issue, but the relevant cause of complaint and other legal periods may be fact-sensitive. Filing a consumer complaint should not be assumed to stop every contractual or civil period.
Record custody and safety decisions
If the provider still holds the consumer's vehicle, equipment, keys, credentials, originals or other property, keep a custody log. Record handover condition, accessories, access authority, storage, inspections and release conditions.
Where the service may be unsafe, note the protective step and who advised it. Preserve the condition before further work if reasonably possible, but do not postpone necessary medical, electrical, structural, vehicle or cybersecurity protection simply to create better evidence.
If evidence is altered by urgent work, photograph or export what can safely be preserved and record the reason, person and time.
Prepare clean outgoing packs
Never send the entire master archive by default. Create a submission copy with a cover summary, chronology, issue table, requested remedy, route explanation and numbered exhibits. Redact unrelated personal information where appropriate and keep a record of every redaction.
Save the exact outgoing bundle and proof of submission. When the forum asks for more information, add a supplement rather than silently replacing the original pack.
Schedule a weekly review of open requests, promised responses, safety issues, route status and dates. Close an item only when the evidence shows it is complete.
Important limitation
This organisation system is general information. It does not establish jurisdiction, preserve every legal period, prove liability or make any complaint outcome certain.
FAQs
Should I rename original files when organising a service complaint?
Keep an untouched original archive with native names and metadata. Use renamed working copies for indexing, and record any conversion, annotation or redaction made for a submission.
How should I record conflicting dates in a provider dispute?
Enter each date with its source and mark the conflict. Do not choose one silently. A source-linked chronology allows the provider, ombud or adviser to assess the difference.
Can I submit the same service complaint to several bodies at once?
Check the rules first. Jurisdiction and existing proceedings can affect whether an ombud or regulator will intervene. Track the selected route and disclose any parallel process.
What is the difference between a remedy tracker and an evidence index?
The evidence index records source material and integrity. The remedy tracker records each proposed correction, refund, credit or settlement, its conditions, implementation steps and current status.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.