Forensic Delay Analysis: Comparing a Baseline vs Update Schedule

What Is Forensic Schedule Analysis?

Forensic schedule analysis is the process of examining project schedules after the fact to determine the causes and extent of delays. It is commonly used in construction claims and disputes to establish entitlement to time extensions or to apportion liability. The core of any forensic analysis is a rigorous comparison between the baseline schedule (the approved plan) and one or more update schedules (progressed versions). This article focuses on the practical steps to compare these schedules and identify critical changes.

Baseline vs Update: What to Compare

A meaningful forensic comparison goes beyond looking at finish dates. You must examine multiple dimensions of the schedule to build a defensible narrative. Here are the key elements to compare:

1. Milestone Dates and Completion

Start with the contractual milestones. Compare the baseline completion dates against each update. Record the variance (delay or gain) for each milestone. This gives you the high-level impact. But milestones alone do not explain why delays occurred.

2. Critical Path Changes

The critical path defines the longest sequence of activities driving the project finish date. In forensic analysis, you need to identify how the critical path shifted between updates. A change in the critical path can indicate that work sequences were altered, or that delays on non-critical activities became critical. Use a tool that can overlay the critical path from two schedules side by side.

3. Logic Changes

One of the most common sources of delay is changes in activity logic. Compare predecessor/successor relationships between the baseline and update. Look for:

• Added or removed logic ties
• Changed relationship types (FS, SS, FF, SF)
• Added or removed lags
• Open ends (missing predecessors or successors)

Logic changes can compress or extend the schedule. They are often contested in disputes because they can be used to manipulate float or excuse delays.

4. Duration Changes

Compare original durations (from the baseline) with remaining durations in the update. Significant increases in remaining duration may indicate productivity loss or rework. Decreases may indicate acceleration or scope reduction. Be careful: a duration change alone is not proof of delay; it must be linked to the critical path.

5. Activity Status and Progress

Review the status of activities: not started, in progress, or completed. Look for activities that started late or finished later than planned. Also note activities that were completed earlier—these may have created float that was consumed elsewhere.

Identifying Slippage and Gained Time

Once you have the comparison data, quantify the net effect. The most straightforward method is to calculate the difference in the project completion date between baseline and update. But a more nuanced approach is to perform a windows analysis: break the project into time periods and analyze delays in each window. This helps isolate when specific delays occurred and who was responsible.

For each window, compare the planned progress (baseline) with actual progress (update). Identify the activities that drove the delay. Common techniques include:

• As-Planned vs As-Built (simplest, but less rigorous)
• Impacted As-Planned (adds delay events to baseline)
• Collapsed As-Built (removes delays from as-built)
• Time Impact Analysis (prospective or retrospective)

Each method has its strengths and weaknesses. The choice depends on the contract requirements and the available data.

How to Produce a Defensible Comparison Quickly

In a forensic context, speed and accuracy are both critical. Manual comparison of two large schedules is error-prone and time-consuming. Here are practical tips:

• Use a dedicated schedule comparison tool. For example, you can run these checks free in the browser with Project Assure, which parses your XER files locally and highlights differences in dates, durations, logic, and critical path.
• Focus on the critical path first. Non-critical delays may be irrelevant if they have no impact on the completion date.
• Document every change. Create a log of all logic and duration changes with timestamps. This log becomes the backbone of your expert report.
• Check for data integrity. Ensure both schedules use the same calendar, workday definitions, and activity coding. Inconsistent calendars can create false delays.
• Validate with contemporaneous evidence. Schedule data alone is not enough. Correlate schedule changes with emails, meeting minutes, and daily reports.

Common Pitfalls in Forensic Schedule Comparison

Even experienced schedulers can make mistakes. Watch out for:

• Ignoring float consumption. If a non-critical activity uses up all its float, it becomes critical. This is often overlooked.
• Assuming all delays are excusable. Some delays may be due to contractor inefficiency rather than owner-caused events.
• Overlooking concurrent delays. When both parties cause delay simultaneously, apportionment becomes complex. Use a concurrency analysis to separate them.
• Failing to account for pacing. Sometimes a contractor intentionally slows down work to match an owner delay. This is not a compensable delay.

Conclusion

Forensic delay analysis requires a methodical comparison of baseline and update schedules. By examining milestones, critical path, logic, durations, and status, you can build a clear picture of what changed and why. Using automated tools speeds up the process and reduces errors. A defensible analysis is one that is transparent, well-documented, and supported by contemporaneous evidence. Whether you are preparing a claim or defending against one, mastering the baseline-vs-update comparison is essential.