TL;DR

Buying for a business?Offer from Amazon

Get business pricing on tools and workshop supplies

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

Weather delays cost you money twice: once in lost productivity and again when you can’t prove the delay was justified. Keep a contemporaneous daily record with times, conditions, photos, and the specific tasks stopped, and communicate promptly per your contract. Documentation explains what happened — it doesn’t automatically get you extra time or money, but without it you’ll get nothing.

Your crew got rained out for three days last month. The owner’s asking for a recovery schedule. Your general contractor wants proof the delay was weather, not bad planning. And your daily log says one word: “rain.”

That single word just cost you a time extension. Weather can disrupt even the best-run jobsite, but a delay you can’t document is a delay you eat. The fix isn’t complicated — it’s building a habit of keeping clear records before, during, and after every weather event.

This guide walks you through how to prepare before conditions turn, what to write down while it’s happening, and how to explain the impact so your delay holds up. Short sentences, concrete steps, no fluff.

Plan Before the Storm: Set Your Decision Points Now

Weather planning means deciding before conditions arrive what triggers a stop-work, who makes the call, and what happens next. If you’re making those decisions at 6 a.m. while lightning cracks overhead, you’re already behind. Decision points written down in advance protect both your crew and your schedule.

Start with seasonal risk. If you’re pouring concrete in Florida in August, afternoon thunderstorms aren’t a surprise — they’re a scheduling fact. If you’re steel-setting in the Plains in spring, plan around wind limits for the crane. Pull the last five years of local weather history and identify your top three risks: rain days, wind, heat, freeze, or smoke.

Then set hard thresholds. Not “bad weather” — specific numbers. For example: stop crane picks at sustained winds over 25 mph. No concrete pours when the temperature is below 40°F and falling. No roof work when lightning is detected within 10 miles. These limits usually come from manufacturer specs, OSHA guidance, or your own safety plan — write them down.

1. List your seasonal weather risks for this project and this location.
2. Set numeric stop-work thresholds for each (wind speed, temperature, rainfall, lightning distance).
3. Name who has authority to stop work — and make sure anyone on the crew can call it without penalty.
4. Identify indoor or low-risk tasks crews can pivot to when outdoor work stops.
5. Subscribe to official alerts and a reliable forecast source, and check them at a set time every morning.

Here’s a real scenario: a framing crew in Texas had a written trigger — stop work when the heat index hits 103°F. When it hit 105 at 1 p.m. in July, they shut down, logged it, and moved to interior punch list work. Zero argument with the GC, because the threshold was set in April, not invented in July.

Never push a crew to keep working in unsafe conditions to protect a schedule. A compressed timeline is recoverable. A heat stroke or a crane tip-over is not.

What a Winning Weather Delay Entry Looks Like

A weather delay entry is a contemporaneous record — written the same day — that captures the date, time, location, conditions, affected activities, start and end of the stoppage, and who made the decision. The word “contemporaneous” matters. Records written days later look manufactured, and owners’ attorneys know it.

Compare two entries. Weak: “Rain — no work today.” Strong: “7/14, 8:15 a.m. — Heavy rain began 06:40, 1.9 in. recorded at site gauge. Excavation Zone B stopped 08:15 due to standing water and saturated spoil piles. Grading crew (6 workers) reassigned to equipment maintenance. Rain ended 14:30; Zone B remained unworkable per site super’s inspection at 15:00. Decision to demobilize earthwork: J. Ortiz, super. Photos 12–18 attached.”

The second entry took four minutes to write. It also tells the whole story: the trigger, the specific task stopped, the people affected, the recovery attempt, and the decision-maker. That’s the difference between a delay you can defend and a delay you can’t.

Your daily log entry should hit these marks every time:

• Date and time work stopped and resumed, plus the time conditions changed
• Conditions — what you observed, with measurements where possible
• Affected activities — the specific tasks, zones, and milestones, not just “site work”
• Crew status — sent home, reassigned, or standing by
• Who decided and when, by name and title
• Recovery steps — what you tried before calling it

Update the log during multi-day events, not just at the end. An entry each morning saying “Day 3, still ponded, pump running since 06:00” builds a timeline no one can argue with.

Evidence That Actually Backs Up Your Log

Your log is the story; your evidence is the proof. You need both. Photos, forecast records, delivery tickets, and site measurements turn a claim into a fact. Without them, your weather delay rests on your word against the owner’s memory of a “pretty nice week.”

Start with photos, and make them time-stamped and location-stamped. Most smartphones do this automatically — just don’t strip the metadata when you share files. Shoot wide shots showing the affected work area, close-ups showing the specific problem (ponded excavation, saturated subgrade, ice on scaffolds), and a shot of your site thermometer or rain gauge if you have one.

Save forecast and alert records before and during the event. Screenshots of National Weather Service alerts, radar images, and forecasts — with visible dates and times — show you made a reasonable call, not a knee-jerk one. Are screenshots enough? Often yes for internal records, but for contract claims many owners and insurers want official records from the NWS or a recognized reporting station. Pull both: screenshot the day of, then download the official record after. Most airport and NWS stations offer free historical data.

Keep the supporting paper trail too:

• Delivery tickets showing concrete or material loads turned away
• Rental receipts for pumps, heaters, or extra equipment
• Pump log or dewatering records with run times
• Texts and emails notifying the GC, subs, or suppliers
• Sign-in sheets showing reduced or absent crews

Label everything with the date and location, and keep originals. One folder per weather event, named by date — “2024-07-14_Rain_ZoneB” — beats a camera roll with 4,000 unlabeled photos when you need something in ten minutes.

One caution: digital tools and automated summaries can organize all this fast, but verify dates, measurements, and claims against the original records before you submit anything. A wrong date in a summary undermines the whole file.

Connect the Weather to the Schedule — Or the Claim Fails

Here’s where most weather delay claims fall apart: the foreman proves it rained but never proves the rain stopped that specific work. Owners approve the first two rain days and reject the rest, because the record shows weather, not impact. The weather is context. The impact is the claim.

So connect the dots explicitly. Don’t write “rain delayed the project.” Write “rain stopped excavation in Zone B, which pushed the slab pour from July 18 to July 25, because the subgrade needed three drying days plus reinspection.” Now the schedule impact is traceable: condition → blocked task → milestone shift.

Use your schedule to make the link visible. On a CPM schedule or even a simple look-ahead, mark the weather-affected activities and show the float you burned. A table like this makes the case in one glance:

Also record what you considered instead. “Evaluated switching to interior framing — interior materials not delivered until 7/20” kills the owner’s comeback that you should have just worked somewhere else.

One more reality check: documentation explains what happened. It does not automatically establish entitlement to extra time or payment. That depends on your contract’s weather delay provisions, any abnormal-weather thresholds written into it, force majeure clauses, and your insurer’s policy. Many contracts only grant relief for weather that’s unusually severe for that place and season — which is exactly why you saved those five-year weather averages in your planning phase.

Notify the Right People Before the Deadline Passes

Prompt notice is half the battle. Most contracts require you to notify the owner or GC of a weather delay within a fixed window — commonly 24 to 72 hours from when you knew or should have known of the impact. Miss that window and you may lose the time extension entirely, no matter how good your documentation is. Check your notice clause today, not after the storm.

Send the notice in writing, by the method the contract specifies. Email works if the contract allows it. A phone call followed by nothing does not. Your first notice doesn’t need every detail — it needs to put the other side on record that a weather delay occurred and that you’re tracking it.

A solid delay notice includes:

• The date and a brief description of the weather event
• The activities and milestones affected
• Your current estimate of the delay duration
• What you’re doing to mitigate (pumping, resequencing, extended hours)
• A statement that you reserve your rights to a time extension and, where applicable, compensation
• When they’ll get your next update — and then hit that date

Communicate uncertainty honestly. “We currently estimate a five-day impact; we’ll confirm by Friday” beats a confident wrong guess. If you promise Friday, deliver Friday, even if the update is “still assessing.” Overpromising and underdelivering costs you credibility on every future delay.

Keep your internal crew in the loop too. Nobody should learn at 5 a.m. whether they’re working. Text chains are fine for heads-ups — just screenshot them for the file, since they’re also evidence of when and how you communicated.

If the forecast changes after you’ve stopped work, don’t quietly restart. Log the reversal the same way you logged the stoppage: “Forecast updated 11:00, front slowed, roof work resumed 12:30.” A record that shows you responding to real conditions strengthens every other entry in the file.

Track Recovery and Costs Separately From Day One

The storm ends and the second phase of documentation begins: recovery. Record when work resumed, what restrictions remained, and what the bounce-back cost you. Weather-related costs get tracked separately from ordinary operating costs — because if they’re blended together, none of them are recoverable.

Say you pumped water for two days, ran generators for heaters, paid a crew to standby for four hours, and paid stand-by time on a crane rental. Each of those is a weather cost. Regular crew wages for the work they did after restart? That’s ordinary cost. Tag them differently in your cost report from day one, with the weather event date as the reference.

Typical weather-related costs worth capturing:

• Dewatering pumps, fuel, and hoses
• Heaters, thawing equipment, or temporary protection (tarps, poly, blankets)
• Crew standby or show-up time under labor agreements
• Idle equipment rental days
• Re-inspection and retesting fees
• Material ruined or rejected (a washed-out slab pour, frozen mortar)
• Accelerating later to recover schedule — overtime premiums

Also log your mitigation steps, even the ones that didn’t fully work. “Deployed two 3-inch pumps 07:00, removed standing water by 15:00, subgrade still over moisture limit” shows you limited the damage. Owners and insurers respond well to contractors who clearly tried. A delay you actively fought is a delay they’re more willing to pay for.

Finally, protect the whole file. Store records securely, share only with people who need them, and keep them well beyond project closeout — many contracts and insurance policies put claim windows at a year or more. That “one nice folder per event” habit pays off eighteen months later when a dispute finally lands.

Frequently Asked Questions

What weather conditions count as a valid reason for a delay?

It depends on your contract. Most US construction contracts grant relief only for abnormally adverse weather — conditions unusually severe for that location and season — not ordinary seasonal rain or cold. Some contracts define thresholds, like days exceeding a set rainfall amount. Check your delay and force majeure clauses, and compare the event against historical averages for your area to see if it qualifies.

Are forecast screenshots enough, or do I need official weather records?

Screenshots work for internal records and showing you made a reasonable call, but many owners and insurers want official data from the National Weather Service or a recognized reporting station. Best practice: screenshot forecasts and alerts the day of the event, then download the official historical record afterward. Most NWS and airport stations provide free historical data.

How do I prove the weather actually caused the delay?

Connect the condition to a specific task and a specific schedule impact. Record what activity stopped, in which work zone, and which milestone shifted as a result — for example, “rain stopped Zone B excavation, pushing the slab pour four days.” Mark affected activities on your schedule and note mitigation you attempted. Weather data alone proves it rained; the linked task record proves the delay.

When should I notify the owner or general contractor about a weather delay?

Check your contract’s notice clause — many require written notice within 24 to 72 hours of when you knew or should have known of the delay. Send it in writing by the method the contract specifies, even if your full impact estimate isn’t ready yet. Missing the notice window can void your right to a time extension regardless of how good your documentation is.

How long should I keep weather delay records?

Keep them until all applicable claim and dispute windows close — often a year or more after project completion, depending on your contract, insurance policy, and state statute of limitations. Store them securely, share only with people who need access, and keep the original files with their metadata intact.

Conclusion

Weather delays are inevitable. Losing money on them is optional. The crews that get their time extensions are the ones with a four-minute log entry, a folder of stamped photos, and a notice sent before the deadline — every single time, not just on the big storms.

Start tonight: check your contract’s weather delay and notice clauses, set your stop-work thresholds, and build the one-folder-per-event habit. Next time the radar turns red, you’ll be the foreman with proof — not the one with a log that says “rain.”