How to Document Construction Delays

March 2026 · 12 min read

Construction delays cost money. Every day a project runs past its scheduled completion, someone is paying for it — extended general conditions, idle equipment, missed revenue from a building that is not open, liquidated damages. The question is who pays. And that question is almost always decided by documentation.

The contractor with thorough, contemporaneous records of what caused the delay, when it happened, and how it impacted the schedule is in a strong position. The contractor who has to reconstruct a timeline from memory six months after the fact is not. This guide covers how to document construction delays properly, by delay type, so your records hold up when it matters.

Types of Construction Delays

Before you can document a delay, you need to understand what type of delay you are dealing with. The classification determines who bears the cost and whether a time extension is justified.

Excusable vs. Non-Excusable

Excusable delays are caused by events beyond the contractor's control — weather, owner-directed changes, differing site conditions, force majeure, permitting holds, or third-party interference. When an excusable delay impacts the critical path, the contractor is typically entitled to a time extension.

Non-excusable delays are caused by the contractor or their subcontractors — inadequate crew sizing, poor scheduling, equipment breakdowns due to lack of maintenance, rework from quality issues. The contractor bears the cost and schedule impact of non-excusable delays.

Compensable vs. Non-Compensable

Compensable delays entitle the contractor to both a time extension and additional compensation. These are typically owner-caused — late design changes, failure to provide site access, slow RFI responses, or directed suspensions of work.

Non-compensable delays entitle the contractor to a time extension but no additional money. Weather delays are the most common example — the contractor gets more time but absorbs their own extended costs.

What to Document for Every Delay

Regardless of delay type, every delay event needs the same core documentation, captured the day it happens. Not the next week. Not when the claim is filed. The day it happens.

• Date and time. When did the delay event start? When did it end? If it is ongoing, note that it continues from a prior date.
• Cause. What caused the delay? Be specific. "Rain" is not enough. "Heavy rain starting at 6:30 AM, 1.5 inches by noon, site access road impassable, standing water in excavation at Grid D-7" is what you need.
• Duration. How long did the delay last? Full day? Half day? Two hours in the morning? Quantify the lost time.
• Impact. What work was affected? Which crews were idle, reassigned, or sent home? What activities on the critical path were delayed? What was the ripple effect on downstream work?
• Who was affected. Which subcontractors were impacted? Were owner representatives or inspectors present? Did anyone acknowledge the delay verbally?
• Photos. GPS-tagged, timestamped photos of the delay condition — flooded site, missing materials, idle equipment, incomplete predecessor work. Photos are the strongest evidence in a delay claim.

This is not optional documentation. This is the minimum required to substantiate a delay claim. If any of these elements is missing, your claim is weaker.

Weather Delay Documentation

Weather delays are the most common type of excusable delay in construction. They are also the easiest to document poorly. "Rain day" in your daily log is not documentation. Here is what weather delay records need to include.

What to Record

• Temperature at the start of the shift and throughout the day. Temperature affects concrete curing, asphalt paving, coating application, and earthwork compaction.
• Precipitation type and amount. Rain, snow, sleet, hail. Measure accumulation if possible. Note start and stop times.
• Wind speed and direction. High winds affect crane operations, steel erection, roofing, and any work at height.
• Site conditions resulting from weather. Muddy access roads, standing water, frozen ground, saturated soil, icy surfaces. These conditions often prevent work even after the weather event ends.
• Impact on work activities. Which specific activities were delayed or stopped? For how long? Which crews were affected?

How Daily Reports Capture This Automatically

With a digital daily report tool like BuildLog, weather conditions can be captured as part of every report. GPS coordinates allow correlation with local weather station data. Timestamped photos of site conditions — standing water, mud, frozen ground — provide visual evidence that goes beyond what any weather station record can show. The daily report creates a contemporaneous record that ties weather conditions to their impact on specific work activities.

Over the course of a project, these daily weather records build into a comprehensive dataset. When a weather delay claim needs to show 23 lost days due to rain over a six-month period, your daily reports provide the day-by-day evidence with photos, timestamps, and impact descriptions for each one.

Material and Supply Chain Delays

Material delays have become increasingly common and are often difficult to prove because the evidence is scattered across emails, purchase orders, and delivery receipts. Proper documentation requires consolidating this evidence and connecting it to your daily reports.

What to Document

• Original order date and expected delivery date. Establish the baseline — when was the material ordered, and when was it supposed to arrive?
• Actual delivery date. When did it actually arrive? The gap between expected and actual delivery is your delay.
• Supplier correspondence. Emails, phone call notes, and written notices about delays, shortages, or substitutions. Save everything.
• Delivery receipts and packing slips. Proof of what was delivered, when, and in what condition. Photograph damaged or incorrect materials.
• Daily report entries. On every day that work was delayed waiting for materials, your daily report should explicitly state: "Concrete pour at Grid A-3 delayed — rebar delivery not received, originally scheduled for March 1, supplier now estimates March 8."
• Impact on schedule. Connect the material delay to the critical path. Which activities were waiting on this material? How many days of productive work were lost?

Substitution Records

If materials are substituted due to supply chain issues, document the substitution request, the approval (or rejection), and any cost or schedule impact. Substitutions often require re-engineering, re-submittal, and re-approval — each adding time. Your daily reports should track this process.

Owner-Caused Delays

Owner-caused delays are typically compensable — meaning the contractor is entitled to both time and money. But proving that the owner caused the delay requires meticulous documentation, because the owner will almost certainly dispute it.

Change Orders

When the owner directs a change to the scope of work, document the following in your daily reports:

• The date the change was communicated (verbal or written).
• The date a formal change order was issued.
• The gap between the two — work often stops or slows while waiting for a formal change order, and that waiting time is a delay.
• The impact on in-progress work. Did crews have to demobilize? Was completed work demolished or modified?
• The impact on the critical path. Did the change push the completion date?

RFI Response Times

Requests for Information (RFIs) are a major source of owner-caused delay. When the contractor submits an RFI and the owner or architect takes weeks to respond, work dependent on that information cannot proceed.

Document RFI submissions and responses in your daily reports. When work is delayed waiting for an RFI response, state it explicitly: "Framing at Level 3 on hold pending RFI #47 response (submitted February 12, no response as of March 5 — 21 days outstanding)." This creates a day-by-day record of the delay caused by slow RFI turnaround.

Access Delays

If the owner fails to provide site access, right-of-way clearance, or utility shutdowns as scheduled, document it daily. Photograph locked gates, occupied work areas, or active utilities that were supposed to be shut down. Note which crews were unable to work and what activities were delayed.

How Daily Reports Create Your Delay Evidence

Individual daily report entries are the raw material. But delay claims are built from patterns — a series of daily entries that together demonstrate a sustained delay event, its cause, and its impact on the project schedule.

This is where consistent daily reporting pays off. If you log every day, your delay evidence is already assembled. You do not need to reconstruct a timeline. You do not need to rely on memory. You filter your daily reports by the delay period, export them, and present a contemporaneous, day-by-day record of exactly what happened.

Connecting Daily Logs to the Critical Path

A delay claim is not just about proving that something slowed you down. It is about proving that the delay impacted the critical path — the sequence of activities that determines the project completion date. Your daily reports should explicitly note when a delay affects critical path activities.

"Foundation pour delayed due to rain — this is on the critical path and will push structural steel erection start date" is far stronger than "No work today, rain." The first entry connects the delay to the schedule. The second is just a weather observation.

Building a Delay Timeline

Claims consultants and attorneys build delay timelines by reviewing daily logs. The easier your logs are to search, filter, and export, the faster and cheaper the claims process. Digital daily report tools like BuildLog let you tag entries as claim-relevant, filter by date range, and export organized PDF packages — turning what used to be a weeks-long binder review into a minutes-long export.

Frequently Asked Questions

What documentation is needed for construction delay claims?

Construction delay claims require contemporaneous daily logs, GPS-tagged timestamped photos, weather records, correspondence (emails, RFIs, change orders), delivery receipts, crew and equipment records, and a clear narrative connecting the delay event to the schedule impact. The strongest claims are supported by daily reports that were created on the same day the delay occurred — not reconstructed after the fact. Digital daily report tools like BuildLog create tamper-evident, timestamped records that establish the authenticity of your documentation.

How do you prove a construction delay?

To prove a construction delay, you need to demonstrate three things: (1) the delay event occurred, documented with daily logs, photos, and contemporaneous records; (2) the delay impacted the critical path of the project schedule, shown through schedule analysis comparing as-planned versus as-built; and (3) the delay was caused by a party or event covered by the contract's delay provisions. Contemporaneous daily records are the foundation — they prove what happened, when, and what impact it had on work activities. Read our guide on how daily site logs win delay claims for a deeper dive.

What is a Delay Defense Pack?

A Delay Defense Pack is BuildLog's automated delay documentation package. It compiles your daily reports, GPS-tagged photos, weather records, and claim-relevant entries into a single, organized PDF evidence package. Instead of manually sifting through months of daily logs to build a delay claim narrative, the Delay Defense Pack filters and organizes the relevant records automatically. Learn more about the Delay Defense Pack and how it works.