What Evidence Helps in a Contract Dispute?

Key takeaways

• Useful evidence in a contract dispute shows who agreed to what, whether the agreement became binding, what each party had to do, what actually happened, how an alleged breach was addressed and what loss or remedy follows. The core file normally combines the complete contract and its versions, formation and authority records, performance and payment records, notices with proof of delivery, a dated communication trail and reliable evidence of loss.
• Do not start by printing every email. Write the disputed propositions first and connect each one to a source record or witness. A signed contract may be central, but it may not answer disputes about annexures, later variations, conditions, authority, delivery, acceptance, defects, waiver, cancellation or the parties' subsequent conduct.
• Preserve favourable and unfavourable material. A lawyer needs the complete record to assess formation, interpretation, breach, defences, remedy, procedure and deadline risk. Deleting, editing or recreating evidence can damage the case and may create separate legal problems.

Start with an issue-to-evidence map

A contract dispute is not proved by the volume of the file. Build a working map around the legal and factual issues:

This is a preparation matrix, not a conclusion that every listed record is admissible or decisive. The contract type, governing law, pleaded claim, defence and forum determine what must ultimately be proved.

1. Preserve the complete contract set

Keep more than the signature page. The contract set may include:

• every signed counterpart and the version each party says is final;
• schedules, annexures, specifications, drawings, pricing tables and service levels;
• documents incorporated by reference;
• terms supplied through a website, portal, purchase order or quotation;
• amendments, addenda, change orders and renewal records;
• guarantees, suretyships, security or insurance linked to the agreement; and
• notices choosing an option, extending a date, varying scope or ending the relationship.

Record where each document came from and when it was received. Compare versions without overwriting them. A missing schedule, inconsistent signature page or later amendment can change the question from “was there a breach?” to “what were the binding terms?”

South African courts interpret contractual text in its setting. In Natal Joint Municipal Pension Fund v Endumeni Municipality, the Supreme Court of Appeal said the words must be read from the outset in the context of the document as a whole and relevant circumstances. That does not mean every recollection of negotiations can rewrite a signed agreement. Preserve the materials and let a qualified reviewer assess their relevance and admissibility.

The breach-of-contract glossary explains the general concept. It does not identify the terms or remedy in a particular agreement.

2. Record how the agreement was formed

Where formation is disputed, preserve the sequence rather than only the accepted version:

1. initial request, tender, proposal or quotation;
2. negotiations and marked-up drafts;
3. offer and any expiry date or condition;
4. acceptance, counter-offer or rejection;
5. signatures and the method used to sign;
6. any approval, deposit, purchase order or other stated precondition; and
7. conduct said to confirm that the parties treated the agreement as binding.

The Electronic Communications and Transactions Act gives legal recognition to data messages and addresses writing, electronic signatures, contract formation and the time and place of electronic communications. It also makes reliability, integrity and origin relevant to evidential weight. An email, platform acceptance or electronic signature may therefore matter, but its effect depends on the statutory requirements, agreed signing clause, system evidence and facts.

Preserve email headers, platform audit records, signature certificates and the original electronic file where available. A screenshot of a signature page may not show who signed, which version was signed or whether the document was later changed.

3. Verify the parties and authority

Use the exact legal names on the agreement, invoices, bank records and correspondence. A trading name, division, group brand, close corporation, company, trust, partnership or individual may not be interchangeable. Record changes of name, cessions, delegations, substitutions or business transfers that may affect the parties or rights.

Where an organisation is involved, keep the records relevant to authority:

• board, member, trustee or partner resolution where one exists;
• delegation or mandate;
• job title and responsibility at the time;
• prior communications about approval limits;
• representations made to the other party; and
• later conduct said to ratify, adopt or reject the agreement.

The Companies Act provides part of the statutory framework for company capacity, powers and dealings with third parties, but authority disputes remain fact-specific. A CIPC record proves certain registered information; it does not by itself prove that a particular employee or director had authority for the transaction.

4. Prove performance with source records

Break each material obligation into actor, action, standard, amount, due date and any dependency. Then show what occurred.

For goods, possible evidence includes purchase orders, dispatch records, delivery notes, inspection records, serial numbers, photographs, returns and stock data. For services, use the agreed scope, project plans, timesheets, work product, milestone approvals, service reports, access logs and change requests. For payment, retain invoices, statements, credit notes, remittance advice, bank proof and allocation records.

Acceptance can be disputed. Preserve sign-off, objections, defect notices, rejected work, continued use, partial payment, snag lists and correction attempts. Identify a witness or system custodian who can explain how a material record was created and what it shows.

The commercial-law checklist can organise the agreement, parties, performance and dispute records. It does not determine liability.

5. Build a breach and notice chronology

Create one chronology containing the contractual due dates and the real-world events. For every alleged breach, record:

• the obligation and clause relied on;
• the act, omission, delay, defect or non-payment alleged;
• when it occurred or became known;
• any dependency or prior non-performance raised by the other party;
• the notice sent and the contractual procedure used;
• how and when the notice was delivered;
• the response and any attempt to remedy; and
• the later election to continue, suspend, cancel, terminate or claim performance.

Do not assume that a complaint, invoice reminder or informal message satisfies a contractual notice clause. Some agreements specify an address, delivery method, notice period or opportunity to remedy. Cancellation, termination, specific performance and damages have different legal requirements and consequences. Obtain advice before communicating an election that may be difficult to reverse.

Keep delivery receipts, email transmission data, courier records and returned mail. If a notice relies on a conversation, make a dated factual note identifying the participants and what was said.

The approved letter-of-demand template can provide structure after the facts and remedy have been checked. It is not a substitute for advice on notice, cancellation, prescription, jurisdiction or the amount claimed.

6. Preserve communications without losing context

Emails, messaging apps, meeting notes, call recordings and project-platform activity may show formation, interpretation context, instructions, variations, admissions, complaints or performance. Keep the complete relevant thread, participants, dates, attachments and original export.

Separate ordinary operational communications from legal advice, settlement communications and privileged material. Do not circulate a lawyer's advice widely or place it in a shared commercial bundle without first checking privilege and waiver. Do not label an ordinary factual exchange “without prejudice” and assume that the label conclusively controls its later use.

Recordings, private accounts and third-party data raise separate interception, privacy, confidentiality and access questions. Do not obtain evidence by guessing passwords, bypassing access controls or copying a complete database merely because some records may be relevant. Preserve what is lawfully held and ask how missing or restricted material should be obtained.

The document-preparation checklist gives a source-preserving structure for an indexed working pack.

7. Prove loss and the proposed remedy

A breach finding does not automatically prove every amount claimed. Separate the claimed remedy from the evidence of breach.

Depending on the case, relevant loss material may include:

• the agreed price and payments already made;
• replacement supplier quotations and invoices;
• repair or completion costs;
• wasted expenditure records;
• revenue and cost records supporting a claimed financial consequence;
• returned goods, credits, insurance recovery or other avoided loss;
• steps taken to limit further loss; and
• expert methodology where causation or quantum requires specialised evidence.

Keep the calculation reproducible. Identify each input, its source and whether VAT, interest, credits, salvage, tax or double recovery may affect it. Forecasts and internal estimates should be labelled as such rather than presented as completed transactions.

Specific performance, cancellation, restitution, damages, declaratory relief and enforcement of a dispute-resolution clause are not interchangeable. The available remedy depends on the agreement, breach, election, feasibility, proof and any applicable statute.

8. Identify special legal regimes and defences

A contract may also be regulated by consumer, credit, rental, employment, insurance, construction, public-procurement or company law. For example, the Consumer Protection Act applies to qualifying transactions and contains rules about consumer information, unfair practices, terms and remedies. Do not assume it applies to every business or transaction.

Give the reviewer the facts needed to test possible issues, including:

• no contract, wrong party or lack of authority;
• a condition that never occurred;
• later variation, waiver, estoppel or election;
• prior or reciprocal non-performance;
• impossibility, force-majeure wording or supervening events;
• misrepresentation, mistake, duress or illegality;
• set-off, payment, release or settlement;
• exclusion, limitation, time-bar or dispute-resolution clauses;
• prescription; and
• statutory unfairness or public-policy objections.

Do not select a defence by label alone. Each has legal elements and may require evidence beyond the contract. In Beadica 231 CC v Trustees for the Oregon Trust, the Constitutional Court confirmed the importance of honouring contracts while explaining that enforcement remains controlled by public policy informed by constitutional values.

9. Treat deadlines and litigation preservation as urgent

The Prescription Act governs when many debts are extinguished by prescription and addresses when prescription begins, is delayed or interrupted. The period and calculation depend on the type of debt and facts. An acknowledgement, demand, negotiation or internal escalation may not have the effect a party assumes. Record the earliest performance, breach, knowledge, notice, acknowledgement and process dates, then obtain advice promptly.

If litigation is underway or reasonably anticipated, preserve relevant documents and electronic records, including material that weakens the case. High Court Uniform Rule 35 and Magistrates' Courts Rule 23 contain discovery procedures, but the precise duty and timing depend on the forum and stage.

The commercial-dispute service route may help when the agreement, notice, prescription, forum, evidence or remedy requires matter-specific advice. It does not promise a result or establish a lawyer-client relationship.

A practical handover pack

Provide a reviewer with:

1. a one-page issue list and desired outcome;
2. the complete contract set and a version note;
3. correct party and authority records;
4. a dated chronology with links to source documents;
5. performance, payment, acceptance and defect evidence;
6. breach notices, proof of delivery and responses;
7. a communication export with attachments;
8. a loss calculation and underlying records;
9. the opposing version and unfavourable evidence; and
10. every deadline, court paper, arbitration notice or dispute clause.

Keep originals in their native format and work from copies. Use neutral filenames, pagination and an index. Mark gaps instead of filling them with assumptions.

FAQs

Related Lexuno paths