Your project finished five months late. The owner is withholding liquidated damages. Your subcontractor just filed for an extension of time. Everyone at the table says it's someone else's fault, and nobody can prove it because nobody can explain exactly what happened to the critical path, when it happened, and who caused it.
You need a forensic delay analysis. Not a schedule review. Not a health check. Not a letter from your scheduler saying "it wasn't our fault." You need a structured, methodology-driven reconstruction of the project timeline that can survive cross-examination in an arbitration hearing.
This is the analysis that determines who owes who — time, money, or both. Here's what it actually is, when you need one, and what to look for in both the deliverable and the analyst.
What Forensic Delay Analysis Is (and Isn't)
A forensic delay analysis is a retrospective, evidence-based examination of what happened to a project's critical path over time. It compares what was planned against what actually occurred, identifies the events that caused the schedule to slip, attributes those delays to the responsible parties, and quantifies the time impact.
It is not the same as a schedule health check. A DCMA 14-point assessment tells you whether your schedule is well-built. A forensic delay analysis tells you who broke it and by how much. The health check is the physical exam. The forensic analysis is the autopsy.
It is not an opinion letter. "In my professional judgment, the owner caused the delays" doesn't survive five minutes of cross-examination without structured methodology behind it. Arbitrators and judges want to see the math — every window, every critical path shift, every concurrent delay attribution — not a narrative with a conclusion stapled to the end.
In most Canadian and U.S. jurisdictions, a forensic delay analysis must follow a recognized methodology to be admitted as expert evidence. An analysis that can't demonstrate its methodology, data sources, and attribution logic can be challenged and excluded before it ever reaches the decision-maker.
The Three Methodologies You Need to Know
The AACE International Recommended Practices define several accepted methods for forensic schedule analysis. In practice, three of them cover the vast majority of construction delay disputes. Each one answers a different question, and a thorough analysis often uses more than one.
1. Windows Analysis (AACE MIP 3.3)
This is the workhorse. The project timeline is divided into discrete periods — "windows" — typically aligned with schedule update cycles. Within each window, the analysis identifies what happened to the critical path: which activities slipped, which new delays appeared, and who was responsible for each one.
The power of windows analysis is its contemporaneous, period-by-period granularity. Instead of looking at the whole project and saying "it was late," you're looking at each month and saying "in this window, the critical path shifted from structural steel to electrical rough-in because the owner's RFI response was 22 days late, causing a 14-day net delay to the completion milestone."
Windows analysis is the primary method for most delay claims because it handles concurrent delay attribution — situations where both the owner and contractor caused delays in the same period. The conservation rule ensures that the total delay attributed across all parties never exceeds the actual observed delay in any given window.
2. Collapsed As-Built / But-For (AACE MIP 3.8)
This is the cross-check. The method takes the as-built schedule and systematically removes one party's delays, then recalculates the project completion date. The difference between the as-built finish and the "but-for" finish is the delay attributable to the removed party.
If opposing counsel is going to challenge your windows analysis, they're going to demand a but-for as an independent validation. Having both methods in your submission — and showing that they produce consistent results — significantly strengthens the claim.
3. Time Impact Analysis (AACE MIP 3.7 / RP 52R-06)
This is the prospective method. Instead of looking backward at what happened, TIA models a specific delay event forward — inserting a "fragnet" (a fragment of network logic representing the delay) into the CPM schedule and recalculating to see how it impacts the completion date.
TIA is most useful for quantifying the impact of a specific change order, RFI delay, or owner-directed scope change before the project finishes. It's the method you use when you're still building and need to demonstrate that a particular event will push the end date — typically as part of an extension of time request.
For a full delay claim submission, you almost always want windows analysis as the primary method plus collapsed as-built as independent validation. If your claim involves specific owner-caused events (late RFIs, change orders, access restrictions), adding TIA fragnets for each event gives you a third layer of evidence. The more methods that align on the same conclusion, the harder it is to challenge.
When You Need a Forensic Delay Analysis
Not every late project needs a forensic analysis. Sometimes the reason is obvious and everyone agrees. But if any of the following are true, you need one:
Liquidated damages are being assessed or threatened. If the owner is withholding money for late completion, the only way to demonstrate that the delays were not your responsibility is a methodology-compliant forensic analysis. "We were delayed by the owner" is a position statement. A forensic analysis makes it evidence.
You're submitting an Extension of Time (EOT) claim. Most contracts require the contractor to demonstrate the impact of owner-caused delays on the critical path. A schedule narrative without forensic methodology behind it will be rejected by any competent owner's consultant.
You're heading into arbitration or litigation. If the dispute has escalated to a legal proceeding, you need an analysis that can be presented as expert evidence. That means recognized methodology, traceable data, and an analyst who can be deposed and cross-examined on their findings.
A subcontractor is filing a backcharge or delay claim against you. You need your own forensic analysis to evaluate their claim. Taking their word for the delay duration and impact — or counter-arguing without your own analysis — is bringing a narrative to a math fight.
The owner is withholding release of holdback. Some contracts tie holdback release to substantial completion. If there's a dispute about whether delays were excusable, the forensic analysis is what unlocks the holdback.
What a Good Deliverable Looks Like
The forensic schedule consulting industry has the same problem as the DCMA assessment industry: most firms ship static PDF reports. You get a Word document with a narrative, some Gantt chart screenshots pasted in, and a summary table at the end. It took the analyst three weeks to produce, and it takes opposing counsel about four hours to find the holes.
Here's what the deliverable should actually include:
Interactive forensic dashboard. A browser-based HTML report where you can drill into each analysis window, see which activities shifted, trace the critical path movement, and explore the delay attribution at the activity level. This is what you screen-share in a mediation session when opposing counsel challenges a specific window.
Per-window and per-activity CSV exports. The raw data behind every conclusion, in a format that can be independently verified. If your analyst can't hand over the underlying data in a structured format, ask why.
Executive summary report. A DOCX narrative that walks through the findings in plain language — suitable for a project executive, a construction lawyer doing intake, or an arbitrator reading the submission for the first time.
Claims-ready packaging. Cover letter, per-event delay exhibits, supporting documents index, and mitigation documentation. A forensic analysis that produces findings but doesn't package them for submission is only doing half the job.
Audit trail. Every assumption, every data source, every methodology decision — documented and traceable. The opposing analyst is going to ask "how did you calculate the 14-day delay in Window 7?" and the answer needs to be in the deliverable, not in your analyst's head.
The best forensic delay analysis in the world cannot save a claim built on bad schedule data. If the contractor didn't maintain regular schedule updates, didn't log actual start and finish dates, and didn't preserve contemporaneous records of delay events, the analysis has nothing to work with. Schedule hygiene during construction is your insurance policy for the claim you hope you never need to file. If you're reading this before your project is in trouble — start with the health check.
What to Look for in a Forensic Analyst
Not every scheduler is a forensic analyst. Scheduling is a technical skill. Forensic delay analysis is a technical skill plus the ability to produce evidence that survives a legal proceeding. Here's what separates the two:
Deposable opinions. Can your analyst sit for a deposition and defend every number in the report under hostile questioning? If they've never been deposed, ask how they plan to handle it.
Methodology compliance. The analysis should explicitly reference and follow a recognized AACE methodology. "I used my professional judgment" is not a methodology. MIP 3.3, MIP 3.7, MIP 3.8, RP 29R-03, RP 52R-06 — these are methodologies.
Audit trail discipline. Every calculation should be reproducible by an independent analyst working from the same data. If your analyst can't explain exactly how they arrived at "22 days of owner-caused delay in Window 4," the opposing analyst will.
Conservation rule compliance. In any window where both parties caused delays, the total attributed delay must not exceed the actual observed delay. An analysis that assigns 15 days to the owner and 12 days to the contractor in a window where the project only slipped 18 days has a math problem — and opposing counsel will find it.
Cross-examination readiness. The deliverable should be written with the assumption that every sentence will be read aloud in front of an arbitrator and challenged. If the report contains hedging language, unsupported conclusions, or attribution without traceable evidence, it will not survive the hearing.
The Cost of Waiting
Forensic delay analysis is most effective when engaged early — ideally as soon as delay events begin accumulating, not after the project is finished and the claim is overdue. Early engagement means the analyst can advise on contemporaneous record-keeping, flag critical path shifts in real time, and build the evidentiary record as the project progresses.
Waiting until the project is over and the lawyers are involved always costs more. The data is stale, the records are incomplete, and the analyst has to reconstruct months or years of project history from whatever documentation survived. That reconstruction takes longer, costs more, and produces a weaker result than an analysis built on clean contemporaneous data.
Put your schedule through the forensic engine
Drop your baseline + current XER. See critical path movement, delay attribution, and risk scoring in 10 seconds or less. No login, no payment, no file storage.
Try It Live →