Weather Day Documentation: How to Claim Weather Delays That Actually Hold Up

Most construction contracts — AIA A201, ConsensusDocs, federal, and custom forms — allow time extensions for unusually severe weather. The qualifier "unusually severe" is important: normal seasonal weather doesn't count. A contractor expecting rain in spring has to plan for it; rain substantially beyond normal seasonal patterns can justify a time extension. The contractor's ability to claim weather days depends entirely on what they can prove with contemporaneous documentation.

Weather delay claims fail most often because of documentation gaps. A contractor who didn't log weather conditions daily, didn't track which activities were impacted, and didn't establish what constitutes unusual weather for the location submits a claim based on recollection — which gets denied. A contractor with daily logs, productivity documentation, and NOAA weather station data submits a defensible claim that typically gets approved. The difference is operational discipline during the project, not negotiation skill at the claim.

What Counts as Adverse Weather

Contracts vary but common adverse weather definitions include:

Specific thresholds depend on the contract and the work. Steel erection has different weather sensitivity than interior drywall. Concrete placement has cold and hot weather limits. The contract or the contractor's safety program should specify the thresholds that make specific activities infeasible.

Baseline Weather Expectation

Weather delay claims require showing the weather was worse than expected — which requires establishing what was expected:

Many contracts include an expected-weather-days table — e.g., "5 adverse weather days per month" — and only days beyond that expectation can be claimed. Understanding the baseline prevents claiming what the contractor already built into the schedule.

Daily Weather Log

The foundation of weather documentation is a daily log:

Daily logging is the discipline. A site superintendent who logs weather conditions every day — even days with no impact — creates the complete record that makes claims credible. Logging only on bad days (which is what most projects do) leaves gaps that opposing parties exploit.

Productivity Impact Quantification

Beyond showing weather occurred, claims require showing weather's impact:

A weather day claim that just says "rained, lost a day" is weak. A weather day claim that says "1.2" of rain starting at 7am caused foundation excavation crew to be sent home at 8am; afternoon work on indoor framing proceeded at 60% normal productivity due to wet conditions; total equivalent lost hours: 18 of 30 planned" is substantive.

Critical Path Analysis

Time extension eligibility typically requires critical path impact:

Weather disrupting non-critical work doesn't extend the project. Weather disrupting critical path work may. Careful critical path analysis at the time of impact (not reconstructed later) supports the claim.

Contractual Notice Requirements

Weather claims typically have notice requirements:

Missing the notice window can forfeit the claim. Monthly claim submissions summarizing all weather days in the period (with notice filed promptly for each) is a practical compliance pattern. Notice is procedural but unforgiving.

Cost Impact (Or Lack Thereof)

Most contracts provide time-only extension for weather — not cost:

Contractors should manage expectations: weather delays typically extend the deadline without paying for the delay. Exceptional weather (hurricanes, fire, extreme events beyond normal variance) may be force majeure with different treatment. Reading the specific contract is essential.

Weather Day Aggregation

Claims often aggregate weather days over a period:

Aggregation makes the claim understandable. A stack of 30 daily logs is harder to evaluate than a monthly summary with daily detail attached. The summary shows the total; the details support it.

Independent Verification

Contractor weather observations are strengthened by independent data:

Independent data confirms the contractor's observations. "Our log shows heavy rain; NOAA confirms 1.8" of rain at the nearest station" is stronger than just contractor logs alone. On important claims, specialist weather documentation services provide certified reports that are hard to dispute.

Common Weather Claim Failures

Weather claims fail in consistent ways:

Each failure mode is preventable by operational discipline during the project. Fixing weak weather documentation after the fact is nearly impossible; doing it right throughout the project is inexpensive.

Concurrent Delays

Weather delays sometimes occur concurrently with other delays:

Concurrent delay analysis requires detailed day-by-day information. Without good documentation, concurrent delay arguments fail on both sides — neither party can prove what caused what.

Bottom Line

Weather day documentation is operational discipline during construction that produces defensible time extension claims. Daily logs including weather conditions, activity impacts, and productivity effects; independent weather data verification; critical path analysis showing project-level impact; timely contractual notice; and aggregation that makes the claim understandable together produce weather claims that get approved. Contractors who document weather routinely have claims that hold up; contractors who reconstruct documentation at claim time typically don't. The documentation cost is minimal — minutes a day of field staff time — and produces substantial value when weather claims need to be substantiated. Weather delay claims won't typically produce cost recovery, but the time extension they provide protects against liquidated damages that otherwise would apply. For projects in weather-variable locations, weather documentation discipline is one of the highest-ROI operational practices a contractor can maintain.