Weather delays: the argument is scheduled for month seven unless the contract settles it now

Documentation: the daily habit that wins the claim

Weather claims are won or lost by records made at the time, not by arguments made afterwards. Four items, recorded daily, are enough:

• Actual conditions — temperature, precipitation, wind — from a defensible source, ideally the nearest official station rather than someone's memory.
• What work was scheduled that day and whether it was weather-exposed.
• What actually happened: crews sent home, work moved indoors, partial day, site inaccessible.
• Photographs, which take fifteen seconds and settle disputes that words do not.

The mistake that costs most is claiming only the days of the storm. The days after are frequently the real loss — a saturated site that cannot take equipment, an excavation that must be dewatered, concrete that cannot be placed on frozen ground. Those days must be documented with the same discipline, and the causal link to the weather event must be recorded as it happens rather than reconstructed later.

Float: who owns it and why it disappears

Float is the amount of time an activity can slip without delaying the project. It is the most valuable and least understood asset on a schedule, and the dispute over who owns it sits underneath most delay claims.

Three positions exist in practice: the owner owns float, the contractor owns float, or the project owns it and it is consumed first-come, first-served. Many contracts now state the last of these explicitly. Whichever applies, the practical consequence is the same — float consumed early by anyone is not available later to anyone, and the party who needed it in month eight is the one who feels the loss.

Two behaviors protect a builder regardless of the clause. The first is transparency: showing float in the schedule and updating it monthly, so its consumption is visible and attributable. The second is timing: notifying the moment an owner-caused event consumes float, rather than absorbing it quietly and raising it when the project is late. A delay absorbed without notice is, in practice, a delay accepted.

A project in numbers

A $6.8M ground-up project, fourteen months, contract allowing time-only relief for unusually severe weather, with the baseline defined against historical averages.

• Baseline: 22 weather days inserted into the schedule for the exposed phases, based on ten-year averages for the site.
• Months 1–5: 31 weather days actually lost, of which 9 exceeded the baseline. All documented daily, with 6 additional days claimed for site recovery following two saturation events.
• Claim: 15 days submitted with dated records and photographs; 13 granted, 2 declined for insufficient documentation on a partial day.
• Months 6–14: structure dry, exposure ended at the enclosure milestone, no further weather claims.

The 13 granted days protected the builder from liquidated damages that, at the contract rate, would have totaled roughly $91,000. The two declined days are the more useful lesson: both were partial days recorded as "rain, crews sent home" without hours or photographs — the same event as the granted days, documented worse.

Planning the season instead of reacting to it

The strongest weather protection is not contractual, it is sequential. A schedule that puts weather-exposed work in the wrong season converts a manageable risk into a certainty, and that decision is made months before anyone looks at a forecast.

Four sequencing choices carry most of the benefit:

• Drive toward enclosure. Every week earlier that the building is dry removes weeks of exposure from every subsequent trade. On projects that start in autumn, enclosure is the milestone that the whole schedule should be built around.
• Front-load the earthwork. Excavation, foundations and site utilities are the most weather-sensitive activities on any project, and doing them in the wettest month of the local year is a choice, not bad luck.
• Keep protected work in reserve. Interior activities that can absorb a crew on a rain day — layout, rough-in in enclosed areas, shop fabrication — are what keeps productivity from collapsing during a bad week.
• Plan winter protection as a cost, not as an improvisation. Temporary heat, enclosures, ground thaw and cold-weather concrete measures belong in the estimate when the schedule puts that work in winter — because they will be spent either way.

When the owner wants the time back

Granting time and wanting it back is a common sequence: the days are approved, and then the owner asks whether the original date can still be met. That request is a different conversation from the delay, and confusing the two is expensive.

Three distinctions keep it clean:

Excusable delay gives time; it does not give money. Under a time-only clause, the builder absorbs the general conditions of those days — which is precisely why the days matter and why they must be claimed.

Acceleration is a change, and it is priced. Overtime, additional crews, extra shifts, expedited material and the productivity loss that comes with a crowded site are real costs. If the owner asks for the date back, that is a change order request, not a scheduling adjustment.

Constructive acceleration is the trap. It arises when a builder is entitled to a time extension, the extension is not granted, and the owner insists on the original completion date — pushing the builder to accelerate without a written change. The protection is procedural: request the extension in writing within the contract window, record the response or the absence of one, and state in writing that any effort to maintain the original date is being made under protest with costs tracked separately.

None of that is adversarial when it is routine. The builders who get into trouble are the ones who avoid the paperwork to preserve the relationship, and then discover that the relationship does not survive an unpriced acceleration either.

Six mistakes on weather and delay

• Accepting an undefined weather clause. "Unusually severe" without a baseline is an argument scheduled for month seven.
• Hiding weather allowance inside activity durations. Invisible float is consumed silently and cannot be defended.
• Claiming only the storm days. The recovery days after are frequently the larger loss.
• Reconstructing records later. Contemporaneous documentation is the entire basis of a delay claim.
• Missing the notice deadline. Most contracts require notice within a short window, and a valid claim submitted late is frequently a lost one.
• Absorbing owner-caused delay quietly. Float given away without notice cannot be recovered when you need it.

Five numbers to track

Five metrics govern schedule risk. Weather days baseline versus actual, by month, which tells you whether your allowances are realistic for your market. Days claimed versus days granted, with the reason for each denial, because the pattern of denials is a documentation diagnosis. Total float remaining on the critical path, updated monthly and shared. Notice compliance — the percentage of claim events noticed within the contract window, which is the single most common reason valid claims fail. And days from event to documented record, which should be zero, because everything about delay claims depends on records made the same day.

Frequently asked questions

Who is responsible for weather delays in construction?

It depends entirely on the contract, which generally handles weather in one of three ways: no relief at all, relief for time only, or relief for time and cost. Time-only is the most common in commercial work, meaning the builder gets additional days but not additional money, so the general conditions of those days come out of margin. What matters more than the category is the definition: unusually severe weather is the standard language and it is meaningless without a baseline, because unusual compared to what. Contracts that define the baseline — typically by reference to historical averages for the location and month — produce a factual conversation, while contracts that leave it undefined produce a negotiation in month seven, after the fact, with the builder in the weaker position.

How do you build weather into a baseline schedule?

By making the allowance visible rather than hiding it inside activity durations. Use historical data for the location and season, from public weather records, to establish how many days per month are typically lost for weather-exposed activities. Insert those days as a schedule activity the owner can see, since hidden float is invisible protection that gets consumed silently. Distinguish exposed work from protected work, because once the building is dry most trades are weather-independent and the schedule should show that the exposure ends at a specific milestone. And state the claim mechanism: what threshold constitutes a lost day, who records it and within how many days notice must be given. An owner who sees the allowance in the baseline argues about it far less later.

What documentation is needed for a weather delay claim?

Records made at the time, not arguments made afterwards. Four items daily are enough: actual conditions including temperature, precipitation and wind from a defensible source such as the nearest official station; what work was scheduled that day and whether it was weather-exposed; what actually happened, whether crews were sent home, work moved indoors, a partial day was worked or the site was inaccessible; and photographs, which take fifteen seconds and settle disputes that words do not. The mistake that costs most is claiming only the storm days — the days after are frequently the real loss, with a saturated site that cannot take equipment, an excavation that must be dewatered or concrete that cannot be placed. Those recovery days need the same discipline and the causal link recorded as it happens.

Who owns float on a construction schedule?

It depends on the contract, and three positions exist in practice: the owner owns float, the contractor owns float, or the project owns it and it is consumed first-come, first-served — the last of which many contracts now state explicitly. Whichever applies, the practical consequence is identical: float consumed early by anyone is not available later to anyone, and the party who needed it in month eight is the one who feels the loss. Two behaviors protect a builder regardless of the clause. Transparency, showing float in the schedule and updating it monthly so consumption is visible and attributable. And timing, notifying the moment an owner-caused event consumes float rather than absorbing it quietly and raising it when the project is late — because a delay absorbed without notice is, in practice, a delay accepted.

What is constructive acceleration and how do you avoid it?

It arises when a builder is entitled to a time extension, the extension is not granted, and the owner insists on the original completion date — effectively forcing acceleration without a written change order. Three distinctions keep the situation clean. Excusable delay gives time but not money under a time-only clause, which is precisely why the days must still be claimed. Acceleration is a change and is priced, since overtime, additional crews, extra shifts, expedited material and the productivity loss of a crowded site are real costs — if the owner wants the date back, that is a change order request. And the protection against the trap is procedural: request the extension in writing within the contract window, record the response or its absence, and state in writing that any effort to maintain the original date is made under protest with costs tracked separately.