Build a breach-of-contract chronology around obligations and their triggering events, not simply document dates. Identify the operative agreement, map performance, notice, cure, termination, and loss events, and connect each factual statement to a precise source location. Preserve conflicting accounts and uncertain dates rather than selecting the version that favors your client. The deliverable is a source-linked chronology that separates documented statements, disputed facts, and legal inferences, with assigned follow-up work for gaps that could change counsel’s assessment.
Use this workflow when litigation counsel or an in-house team receives a demand, evaluates alleged nonperformance, prepares a witness, or incorporates a new production. Define the decision the chronology must support: whether delivery was timely, acceptance occurred, notice reached the designated recipient, or termination preceded the contractual opportunity to cure.
Keep the scope narrower than a complete matter history. Prioritize execution, amendments, performance dependencies, disputed conduct, contractual notices, and claimed losses. Include negotiations when relevant, but keep their possible interpretive significance separate from executed obligations.
This is a general US-oriented workflow guide framed as of October 13, 2026. Determine governing substantive law and forum requirements separately. The federal rules cited below should not be assumed to govern state proceedings or arbitration. Contractual rights depend on the actual language, governing law, facts, and deal context; a timeline does not establish those rights by itself.
Collect these inputs before substantive event coding:
Assign stable document IDs before Bates numbering if necessary, then maintain a crosswalk. Preserve source files separately from working copies and flag missing attachments. Record collection boundaries so absence from the reviewed set is not mistaken for proof that an event never occurred.
Escalate apparent preservation gaps. In federal civil litigation, Rule 37(e) addresses ESI lost after a failure to take reasonable preservation steps when it cannot be restored or replaced through additional discovery. Its specified measures require further findings; a missing document alone does not establish entitlement to sanctions. FRCP 37(e)
Use Breach-of-Contract Disputes — Case chronology as the working record. Copy this table into your working document or spreadsheet.
| Event ID | Date / basis | Actor and event | Obligation / issue | Source pinpoint | Evidence status | Gap / conflict | Action / owner |
|---|---|---|---|---|---|---|---|
Keep event IDs stable when sorting. In Date / basis, distinguish occurrence from reporting, dispatch, receipt, and calculation. Include time zones where material; use a supported range or “unknown” rather than invented precision.
In Obligation / issue, identify the contract version and clause, not merely “breach.” In Source pinpoint, cite the event evidence and contractual term separately, using document ID plus page, message timestamp, transcript lines, or spreadsheet sheet and cells.
Use Evidence status to distinguish source-verified content, reported events, disputed propositions, and inferences. These labels can overlap: a source-verified email may report a disputed event. Source verification means the row accurately describes the source, not that the assertion is true or admissible. Put uncertainty, the next action, responsible person, and internal target date in the final columns; use linked notes for longer explanations.
Write a scope statement above the table identifying the parties, disputed obligations, collection boundary, review cutoff, and intended use. Separate signature, effective, and performance commencement dates where the documents distinguish them.
Compare amendments with the base agreement. Identify which document supplies the relevant delivery milestone, acceptance procedure, payment trigger, notice address, cure provision, or termination mechanism. If execution or incorporation is disputed, preserve both positions and their supporting evidence rather than silently selecting a version.
Record: execution and amendment events, clause citations, and unresolved version questions. Put the scope and cutoff in the table header or accompanying notes.
For each contested obligation, identify what makes performance due and what evidence would establish that trigger. Distinguish shipment from delivery, delivery from acceptance, and invoice issuance from receipt.
Read definitions and cross-references alongside the operative provision. Capture dependencies such as customer specifications, access credentials, testing materials, or change-order approval. Record whether the agreement expressly addresses the effect of an unmet dependency; do not assume a customer delay automatically extends a supplier’s deadline.
Record: documented triggers and scheduled milestones, each linked to its clause. Label a due date as a scheduled obligation, not an accomplished event. Identify missing trigger evidence and reserve breach conclusions for counsel.
Read documents in context, including attachments and preceding messages. Use one independently testable proposition per row. A supplier’s completion announcement, a failed acceptance test, and the customer’s refusal to pay are separate events even if one thread contains all three.
Write “supplier stated installation was complete” when the message is the only support. Attribute allegations to their speaker. If a later document recounts an earlier conversation, distinguish the reported conversation date from the recording date.
Record: actor, neutral description, source pinpoint, and evidence status. Add genuinely independent corroboration to the existing event. Consolidate duplicate copies while preserving provenance and relevant differences between versions.
Retain original timestamps and explain normalization in the date field or linked notes. Distinguish the date printed on a letter from dispatch, delivery, and acknowledgment. Do not assign an undated attachment its parent email’s date without qualification.
For notice and cure, create separate rows for alleged default, notice preparation, sending, receipt evidence, response, cure activity, and termination. Check designated recipients, permitted methods, effectiveness language, and counting provisions before proposing a cure endpoint. Treat contractual notice timing separately from procedural filing deadlines.
Record: date basis, clause references, provisional calculations, and assumptions requiring approval. Keep alternative sequences visible when receipt, notice compliance, or interpretation remains disputed.
Read the chronology from each party’s position. Look for customer delays, changed specifications, rejected access requests, partial performance, continued use, and reservations of rights. Keep adverse evidence visible rather than removing it to simplify the narrative.
Connect claimed losses to the alleged nonperformance and supporting amounts. Separate estimates, purchase commitments, invoices, payments, and credits. Record substitute-performance decisions and alternative causes without assuming that every later expense is recoverable.
Record: contradictory sources, linked event IDs, loss-document references, and the question each conflict creates. For spreadsheet amounts, cite cells and calculation inputs; distinguish incurred, invoiced, paid, and claimed amounts.
Open every source supporting a consequential entry. Confirm that the passage supports the proposition at the stated level of certainty. Check names, attachments, pagination, OCR errors, and quoted-message attribution. Compare a material extracted date or amount against the underlying image or native record.
For likely exhibits, identify a knowledgeable witness, records custodian, or other potential authentication route. Federal Rule of Evidence 901 requires evidence sufficient to support a finding that an item is what its proponent claims. A chronology citation does not supply that foundation by itself. FRE 901
Record: source-verification status and specific foundation tasks in linked notes or the action field. Refer hearsay, completeness, privilege, and confidentiality questions to counsel separately from factual verification.
Prioritize issues that could change the sequence or assessment. Missing receipt evidence may matter more than an immaterial discrepancy in an internal meeting date. Assign a concrete task: retrieve a mailbox, locate a courier record, interview a recipient, or obtain an attachment.
Have a second reviewer test decisive rows against their sources. Preserve revision history and explain material changes. Reconcile new production documents against existing event IDs before adding entries. Keep restricted legal analysis apart from versions intended for witnesses or external use, without assuming separation alone establishes privilege.
Record: owner, internal target date, resolution or retained uncertainty, reviewer, and version date. Release with the collection boundary and open issues visible.
Fictional scenario: Alder Quay Foods retains North Vale Systems to install warehouse software for $240,000. All parties, documents, amounts, and terms below are fictional.
Signed agreement D001 requires installation by June 10, 2026, subject to Alder providing test data by June 3. Section 8 gives North Vale ten calendar days to cure after receipt of a default notice complying with section 12, before Alder may terminate for that default. Section 12 specifies the recipient and delivery method.
Counsel has D001, a June 5 email stating that test data is attached, a June 11 internal test report, a default letter dated June 12, and a termination letter dated June 20. The email attachment and notice transmission records have not been collected. A $36,000 replacement-services invoice exists, but payment evidence is missing.
| Event ID | Date / basis | Actor and event | Obligation / issue | Source pinpoint | Evidence status | Gap / conflict | Action / owner |
|---|---|---|---|---|---|---|---|
| E01 | June 5, 2026; email timestamp | Alder states test data is attached | D001 §3; June 3 input milestone | D014 p.1; D001 p.4 | Source-verified statement; delivery unconfirmed | Attachment absent; earlier delivery unknown | Associate: obtain attachment and earlier transfers; test dependency’s effect |
| E02 | June 11, 2026; report date | Alder tester reports failed checks | D001 §4; installation and acceptance | D021 pp.2–3; D001 p.5 | Source-verified report; reported results | Test time, conditions, and supplier access unclear | Technical witness: check logs; failures alone do not allocate responsibility |
| E03 | June 12, 2026; letter date | Alder’s letter asserts default | D001 §§8, 12; notice and cure | D025 p.1; D001 pp.8, 10 | Source-verified contents; effectiveness unconfirmed | Dispatch and receipt missing; D031 p.1 dated June 20 asserts termination | Lead counsel: obtain delivery records and assess cure sequence |
These entries change the inquiry. June 10 cannot be assessed without investigating the customer-input dependency and its contractual effect. June 12 is a letter date, not established receipt. Even receipt that day would raise a sequencing problem for the June 20 termination under the fictional ten-day provision; counsel must still assess notice compliance and the full contract.
Add D031 as its own termination entry in the full chronology rather than treating the cross-reference in E03 as sufficient. Add the replacement invoice as a separate loss entry marked invoiced, not paid, and investigate scope and credits. The three rows identify priority questions, not a complete history or either party’s entitlement to relief.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its Chronology Viewer connects timeline findings to source passages, while its trial-preparation capabilities include chronology, evidence analysis, and deposition preparation. Use these capabilities to support document-backed event review; counsel remains responsible for verifying passages, interpreting contractual dependencies, and resolving uncertainty. To assess this workflow with your team’s document set, book a demo.
Usually, but include earlier events when they bear on disputed language, incorporated specifications, or alleged representations. Distinguish negotiations from executed obligations and ask counsel to assess their proposed legal use under governing law.
Use “unknown” or the narrowest supported range. Explain the basis, such as a later message describing an earlier meeting. Keep the recording date separate and do not invent an occurrence date for convenient sorting.
Not automatically. In federal proceedings, Rule 1006 permits qualifying evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not those materials were introduced into evidence. Underlying originals or duplicates must be available for examination or copying. Rule 107 governs illustrative aids, which are not evidence. Determine the proposed use and applicable forum requirements before repurposing the working chronology. FRE 1006 and 107
State that collection boundary prominently. Attribute uncorroborated accounts and prioritize recipient-side notice records, performance logs, and complete communications. Reassess consequential entries when opposing-party or third-party records arrive; absence from a partial collection does not establish nonoccurrence.
This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.