Every superintendent has lived some version of this: it rains hard for three days, the site turns to soup, nobody can pour or excavate or set steel, and two months later the owner's scheduler sends a letter arguing the delay was "your inefficiency, not weather." You know it was weather. You watched it happen. But your proof is a coffee-stained daily report that says "rain, no work" — and that thin note is going to lose you a legitimate time extension.
Weather is one of the few delay causes that's genuinely outside anyone's control, and it's also the one contractors most often fail to document well enough to recover. The conditions themselves aren't the problem. The problem is that nobody writes down, in real time and in usable detail, what fell from the sky, how much of it, when, and exactly which activities it stopped. Good field documentation closes that gap, and when it's tied to your look-ahead schedule, it does something better than justify claims after the fact — it helps you dodge the delay in the first place.
What a defensible weather record actually contains
"Rain" is not documentation. When you're trying to prove a weather day or support a schedule extension, the reviewer on the other side is looking for specifics they can't wave away. At minimum, a record worth anything captures:
- Measured amount and timing — not "rained all day," but "0.9 inches between 0600 and 1100." Timing matters because a half-inch overnight that's gone by 8 a.m. is a very different story from a half-inch that lands mid-pour.
- Temperature highs, lows, and when they occurred — a low of 28°F at 5 a.m. that's up to 45°F by 10 a.m. affects your morning masonry but may not cost the whole day.
- Wind speed and gusts — the number that stops your crane is a gust reading, not an average.
- Site conditions that resulted — standing water, saturated subgrade, mud, ice, frost heave. This is the causal link between the weather and the lost work.
- Which specific activities were stopped or slowed, and for how long — this is the part everyone skips, and it's the part that wins claims.
That last item is the whole game. A weather record that says "1.2 inches of rain" proves it rained. A weather record that says "1.2 inches of rain; south building pad excavation halted 0700–1500; two operators and a labor crew idle; pad not workable until following afternoon after it drained" proves damages. One is trivia. The other is money.
Log conditions at the site, not from the regional forecast
Here's a mistake I've watched cost real time extensions: the contractor's daily reports cite the nearest airport's weather station because that's what's convenient. Then the owner's team pulls the same station's data, points out it only recorded 0.3 inches that day, and your claim for a washout evaporates. Meanwhile your actual site — eight miles away, lower ground, in the path of a cell the airport missed — took an inch and a half.
Microclimates are real. A ridge, a valley, proximity to water, and plain bad luck with a storm cell can put dramatically different weather on your site than on the official station a few miles off. So record what happened where the work is. A cheap tipping-bucket rain gauge on site and a min/max thermometer cost almost nothing and give you your own defensible numbers. Better still, note the site reading and the nearest official station reading side by side — showing you had more water than the station explains why your ground was unworkable when the "official" record looks mild.
This is where doing it in the field, in the moment, beats reconstructing it later. Field documentation software that pulls GPS-tagged conditions for the actual jobsite coordinates, timestamps them, and lets the foreman drop a photo of the ponding right into the daily log turns a chore everyone neglects into a record that holds up. The point isn't the technology — it's that the record gets made consistently, at the site, tied to the day's work, instead of being backfilled from memory a week later when the pattern of the storm has already gone fuzzy.
Know the trigger points before you're standing in it
Weather documentation isn't only a legal exercise. Half its value is operational: knowing the thresholds that stop specific work so you can call the day early, protect what's in place, and reschedule instead of burning crew hours watching the sky. A few of the trigger points worth having taped inside the trailer:
- Concrete, cold. Below 40°F and falling, you're in cold-weather concreting territory — blankets, heated enclosures, accelerators, and protecting the pour for its first several days. Placing on frozen subgrade is a callback waiting to happen; the ground heaves as it thaws.
- Concrete, hot. Above roughly 90°F with wind and low humidity, you're fighting flash set and plastic shrinkage cracking. Move pours to early morning, have your evaporation retarder and water ready, and don't let the truck sit.
- Masonry. Mortar doesn't want to be laid below 40°F without cold-weather measures, and green masonry needs protection from freezing for a couple of days after.
- Coatings, sealants, and flooring. Most product data sheets specify a temperature range and a maximum relative humidity, and many require the surface to be a set number of degrees above the dew point. Paint or seal outside those numbers and you own the adhesion failure. This is a documentation issue as much as a scheduling one — record the conditions at the time of application so you can prove you were in spec.
- Crane and elevated work. Crane load charts and the manufacturer typically set a wind limit, and gusts hit it before the sustained wind does. Roofing, steel erection, and anything on a lift get exposed at height well before ground crews feel it.
- Earthwork. Once the subgrade is saturated you can't get compaction, and running equipment over it just churns it deeper. The lost day is often the day after the rain, waiting for it to drain — and reviewers frequently forget to credit that drying day, so document it explicitly.
Have these numbers ready and the weather stops being a surprise. You'll call the pour off at 6 a.m. based on the forecast instead of paying a crew to stand around until you accept the obvious at 9.
Fold the forecast into your look-ahead, not just the rearview
Most weather documentation is backward-looking — proving what already happened. The bigger win is looking forward. Your weekly work plan and your three-to-six-week look-ahead are exactly where forecast weather should live, because that's where you decide the sequence of work.
Practically, that means when you build the coming week's plan, you weather-sort the tasks. If there's a clear stretch Tuesday and Wednesday and rain Thursday, the exterior pours, the roofing, and the site work go early in the week and the interior drywall, MEP rough-in, and anything under roof slides to Thursday. It's obvious in hindsight and constantly ignored in practice, because the plan gets built on Friday without anyone glancing at the forecast.
A rolling look-ahead is the right home for this because it updates. A forecast eight days out is a rumor; two days out it's reliable. So the weather-sensitive activities on the near edge of your look-ahead get real scrutiny as their window firms up, and the plan flexes accordingly. This is exactly the kind of short-interval adjustment that a live look-ahead tool like LookAheadWall is built for — you're already reshuffling the weekly plan and the trade-flow sequence in one place, so pulling the exterior work forward when the radar turns ugly is a drag-and-drop, not a fire drill. The scheduling discipline does the work; the software just keeps everyone looking at the same, current plan.
Connect weather to the schedule, and to the variance you record
If you run any flavor of short-interval or Last Planner-style planning, you're already tracking why planned work didn't get done — the variance or reason-not-complete. Weather belongs in that loop as its own tagged cause, kept distinct from "manpower," "materials," "prior trade not finished," and the rest. Two reasons this matters.
First, it keeps your claims honest and therefore credible. If your own variance log shows the drywall slipped because the framer was behind — not because of weather — then when weather genuinely does hit, your records have a track record of telling the truth. Reviewers can smell a log where everything is blamed on rain.
Second, the pattern is planning gold. Tag weather variances all season and you'll see, in your own project's data, which trades and which activities actually eat delay when the weather turns. Next project, next season, you plan around your real exposure instead of a guess.
Match your records to the contract's weather-day language
Before you can count a weather day, you have to know how the contract defines one — and they vary a lot. Some contracts grant an excusable, non-compensable extension for adverse weather beyond a monthly baseline of "normal" days derived from historical averages; you only get relief for the days exceeding that baseline. Others require the weather to actually prevent work on a controlling, critical-path activity — a rained-out day on float buys you nothing. Many require notice within a set number of days of the event, and a late notice can waive an otherwise valid claim.
So read the weather clause at the start of the job, not when you're filing. Then build your documentation to answer the exact question the contract asks: Was it more than a "normal" day? Did it stop critical work? Did we give notice in time? If your daily records already carry the amount, the timing, the specific activity affected, its position in the schedule, and a photo, you can answer all of that without reconstructing anything.
Don't forget the costs weather drags behind it
Weather documentation tends to focus on lost days, but the money isn't only in the schedule. Cold and wet weather bring real out-of-pocket costs that are frequently recoverable if you tracked them: temporary heat and the fuel to run it, blankets and enclosures, dewatering and pumping, snow removal, re-compaction of subgrade that got soaked, standby time for idled crews and equipment, and the overtime you spend clawing back the lost days later. Capture those costs against the weather event as they happen. Trying to assemble them months later from scattered invoices is how legitimate money gets left on the table.
The habit that makes it work
None of this requires anything exotic — a rain gauge, a thermometer, a phone camera, and the discipline to record conditions and their specific impact every single day, at the site, tied to the day's work. The contractors who recover weather delays aren't luckier with the weather. They're just the ones whose daily record, on the ordinary sunny days as much as the washouts, is detailed and consistent enough that when the storm comes, the paper trail is already there. Do it in the field, keep it connected to your look-ahead so the forecast actually changes what you plan, and weather goes from a dispute you usually lose to a documented, manageable fact of the job.