Build a construction delay chronology by linking each material event to its source, the affected work, the relevant schedule version, and the contractual issue it raises. Keep documented facts separate from witness accounts and counsel’s inferences. Test competing explanations, notice evidence, overlapping events, and claimed consequences rather than adding incident durations together. The deliverable is a source-linked chronology that identifies what happened, what remains disputed, and which records or witnesses counsel needs before advancing a delay position.
Use this workflow when counsel receives a delay demand, prepares an early merits assessment, or reconciles competing project narratives before expert analysis or depositions. It suits owner, contractor, and subcontractor disputes involving late access, design changes, procurement problems, resequencing, suspensions, and disputed completion dates.
Start with a defined claim period or milestone. A chronology covering every project communication can obscure the sequence that matters. Maintain separate but linked project and litigation chronologies: an access restriction belongs in the former; service of a discovery request belongs in the latter.
This is a US-oriented workflow guide, not advice for a particular matter. The federal evidence provisions below require separate consideration from state-court or arbitral requirements; check the applicable forum rules. Contract interpretation and procurement authorities must likewise remain tied to the governing agreement and dispute context.
Collect the executed agreement, amendments, incorporated conditions, milestone provisions, change procedures, notice clauses, extensions, and releases. Identify the contract tier governing the claim rather than importing owner-contract provisions into a subcontract analysis.
For the disputed period, assemble:
Preserve existing document identifiers. Assign stable internal IDs where none exist, and retain email attachments and schedule companion files together. Record the collection cutoff so silence in an incomplete production is not treated as proof that an event never occurred.
Copy the Construction Delay Claims — Case chronology table into your working document or spreadsheet. Use one row per material event or distinct proposition, not necessarily one row per document.
| Event ID | Event / record dates | Event and status | Source / locator | Work / schedule | Contract issue | Conflict / gap | Next action / owner |
|---|---|---|---|---|---|---|---|
In Event / record dates, distinguish occurrence from documentation: “Event: June 4; email: June 6.” Use a range or “date unresolved” where precision is unsupported.
In Event and status, label the proposition as documented fact, witness account, disputed allegation, or counsel inference. A verified document containing an allegation does not verify the allegation. “Email reports unavailable access” is narrower than “owner prevented all work.”
In Source / locator, enter the document ID, author, and exact page, paragraph, attachment, photograph, or spreadsheet cell. For Work / schedule, identify the activity ID and schedule version or data date; leave critical-path impact unresolved unless supported.
Use Contract issue for the clause and question, not an assumed entitlement conclusion. Conflict / gap should link adverse evidence or identify missing proof. Next action / owner makes unresolved points assignable. Keep longer analyses and verification records in linked notes keyed to the event ID.
Identify the milestone, claimed period, affected scope, and requested remedy. Separate the factual questions supporting a time extension, compensation, disruption, acceleration, or a liquidated-damages defense. Do not merge them merely because they share dates.
Write a neutral question: “Did restricted electrical-room access affect the September commissioning milestone?” Identify the asserted cause and plausible alternatives, including incomplete predecessor work. Define whether the chronology covers one delay window or several linked windows.
Record: Create a scope row identifying the milestone, claim period, requested relief, relevant contract provisions, and counsel responsible for the chronology’s boundaries.
Inventory available collections before extracting events. Distinguish project-created records from later claim narratives and litigation analyses. Preserve provenance and link duplicate copies without losing differing annotations or attachments.
Record event dates separately from sent, received, uploaded, and document dates. If a daily report was entered later, preserve both dates. Where timestamps matter, retain the original time zone and document normalization. Do not silently replace an uncertain date with a convenient sorting value.
For schedules, identify the data date as well as the filename and revision. Flag a later update describing earlier progress rather than presenting it as contemporaneous knowledge.
Record: Populate source locators and date qualifiers; assign missing-file and version questions to named reviewers.
Read each source for discrete events: access denied, drawing issued, RFI answered, equipment delivered, work resumed, or notice transmitted. Split a letter’s factual report from its attribution of responsibility and request for relief.
Capture the author and stated basis of knowledge. Distinguish a project manager repeating a subcontractor’s account from a superintendent describing a firsthand observation. Link contrary evidence immediately rather than maintaining an advocacy-only timeline.
Treat worker count, idle duration, and completion impact as separate propositions. An email reporting idle crews should not become a chronology entry asserting all three without supporting records.
Record: Enter the narrow event, evidentiary status, exact source location, and competing account under a stable event ID.
Map events to affected activities, predecessors, successors, and relevant schedule updates. Compare the planned sequence with reported progress and actual work. Ask the scheduler to explain changes in logic, constraints, calendars, and critical-path identification where they affect the asserted delay.
Do not add incident durations together or assume that an activity stoppage equally extends project completion. In Lusk Mechanical Contractors, the CBCA emphasized missing proof of critical-path impact for an additional interior-work suspension and also found its duration reasonable. This was a fact-specific federal procurement decision, not a universal test for private-project disruption claims (decision, pp. 8–10). (cbca.gov)
Record: Identify the activity and schedule version, distinguish claimed impact from checked analysis, and assign unresolved schedule questions.
Locate notices, change instructions, extension requests, reservations, and releases relative to the underlying events. Read the operative clause before identifying its trigger, sender, recipient, delivery method, required contents, and timing question.
Separate issuance from receipt and a request from approval. Classify meeting discussions, formal notices, and change orders separately, then assess their contractual significance. Record delivery evidence rather than assuming an attachment reached the required recipient.
For a potentially relevant release or extension, link its wording and covered period. Assign counsel its interpretation under the agreement and governing law instead of recording an unsupported dispositive conclusion.
Record: Add the clause citation, communication dates, delivery proof, and unresolved compliance or scope question beside the affected event.
Review the chronology by delay window. Compare access restrictions against procurement readiness, design status, labor availability, weather, and unfinished predecessor activities. Flag overlap for concurrency analysis rather than labeling it a resolved legal conclusion.
Identify mitigation evidence: alternative work areas, resequencing proposals, replacement deliveries, or rejected recovery plans. Link cost records to specific alleged consequences; do not allocate an entire monthly ledger total to one event without a supported reconciliation.
Keep claimed days and amounts distinct from checked calculations. Preserve source cells, assumptions, and treatment of overlapping periods so another reviewer can reproduce the calculation. Keep detailed damages analysis outside the chronology, linked by event ID.
Record: Add adverse records, alternative explanations, calculation references, and questions for counsel, the scheduler, or cost reviewer.
Have a second reviewer open cited sources and check representative entries, every decisive event, and contested dates or quotations. Identify witnesses who can explain record creation and underlying events. Federal Rule of Evidence 901 requires sufficient evidence that an item is what its proponent claims; knowledgeable-witness testimony is one authentication example. Separately assess hearsay and other admissibility issues (Rule 901). (uscourts.gov)
Specify whether the output is working analysis, expert input, or a proposed courtroom presentation. Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced. Underlying originals or duplicates must be available to other parties at a reasonable time and place. An illustrative aid under Rule 107 is different: it is not evidence (Rules 1006 and 107). (uscourts.gov)
Record: In event-linked notes, record reviewer, verification date, and outstanding evidentiary questions. Assign open issues before circulating a dated version.
Fictional scenario: Alder Quay Properties retained Meridian Works to construct a private warehouse. Meridian claims a June 3–14 electrical-room access restriction delayed September 30 commissioning by twelve calendar days. Its demand cites daily reports and a June 14 notice. The fictional contract’s §8.3 addresses delay notices; compliance remains unassessed.
The collection contains daily reports, an equipment log, and a June schedule PDF. The native schedule and notice delivery evidence are missing. All parties, documents, provisions, and dates are invented.
| Event ID | Event / record dates | Event and status | Source / locator | Work / schedule | Contract issue | Conflict / gap | Next action / owner |
|---|---|---|---|---|---|---|---|
| E01 | June 3 / June 3 | Report states room inaccessible; documented report, extent unverified | DR-061; superintendent; p. 2 | Switchgear installation; June PDF, data date unresolved | §8.3 trigger question | No all-day access or completion-impact proof | Associate: obtain access log and interview superintendent to test duration |
| E02 | June 10 / June 11 | Log records switchgear delivery June 10; documented entry | PR-019; procurement lead; row 18 | Installation readiness; activity linkage unresolved | Alternative causation | Expected delivery and preparatory-work readiness unclear | Scheduler: reconcile readiness; access may not explain entire window |
| E03 | June 14 / June 14 | Letter asserts twelve calendar days’ completion delay; disputed allegation | NT-004; project manager; p. 1 | Commissioning; schedule linkage unverified | §8.3 notice | Delivery proof and native schedule missing | Counsel: collect transmittal and native file before assessing notice and duration |
The sequence changes the immediate decision. Counsel should not repeat the twelve-day demand as established completion delay. The June 10 delivery entry raises a competing readiness question, but does not prove access was immaterial before delivery. Installation preparation or other activities may have been affected; the available records do not answer that question.
Targeted collection and schedule analysis should precede a revised estimate. Preserve both explanations while testing what work could proceed during each part of the window, whether available float absorbed any impact, and whether the commissioning sequence changed.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its chronology capabilities alongside document and evidence analysis to support event review; its trial preparation capabilities also support deposition preparation and privilege and confidentiality analysis. Keep counsel responsible for source verification, contract interpretation, and delay conclusions. To discuss applying these capabilities to construction-delay records, book a demo.
No. Select reports establishing material events, continuity, contradictions, or disputed inactivity. Keep the broader collection accessible and document the selection approach. For repetitive conditions, use a supported date-range entry with locators for the underlying reports.
Record what they show without assuming they reveal all logic or settings. Identify missing native files, calendars, narratives, and revision history. Ask the scheduler to identify supportable conclusions and limitations; retain those qualifications beside affected events.
Use it to identify overlapping events and competing explanations. Reserve a concurrency conclusion for schedule analysis and counsel’s assessment of the agreement and applicable law. State whether an entry describes simultaneous incidents, affected activities, or an analyzed completion impact.
Set intended use and access before adding strategy. Keep legal analysis distinguishable from factual source entries, and review mixed records individually. Do not rely on a blanket privilege label; assign counsel the protection and disclosure assessment before circulation.
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.