Weather Delays and Schedule Impacts: Documenting Non-Workable Days

Everyone on a project remembers that a stretch of bad weather pushed the schedule back. Almost nobody, months later, can say with any precision which specific days were actually unworkable, which trades were affected, and whether the delay was properly communicated at the time. That gap matters more than it seems to in the moment. A schedule slip that's vague and after-the-fact is much harder to explain, and much harder to support if it ever needs to be, than one with a dated, specific record behind it.

The goal is a record specific enough that someone who wasn't there could understand exactly what happened and why work didn't proceed.

• The date and the specific weather condition: heavy rain, high wind, extreme heat or cold, snow, lightning
• Which activities or trades were actually prevented from working, rather than a blanket "no work today"
• Whether partial work was possible, since a day that stopped concrete pours but allowed interior framing isn't the same as a full shutdown
• A photo of site conditions when it's useful evidence, particularly for things like standing water, saturated ground, or ice
• Who was on site, if anyone, and what if any work did get done that day

Light rain that doesn't stop interior work isn't the same as a day lost entirely to a storm. Treating every day with any weather as a documented delay dilutes the record and makes genuine delays harder to distinguish later. Be specific about which days actually prevented scheduled work from happening, as opposed to days that were simply unpleasant or required minor adjustments but didn't change the schedule.

A weather delay is easiest to document accurately as part of the same daily record you'd already want to keep for any construction project, rather than a separate weather log that someone has to remember to fill out on top of everything else. If a day's conditions prevented work, note it the same place and the same way you'd note anything else that happened, or didn't happen, that day. A consistent daily habit is far more reliable than a special process that only gets used when someone remembers it exists.

A weather delay that affects the schedule is worth flagging to the owner, the client, or whoever else is tracking project timeline, at the time it happens rather than weeks later when the overall schedule has clearly slipped and someone asks why. A brief note sent the same day, saying what the condition was and what it affected, costs little and avoids the far more uncomfortable conversation of explaining a month-old delay after the fact with no contemporaneous record to back it up.

Many construction contracts include specific requirements for claiming a weather-related schedule extension: a deadline for giving written notice after the delay occurs, a defined threshold for what counts as an excusable weather event, or a requirement to use a particular form or process. These terms differ significantly from contract to contract and jurisdiction to jurisdiction, and missing a notice deadline can mean losing the right to claim the delay at all, regardless of how well documented it was. This article describes general documentation practice, not legal advice. Check the specific notice provisions in your contract, and when a delay is significant enough to matter financially, loop in whoever handles contract administration or legal review before assuming informal documentation alone is sufficient.

The value of this documentation usually isn't obvious until months later, when a schedule dispute comes up or an owner questions why a project finished later than expected. At that point, a dated list of specific non-workable days, what was affected, and who was notified when, is far more persuasive than a general recollection that "it was a rainy spring." Keep the records attached to the project they belong to, not scattered across personal notes or a phone's photo album, so they're findable by whoever needs them later, which may not be the same person who created them.

A rained-out concrete pour doesn't just cost the day it happened on. Every trade scheduled to follow that pour shifts too, and that downstream effect is easy to lose track of if only the original delay gets documented. When a non-workable day affects a trade with other work stacked behind it, note the dependency explicitly, which activities got pushed and by roughly how long, rather than treating each day's delay as an isolated event disconnected from the rest of the schedule.

The project and people below are fictional and for illustration only. They do not describe a real ConstruDo customer or project.

A general contractor building a small commercial addition hit a stretch of storms in late spring. At the time, the superintendent made a mental note that "weather set us back about a week" but didn't log specific days or conditions.

When the owner later questioned a two-week schedule overrun, the contractor could only describe the delay generally, with no dated record of which days were actually lost to weather versus other causes, and no documentation that notice had been given under the contract's weather-delay clause. The claim for a schedule extension was disputed, in part because there was nothing contemporaneous to support it.

On the next phase of the project, the superintendent logged each non-workable day as it happened: date, condition, trades affected, and a same-day note to the owner. When a similar weather stretch hit months later, the schedule-extension conversation took ten minutes instead of becoming a dispute.