Comprehensive Guide

The Complete Guide to Forensic Schedule Analysis

Forensic schedule analysis is the after-the-fact examination of construction project schedules to determine the causes, timing, and impact of delays. This guide covers every major method, from Time Impact Analysis to Collapsed As-Built, with practical guidance on choosing the right approach for your dispute.

By Constroma Team·25 min read·Last updated May 2026

1. What Is Forensic Schedule Analysis?

Forensic schedule analysis is the systematic, retrospective examination of construction project scheduling data to determine the causes, timing, and responsibility for delays to project completion. The word “forensic” refers to the fact that this analysis is performed after the fact, typically in the context of a construction dispute, claim, or litigation.

At its core, forensic schedule analysis answers three fundamental questions: (1) What events caused delays to the project? (2) How much time did each delay event add to the project duration? (3) Who is responsible for each delay?

The analyst examines historical scheduling data — including the original baseline schedule, periodic schedule updates, as-built records, and contemporaneous project documentation — to reconstruct the project timeline and trace the causes and effects of delays. The results inform extension of time (EOT) claims, liquidated damages assessments, and dispute resolution proceedings.

2. When Is Forensic Schedule Analysis Needed?

Forensic schedule analysis is required whenever there is a dispute about construction project delays. Common scenarios include:

Extension of time claims: When a contractor submits a claim for additional time due to delays that were not their fault, forensic analysis provides the evidence that the claimed delays actually impacted the critical path and the project completion date.

Liquidated damages disputes:When an employer seeks to apply liquidated damages for late completion, forensic analysis determines whether the delays were the contractor’s responsibility or whether concurrent employer-caused delays reduced the contractor’s liability.

Arbitration and litigation: In formal dispute resolution, forensic schedule analysis provides expert evidence. Courts and arbitration tribunals expect methodology-based analysis prepared by qualified professionals.

Mediation and negotiation: Even before formal proceedings, forensic analysis provides an objective basis for settlement discussions by quantifying the delay attributable to each party.

3. Industry Standards

Two primary industry standards guide forensic schedule analysis practice:

AACE International Recommended Practice 29R-03:“Forensic Schedule Analysis” classifies delay analysis methods into categories: observational (comparing as-planned and as-built data without modeling), modelled (inserting delays into schedules and recalculating), and additive vs. subtractive approaches. AACE RP 29R-03 is the most widely referenced standard in North America and internationally.

Society of Construction Law (SCL) Delay and Disruption Protocol: The SCL Protocol provides guidance on how delay analysis should be performed and how results should be interpreted in the context of construction contracts. It addresses topics such as concurrent delay, float ownership, and the appropriate level of analysis required for different dispute values.

4. Delay Analysis Methods Overview

AACE RP 29R-03 describes multiple methodologies, each with different data requirements, levels of rigor, and applicability. The main methods are:

MethodApproachRigorData Needed
As-Planned vs As-BuiltObservationalLowBaseline + as-built
Impacted As-PlannedAdditive / ModelledMediumBaseline + delay data
Collapsed As-BuiltSubtractive / ModelledMedium-HighAs-built + delay data
Time Impact AnalysisAdditive / ModelledHighUpdates + delay fragnets
Windows Analysis (MIP 3.7)Modelled in WindowsHighestUpdates + delay fragnets

5. Time Impact Analysis (TIA) In Depth

Time Impact Analysis is the most widely accepted modelled approach for forensic schedule analysis. It evaluates the impact of each delay event by inserting a fragnet into the CPM schedule at the time the delay occurred, then recalculating the schedule to measure the change in the completion date.

Step 1 — Establish the pre-delay schedule: Begin with the baseline schedule or the most recent schedule update before the delay event occurred. This represents the project plan at the time the delay event was known.

Step 2 — Create the delay fragnet: Build a fragment network of activities that models the delay event. The fragnet includes the delay activities with appropriate durations and logical relationships to existing schedule activities.

Step 3 — Insert and recalculate: Insert the fragnet into the schedule with logical ties to the affected activities. Run CPM forward and backward pass calculations to determine the new critical path and completion date.

Step 4 — Measure the impact: The difference between the completion date before and after fragnet insertion is the delay impact of that event. If the completion date did not change, the delay event did not impact the critical path.

Step 5 — Repeat for each delay event: Process all delay events chronologically, building up the cumulative delay picture.

6. Windows Analysis (MIP 3.7)

The Modelled-in-Windows approach (MIP 3.7 in AACE terminology) is considered the most rigorous forensic schedule analysis methodology. It combines Time Impact Analysis with a windowed approach, analyzing delays within defined time periods that correspond to schedule update cycles.

Each analysis window typically spans one schedule update period. Within each window, the analyst identifies the delay events that occurred, creates fragnets for each, and inserts them chronologically into the schedule that was current at the start of the window. After processing all events in a window, the analyst compares the resulting schedule against the actual update at the end of the window.

This approach captures critical path shifts that occur during the project, identifies concurrent delays, and accounts for the actual state of the schedule at the time each delay occurred — advantages that simpler methods cannot provide.

7. Collapsed As-Built Analysis

The Collapsed As-Built method takes the opposite approach from TIA. Instead of adding delays to a planned schedule, it starts with the actual (as-built) completion and removes delay events to determine what the completion date would have been without those delays.

This “but-for” analysis is useful when detailed contemporaneous schedule updates are not available, because it works primarily from as-built data. However, it can produce misleading results when there are complex interactions between delays, as removing events in a network schedule can produce different results depending on the order of removal.

8. How to Choose the Right Method

The choice of method depends on several factors: the available data, the contract requirements, the complexity and value of the dispute, and the jurisdiction’s expectations. As a general guideline:

Use MIP 3.7 (Windows TIA) for high-value disputes where detailed schedule updates are available and the analysis must withstand scrutiny in arbitration or litigation.

Use Time Impact Analysis when schedule updates are available but a windowed approach is impractical or unnecessary for the dispute value.

Use Collapsed As-Built when detailed schedule updates are limited but as-built records are available.

Use As-Planned vs As-Built for preliminary assessments, low-value disputes, or when very limited data is available.

9. Data Requirements

The quality of a forensic schedule analysis depends directly on the quality of the input data. Essential documents include: the original baseline schedule (ideally as a P6 XER file), all periodic schedule updates, contemporaneous project records (daily reports, correspondence, meeting minutes, photos), delay event documentation, weather records, and the contract documents including programme and notice requirements.

10. Tools & Software

Forensic schedule analysis has traditionally been performed manually using Oracle Primavera P6 and Microsoft Excel. Analysts would import schedules into P6, manually create fragnets, run CPM, and document results in spreadsheets — a time-consuming process.

Constromaautomates much of this process. The platform imports P6 XER schedules, provides a fragnet builder for delay events, runs automated CPM calculations within analysis windows (MIP 3.7), and produces structured analysis results — reducing weeks of manual work to hours.

11. Conclusion

Forensic schedule analysis is a critical discipline in construction dispute resolution. The choice of methodology, quality of data, and rigor of analysis directly affect the defensibility and credibility of delay claims. By understanding the strengths and limitations of each method, and by leveraging modern tools that automate the computational work, construction professionals can produce more accurate, efficient, and defensible analyses.

Automate Your Forensic Schedule Analysis

Upload your P6 XER files, build fragnets, and run TIA automatically with Constroma.

Start Free Trial

Frequently Asked Questions

What qualifications do I need to perform forensic schedule analysis?
Forensic schedule analysis is typically performed by experienced scheduling professionals, claims consultants, or expert witnesses with deep knowledge of CPM scheduling, construction contracts, and delay analysis methodologies. Relevant certifications include AACE PSP (Planning and Scheduling Professional), AACE CCP (Certified Cost Professional), and PMI PMP (Project Management Professional). Experience with P6 scheduling software and familiarity with AACE RP 29R-03 are considered essential.
Which delay analysis method should I use?
The choice of method depends on the available data, contract requirements, and dispute complexity. Time Impact Analysis (TIA) within analysis windows (MIP 3.7) is generally considered the most rigorous and defensible method. Collapsed As-Built is useful when detailed contemporaneous schedule data is limited. As-Planned vs As-Built is the simplest method but may not adequately address concurrent delays. The SCL Protocol and AACE RP 29R-03 provide guidance on method selection.
What data do I need for forensic schedule analysis?
At minimum, you need the baseline schedule and as-built records. Ideally, you should have: the original baseline schedule (P6 XER or equivalent), all periodic schedule updates, contemporaneous project records (daily reports, correspondence, meeting minutes), delay event documentation, weather records, and contract documents including the original contract programme requirements.
How long does a forensic schedule analysis take?
Manual forensic schedule analysis can take weeks to months depending on project size and complexity. A Time Impact Analysis on a large project with dozens of delay events might require 200-400 hours of professional time. Constroma automates much of this process, reducing analysis time to hours for the computational work, though expert judgment is still needed for delay event identification and report interpretation.
What is the difference between prospective and retrospective analysis?
Prospective analysis is performed at the time of the delay event, looking forward to predict the impact on the completion date. Retrospective analysis is performed after the fact, using actual schedule data to determine what happened. Retrospective analysis is more common in dispute resolution because it uses real data rather than projections. MIP 3.7 (Modelled in Windows, retrospective) is considered the most rigorous approach.
Can forensic schedule analysis determine concurrent delay?
Yes. Methods like Time Impact Analysis within windows can identify concurrent delays — situations where multiple delay events affect the critical path during the same time period. Identifying concurrent delay is important because many contracts provide that concurrent delay events may reduce or eliminate the contractor's entitlement to time or cost.

Related Guides