Why Variance Reports Don't Explain Construction Delays: Understanding Forensic Delay Analysis for US Contractors

 

Understanding Forensic Delay Analysis: Why Primavera Variance Does Not Tell the Full Delay Story

Introduction

One of the most misunderstood concepts in project scheduling is the difference between schedule variance and delay analysis.

Many planners and project managers assume that if an activity shows a variance in Primavera P6 or Microsoft Project, that variance represents the delay caused to the project.

Unfortunately, that assumption is incorrect.

Variance simply measures the difference between planned dates and actual dates. It does not quantify the impact of a delay on project completion.

To determine the true effect of a delay on a project's finish date, project controls professionals perform Forensic Delay Analysis.

---

What is Schedule Variance?

In Primavera P6 and Microsoft Project:

Schedule Variance = Actual Date – Baseline Date

Examples:

• Planned Start: 01-Jan

• Actual Start: 10-Jan

Variance = 9 Days

Similarly:

• Planned Finish: 30-Jan

• Actual Finish: 10-Feb

Variance = 11 Days

While these variances indicate slippage, they do not tell us:

• Whether the delay affected the critical path

• Whether the delay impacted project completion

• How many days of project delay were caused

• Who is responsible for the delay

This is where Forensic Delay Analysis becomes important.

---

What is Forensic Delay Analysis?

Forensic Delay Analysis is a structured methodology used to determine:

• The existence of delay

• The cause of delay

• The responsibility for delay

• The impact of delay on project completion

It is extensively used in:

• Construction Claims

• Extension of Time (EOT) Requests

• Arbitration

• Litigation

• Delay Recovery Planning

The objective is simple:

Determine how many days a particular event delayed the project.

---

How Does Forensic Delay Analysis Work?

One common technique involves introducing a delay fragment (fragnet) into the approved schedule.

A fragnet is a miniature network of activities representing the delaying event.

The process generally involves:

Step 1 – Insert Delay Fragnet

Examples:

• Design approval delay

• Material delivery delay

• Weather disruption

• Change order delay

Step 2 – Connect Fragnet

The fragnet is logically connected to:

• Activities affected by the delay

• Predecessors causing the delay

• Successors impacted by the delay

Step 3 – Reschedule the Program

The schedule is recalculated.

Step 4 – Measure Project Finish Impact

The difference between:

• Original completion date

• New completion date

represents the actual delay impact.

This delay may be:

• 0 days

• 5 days

• 30 days

• 100 days

depending on the schedule logic.

This is the actual project delay—not the variance.

---

Why Variance Does Not Measure Delay

Consider an activity delayed by 30 days.

Many planners immediately conclude:

"The project is delayed by 30 days."

Not necessarily.

If the activity is:

• Non-critical

• Has available float

• Is not driving project completion

The project delay may be:

0 Days

Conversely, a 5-day delay on a critical path activity may cause:

5 Days project delay

Therefore:

Activity Variance ≠ Project Delay

This distinction is fundamental in project controls.

---

Major Types of Delay Analysis

There are several recognized forensic delay analysis methodologies.

1. Impacted As-Planned Analysis

Most commonly used.

Method:

• Insert delay fragnet into baseline schedule

• Measure completion impact

Advantages:

• Simple

• Easy to explain

Limitations:

• Does not account for actual project progress

---

2. Time Impact Analysis (TIA)

Industry-preferred methodology.

Method:

• Insert delay event into contemporaneous schedule update

• Measure impact prospectively

Used extensively for:

• Change Orders

• Extension of Time Claims

---

3. Collapsed As-Built Analysis (But-For Analysis)

Method:

• Start with actual completed schedule

• Remove delaying events

• Determine hypothetical completion

Question answered:

"When would the project have finished but for this delay?"

---

4. As-Planned vs As-Built Analysis

Method:

• Compare original baseline against actual completion

Simple but often lacks detailed causation analysis.

---

5. Windows Analysis

One of the most reliable methods.

Method:

• Divide project into time periods

• Analyze critical path movement during each period

Provides a realistic view of changing project conditions.

---

6. Contemporaneous Period Analysis

Method:

• Analyze schedule updates period by period

• Determine actual critical path evolution

Frequently used in major disputes.

---

7. Earned Schedule Analysis

Method:

• Uses Earned Value and schedule metrics

• Measures schedule performance trends

Useful for forecasting future delays.

---

Which Delay Analysis Method is Best?

There is no universal answer.

The appropriate methodology depends on:

• Contract requirements

• Schedule quality

• Available updates

• Claim type

• Legal jurisdiction

However, for major construction claims, the most widely accepted methods are:

✔ Time Impact Analysis (TIA)

✔ Windows Analysis

✔ Contemporaneous Period Analysis

---

Conclusion

Many project professionals rely solely on Primavera variance reports to evaluate project delays.

This approach can be misleading.

Variance only indicates date differences.

True delay analysis requires understanding:

• Critical Path

• Float Consumption

• Fragnets

• Time Impact Analysis

• Forensic Schedule Methodologies

A project may show significant activity variances and still finish on time.

Conversely, a small variance on a critical path activity may delay the entire project.

Understanding this distinction is what separates a scheduler from a Project Controls professional.

The next time someone says, "The activity is delayed by 20 days," ask a simple question:

"How many days did it delay the project?"