Construction Delay Log: What Owners Expect Before Approving a Time Extension

A concrete delivery shows up four hours late. The crew stands around. The pour gets pushed to the next day, and the schedule slips with it. Three weeks later, the PM submits a time extension request.

The owner's response: "Where's the documentation?"

This is where most extension requests break down. The owner isn't questioning whether the delay happened. They're questioning whether the contractor can prove it, who caused it, and how much time it cost.

It's one of several undocumented jobsite events that quietly cost contractors money, not because the event didn't happen, but because nobody captured it.

That proof lives in one place: the construction delay log.

What Is a Construction Delay Log?

A construction delay log is a running record of schedule-impacting events, captured as they happen on the jobsite. It tracks the start and end of each delay, the cause, the work affected, and any recovery efforts taken.

It is not the same as a daily report, a schedule update, or a change order request. Each document serves a different purpose, and owners know the difference even when contractors don't.

Daily Report: Records daily work, manpower, equipment, and weather to show what happened on site that day.

Delay Log: Records schedule delays, their cause, impact, and duration to support time extension requests.

Project Schedule: Shows the planned and updated sequence of work but does not explain why delays occurred.

Change Order: Requests additional time or cost based on documented changes or delays.

A daily report might mention that concrete didn't arrive until 1 p.m. A delay log records the exact delay window, the crew affected, and what was done to recover lost time. One is a summary. The other is evidence.

Owners treat a delay log as its own category of construction schedule documentation, and mixing it with routine daily reporting is a fast way to lose credibility on a time extension request.

Why Owners Ask for Delay Logs Before Approving Time Extensions

Owners aren't in the field. They weren't standing next to the crane when it went down or watching the inspector walk the site for two hours. All they have is what gets handed to them, and they're skeptical of anything that shows up without a paper trail.

Before approving a time extension, an owner (or their construction manager) is typically asking:

• Did this delay actually happen, and when?

• Who or what caused it?

• Could the contractor have reasonably avoided it?

• How much work was actually stopped or slowed?

• Did the contractor try to recover the lost time?

For example, if a masonry crew sits idle for two days waiting on a shop drawing approval, the owner wants delay records showing the submission date, approval date, and crew affected, not the PM's word for it. Without that, the delay claim reads like an excuse, and the time extension gets pushed back for more information instead of approved.

A delay log answers these questions with dates, photos, and specifics instead of a general statement like "we lost about a week due to weather and inspections." Owners approve evidence, not opinions, and a request built on memory reads like an opinion no matter how confident it sounds.

A documented log also matters beyond the extension request. It's what lets an incoming superintendent handoff pick up an open delay claim without starting from zero.

Five Things Every Construction Delay Log Should Include

A delay log only holds up if it's specific enough to stand on its own. These five elements separate a log an owner will approve from one they'll send back.

1. Record exactly when the delay started and ended

Vague ranges like "delayed most of the week" don't hold up. If the concrete truck was supposed to arrive at 7 a.m. and showed up at 11 a.m., that four-hour window is what gets recorded, not "late delivery."

2. Document the specific cause

"Weather" is not a cause an owner can verify. "Rain from 6 a.m. to 11 a.m. prevented excavation in the north footing area" is, and the more specific the cause, the harder it is to dispute. The same applies to unexpected site conditions like buried utilities: naming the exact condition and where it was found carries more weight than saying the site "wasn't as expected."

3. Identify the work affected

Note which crews or activities were stopped, and whether the delay hit the critical path or just a task with float. An owner needs to see the connection between the event and the actual schedule impact, not just that "work was delayed."

4. Attach supporting evidence

A delay log without evidence is just a claim. Attach whatever exists:

• Timestamped photos of the site condition or the idle crew

• Voice notes recorded on the spot

• Weather data for the exact date and location

• Emails or texts confirming the delay (a supplier notice, an inspector cancellation)

• Inspection records or failed inspection reports

5. Record recovery efforts

If the crew worked overtime, resequenced tasks, or brought in extra manpower to make up time, that needs to be in the log too. It shows the contractor made a good-faith effort to mitigate the delay, which strengthens the extension request.

Common Delay Log Mistakes That Weaken Time Extension Requests

Most delay logs don't fail because the delay wasn't real. They fail because the documentation can't carry the weight of the claim:

Bad: "Rain delayed work this week." Better: "Rain from 7 a.m. to 1 p.m. on May 14 prevented concrete placement for the east wing slab. The crew of 6 idle for 4 hours. Photos attached."

Other common issues:

• Generic notes written days after the fact, based on memory instead of the actual event

• No timestamps, so there's no way to confirm when the delay started or ended

• Missing photos or field evidence to back up the written entry

• No responsible party identified, leaving the cause open to argument

• No mention of recovery efforts, making it look like the lost time was simply absorbed

Any one of these gives the owner a reason to send the request back.

Why Waiting Until the Weekly Report Is Too Late

By Friday, nobody remembers the exact time the crane went down on Tuesday. Memory fades fast on an active jobsite, and the details that matter most to an owner (exact times, specific causes, who was on site) are the first to go.

When delay information only gets captured in a weekly report, the PM is reconstructing the week from memory, and that's where the specifics disappear into general statements. The office ends up chasing the field for details that should have been captured the day it happened, slowing the extension request further.

The fix isn't a better weekly report format. It's capturing the delay the same day it occurs, while the details are still accurate.

Building Delay Documentation While the Work Is Happening

Same-day capture doesn't require a complicated process, just a habit: when a delay happens, someone in the field records it before it gets buried under the rest of the day's work.

That means capturing:

• A quick voice note describing what happened and when

• Photos of the site condition, idle crews, or the cause itself

• Field notes with the specific time window

• A timestamp tied to the actual event, not the end of the day

Take the same masonry crew delay. A 30-second voice note recorded on the spot already has the date, the reason, and the crew count baked in, something a Friday reconstruction from memory can't match. The first version is usable construction delay documentation. The second is a guess dressed up as a report.

This is where Construction.live fits into the workflow. Instead of relying on someone to remember and write up delays at week's end, field teams capture voice updates, photos, and notes as events happen, and that information is organized into documentation the office can use to build a time extension request. The same records often double as T&M billing documentation for force account work, so nothing gets documented twice. The goal isn't more paperwork. It's making sure the record exists before it's needed.

Delay Documentation Determines Whether a Time Extension Gets Approved

Owners rarely reject a time extension because they don't believe a delay occurred. They reject it because the documentation can't prove what happened, when, why, and for how long.

Strong delay documentation starts in the field, not in the office. Construction.live helps teams capture schedule impacts while they happen, making time extension requests easier to support later.

That same documentation typically feeds into the next billing cycle too, making it easier to work through a construction pay application checklist without digging back through old texts and photos.

FAQ

What is a construction delay log? A record of schedule-impacting events on a construction project, documented with the start and end time, cause, affected work, and supporting evidence for each delay.

What should a construction delay log include? The exact start and end time of the delay, a specific cause, the work or crews affected, supporting evidence like photos or emails, and any recovery efforts taken to make up lost time.

How does a delay log support a time extension? It gives the owner a documented, verifiable record connecting the delay event to its schedule impact, which is what owners require before approving additional time on a project.

Can a daily report replace a construction delay log? No. A daily report summarizes general site activity, while a delay log focuses on schedule-impacting events with the detail needed to support a time extension or claim.