You prove an agreement by building the record made at the time of what the parties said, accepted and did.
Contract disputes are often evidence disputes. The most persuasive material is usually created at the time: the quote, checkout screens, call recording, order confirmation, signed document, payment, delivery, account notes and subsequent performance.
A later assertion such as “our system would never allow that” should be tested against the records produced by that system in the actual transaction.
Key points
- Records made at the time usually matter more than reconstructed memory.
- Different documents may prove different parts of the agreement.
- Metadata, timestamps and internal document references can authenticate the sequence.
- Absence of one “master contract” does not mean there was no agreement.
Build a document chain
Start with the offer or quote, then place acceptance, confirmation, payment, performance and later communications in order. Give each document a date and explain what point it proves.
Use internal records carefully
SAR material, CRM notes and system logs can be valuable, but interpret them in context. An unexplained status code should not be treated as self-evident; ask what the field means, who populated it and what event triggers it.
Contradictions can be evidence
If a final response says the order was accepted but a later litigation position says it was declined, put the statements side by side with dates and source. A decision-maker can then see the factual conflict without reading hundreds of pages.
In practice
- Create an evidence index rather than sending an unstructured data dump.
- Keep original file names and metadata where authenticity might be disputed.
- Ask for the trader’s version of any document you were shown but which is missing from disclosure.
What to do
A practical next-step plan
- Create a chronology.
- Index documents by date and purpose.
- Identify gaps in the record.
- Map contradictions between different accounts.
- Ask focused questions about missing or unexplained documents.
Common traps
Things that often confuse the issue
- Do not assume a SAR contains every legally relevant record merely because the organisation calls it complete.
- Do not mix allegation and evidence in one long narrative.
- Do not rely on screenshots without dates/context if original files are available.
Evidence worth keeping
Write the proof gap as a precise request.
Useful wording.
“You say I agreed to [term] on [date]. Please identify and provide the acceptance record you rely upon, together with the version of the terms presented before acceptance. Your current account record states the outcome but does not show the act by which I agreed.”
This is especially important where the dispute concerns a long minimum term, finance, recurring charge or waiver of an important right.
Where terms conflict, chronology becomes critical.
A quote can say one price, the order another and the invoice a third. Do not choose the document you prefer and ignore the rest. Explain which communication formed or varied the agreement and why later inconsistent paperwork did or did not change it.
A missing signed document does not automatically mean no contract, but neither does an account entry prove one.
Many contracts are valid without signatures. Equally, an internal system saying “customer agreed” is only one piece of evidence. Ask for the acceptance event: signed form, call recording, click record, order submission, confirmation or conduct relied upon.
| Dispute | Evidence to seek |
|---|---|
| “You agreed by phone.” | Call recording/transcript, date/time, sales notes. |
| “You accepted online.” | Checkout audit, click/consent record, versioned terms. |
| “You renewed.” | Renewal notice, recontract event, acceptance evidence. |
| “This price was agreed.” | Quote/order/payment schedule and subsequent invoices. |
Proving a contract is an evidence exercise.
The question is not whether either side can produce a document headed “CONTRACT”. Courts and complaint bodies can infer an agreement from emails, orders, invoices, payments, performance and conduct. Build the sequence showing what each side proposed, what was accepted and what happened afterwards.
Official sources
Check the rules behind this guide
Contract formation is largely based on common-law principles rather than one consumer statute. The official material below is included because it gives an accessible statement of the basic formation principles and, where relevant, the statutory consumer overlay.
These are official or primary sources for this topic. Rules, scheme terms and deadlines can change, so check the live source before relying on a formal time limit or procedure.