Forensic schedule analysis becomes critical when a project delay is no longer just a schedule update issue, but a question of proof, responsibility, and entitlement.
If you are a planner, scheduler, or project controls professional, you have probably experienced this before.
You update the schedule. You review the critical path. You compare progress against the previous update. You see the completion date slipping, float disappearing, and certain activities starting to push the project in the wrong direction.
Then the questions begin.
➡️ Why did the project slip?
➡️ Who caused the delay?
➡️ Can we claim an Extension of Time?
➡️ Was this really on the critical path?
➡️ Can the schedule prove it?
And suddenly, the schedule is no longer just a planning tool.
It becomes evidence.
That is where things get serious.
Because in real projects, it is one thing to see that a project is late. It is another thing to prove why it is late, who is responsible, and whether that delay creates entitlement to additional time or cost.
This is where many project teams struggle.
The field team may know what happened. The planner may see the dates moving. The project manager may remember the late approvals, access issues, design changes, and coordination problems.
But when a delay claim is prepared or challenged, memories and assumptions are not enough. You need a clear, evidence-based delay analysis. And depending on where you are in the project, that analysis may be very different.
That is why every scheduler should understand the difference between delay analysis and forensic schedule analysis.
Why Delay Analysis Must Prove More Than a Slipped Activity
On most projects, delays are not hard to notice.
You see activities slipping. You see float being consumed. You see the forecast completion date moving beyond the contractual completion date.
Figure 1. Delay Impact and Time Extension
But noticing delay is only the first step.
The harder question is:
Can you prove what caused the delay?
This is where the conversation often becomes more complex.
💬 A contractor may say: “The owner delayed us by 60 days.”
💬 The owner may respond: “You were already behind before that event happened.”
💬 The scheduler may point to a shift in the longest path.
💬 The project manager may argue that the field impact was obvious.
💬 The claims team may ask whether the schedule updates are reliable.
Each person may be looking at the same project, but from a different angle.
That is why delay analysis is not just about showing that dates moved. It is about connecting the delay event to the schedule impact.
You need to show:
- What happened
- When it happened
- What the schedule looked like before the event
- How the critical path changed
- Whether the event actually delayed completion
Without that connection, even a real delay can become difficult to defend.
So, what is “Delay Analysis” exactly?
What Delay Analysis Means in Project Delay Claims
In schedule delay analysis, the term “delay analysis” can be broad.
It may be used to evaluate delays that may happen in the future, or delays that have already occurred and been absorbed into the project record.
You may use delay analysis to forecast the effect of a change, review an Extension of Time claim, assess contractor or owner responsibility, or understand why the project completion date moved.
But the type of delay analysis you need depends heavily on timing.
Ask yourself:
🔹 Are you trying to forecast the impact of an event before it fully happens?
🔹 Or are you trying to investigate an event after the delay has already been absorbed into the project?
That one question changes the nature of the analysis.
If the delay is still expected to happen, you are mostly working with a forecast. You are trying to estimate how a known or anticipated event may affect the remaining work.
If the delay has already happened, you are no longer only forecasting. You are looking back at the actual project record to determine what really occurred.
That is where forensic schedule analysis becomes important.
What Forensic Schedule Analysis Adds to Delay Claims
Once you move from forecasting a possible delay to investigating an actual delay, the focus of the analysis changes.
You are no longer simply asking: “What might happen?”
You are asking: “What actually happened?”
That is the key difference between a “prospective delay analysis” and a “forensic delay analysis.”
For example, let’s say the owner is supposed to release an area to the contractor on June 1. By mid-May, the project team already knows that access may be delayed. At that point, the contractor may prepare a Time Impact Analysis to show how the anticipated late access may affect the project completion date.
That is a prospective delay analysis.
The project team is trying to understand the likely impact before the full outcome is known.
Now imagine the same project six months later.
The area was released late. The contractor worked around the issue. Some activities were re-sequenced. Some impacts were mitigated. Other delays occurred during the same period. The project is now 45 days behind.
At that point, the question is no longer only what the delay might have done.
The question becomes:
What did the delay actually do to the project?
That is where forensic schedule analysis fits in.
Forensic schedule analysis is used when you need to investigate delay based on actual project data. It is especially important when the delay has already occurred, the project has moved forward, and the parties now need to understand what actually drove the project completion date.
At this stage, you need to ask:
➡️ What actually happened?
➡️ What was driving the project at the time?
➡️ Did the delay affect the critical or longest path?
➡️ Was the project already late?
➡️ Were there other delays happening at the same time?
➡️ Did the contractor mitigate or recover some of the impact?
➡️ Do the records support the claimed delay?
That means the analysis must go beyond a single schedule printout.
You may need to review schedule updates, actual start and finish dates, as-built data, daily reports, correspondence, meeting minutes, change records, logic revisions, schedule narratives, and movement of the critical or longest path over time.
In other words, forensic schedule analysis is not just a scheduling exercise. It is a structured investigation into the project timeline.
And like any investigation, the strength of the conclusion depends on the quality of the evidence.
This is why timing matters so much in delay analysis.
When the impact is still ahead of you, you are dealing with prospective delay analysis — looking forward to forecast what may happen and giving the project team a way to make decisions before the delay is fully absorbed. But once the delay has already moved through the project, it becomes retrospective delay analysis— looking back at the actual records to understand what really happened.
That is where forensic schedule analysis becomes especially valuable. It takes the retrospective review deeper by testing the actual records, evaluating the critical or longest path, identifying what truly drove completion, and determining whether the claimed delay is supported by project evidence.
In simple terms, prospective delay analysis helps you forecast the possible impact. Retrospective delay analysis helps you look back and understand the actual impact. Forensic schedule analysis helps you investigate, prove, and explain that impact in a way that can support or challenge a delay claim.
Figure 2. From Absorbed Delay to Predicted Delay: Prospective vs. Retrospective Analysis
This distinction becomes especially important when a project team relies on a Time Impact Analysis (TIA). A TIA can be very useful when you are still looking forward, but once the delay has already occurred, you have to be careful not to treat a forecast as if it proves what actually happened.
Why a Time Impact Analysis May Not Tell the Full Story
When the project team is evaluating a potential delay before it fully impacts the project, a Time Impact Analysis can help forecast the likely effect on the remaining work.
For example, if a change order is issued and the contractor wants to show how that change may affect the remaining work, a Time Impact Analysis can help forecast the potential impact on completion.
But once the delay has already happened, relying only on a modeled prediction may not be enough.
Why?
Because the project may not have unfolded exactly as the model predicted.
- The contractor may have re-sequenced work.
- The project may have experienced other delays.
- The critical path may have shifted.
- Some delay may have been mitigated.
- Some impact may have been absorbed.
- The project may already have been late before the event occurred.
That is why, after the fact, you need to compare the model with actual project reality.
A forecast can help predict impact.
A forensic review helps determine what impact actually occurred.
Both can be useful, but they are not the same.
That difference matters because, in a delay claim, the real issue is not only whether a delay event occurred or whether a model shows potential impact. The real issue is whether the event actually changed the project outcome.
That is where the analysis has to move from prediction to proof and from impact modeling to causation.
The Real Question: Did the Event Actually Delay the Project?
This is where the analysis becomes more disciplined.
To support a delay claim, you need to show that the event did more than create a problem on the project. You need to show that it actually caused a delay to the project completion date or an applicable contractual milestone.
It is not enough to say:
❌ “The owner was late.”
❌ “The contractor could not work.”
❌ “This activity slipped by 30 days.”
You need to connect the event to the schedule impact.
You need to show what changed, when it changed, who was responsible, and whether that change affected the path controlling completion.
That connection is called causation.
And causation is often where delay claims become weak.
The project team may remember the frustration. They may remember the late drawings, the unanswered RFIs, the access constraints, the rework, the meetings, and the pressure from leadership.
But in a claim situation, memory is not enough.
You need:
✅ Records
✅ Schedules
✅ Actual dates
✅ A clear cause-and-effect link
Imagine a contractor claims 60 days of delay because late design information delayed mechanical rough-in.
At first, that sounds like a strong claim. The design information was late. The contractor could not proceed as planned. The team lost time.
But when you review the schedule update before the design issue, you find that the project was already forecasting a 35-day late finish because structural work was behind.
Then, during the design delay period, the contractor re-sequenced some mechanical work, recovered part of the impact, and continued progressing in other areas.
Now the question is not simply: “Was the design information late?”
It was.
The real question is: “How much of the final project delay was actually caused by the late design information?”
That is the difference forensic schedule analysis can make.
It helps you separate what felt like delay from what can actually be proven as delay.
The late design information may still be relevant. It may still have caused impact. It may still support some entitlement. But the analysis must determine how much delay was truly caused by that event after considering the project status, critical path, other delays, mitigation, and actual progress.
That is where forensic schedule analysis becomes essential.
This is also why forensic delay analysis should not be treated as something you only think about after a dispute begins.
Why Forensic Delay Analysis Matters Before a Project Dispute
Many professionals think forensic schedule analysis only matters when a project is already in dispute.
By the time a formal claim is prepared, the quality of the analysis often depends on what was captured months earlier — in the schedule updates, actual dates, logic changes, narratives, correspondence, and project records.
That is why the foundation for a strong delay analysis is built during the project, not after the dispute begins.
✔️Every schedule update matters.
✔️Every actual date matters.
✔️Every logic change matters.
✔️Every schedule narrative matters.
✔️Every documented delay event matters.
✔️Every critical path review matters.
The way you maintain and explain the schedule today can determine whether a delay can be proven later.
If the updates are inconsistent, actual dates are unreliable, logic changes are unexplained, and delay events are not properly documented, the claim becomes much harder to defend.
But when the project record is clear, the analysis becomes stronger.
You are no longer relying on opinions or memories.
You are relying on evidence.
How Schedulers Can Move From Delay Tracking to Delay Proof
The next time someone says, “We were delayed by 60 days,” do not stop there.
Ask better questions:
- What was the project status before the delay event?
- What was the critical or longest path at that time?
- Was the project already forecasting late completion?
- Did the event actually move the completion date?
- Were there other delays happening at the same time?
- Was any part of the delay mitigated or recovered?
- Do the schedule updates support the claimed impact?
- Can the analysis be defended if challenged?
These questions move you from delay tracking to forensic schedule analysis.
And that shift matters.
Because project controls is not just about reporting what happened.
At its best, project controls helps the project team understand what happened, why it happened, and what the consequences are.
Final Thought: Build the Evidence Before You Need the Claim
You may never be able to eliminate delays from your projects. Delays are part of the reality of construction, capital projects, and complex project delivery.
But you can change how prepared you are when delays happen.
You can move from reacting emotionally to analyzing objectively.
You can move from saying: “We know this delayed us.”
To showing: “Here is what the records prove.”
That is the real value of forensic schedule analysis.
It helps you understand not only that time was lost, but why it was lost, how it affected the project, and whether it created entitlement.
And for planners, schedulers, and project controls professionals, this skill can completely change the way you look at schedules.
Because today, your role is not only to update dates, run the schedule, and report variances. You are often the person expected to explain what changed, why the completion date moved, whether the critical path was affected, and whether the project records support the story being told.
That requires more than basic scheduling knowledge.
It requires an understanding of how delay analysis works, how different forensic delay analysis methodologies are applied, how schedule updates are evaluated, how causation is established, and how delay impacts are proven or challenged.
Your schedule is not just a reporting tool. It is the project’s time story.
And when a delay claim arises, that story needs to be clear, credible, and defensible.
That is why every project planner/ scheduler should understand forensic schedule delay analysis before the project reaches a dispute.
The earlier you understand what makes a schedule reliable, what records matter, how delay methodologies differ, and how critical path impact is proven, the better prepared you are to support the project team when delays occur.
If you want to build that capability, Project Control Academy’s Forensic Schedule Delay Analysis training walks you through how to analyze, prove, and defend delay impacts using practical forensic delay analysis methodologies, real project examples, and industry-recognized approaches used in schedule delay analysis and project delay claims.
Because the strongest delay claims are not built after the fact.
They are built through the schedules, records, updates, and decisions you protect along the way.
What are your thoughts?
Have you experienced situations where delays were easy to see during the project, but much harder to explain, analyze, or prove later?
👇 Share your experience in the comments below. I’d love to hear how you approach delay analysis and schedule documentation on your projects.
References:
This blog post was developed using Project Control Academy’s educational resources and subject matter expertise in forensic schedule delay analysis, including:
[1] Forensic Schedule Delay Analysis Training — Project Control Academy: https://projectcontroltraining.com/forensic-schedule-delay-analysis-training
[2] Forensic Schedule Delay Analysis Training FAQ Resource — Project Control Academy
Internal students Q&A-based resource covering common questions on delay analysis, Time Impact Analysis, schedule updates, forensic review, critical path impact, and delay claim defensibility.
[3] Interview series with Chris Carson — Project Control Academy
[4] How to Choose the Best Forensic Schedule Delay Analysis Methodology — Project Control Academy: https://www.projectcontrolacademy.com/forensic-schedule-delay-analysis-methodology
[5] Project Control Academy Educational Materials and Course Discussions
Additional insights drawn from PCA’s training materials, learner questions, and practical examples related to schedule delay analysis, EOT claims, and forensic review.
About the Author, Shohreh Ghorbani:
Shohreh Ghorbani is the Founder and Technical Director of Project Control Academy and a passionate advocate for making project controls education practical, accessible, and career-changing.
With more than two decades of experience in project controls on major capital projects, Shohreh brings a blend of real-world expertise, teaching clarity, and industry vision to everything she creates.
After entering project controls without a clear training path, she built the platform she wished had existed — one that helps professionals not only learn the concepts, but also apply them with confidence on real projects.
Today, through Project Control Academy’s global training programs, expert-led webinars, interviews, educational resources, and the annual conference, Project Control Summit, Shohreh continues to help project professionals strengthen their project controls skills, expand their impact, and lead the future of project controls.
Meet Shohreh at Project Control Academy or connect with her on LinkedIn.
![[Free 90-min Masterclass] How to Avoid Project Delays Turning into Costly Claims](https://www.projectcontrolacademy.com/wp-content/uploads/2025/08/September-2025-Webcast-Chris-Carson-H01-Yellow-2048x1152.jpg.webp)
![[Free 90-min Masterclass] The Ultimate Leadership Recipe for Project Professionals](https://www.projectcontrolacademy.com/wp-content/uploads/2024/08/4-2048x1152.jpg.webp)
