Every superintendent has lived some version of this morning: you pull up to the gate at 6:15, the concrete trucks are already staged, and the sky opens up. Now you've got a batch plant on the phone, a pump operator on the clock, a finishing crew standing under the eave, and a slab you can't pour. That's the day weather beats you. The next one, you saw the front coming three days out, shifted the pour, moved the finishers to a covered deck, and nobody lost a paycheck. Same weather. Different plan.
The difference isn't a fancier forecast. It's whether your look-ahead schedule and your sub coordination actually talk to each other about weather before the week starts. Below is how experienced teams fold weather into short-interval planning so it stops being the thing that blows up your Monday.
Know which of your activities weather actually cares about
Not everything on your board is weather-sensitive, and treating it all the same just makes you paranoid. Get specific. On most commercial and multi-family jobs, the real constraints break down like this:
- Concrete flatwork and pours: Cold-weather concreting generally kicks in below 40°F, and you don't want it dropping below freezing for the first several days of curing. Hot-weather placing gets dicey above roughly 90°F because of flash set and plastic shrinkage cracking. Rain on fresh flatwork before it sets is a finish-killer.
- Masonry: Mortar doesn't like cold. Below about 40°F you're into cold-weather masonry procedures, heated materials, and protection, which adds cost and time you'd rather schedule around than react to.
- Roofing and waterproofing: Most single-ply and self-adhered membranes have a minimum application temperature (frequently around 40°F, sometimes higher), and adhesives won't grab on a damp deck. Torch and hot-mop work has its own wind and moisture limits.
- Painting and coatings: Read the data sheet, but you're usually looking at a temperature floor, a dew-point spread you have to stay above, and no rain on fresh exterior coating.
- Crane and lift operations: Wind is the killer here. Many tower and mobile crane operations stand down around 20–30 mph depending on the load and the manufacturer's chart, and a light panel or a big form catches wind like a sail long before the crane itself is at its limit.
- Earthwork and excavation: Rain turns your subgrade to soup. Wet clay won't compact, and you'll be pumping trenches instead of setting pipe.
Tag those activities in your plan. Everything else — interior framing, drywall, MEP rough-in behind a dried-in building, most finish work — is weather-independent and becomes your rainy-day inventory. That distinction is the whole game.
Read the forecast into the three-week window, not just tomorrow
Daily weather is a field decision. Scheduling is a planning decision, and it lives in your look-ahead. When you're building a weekly work plan and looking three to four weeks out, you're not trying to predict the temperature on a specific Thursday — nobody can. You're managing probability.
Here's the practical rule of thumb on forecast confidence: the 24–48 hour window is solid enough to commit crews around. The three-to-five day window is good for staging and pre-positioning — getting protection materials on site, warning the pump operator, giving a sub a heads-up. Beyond about seven days, treat it as climate, not forecast. You're not scheduling to a ten-day icon; you're asking "is this the season and the region where I should expect to lose pour days," and building buffer accordingly.
That's why weather belongs in a rolling look-ahead rather than a static bar chart. A tool like LookAheadWall shows your weather-sensitive activities laid out by location and week, so when a front changes the picture you can see at a glance which pours, lifts, or roofing days are exposed and slide them — instead of finding out at the tailgate meeting.
Build the swap before you need it
The single most valuable habit in weather planning is keeping a bench of indoor, weather-independent work ready to activate. When the outdoor plan dies, you don't send people home — you flip to the bench. On a job that's dried-in, that bench is deep: drywall, in-wall rough-in, insulation, blocking, fire-stopping, prepping the next area. On a job that's still open, the bench is thinner and you have to protect it harder.
The failure mode I see constantly is a superintendent who has the swap in his head but never told the subs. Come the rain day, the framer's already released his crew to another job because nobody gave him a reason to expect indoor work. The swap only works if it's pre-negotiated. In your weekly sub coordination, say it out loud: "If Wednesday's pour washes, I need your rough-in crew on Building C instead — keep them available." Now it's a plan, not a scramble.
A couple of coordination gotchas that bite people:
- Curing windows outlast the rain. A washed-out pour doesn't just cost the pour day. If you slide the slab two days, everything stacked on top of it — wall layout, MEP underslab sign-off if it's a second pour, the whole trade flow behind it — slides too. Model the downstream ripple, not just the missing day.
- Protection is its own activity. Blankets on cold concrete, tenting a masonry wall, ballast against wind — that's labor and material that has to be on site before the weather, not ordered the morning of. Put it on the schedule as a real task.
- The batch plant and the pump have lead times. You can't cancel a pour at 6 a.m. for free, and you can't conjure one on a clear day with no notice. Give and get 24–48 hours where the trades allow it.
Phase the big weather risks against the calendar
Some weather planning happens a year before the storm. If you're setting a baseline schedule and you know your region's patterns, sequence the weather-sensitive scopes to land in favorable seasons. Don't plan the bulk of your exterior masonry and roofing for the dead of winter in a cold climate if the logic lets you get dried-in first. Don't schedule mass excavation for the wettest month on record if you can pull it earlier.
You already know your local pattern in your gut — the afternoon thunderstorms that roll in every summer day at 3, the January stretch where nothing cures, the spring mud season. Historical weather data just puts numbers on that instinct so you can defend the sequencing to an owner who's asking why you're not pouring in February. Plan to the typical bad month, not the optimistic average, and you'll stop writing recovery schedules every spring.
Document weather like you'll end up arguing about it — because you will
Here's the unglamorous part that pays for itself the one time it matters. On most contracts, weather delay is only excusable if it's abnormal — worse than the typical conditions for that time and place — and if it actually hit work on the critical path. To win that argument at the end of the job, you need contemporaneous records, not memory.
Capture it daily, and capture specifics, not "rainy." Log the measured temperature, precipitation amount, wind speed, and what it actually stopped. "0.8 in. rain, subgrade unworkable, excavation crew of 6 idle, pour of slab-on-grade Area B pushed from 6/12 to 6/15" is a claim. "Bad weather, no work" is nothing. Tie the condition to the specific affected activity and its schedule impact. The daily log in your field software should make this a thirty-second habit, and pulling actual observed data from a nearby station beats eyeballing the sky for defensibility.
Two things owners' reps look for and love to deny: weather that wasn't actually abnormal for the season, and delays to work that wasn't controlling the schedule anyway. Your look-ahead is your evidence for the second one — it shows what was driving the job that week and that the lost activity was really on the critical path, not float you had to spare.
Track weather as a variance reason, not an excuse
If you're running a disciplined weekly work plan, you're already measuring how much of what you promised actually got done and why the misses happened. Weather should be one of your logged reasons for a missed commitment — and tracking it honestly over a few months tells you something useful: how many plan failures are genuinely weather versus weather being the convenient scapegoat for a coordination miss.
When you see, say, that weather accounts for a real chunk of your misses in one quarter, you can calibrate. Add buffer to weather-sensitive scopes during the bad season. Deepen the indoor bench. Front-load protection. That's the loop — plan, measure the misses, adjust the plan — and it's how weather stops feeling random and starts looking like a managed line item.
Keep the owner ahead of the weather, not behind it
The last piece is communication, and the principle is simple: an owner who hears about a weather risk three weeks early trusts you; an owner who discovers it as a delay at closeout does not. When your look-ahead shows a stretch of exposed pours during a forecast wet spell, say so in your report before it happens. "We've got four weather-sensitive pours in the next three weeks; here's the protection plan and here's the indoor work we'll shift to if we lose days." That's a superintendent in control of the job.
Multi-site teams have the added wrinkle that weather is local — a front hammering one project might miss another twenty miles away — so plan each site to its own conditions rather than one blanket rule.
You can't control the weather. You never will. But nearly everything that makes weather expensive — the wasted crew day, the botched pour, the denied delay claim, the surprised owner — comes from reacting instead of planning. Fold weather into your look-ahead, keep an indoor bench pre-negotiated with your subs, document like you'll defend it, and the sky goes from being the thing that runs your schedule to just another variable you plan around. That's the whole difference between the two mornings we started with.