How to build a project delay chronology for Construction Delay Claims

Build a project delay chronology by linking each alleged delaying event to contemporaneous records, affected schedule activities, contractual notice evidence, and competing explanations for lost time. Separate event dates from document dates, distinguish recorded facts from witness accounts and counsel’s inferences, and preserve uncertainty rather than filling gaps. The deliverable is a source-linked chronology that helps counsel test causation, assign missing proof, and give scheduling experts and witnesses a consistent record without treating every disruption as a delay to completion.

When to use this workflow

Use this workflow when an owner, contractor, or subcontractor alleges that late design information, restricted access, procurement problems, changed work, or another event delayed a construction milestone. It is particularly useful when a demand adds incident durations without explaining their relationship to the project schedule.

The task is evidence analysis: establish what happened, when, and what supports the asserted schedule effect. Keep pleadings, discovery deadlines, and hearing dates in a separate litigation chronology linked by event IDs.

This is a general US legal-workflow guide. Rights depend on the executed contract, governing law, facts, and forum. The federal evidence rules cited below supply a federal evidentiary framework, not requirements automatically applicable in state proceedings, arbitration, or contract appeals boards. Check the rules governing the actual proceeding. (Federal Rules of Evidence, Rule 1101)

What you need

Collect a bounded starting record for the disputed period:

• The executed contract, amendments, milestone definitions, schedule specifications, notice clauses, change orders, and relevant releases.
• Baseline and updated schedules, preferably native files, with data dates, calendars, logic, constraints, narratives, and revision history.
• Daily reports, RFIs, submittals, meeting minutes, photographs, access records, procurement logs, and correspondence.
• Delay notices, delivery evidence, responses, extension requests, and records of resequencing or recovery efforts.
• Asserted delay periods, available witness accounts, and collection or production identifiers.

Identify who maintained each record set. Preserve received versions before creating working copies. A schedule PDF may display dates without exposing the assumptions needed to test them. Identify missing attachments and unavailable native files at intake, rather than discovering those limitations after drafting the narrative.

Use the template

The companion template is Construction Delay Claims — Project delay chronology. You can copy this table into your working document or spreadsheet. Use one row per material event or change in event status, not one row per document.

Give each event a stable ID, such as E-001, that survives sorting. Cite the document ID and page, paragraph, message timestamp, or native schedule activity reference. A linked source register can hold author, custodian, file location, and version details.

Under evidence status, distinguish a documented occurrence, a recorded assertion, witness recollection, and counsel inference. An email proves that someone made a statement; its contents may need corroboration. Under impact, separate the observed restriction, asserted activity effect, and unverified milestone effect. Include contrary evidence and gaps. The final column should identify a responsible reviewer and concrete task.

Step by step

1. Define the disputed milestone and analysis window

Start with the proposition being tested: for example, whether delayed structural drawings moved the contractual dry-in milestone. Identify the milestone’s source, agreed revisions, and whether the demand seeks time, compensation, or both. Distinguish a contractual milestone from a contractor’s forecast or internal target.

Choose a window beginning early enough to show the pre-event schedule position and ending late enough to capture recovery or continuing effects. State exclusions, including any separate productivity claim.

Record in the template: an opening reference row identifying the milestone, contract citation, schedule versions, analysis window, and unresolved scope questions.

2. Normalize dates without erasing discrepancies

Distinguish when an event occurred from when someone recorded or reported it. A Friday email describing a Tuesday stoppage is not equivalent to a Tuesday daily report.

For uncertain dates, use a range and explain its basis. Check whether schedules use working days while correspondence uses calendar days. Preserve source timestamps and explain any time-zone normalization. Do not silently choose between conflicting reports or convert a forecast date into an actual completion date.

Record in the template: event date or range, record date, pinpoint source, evidence status, and applicable day-count convention. Assign conflicting dates for resolution rather than averaging them.

3. Assemble a source-linked event sequence

Group records around events such as an access restriction, RFI response, equipment delivery, or drawing release. Include the start, intermediate changes, and apparent end of each restriction. Link supporting and adverse records to the same event or related IDs.

Describe what each source establishes. “Minutes report that the contractor lacked access” is narrower than “the owner prevented all work.” Preserve originals behind extracted text and check attachments, drawing revisions, and referenced correspondence. Avoid counting copies of one report as independent corroboration.

Record in the template: a neutral event statement, pinpoint citations, related IDs, and any gap between the evidence and the allegation.

4. Test the connection to the schedule

Map each event to activity IDs and the contemporaneous schedule version. Compare pre-event and subsequent updates, including data dates, logic changes, calendars, constraints, float, and out-of-sequence work. Ask the scheduler whether forecast movement reflects the event, changed assumptions, or both.

Do not simply add incident durations. In Lusk, a fact-specific federal procurement dispute, the CBCA emphasized the contractor’s failure to establish critical-path impact during an additional interior-work suspension and also found the suspension reasonable. The decision does not establish a universal rule for private construction disputes or every disruption claim. (Lusk, pp. 8–10)

Record in the template: affected activities, schedule versions and data dates, observed forecast movement, and the expert question requiring analysis. Label untested critical-path assertions accordingly.

5. Place notice and authorization beside the event

Link the event to the actual provisions governing directions, notice, time extensions, and changes. Separate instruction, receipt, notice, and delivery dates. Check the required sender, recipient, method, content, and trigger; do not infer compliance from an email subject line.

Keep contractual analysis distinct from historical facts. Receipt of revised drawings may be documented while their treatment as a compensable change remains disputed. Do not import federal procurement notice periods into a private agreement. Check amendments and any release language affecting the event separately.

Record in the template: clause citations, notice and delivery references, disputed trigger, and counsel’s compliance question. Cross-reference a separate notice analysis where necessary.

6. Examine overlap, alternatives, and mitigation

For each window, look for other constraints on the same activity or milestone: unavailable labor, unfinished predecessor work, equipment delivery, weather, or subcontractor sequencing. Treat temporal overlap as a question to investigate, not an automatic finding of concurrent causation. Reserve legal characterization for the applicable contract and law.

Record proposed workarounds, who evaluated them, implementation, and resulting progress. A suggestion to move crews does not establish that suitable alternative work existed. Include unfavorable records in the same sequence.

Record in the template: competing event IDs, mitigation evidence, disputed assumptions, and the record or witness needed to test each explanation.

7. Verify the chronology and assign unresolved proof

Have a second reviewer trace material propositions to their sources. Ask project witnesses to distinguish personal observations from reported information. Send scheduling questions to the appropriate expert rather than converting counsel’s chronology into an unsupported scheduling opinion.

For federal evidentiary planning, Rule 901 requires sufficient evidence that an item is what its proponent claims; knowledgeable-witness testimony is one listed authentication method. Authentication alone does not resolve hearsay or other admissibility objections. (Federal Rules of Evidence, Rule 901)

Record in the template: verification status, potential authenticating witness, unresolved questions, and responsible owners. Save a dated version and change log. Keep counsel’s legal assessments identifiable when preparing a separate factual version for potential external use.

Worked example

Fictional scenario: Alder Quay Development retains Mason Ridge Builders to construct a distribution building. All parties, documents, dates, and contract terms in this example are invented. The contract sets September 30 as the dry-in milestone. Clause 12.4 calls for written notice to the owner’s project representative within seven calendar days after the contractor identifies an event likely to affect that milestone.

Mason Ridge alleges unresolved roof-curb dimensions prevented installation from June 3 through June 12 and delayed dry-in by ten days. Counsel has daily reports, an RFI exchange, a notice email, procurement correspondence, and schedule PDFs. The May 31 PDF forecasts September 30 dry-in; the June 30 PDF forecasts October 7. Native updates and confirmation of notice receipt are missing. Activity references below come from the PDFs, not verified native logic.

The chronology replaces “ten days awaiting dimensions equals ten days of completion delay” with testable questions. Did curb installation control dry-in? Would panel availability have prevented progress anyway? When could installation resume?

The June update shows forecast movement, not attribution. The supplier statement does not establish site delivery or pre-shipment unavailability. Sending notice June 10 does not itself resolve compliance: counsel must determine the contractual trigger and delivery facts. Qualify the claim pending those records rather than manufacture a complete narrative.

Common mistakes

• Using correspondence dates as event dates. Retain both and identify retrospective accounts.
• Treating idle days as completion delay. Link restrictions to activities and obtain milestone-impact analysis.
• Using only the final schedule. Preserve contemporaneous versions and identify changes affecting comparisons.
• Turning allegations into facts. Attribute statements and distinguish corroboration from duplicate reporting.
• Omitting contractor-side constraints. Include competing causes and mitigation evidence so the chronology tests the demand.

Final quality check

• Every material event has a stable ID and verified pinpoint source.
• Event dates, record dates, uncertain ranges, and day-count conventions are distinguishable.
• Schedule references identify versions, available data dates, and relevant activities.
• Supporting, adverse, and missing evidence appear beside the affected proposition.
• Notice entries identify controlling provisions and delivery evidence without assuming compliance.
• Claimed periods are checked for overlap; incident days are not presented as established milestone-delay days.
• Material propositions have been independently checked, and open issues are resolved or assigned.
• The intended audience and version are clear; internal assessments are not inadvertently carried into an external exhibit.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, and chronology capabilities can support examination of project records and identification of disputed propositions. Connect that work to focused witness questions through trial preparation. Counsel retains source verification, privilege decisions, contractual analysis, and expert scheduling judgments. To discuss this workflow for your construction record set, book a demo.

Frequently asked questions

Is a project delay chronology the same as a delay analysis?

No. The chronology organizes events and evidentiary support. Schedule analysis tests effects on activities and milestones. Link them without presenting counsel’s event list as an expert conclusion.

What if native schedules are unavailable?

Use available PDFs and narratives, identify versions, and state what cannot be tested. Assign collection of native files and associated scheduling information. Do not present reconstructed logic as contemporaneous evidence.

Should the chronology include cost records?

Include records that establish timing, activity, or a claimed consequence. Cross-reference the damages analysis rather than reproducing it. A dated expenditure alone does not establish responsibility for delay.

Can the working chronology become a trial exhibit?

Possibly, but not automatically. Federal Rule 1006 permits 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. Distinguish that evidentiary summary from a Rule 107 illustrative aid, which is not evidence. (Federal Rules of Evidence, Rules 1006 and 107)

Sources

• Federal Rules of Evidence: Rules 901, 1006, 107, and 1101.
• Lusk Mechanical Contractors, Inc. v. General Services Administration, CBCA 7759: suspension and critical-path discussion, pages 8–10.

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.