Critical path delay analysis checklist

15 steps every GC must work through before submitting a delay claim or time impact analysis.

ExcelWordPDF

The 15-step checklist every GC and federal prime must work through before submitting a delay claim or time impact analysis. From baseline integrity verification through concurrent delay documentation and entitlement confirmation.

Why construction delay claims fail, and what the analysis actually requires

Most construction delay claims fail not because the delay didn’t happen, but because the analysis doesn’t hold up. The contractor can prove the owner’s design was late. The contractor can prove the redesign took 6 weeks. What the contractor can’t prove, because nobody documented it at the time, is that the 6-week redesign was on the critical path when it happened, that there was no concurrent contractor-caused delay running simultaneously, and that the project actually lost 6 weeks of contract time as a result.

Those three things are what a delay claim requires. They’re also the three things that get challenged in every mediation, arbitration, and litigation involving a construction schedule delay. An experienced scheduling expert on the opposing side will take a delay claim apart in about four hours if the underlying analysis skips any of them.

The problem isn’t that project teams don’t know a delay happened. They know. The problem is that by the time the claim is assembled, usually 12 to 18 months after the delay event, the documentation to support those three elements is scattered across RFI logs, meeting minutes, schedule updates, email chains, and the memories of superintendents who are now on different projects. A contemporaneous delay analysis, or at least a contemporaneous documentation practice, is worth more than the most sophisticated retrospective forensic analysis.

This checklist is the practitioner’s guide to running a delay analysis that survives scrutiny. The 15 steps here are the ones that separate delay analyses that get paid from delay analyses that get denied. The first 7 steps are about the baseline. Steps 8 through 12 are about the delay event itself. Steps 13 through 15 are about entitlement.

Who this checklist is for

  • General contractors documenting delay events for time extension requests and change order time impacts
  • Federal prime contractors preparing REAs (Requests for Equitable Adjustment) on government contracts
  • Project controls engineers conducting time impact analyses for owner-directed changes
  • Construction attorneys and claims consultants reviewing contractor delay documentation before submission
  • Project managers building contemporaneous delay records during the project rather than reconstructing them at claim time

If you’re building a TIA for a change order, this checklist works as a pre-submission review. If you’re running a forensic delay analysis at project closeout, it works as a gap analysis on the documentation you have versus the documentation you need.

The 15-step delay analysis review

The checklist covers 15 steps every delay analysis must work through before submission:

  1. Confirm the baseline schedule is approved and admissible. A delay analysis is only as strong as its baseline. Before any delay calculation, verify that the baseline schedule was formally approved by the owner, that the approval is documented in writing, and that the approved baseline file is the one being used for comparison. An unapproved or disputed baseline is a vulnerability that the opposing party will exploit.
  2. Verify baseline CPM logic is free of open ends, unsupported lags, and hard constraints. Run a logic check on the baseline: zero open-end activities except project start and finish, no FS lags over 5 days without field-verifiable justification, and no hard constraints on intermediate activities that suppress float. A baseline with these defects will fail scheduling expert scrutiny. Fix the baseline defects first, then run the delay analysis.
  3. Identify the schedule update that was current at the time of the delay event. Pull the schedule update whose data date immediately precedes the delay event. This is the schedule-as-it-stood before the delay, the before-snapshot. Document the data date of the before-snapshot and confirm it was submitted to the owner on the project’s normal update cadence.
  4. Extract the critical path from the before-snapshot, not from the baseline. The baseline critical path may differ from the critical path at the time of the delay if prior progress has shifted which activities are driving the project finish. Run the critical path filter on the before-snapshot. The activity affected by the delay event must appear on the critical path in the before-snapshot for the delay to be project-affecting.
  5. Document the delay event: cause, date of occurrence, and affected activities. For each delay event in the analysis, establish: what caused it (owner-furnished design, differing site condition, owner-directed scope change, weather, etc.), the date it first affected the project, and which schedule activities it directly affects. The cause determines entitlement; the date determines the critical path test; the affected activities determine the schedule impact calculation.
  6. Model the delay event into the before-snapshot using the as-impacted method. Add the delay activities, extend the affected durations, or insert delay logic fragments into the before-snapshot schedule. Run the schedule with the delay modeled in. The difference between the before-snapshot finish date and the as-impacted finish date is the theoretical schedule impact of this delay event in isolation.
  7. Run the collapsed as-built method as a cross-check if contemporaneous updates aren’t available. If contemporaneous schedule updates don’t exist or weren’t accepted by the owner, the collapsed as-built method provides an alternative analytical path. Both methods should yield consistent results if the delay documentation is sound. A large discrepancy between the two methods signals a documentation gap.
  8. Verify the delay event is on the critical path, not just near it. The as-impacted schedule must show the delay event extending the project finish date. An activity with 15 days of total float at the time of the delay event is not critical. Even if the delay consumed 20 days of activity duration, the 15 days of float absorb the first 15 days of the impact. Only delay that actually pushes the project finish date is compensable as a project delay.
  9. Document concurrent delays. Both owner-caused and contractor-caused. A concurrent delay is any delay event not caused by the party presenting the claim that was also operating on the critical path during the same time period. Document concurrent delays even if they hurt your claim. Omitting them makes the analysis look cherry-picked, which is worse.
  10. Pull the contemporaneous documentation for each delay event. For every delay event: pull the RFI that identified the issue, the owner’s response date, the meeting minutes or correspondence that established the redesign requirement, the schedule update showing the delay impact, and the change order or change order request. The strength of a delay claim is directly proportional to the contemporaneous documentation behind it.
  11. Calculate the excusable and compensable delay periods separately. Excusable delays entitle the contractor to a time extension. Compensable delays entitle the contractor to both a time extension and additional compensation. Separate the analysis. Present the excusable delay period, then subset it into the compensable portion with the entitlement basis for each event.
  12. Confirm the notice requirements in the contract were met for each delay event. Most construction contracts require written notice of delay within 7, 14, or 21 days of the delay event’s occurrence. Federal contracts under FAR and DFARS require timely written notice as a condition of entitlement. A delay that wasn’t noticed timely is an entitlement vulnerability regardless of how solid the schedule analysis is.
  13. Verify the time extension request ties to the contract’s change clause. The delay claim must be presented under the contract’s change clause (FAR 52.243-4 on federal contracts, the equivalent clause in private contracts) with the correct clause cited in the submission. A delay claim presented as a standalone document without citing the contract mechanism is procedurally vulnerable.
  14. Quantify the delay in contract days, not calendar days, unless the contract measures in calendar days. Most construction contracts measure delay in calendar days (including weekends). Some federal contracts and some private contracts with defined workweeks measure in working days. Using the wrong denominator inflates or deflates the claimed period. Check the contract’s definition of “day” before the final calculation.
  15. Run the completed analysis past a scheduling expert or construction attorney before submission. A delay analysis that hasn’t been stress-tested before submission is one that gets stress-tested by the opposing party’s expert in an adversarial setting. Internal review, by a scheduling consultant, a claims-experienced attorney, or a senior project controls professional not involved in the original analysis, catches the gaps that the analysis team has normalized.

How to work through the delay analysis in sequence

Work through this checklist in sequence. The first 7 steps are prerequisite to the delay event analysis in steps 8–12, which are prerequisite to the entitlement analysis in steps 13–15:

  • Mark
  • Complete, In Progress, or
  • Gap (with documentation of what’s missing) for each step.
  • Any Gap item needs an owner and a plan: either find the documentation, reconstruct it with explicit acknowledgment that it’s reconstructed, or flag the gap as a vulnerability in the submission narrative.
  • Do not submit a delay claim or TIA while a Gap on steps 1–7 or steps 11–12 is open. These are entitlement killers.
  • Attach the completed checklist to the claim submission package as evidence of the review process.

Stop reconstructing delay documentation at claim time

The 15 steps above take 4–6 hours when the documentation is organized and contemporaneous. They take weeks when the project team is reconstructing email chains and trying to match RFI logs to schedule updates from 18 months ago. Contracts Connected’s contract intelligence module keeps RFIs, change events, schedule updates, and correspondence indexed by project activity, so when a delay needs to be analyzed, the documentation exists in one place rather than across five systems and three former employees’ inboxes.

For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.

Frequently asked questions about critical path delay analysis

What is the critical path in the context of a delay claim?

The critical path is the longest sequence of logically connected activities that determines the earliest possible project completion date. A delay is critical for claim purposes when it extends the project completion date. Meaning the delayed activity is on the critical path at the time of the delay with zero total float, and the delay duration exceeds any available float on that path. An activity with positive float at the time of the delay is not critical even if the delay consumes the activity’s entire duration.

What’s the difference between excusable and compensable delay?

Excusable delays entitle the contractor to additional contract time (a time extension), which protects the contractor from liquidated damages. Common excusable causes: owner-directed changes, differing site conditions, government-caused delays, and unforeseeable weather beyond what historical data would predict. Compensable delays are a subset of excusable delays where the owner caused the delay. Making the contractor eligible for both time and additional compensation. Not all excusable delay is compensable; unforeseeable weather is typically excusable but not compensable.

How does concurrent delay affect a delay claim?

Concurrent delay, owner-caused and contractor-caused delays occurring simultaneously on the critical path, is the most common defense to a construction delay claim. If the project would have been delayed by the contractor’s actions regardless of the owner’s actions, the owner’s compensable delay exposure is reduced or eliminated for the concurrent period. The legal standard varies by jurisdiction and contract language, but the practical standard is: document the contractor’s own concurrent delays in the analysis and present them honestly. Omitting them destroys credibility.

What notice is required for a construction delay claim?

Notice requirements are contract-specific, but on most commercial contracts the contractor must provide written notice within 7–21 days of the delay event’s occurrence or first impact. Federal contracts under FAR 52.243-4 require written notice as soon as practicable and within 20 days after cessation of the delay. Failure to provide timely notice is a condition precedent to entitlement in most jurisdictions. Meaning a delay that wasn’t noticed timely may be barred regardless of how well the schedule analysis supports it. Check the contract clause and the controlling jurisdiction.

When is a forensic schedule analysis required versus a time impact analysis?

A time impact analysis (TIA) is a prospective or near-contemporaneous analysis of a specific delay event, typically prepared at the time of the change or shortly after. A forensic schedule analysis is a retrospective analysis prepared well after the project or delay period, often using the project’s schedule update history to reconstruct the critical path as it evolved over time. TIAs are stronger claim vehicles when prepared contemporaneously. Forensic analyses are more common in litigation but more vulnerable to challenge because they involve reconstruction.

Can a contractor claim delay damages if the project finished on time?

Generally no. Project delay damages require that the project’s completion date was actually extended beyond the contract completion date. If the project finishes on time, delay damages for project-level delay are typically not available. However, a contractor may still recover for disruption damages (inefficiency, acceleration costs, extended general conditions on individual activities that were delayed but didn’t push project completion) even when the project finishes on time or early.

Where this document lives in the system
Back-Office System · Contracts Connected
Product bridge

Contracts Connected tracks every document a vendor owes you against the contract, reads what comes back, and shows who can mobilize, who is compliant on site, and who can be paid. Construction compliance.

More in Project management

All Project management templates