Construction Delay Analysis Methods: Types, Techniques & Documentation | Projul

Every contractor has been there. You bid the job, set the schedule, and then reality shows up with a different plan. Maybe the owner takes three weeks to approve a submittal. Maybe the city holds up a permit. Maybe rain washes out two weeks of site work and a subcontractor no-shows on the same Monday.

When delays stack up and the project end date starts sliding, you need more than a gut feeling to protect your business. You need a structured way to prove what happened, why it happened, and who is responsible. That is what delay analysis is all about.

This guide walks through the types of construction delays, the most common analysis methods used to assign responsibility, and the documentation practices that will make or break your claim if things end up in a dispute.

Understanding the Three Types of Construction Delays

Before you can analyze a delay, you need to classify it. Not all delays are created equal, and the category a delay falls into determines what relief you are entitled to. There are three primary types.

Excusable delays are caused by events outside the control of both the contractor and the owner. Think severe weather that goes beyond what is normal for the area and time of year, natural disasters, labor strikes that affect an entire region, or government actions like unexpected moratoriums. When a delay is excusable, the contractor is typically entitled to a time extension but not additional compensation. You get more time to finish, but you eat the added general conditions costs yourself.

If you have dealt with weather-related disruptions, you know how tricky these can be to prove. Our guide to construction weather delay claims goes deeper into how to handle those situations.

Compensable delays are caused by the owner or the owner’s agents, and they entitle the contractor to both extra time and extra money. Common examples include late delivery of owner-furnished materials, design changes after work has started, differing site conditions the owner should have disclosed, and slow responses to RFIs or submittals. If the owner caused the holdup, you should not be the one paying for it.

Non-excusable delays fall squarely on the contractor. Maybe you underestimated how long the foundation would take. Maybe your supplier dropped the ball and you did not have a backup plan. These delays do not earn you any time extension, and they can expose you to liquidated damages or worse.

Understanding these categories is the first step in any delay analysis. If you cannot classify the delay, you cannot build a credible argument for relief.

How Concurrent Delays Complicate Everything

In a perfect world, delays would happen one at a time with a clear responsible party. In the real world, they overlap. Concurrent delay is one of the most contested issues in construction disputes, and it trips up experienced contractors all the time.

Concurrent delay happens when two or more independent delay events occur during the same window, each one affecting the critical path or an important near-critical path. The classic example: the owner is late approving shop drawings (compensable delay) while your electrical subcontractor is behind schedule on rough-in (non-excusable delay). Both are pushing the completion date, and both are happening at the same time.

Why does this matter so much? Because many jurisdictions and contract provisions say that when delays are truly concurrent, neither party can recover damages from the other. Some contracts go even further and deny time extensions in concurrent delay situations. The practical effect is that concurrent delay can wipe out what would otherwise be a strong claim.

There are a few things you can do to protect yourself:

• Separate the timelines. If you can show that the owner’s delay started first and was already pushing the critical path before your issue arose, the delays may not actually be concurrent. Timing and sequencing matter enormously.
• Track the critical path religiously. Concurrent delay analysis hinges on whether both events independently affected the project completion date. If your delay only affected a float-heavy activity while the owner’s delay hit the critical path, that is not true concurrency.
• Update your schedule regularly. Monthly schedule updates with clear narrative reports give you the granular data needed to untangle overlapping delays after the fact.

Good construction scheduling practices are your first line of defense against concurrent delay arguments gutting your claim.

The Four Main Delay Analysis Methods

Now for the technical core. There are four widely recognized delay analysis methods, and each one has strengths, weaknesses, and situations where it fits best. Picking the right method depends on the complexity of the dispute, the quality of your schedule data, and sometimes what the contract requires.

As-Planned vs As-Built

Curious what other contractors think? Check out Projul reviews from real users.

This is the simplest and most commonly used method. You take the original baseline schedule (as-planned) and compare it side by side with what actually happened on the project (as-built). The gaps between the two tell the story of where time was lost.

How it works: You lay out the planned start and finish dates for each activity next to the actual start and finish dates. Where activities slipped, you identify the cause and assign responsibility using project records, daily logs, and correspondence.

Strengths: It is easy to understand, relatively inexpensive to prepare, and works well for smaller projects or disputes where the delay causes are fairly obvious. Owners, mediators, and judges can follow the logic without needing a scheduling expert to translate.

Weaknesses: It does not account for the critical path in a rigorous way. It also ignores the dynamic nature of the schedule, meaning it does not reflect how delays early in the project may have shifted the critical path for later activities. And it assumes the baseline schedule was reasonable and achievable in the first place, which is not always the case.

Best for: Straightforward disputes on smaller projects, initial assessments to identify potential claims, and situations where detailed schedule data is limited.

Impacted As-Planned

This method starts with the baseline schedule and then inserts the delay events into it to show their projected impact on the completion date. You are essentially asking: “If we take the original plan and add these specific disruptions, what would the new completion date be?”

How it works: You take the approved baseline CPM schedule and add activity fragments or constraints representing each delay event. Then you recalculate the schedule to see how the end date shifts. Each delay event is added one at a time or in chronological groups so you can see the individual and cumulative impact.

Strengths: It is prospective, meaning it looks forward from the baseline, which makes it intuitive. It clearly ties specific delay events to specific schedule impacts. And it is relatively straightforward if you have a good CPM baseline to work from.

Weaknesses: It relies heavily on the baseline schedule being accurate and reasonable. If the baseline was overly optimistic or did not reflect how the work was actually going to be performed, the analysis inherits those problems. It also does not account for contractor acceleration, re-sequencing, or other mitigation efforts that happened during the project.

Best for: Owner-caused delays where you have a solid baseline schedule, early-stage analysis to quantify potential claims, and contract provisions that specifically reference impact to the as-planned schedule.

Collapsed As-Built (But-For Analysis)

This method works backward from what actually happened. You start with the as-built schedule and then remove the delay events one at a time to determine what the completion date would have been “but for” those delays. It is sometimes called the “but-for” method for that reason.

How it works: You build or reconstruct the as-built CPM schedule showing actual dates for all activities. Then you systematically remove delay events attributable to the other party and recalculate. The difference between the as-built completion date and the collapsed completion date represents the delay caused by that party.

Strengths: It is grounded in reality because it starts with what actually happened rather than what was supposed to happen. It accounts for the actual critical path as the project unfolded, including any re-sequencing or acceleration that occurred. Courts and arbitrators tend to view it as credible because it is based on facts rather than projections.

Weaknesses: It is expensive and time-consuming. Building a reliable as-built CPM schedule from project records takes significant effort. It also requires judgment calls about which activities were on the critical path, and those judgment calls can be challenged. It can be difficult to cleanly extract a single delay event from a complex web of overlapping activities.

Best for: Complex disputes heading toward litigation or arbitration, projects where the baseline schedule was unreliable or significantly changed, and situations where you need the strongest possible evidentiary foundation.

Time Impact Analysis

This is the most rigorous and most expensive method. It evaluates each delay event at the point in time it occurred, using schedule updates contemporaneous to that period. You are essentially re-living the project month by month and measuring the impact of each delay as it happened.

How it works: You take the schedule update in effect just before a delay event occurred. You insert the delay event into that schedule and recalculate to measure the impact on the completion date. Then you move to the next delay event and repeat using the next relevant schedule update. Each delay is measured against the schedule conditions that existed when it actually happened.

Strengths: It is the most accurate method because it considers the state of the project at the time each delay occurred. It properly accounts for changes in the critical path over the life of the project. It handles concurrent delays well because you can see exactly what was critical at each point in time.

Weaknesses: It is by far the most expensive and labor-intensive method. It requires detailed, contemporaneous schedule updates throughout the project. If monthly updates were not maintained or were unreliable, the analysis falls apart. It also requires significant expertise to perform and to present convincingly.

Best for: High-value disputes, projects with detailed monthly schedule updates, and situations involving multiple overlapping delay events from both parties.

Choosing the Right Method for Your Project

Selecting a delay analysis method is not just a technical decision. It is a strategic one. Several factors should guide your choice.

Contract requirements come first. Some contracts specify which delay analysis method must be used or which schedule serves as the baseline for delay claims. Read your contract before you pick a method. If it says “time impact analysis,” that is what you are doing whether you like it or not.

Quality of schedule data matters. If you maintained monthly CPM schedule updates with narratives throughout the project, you have the raw material for a time impact analysis. If you only have the baseline and the final as-built dates, you are probably limited to as-planned vs as-built or impacted as-planned. The construction scheduling methods guide covers how to build and maintain schedules that support claims down the road.

Dispute value drives investment. A $50,000 delay claim does not justify a $40,000 time impact analysis. Match the rigor and expense of the method to the stakes involved. For smaller claims, as-planned vs as-built may be perfectly adequate. For seven-figure disputes, you want the most defensible method you can support with your records.

Consider the audience. If you are presenting to a mediator who is not a scheduling expert, a simpler method with clear visuals may be more persuasive than a technically perfect but hard-to-follow time impact analysis. If you are in front of an arbitration panel with construction experience, they will expect rigor.

Think about your weaknesses. Every method has assumptions that can be attacked. If your baseline schedule was aggressive, methods that rely on it (as-planned vs as-built, impacted as-planned) are vulnerable. If your as-built records are incomplete, collapsed as-built will be difficult. Choose the method that plays to your documentation strengths.

Building Bulletproof Delay Documentation

The best delay analysis in the world is worthless without the records to back it up. Documentation is where claims are won or lost, and the time to build your file is while the project is happening, not after the dispute starts.

Daily logs are your foundation. Every day on the job site should produce a log entry that captures weather conditions, crew counts by trade, equipment on site, work performed, and any unusual events or delays. These logs are the raw evidence that feeds every delay analysis method. If your crew lead writes “rained all day, no work” on a napkin and throws it in the truck, that is not going to hold up. Use a consistent format and make it a non-negotiable daily habit.

Good construction project documentation practices pay for themselves many times over when a claim arises.

Photos and videos with timestamps. A photo of a flooded site with a date stamp is worth more than a paragraph in a delay letter. Document conditions before, during, and after delay events. Capture the lack of progress when owner-caused delays are preventing work. Our construction photo documentation guide covers best practices for making your photos count as evidence.

Written notice is not optional. Most contracts require written notice of delays within a specific number of days. Miss that window and you may waive your right to claim entirely, regardless of how clear the delay is. Send notice letters promptly, describe the delay event, reference the contract provision you are claiming under, and state the anticipated impact. Keep copies of everything you send and document when and how it was delivered.

Schedule updates tell the story over time. Monthly schedule updates with narrative reports create a contemporaneous record of how the project evolved. They show when the critical path shifted, when delays started affecting downstream work, and what mitigation efforts you made. Without regular updates, you are trying to reconstruct history from fragments rather than pointing to a clear, timestamped record.

Track your costs. Delay claims require proof of damages, and that means showing the actual costs you incurred because of the delay. Keep detailed records of extended general conditions, idle equipment charges, labor inefficiency, subcontractor delay claims passed up to you, and any acceleration costs if you tried to make up lost time. A solid job costing system makes this much easier than digging through shoe boxes of receipts.

Change order logs matter. Document every change order, pending change order, and rejected change order request. Change order management ties directly into delay claims because design changes are one of the most common sources of compensable delay. If you can show a pattern of late owner decisions or excessive changes, it strengthens your overall narrative.

Putting It All Together: From Analysis to Resolution

Delay analysis is not just an academic exercise. It is a tool for getting paid what you are owed or, at minimum, for protecting yourself from unfair liquidated damages. Here is how the pieces fit together in practice.

Start with prevention. The best delay claim is the one you never have to file. Proactive scheduling, regular communication with the owner and design team, and early identification of potential problems can prevent many delays from happening in the first place. When you see a delay forming, raise it immediately rather than waiting to see if it resolves itself.

Classify early. As soon as a delay event occurs, classify it. Is it excusable? Compensable? Non-excusable? This initial classification guides your notice obligations, your documentation focus, and your negotiation strategy. Do not wait until the end of the project to figure out who caused what.

Analyze periodically, not just at the end. Running delay analysis during the project, even informally, helps you understand your schedule position and strengthens your position at the table. If you can walk into a progress meeting and show the owner exactly how their slow submittal reviews have pushed your critical path by three weeks, you are more likely to get cooperation than if you drop a 200-page claim at closeout.

Get expert help when the stakes are high. For major disputes, hire a scheduling consultant or forensic delay analyst. They bring objectivity, technical credibility, and experience presenting delay claims to arbitrators and courts. The cost of an expert is a fraction of what you stand to recover or lose.

Negotiate before you litigate. Most delay disputes settle before they ever reach a hearing. A well-documented claim with a clear analysis gives you a strong position at the negotiation table. Present your analysis professionally, be prepared to discuss the methodology and assumptions, and be open to reasonable compromise. Litigation is expensive for everyone and should be the last resort, not the first move.

Ready to see how Projul can work for your crew? Schedule a free demo and we will walk you through it.

Construction delays are inevitable. How you document, analyze, and present them is what separates contractors who absorb losses from contractors who recover what they are owed. Build the habits now, keep the records clean, and when delays do hit your project, you will be ready to prove your case.