A weather delay claim survives when the daily record, written on the day, shows three things: the condition as measured, the specific work it prevented and the hours it cost. "Rain" shows none of them. An owner's rep, a construction manager or an arbitrator reading that word months later can't tell whether it drizzled at lunch or dumped two inches before the pour — and when they can't tell, the time goes to whoever kept the better record.
What follows is what each of those three elements looks like in an actual log entry, why same-day matters more than detail and the step most builders skip.
"Rain" answers none of the questions a reviewer asks
Weather clauses rarely grant time for weather as such. They grant time for weather worse than could reasonably be expected for that location and season — and only where it actually delayed the work. Wording varies. Some contracts set a number of anticipated weather days the builder absorbs before any extension starts. Read yours before the season turns, not after.
That turns every claimed day into three questions:
- Was it abnormal? — the reviewer needs a measured condition to compare against what was expected.
- Did it stop work that mattered? — the reviewer needs the activity named and the reason the condition stopped it.
- How much did it cost? — the reviewer needs crew hours, idle equipment and anything that mobilized and left.
A log that reads "Rain. Sent crew home." answers none of them. It isn't false. It just isn't evidence.
The three things the entry has to show
The condition, measured
Numbers with a source and a time. Rainfall total and when it fell. Wind speed and gusts. Temperature at the start of the shift and when it changed. Ground condition — standing water in the footing excavation, ruts deep enough to stop the skid steer. Note where each number came from: a site gauge, the nearest official weather station or a screenshot saved that day. A station reading is easier to defend than memory. A dated photo of the site is easier to defend than either.
What it prevented — and why
Name the activity and the reason the condition stopped it. Not "no work" but "slab pour Building B cancelled 6:40 a.m. — subgrade standing water, supplier cancelled the trucks." Not "too windy" but "truss set stopped 10:15 a.m. — gusts over the crane's limit for the pick." The reason is what separates a weather delay from a decision the builder made.
Record what did proceed, too. If the framers worked interior partitions while the site crew sat, say so. A reviewer who sees partial productivity recorded honestly trusts the lost hours more — and the split is needed to price the day anyway.
The hours it cost
Headcount by trade, hours on site, hours idle, hours sent home. Rented equipment that sat. Subs who mobilized and demobilized. These numbers become the time and, where the contract allows it, the money. A day is rarely all or nothing — a crew that worked until 11 and left lost half a day, and the log should say half.
- The entry that fails: "Rain. No work." — no condition, no activity, no hours.
- The entry that's arguable: "Heavy rain all morning, couldn't pour, crew left early." — condition vague, activity named, hours missing.
- The entry that holds: "1.3 in rain 5:00–11:00 a.m. (site gauge, photo 1). Slab pour Bldg B cancelled 6:40 a.m. by supplier; standing water on subgrade, photo 3. Concrete crew 6 x 8 hrs idle, released 7:30 a.m. Framing crew 4 worked interior partitions full day." — all three, on the day.
Same day beats detailed
Delay claims turn on contemporaneous records. An entry written that evening by the superintendent who stood in the mud carries weight that a thorough narrative assembled three months later does not — however accurate the later one is. The first question about a reconstructed log is who wrote it and when. "The PM, from memory, when we started the claim" ends that conversation badly.
So good weather delay construction documentation is mostly a habit, not a writing skill. A short, specific entry filed at 4 p.m. beats a polished one filed next week. Photos taken that day with their dates intact beat photos pulled off someone's phone later. Corrections after the fact should leave a trail rather than overwrite the original.
The days after the storm count as well. Ground that takes two days to dry can cost as much as the rain did, and those days often get logged as "site wet" or not at all. The same three elements apply — a photo of the saturated subgrade or the stuck machine, the activity it prevented, the hours lost. Drying days are where time quietly goes unclaimed.
Lost hours become days only on the critical path
A rained-out day on work with float doesn't usually move the completion date, and most contracts won't extend for it. The claim has to show the weather stopped an activity on the critical path or pushed one onto it. Know which activities those are before the forecast turns — the post on the four activities in a critical path that can't slip covers how to find them.
This is also where weather gets tangled with everything else. If a late owner approval had already stalled the slab, a rain day that week may be concurrent, and the record has to show which cause actually controlled. The types of construction delays and who pays for each are covered separately. The point here is narrower: the weather entry should note anything else holding the activity that day, even when it weakens the claim. An entry that admits a competing cause is believed on the days it doesn't.
Notice is a separate deadline
Most weather clauses require written notice to the owner within a set window — sometimes days, not weeks — and name who must receive it. A perfect daily log does not satisfy that clause. Send the notice, reference the log entries by date and keep proof it went out. A missed notice window can cost the extension no matter how good the record is.
The formal request follows: a change order asking for time, listing each claimed day with its condition, activity and hours, and the log entries and photos attached behind it. If the entries were written properly, the change order is mostly copying.
How BuilderSolve handles the record
Daily logs in BuilderSolve hold conditions, crew hours, notes and photos against the job and the date. The AI assistant can draft the day's log from the superintendent's notes and draft the schedule shift that follows a lost day — neither posts until a person approves or rejects it. A draft still has to be checked by someone who was there. A drafted record nobody reviewed is the reconstruction problem with better grammar.
When weather is also a safety call — lightning, high wind on an elevated deck — the stop-work decision belongs in construction safety reports as well as the log, so the record shows the stoppage was required rather than elected. The time request goes through change orders with an audit trail, so the request, the attached entries and the owner's response sit in one history. The schedule is built from the estimate, which makes it plain whether the lost activity was critical.
What it doesn't do: it doesn't decide whether a day is excusable under your contract, and it doesn't send contractual notice for you. If the back-office operations team is on your contract, they can assemble the claim package — the day-by-day table, the entries, the photos, the schedule impact — from what the field recorded. They can't add what the field didn't write down.
What to set up before the next storm
- Read the weather clause in every active contract: what counts as abnormal, any anticipated-days allowance, the notice window and who receives notice.
- Pick one source for weather numbers on each job — site gauge, named station or saved screenshot — and tell supers to cite it.
- Give supers the three-line entry: condition with numbers, activity stopped and why, hours by trade. Written the same day, before they leave site.
- Mark which activities are on the critical path this month so the super knows which lost hours carry the most weight.
- Log drying days with the same discipline as the rain day.
- Send written notice inside the window and file the proof with the log entries.
None of this takes more than ten minutes a day on site. What it replaces is a week of arguing over a one-word entry — and weather delay construction documentation that wasn't written on the day can't be written later.
Common questions
what should a daily log say about a weather delay
It should state the measured condition, the specific activity it stopped and the crew hours it cost. Give rainfall, wind or temperature with a time and a source, name the work and why the condition prevented it, then list headcount by trade with hours idle or sent home. Record any work that did proceed. Attach dated photos and write it the same day.
can I document weather delays after the fact
You can, but a reconstructed record is much weaker than a same-day entry. Reviewers ask who wrote the log and when, and an account assembled months later by someone who wasn't on site is easy to challenge. A short, specific entry written that evening by the superintendent carries more weight than a detailed narrative pieced together when the claim starts.
does every rain day get a construction time extension
No. Most contracts grant time only for weather worse than normally expected for the location and season, and only when it delayed critical path work. Some contracts also set anticipated weather days the builder absorbs first. A rain day on work with float usually won't move the completion date. Read the weather clause in each contract to know what qualifies.
are mud days after rain claimable as weather delay
Often, if the contract covers the effects of weather and the record proves the ground condition stopped critical work. Log drying days the way you log the rain day — photos of the saturated subgrade or stuck equipment, the activity it prevented and crew hours lost. A log that just says "site wet" for two days rarely supports the time.