Quick answer
Create an indexed pack that lets another person move from the agreement to the disputed event without guessing. Keep documents in their original form, add a working copy only for annotations, and distinguish records created during ordinary trading from summaries produced after the dispute began.
How to use this guide
Prepare a traceable chain from contract formation to the disputed performance and claimed consequence. The objective is not maximum volume. It is to let a reviewer verify which terms applied, who had authority, what each party did, how notice was delivered and how the claimed loss was calculated from ordinary-course records.
Define the document question
Build the bundle around a chain that another person can verify: contract formation, the particular obligation, the performance event, the response, the notice and the financial consequence. A signed master agreement may incorporate quotations, specifications or purchase orders, and later changes may have formal requirements. Record which version governed each disputed delivery instead of selecting documents only after the dispute arose.
Assemble the contract-to-performance chain
Collect the documents in the order the transaction unfolded:
- Collect every signed contract, schedule, standard term, quotation, order and document incorporated by reference.
- Preserve board, delegation or signing records that show who had authority to commit or vary each party's obligations.
- Export purchase orders, delivery notes, acceptance tests, service-level reports, tickets and rejection records from their source systems.
- Reconcile invoices, credit notes, statements, payments and disputed deductions to the relevant goods or services.
- Keep notices, acknowledgments and negotiations with complete headers, attachments and proof of delivery or receipt.
- Support claimed loss with replacement quotations, downtime records, mitigation steps and calculations that identify assumptions.
Preserve originals and system history
Keep original files and system exports separately from summaries prepared for the lawyer. Record the source, custodian, date range and export method for operational data, and retain attachments and complete conversation threads. For physical goods, link dispatch, receipt, inspection and rejection records to the relevant batch. For services, connect milestones, acceptance tests, tickets and approvals to the invoiced period.
Separate proof from explanation
Use the index to expose gaps rather than hide them. Mark a missing schedule, disputed signature, incomplete test result or unavailable message, then identify the likely custodian and the steps already taken to locate it. A lawyer can assess the effect of the gap and advise what further evidence is proportionate; reconstructed proof should never be presented as a contemporaneous source record.
Avoid contaminating the record
Protect the usefulness of the evidence by avoiding these practices:
- Do not treat a later spreadsheet as a substitute for the records from which its totals were derived.
- Do not omit unfavourable messages, rejected work or internal records that may explain the supplier's defence.
- Do not rename original files in a way that destroys their date, version or source-system connection.
- Do not assume a without-prejudice label makes every statement legally consequence-free.
Index the legal pack
Create an indexed pack that separates source records from analysis:
- Number each document and create an index with date, author, recipient, source and short relevance note.
- Mark the contract hierarchy and place every variation beside the authority supporting it.
- Link each allegation to the best performance record and to the other party's response.
- Prepare a separate loss schedule with underlying proof and mitigation records.
- List missing records and who controls them instead of filling gaps with assumptions.
Deeper analysis: supplier-dispute evidence pack
Start the index with contract hierarchy. A signed master agreement may incorporate schedules, quotations, purchase orders, service levels or web terms, while later variations may have their own formality requirements. Record the date and authority for each version and do not silently choose the document that best supports the current position when another version was used operationally.
Performance proof should be transaction-specific. Link each disputed batch, delivery, milestone or service period to source records such as dispatch data, acceptance testing, support tickets, quality reports and rejection notices. If the parties measure performance differently, preserve both methods and the communications that show whether the difference was raised at the time.
Treat the loss schedule as a working analysis supported by separate evidence. Identify replacement costs, downtime or other effects, then show the invoice, system report or witness source for each figure and the steps taken to reduce loss. Keep estimates visibly distinct from incurred amounts, and retain unfavourable records that may support causation or mitigation arguments.
Build an adverse-evidence register
Create a short register for records that appear inconsistent with the claim: accepted late deliveries, approved invoices, internal quality concerns, concessions, credits or messages suggesting that the disputed obligation changed. For each item, identify its source, author, date and the issue it may affect. Do not bury it in the general archive or try to explain it away in the index.
The register helps the lawyer test whether the record concerns liability, causation, mitigation, waiver, a later variation or only an incomplete operational view. It also prevents the first opinion from being based on a one-sided pack that the supplier can readily contradict. Preserve the full surrounding communication so an isolated sentence is not mistaken for the complete transaction.
Limits of a document pack
A well-organised file makes legal analysis faster but does not turn every record into proof of liability. Authority, admissibility, reliability, contract interpretation and causation remain open questions. Missing originals or adverse material should be identified in the index rather than reconstructed, omitted or described as immaterial without advice.
FAQs
Do I need every email with the supplier?
No. Preserve the complete source set, then prepare a focused bundle containing the communications that prove formation, variation, performance, notice, response or loss.
Are screenshots enough for electronic evidence?
They can assist, but native messages, headers, exports and audit information usually provide stronger context for integrity, origin and timing.
How should I index records that appear to support the supplier?
Place them in an adverse-evidence register with source, date and the issue each may affect. Preserve surrounding context so the lawyer can test their legal significance rather than receiving a one-sided pack.
How should I present a damages calculation?
Separate source figures from assumptions, show the calculation method, and retain proof of reasonable mitigation steps.
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.