Quick answer
Collect the operational records that can test each allegation independently of the parties' letters. The useful record is often not the final report but the source-system history showing what was approved, delivered, measured, rejected, changed, paid or escalated at the time.
How to use this guide
Collect the ordinary-course records that test each allegation independently of the parties' letters. Map the contract requirement to the authoritative system, approval, performance event, communication and financial entry. The aim is a reproducible record trail, not a later narrative that selects only data supporting the preferred response.
Map allegations to ordinary-course records
Build a record map allegation by allegation. For each claimed failure, identify the contractual obligation, responsible team, period, performance measure and source system. Then list the records that support, qualify or contradict the assertion. This approach is more reliable than exporting every file associated with the customer and expecting a lawyer to discover the operational story unaided.
Collect the performance trail
For every allegation, identify the matching operational trail:
- Preserve contract and template repositories showing version history, approvals, incorporated terms and authorised changes.
- Export order, delivery, production, service-level, ticket, quality, access or acceptance records from source systems.
- Keep delegations, approval workflows and decision records showing who could instruct, vary, accept or reject performance.
- Reconcile invoices, credits, payment holds, deductions, loss entries and claimed set-off to accounting records.
- Retain complete communications, meeting notes and change requests with attachments, participants and delivery information.
- Record audit logs, system migrations, data corrections and retention limits affecting reliability or availability.
Preserve source-system provenance
Use ordinary-course material with its provenance intact: approved contract versions, purchase orders, tickets, delivery data, quality reports, timesheets, access logs, invoices, credits and correspondence. Record report names, filters, timezones and custodians. Preserve version history and later corrections. A reconstructed spreadsheet should cite the sources it summarises and remain separate from the original systems.
Reconcile changes and financial effects
Reconcile contradictions rather than deleting them. A project plan may show completion while a support system records unresolved defects; an invoice approval may coexist with a later complaint. Explain what each record was designed to capture and who can speak to it. The response team can then distinguish a genuine conflict, a timing difference and a record that does not answer the allegation.
Avoid selective exports
Keep the record map reliable by avoiding these shortcuts:
- Do not create replacement minutes or approvals after receiving the notice.
- Do not export only favourable date ranges or omit failed tests, rejected work or internal warnings.
- Do not assume a dashboard screenshot proves the underlying event without parameters and source history.
- Do not collect unrelated personal information merely because broad discovery may occur later.
Build the response record map
Create a response index that makes each source testable:
- Map each allegation to the contract requirement and the authoritative system or custodian.
- Create read-only exports before retention cycles, account changes or routine deletion affect them.
- Record the report date, filters, timezone, version and person who generated each export.
- Separate records proving performance from records proving notice, authority, loss or mitigation.
- List missing, contested or inaccessible data for the response strategy.
Deeper analysis: breach-response business record map
Performance evidence should reflect how the business actually measured the work. Preserve orders, production data, access logs, service tickets, quality results, delivery records, acceptance events and rejection reasons with the report parameters used. If the notice relies on a different measure, retain both datasets and the agreement or communication explaining which standard governed.
Change and authority records often decide whether apparent non-performance was authorised. Link instructions, variations, waivers, approvals and meeting decisions to the person who issued them and the contract formality relied upon. Keep draft and final versions distinct, and do not backdate a resolution or approval to fill a governance gap discovered after the notice.
Reconcile operational and financial consequences without treating them as the same question. A ledger hold, deduction or set-off claim may show how the dispute affected payment while not proving the underlying right. Preserve invoices, credits, manual journals and loss calculations with source support and mark estimates separately from incurred amounts.
Version history can decide whether an apparent contradiction is real. Keep the approved contract, later variations, purchase orders, project plans and system exports in their original form, with dates and user details where available. Then connect each disputed obligation to the operational record that shows performance, rejection, delay or acceptance. If staff used informal channels, preserve those messages lawfully and explain the business process around them instead of presenting isolated screenshots with no source or surrounding conversation.
Limits of operational records
Business records can support or contradict the notice without conclusively deciding contract interpretation, authority, causation or remedy. Their reliability depends on source, integrity and context. Preserve adverse data, restrict unrelated personal information and record missing or contested sources so the response is not based on a misleading subset.
FAQs
Why are system audit trails important?
They can show when data was created or changed and help explain whether a later export reliably reflects the relevant event.
Should internal problem reports be included?
Preserve material records, including adverse ones, so advice and the response are not based on a misleading subset.
Are meeting notes useful if unsigned?
They may provide context, but their author, timing, completeness and consistency with authoritative records affect weight.
How much personal information should be collected?
Only what is lawful, relevant and necessary, with access and security controls appropriate to the dispute.
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.