Back to Insights
Evidence Note · Disputes
6 min · 2026-02-28

Supplier disputes: what was known, and when it was known

Disputes rarely hinge on one document. They hinge on sequence: notices, change orders, meetings, and the record around them.

DisputesContractsForensicsChronology

The failure mode

Supplier disputes escalate when parties disagree on sequence. The record fragments across email, annexes, meeting notes, and late changes. The work is to reconstruct a chronology that survives challenge — and to surface where the narrative relies on absent evidence.

Chronology excerpt

T0 · Week 0
Contract executed
Gap
Reported

Baseline scope and delivery dates agreed.

Observed

Execution complete; annexes referenced but not present in package.

Missing verification

Full annex set as executed (not just the template).

T1 · Week 6
Change order requested
Contradiction
Reported

Change framed as minor variation.

Observed

Internal comms treat change as schedule-critical.

Missing verification

Decision trail explaining why change was accepted without schedule reset.

T2 · Week 12
Delay crystallises
Contradiction
Reported

Supplier states delay caused by customer.

Observed

Notice timing inconsistent with contract notice requirements.

Missing verification

Proof of timely notice and mitigation record.

What the pack delivers

  • An annotated master chronology with stable evidence references.
  • A divergence matrix: claim vs record vs missing verification.
  • Exportable index suitable for counsel, experts, or internal review teams.

Need a dispute record you can stand over?

We scope to one dispute and one document set. Output is designed for scrutiny.