Construction Delay Claims: How to Document and Recover Lost Time | Projul

If you have been in construction long enough, you have lived through a delay that cost you real money. Maybe the owner took six weeks to approve a finish selection. Maybe the city sat on a permit while your crew had nothing to do. Maybe rain wiped out two weeks of earthwork and suddenly your entire schedule was sideways.

Delays happen on every project. That is just the reality of building things outside with dozens of moving parts. But here is the part that separates contractors who eat those costs from contractors who recover them: documentation. The ones who get paid for delays are not louder or more aggressive. They just have better records.

This guide breaks down how construction delay claims actually work, what documentation you need to build a strong claim, and how to recover lost time and money without turning every project into a legal fight.

What Is a Construction Delay Claim and When Does It Apply

A construction delay claim is a formal request for additional time, additional compensation, or both, submitted when something outside your control pushes the project past its scheduled completion date. It is not a complaint. It is not an email saying “we are running behind.” It is a documented, evidence-backed position that ties a specific cause to a specific impact on the project schedule.

Delay claims apply when the delay was not your fault and the contract entitles you to relief. That second part matters. Your contract is the rulebook. It defines what counts as an excusable delay, what notice you have to provide, and what you can recover.

There are three categories that matter in practice.

Excusable, compensable delays. These are caused by the owner or their agents. Think late design decisions, slow responses to submittals, failure to provide site access, or owner-directed changes that disrupt the sequence of work. For these delays, you can typically recover both a time extension and additional costs.

Excusable, non-compensable delays. These are caused by events outside anyone’s control. Weather, natural disasters, pandemics, labor strikes. Your contract probably has a force majeure clause covering these. You get more time on the calendar, but you generally cannot bill for the added cost.

Non-excusable delays. These are on you. Understaffing, poor coordination, late material orders that you should have placed earlier. No time extension. No additional money. Just a lesson learned.

The first step in any delay claim is figuring out which category your delay falls into. If you are not sure, look at your contract language and talk to someone who has been through the process before.

The Six Documents That Make or Break Your Delay Claim

You can have the most legitimate delay claim in the world, and it will not matter if you cannot prove it. Documentation is not just helpful for delay claims. It is everything. The contractor with the best records wins. The contractor with nothing written down loses, even when they are right.

Here are the six documents that form the backbone of every strong delay claim.

1. Daily logs

Your daily log is the single most important piece of evidence in a delay claim. It captures what happened on the job site each day, including weather conditions, crew counts, work performed, equipment on site, visitors, and any events that affected production.

The key is that daily logs are contemporaneous. They were written on the day they describe, not reconstructed weeks later from memory. That real-time quality is what gives them weight in a dispute. A daily log entry that says “rain from 6 AM to 2 PM, no earthwork possible, crew sent home at 9 AM” is hard to argue with.

If you are still using paper logs or spreadsheets, you are making this harder than it needs to be. A tool like Projul’s daily logs feature lets your field team capture entries from their phone with timestamps, weather data, and crew details attached automatically. That kind of structured, timestamped record is exactly what you need when a claim goes sideways.

2. The original project schedule

You cannot prove a delay without a baseline to measure against. Your original project schedule, the one that was accepted at the start of the project, establishes what the plan was before things went wrong. Every delay analysis compares the as-planned schedule to the as-built timeline to quantify the impact.

Keep every version of your schedule. The original baseline, every update, and every revision. If you are using scheduling software that tracks changes over time, you already have this. If you are working from a static spreadsheet or a bar chart taped to the wall, start saving copies every time something changes.

3. Timestamped photos and videos

Read real contractor reviews and see why Projul carries a 9.8/10 on G2.

Photos do not lie, and they do not forget. A timestamped photo showing standing water on a grade that was supposed to be ready for concrete tells a story that no amount of back-and-forth emails can argue with. Photos of site conditions before work begins, during delays, and after delays resolve create a visual timeline that supports your written records.

Take more photos than you think you need. Storage is cheap. Losing a claim because you did not document the condition is expensive. Photo and document management tools that automatically tag photos with dates, locations, and project details save you from the nightmare of scrolling through a camera roll trying to figure out when something was taken.

4. Written notice letters

Almost every construction contract requires written notice of a delay within a specific number of days from when the delay event starts. This is not optional. Missing your notice window can destroy a perfectly valid claim. Courts and arbitrators regularly throw out delay claims where the contractor failed to provide timely notice, regardless of how obvious the delay was.

Your notice letter does not need to be a legal brief. It needs to identify the delay event, state when it began, describe the anticipated impact on the schedule, and reference the contract clause that entitles you to relief. Send it by email and certified mail. Keep copies of everything.

5. Correspondence records

Emails, text messages, meeting minutes, RFI responses, submittal logs. Every piece of written communication between you, the owner, the architect, and your subs tells part of the delay story. A chain of emails showing that you submitted shop drawings on March 1 and did not get approval until April 15 is powerful evidence of an owner-caused delay.

Save everything. Create a filing system that lets you find correspondence by date and subject. When it is time to build your claim narrative, you will be glad you did.

6. Cost records tied to the delay

If you are seeking compensation and not just a time extension, you need to show what the delay actually cost you. That means labor timesheets for standby crews, equipment rental invoices for idle machinery, receipts for extended trailer rental, and documentation of any acceleration costs you incurred trying to make up lost time.

Tie every cost directly to the delay event. General overhead claims are harder to prove. Specific, documented expenses with clear connections to the delay are much stronger.

How to Build a Delay Claim Timeline That Holds Up

A delay claim lives or dies on the timeline. You need to show a clear chain from cause to effect: this event happened, it impacted this activity, which pushed these downstream tasks, which delayed the project completion by this many days.

The process looks like this in practice.

Start with the baseline schedule. Pull the original accepted schedule and identify the critical path. The critical path is the longest sequence of dependent activities that determines the project completion date. A delay only extends the project if it hits an activity on the critical path or creates a new critical path.

Map the delay event to a specific activity. Do not say “the project was delayed by rain.” Say “fourteen days of rainfall between March 3 and March 22 prevented excavation of the foundation, which was a critical path activity scheduled to start March 1 and finish March 12.”

Show the ripple effect. Trace the delay through the schedule. If the foundation excavation was delayed by fourteen days, and the foundation pour could not start until excavation was complete, and the framing could not start until the foundation cured, the entire downstream sequence shifted. Map each activity and its new dates.

Quantify the total impact. Compare the as-planned completion date to the as-built or projected completion date. The difference is your delay claim. If the contract completion date was June 15 and the delay pushed it to July 10, you are claiming 25 calendar days.

Account for concurrent delays. This is where claims get complicated. If the owner was late approving the finish schedule and you were also late ordering the HVAC equipment, those delays might overlap. Concurrent delays are tricky because neither party can typically recover for the overlapping period. Be honest about concurrent issues in your analysis. Trying to hide them will destroy your credibility if the other side finds them.

There are several formal delay analysis methods that experts use, including as-planned versus as-built, impacted as-planned, collapsed as-built, and time impact analysis. For large or complex claims, you may need a scheduling consultant to perform a proper analysis. For smaller claims, a clear written narrative supported by schedule comparisons and daily logs is often enough.

Common Mistakes That Kill Delay Claims Before They Start

Most delay claims that fail do not fail because the delay was not real. They fail because the contractor made avoidable mistakes in how they documented, noticed, or presented the claim. Here are the ones that come up over and over again.

Waiting too long to send notice. This is the number one claim killer. Your contract says you have 14 days to provide written notice. You wait until the end of the project to raise the issue. The owner’s attorney points to the notice clause and your claim is dead. Send notice early. Send it even if you are not sure yet how big the impact will be. You can always update the claim later. You cannot go back in time and send a notice you never sent.

Reconstructing records after the fact. Daily logs written three weeks after the fact are not daily logs. They are recollections. And opposing counsel will tear them apart. The entire value of contemporaneous documentation is that it was created in real time. If you did not write it down when it happened, you have a much weaker position.

Failing to update the schedule. If your schedule still shows the original dates months after a major delay, it undercuts your entire claim. How can you argue that the delay impacted the project when your own schedule does not reflect it? Update your schedule regularly. Issue revised schedules that show the impact of delay events. This creates a documented record of how the project evolved.

Lumping everything together. A delay claim that says “various owner delays pushed the project back four months” is not a claim. It is a grievance. Strong claims tie specific delay events to specific schedule impacts with specific documentation. Break your delays into individual events and analyze each one separately.

Ignoring your own contributions to delay. If you caused some of the delay, acknowledge it. Trying to claim 60 days when 20 of them were your own doing will wreck your credibility on the other 40 days. Owners and their consultants will find the concurrent delays. It is better to present a clean, honest claim for 40 days than a bloated claim for 60 that gets thrown out entirely.

Not tracking costs as they happen. If you wait until the claim is assembled to figure out what the delay cost you, you will miss things and your numbers will look soft. Track delay-related costs in real time. Code them separately in your accounting system. When it is time to present the claim, you will have clean, organized cost data ready to go.

How to Present Your Delay Claim for Maximum Impact

The way you present a delay claim matters almost as much as the substance behind it. A well-organized claim gets taken seriously. A messy, disorganized submission gets pushed to the bottom of the pile or rejected outright.

Lead with a clear executive summary. Open with a one-page summary that identifies the delay events, the total time impact, and the compensation requested. Decision-makers are busy. Give them the big picture first, then let them dig into the details.

Organize chronologically. Walk through the delay events in the order they happened. For each event, include the date range, the cause, the contract clause that applies, the schedule impact, the supporting documentation, and the associated costs. This structure makes it easy for the reviewer to follow your logic.

Include a schedule comparison. A visual side-by-side of the as-planned schedule and the as-built or impacted schedule is one of the most effective tools in a delay claim. Bar charts, Gantt charts, or even simple timeline graphics make the impact tangible in a way that paragraphs of text cannot.

Attach supporting documents as exhibits. Do not bury your evidence in the narrative. Reference it and attach it as numbered exhibits. “See Exhibit 7, Daily Log Entry dated March 14, 2026” is clean and professional. Dumping a 200-page appendix with no organization is not.

Be professional, not adversarial. The goal is to get paid and maintain the relationship if possible. Present your claim as a factual, evidence-based business matter. Avoid accusatory language. Avoid emotional arguments. Stick to the facts, the contract, and the documentation.

If the owner disputes your claim or the negotiation stalls, you may need to move to mediation or arbitration. Our complete guide to construction dispute resolution covers those processes in detail, including how to prepare and what to expect.

Preventing Delay Claims With Better Project Management

The best delay claim is the one you never have to file. While you cannot control the weather or the speed of a building department, you can control how well your projects are planned, communicated, and documented from day one.

Build float into your schedule. Every experienced contractor knows that a schedule with zero float is a schedule that will fail. Build reasonable buffers into your timelines, especially for activities that depend on third-party approvals, material deliveries, or weather-sensitive work. Float is not padding. It is realistic planning.

Track submittals and RFIs aggressively. Owner-caused delays often start with slow submittal reviews or unanswered RFIs. Track every submittal and RFI with a log that shows the date sent, the date a response is needed, and the date the response was actually received. When approvals are late, send a written reminder referencing the contractual review period. This creates a paper trail that supports a delay claim if one becomes necessary.

Hold regular schedule update meetings. Sit down with your team weekly and update the schedule based on actual progress. Identify activities that are falling behind. Discuss the cause and document it. These meetings serve double duty: they help you manage the project in real time and they create a record of schedule performance that supports future claims.

Invest in tools that make documentation automatic. The reason so many contractors have weak documentation is not that they do not care. It is that capturing everything manually takes too much time when you are running multiple jobs. Project management software that handles daily logs, scheduling, and photo documentation in one platform removes the friction from documentation. When it is easy, it actually gets done.

If you are evaluating tools to strengthen your documentation process, take a look at Projul’s pricing to see what is available at each tier. The cost of good project management software is a fraction of what a single undocumented delay claim can cost you.

Communicate early and in writing. When you see a potential delay forming, do not wait to see if it resolves itself. Send an email to the owner and architect identifying the risk, the potential impact, and what you need from them to keep things on track. Even if the delay never materializes, you have demonstrated proactive management. And if it does turn into a claim, you have early written communication showing you flagged the issue before it became a problem.

Construction delay claims are not about being difficult or litigious. They are about protecting your business when things happen that are outside your control. The contractors who do this well are not the ones who file the most claims. They are the ones who document so thoroughly that when a claim is necessary, the facts speak for themselves.

Curious how this looks in practice? Schedule a demo and we will show you.

Build the habit of documenting everything, every day, on every project. When a delay hits and you need to make your case, you will be ready.