Construction Weather Delay Documentation: What Your Contract Requires

The U.S. construction industry generated $2.2 trillion in spending in 2024. Nearly every commercial construction contract includes provisions for weather delays, including force majeure clauses, adverse weather definitions, or excusable delay provisions. Yet when weather actually disrupts a project, many contractors lose their entitlement to time extensions simply because they didn’t document the conditions properly.

Whether you’re a general contractor, subcontractor, project manager, or construction attorney, understanding what your contract requires for weather delay documentation, and how to provide it, matters when schedule extensions are on the line.

How Construction Contracts Handle Weather

Most standard construction contracts address weather delays, though the specific language varies significantly. Understanding your contract’s approach is the first step.

The AIA A201-2017 (General Conditions of the Contract for Construction) provides that the contractor is entitled to a time extension for adverse weather conditions documented in accordance with its notice and claims provisions. The key phrase is “documented in accordance with”: without proper documentation, the entitlement may not hold up.

ConsensusDocs 200 lists weather among justifiable delays and specifically references events beyond the contractor’s control. EJCDC C-700 (2013) addresses force majeure events including abnormal weather, providing that such events may entitle the contractor to a change in contract times but generally not a change in contract price.

FIDIC contracts (Red, Yellow, and Silver Books) use the term “exceptionally adverse climatic conditions” and vary in whether the contractor can recover prolongation costs in addition to time extensions.

The common thread across these contract forms: weather delays generally must be documented, noticed within a specific timeframe, and shown to have affected the critical path of the project.

What “Documented” Actually Means

Construction contracts that reference weather delays typically require several elements of documentation.

Written notice within a specified timeframe. Most contracts require the contractor to provide written notice of a weather delay within 24 to 72 hours of the event. Some contracts have even stricter requirements. Missing this notice window can jeopardize the right to a time extension, even when the delay clearly qualifies.

Evidence that the weather event occurred. This means objective, third-party weather data, not the superintendent’s notes that it rained all day. Daily weather logs kept by site personnel are helpful supplemental documentation, but they’re stronger when supported by records from recognized weather data sources.

Proof that the weather was abnormal or adverse. This is where contracts diverge and disputes arise. Many contracts distinguish between normal weather (which the contractor should have anticipated and built into the schedule) and abnormal or adverse weather that may justify an extension. Establishing this distinction involves comparing actual conditions against historical averages for the project location, and different parties may disagree on what constitutes a sufficient historical baseline.

Demonstrated impact on the critical path. A weather delay that affected non-critical activities may not justify extending the completion date. The delayed work typically needs to be on the critical path at the time the weather event occurred. This usually requires an updated schedule showing the impact.

Weather data from a recognized source. Contract language increasingly references weather data from the nearest official station or similar phrasing. NOAA, the National Weather Service, and NCEI are widely recognized as authoritative sources. Data from personal weather stations, phone apps, or unverified websites may face challenges during review.

The Daily Weather Log Problem

Most construction projects keep daily logs that include weather observations. The superintendent notes temperature, precipitation, wind, and whether work was performed. These logs are essential, but they have limitations.

Daily logs reflect one person’s observation, typically made once or twice per day. They don’t capture hourly variations, they don’t record official weather station data, and they’re created by an interested party. An owner or architect reviewing a delay claim will reasonably point out that the superintendent’s log is not an independent record.

The strongest weather delay documentation pairs site-specific daily logs with official weather station data. The log shows what happened on the ground at the project site. The official data confirms that conditions were consistent with what was recorded at recognized meteorological stations nearby.

Force Majeure vs. Adverse Weather

These two categories of weather delays are treated differently in most contracts, and the distinction matters.

Adverse weather (rain, cold, heat, or wind that exceeds defined thresholds or historical norms) may allow a contractor to request a time extension, depending on contract terms, but generally not additional compensation. The logic is that some weather delays are foreseeable, but when actual conditions exceed what’s normal for the area and season, the contractor shouldn’t be penalized for schedule impact.

Force majeure weather events (hurricanes, tornadoes, extreme flooding, unprecedented storms) typically qualify under the contract’s force majeure clause and may entitle the contractor to both time extensions and additional costs, depending on contract language. These events must be genuinely unforeseeable and beyond anyone’s control.

The documentation requirements are similar for both, but force majeure claims generally carry a higher burden of proof. You need to demonstrate that the event was beyond your reasonable control, that you took reasonable steps to mitigate the impact, that you provided timely notice, and that the event actually prevented performance, not just made it more difficult or expensive.

Multi-Day Documentation Requirements

Construction weather delays often span multiple days: a week of continuous rain, a month with abnormal snowfall, or a series of freeze-thaw cycles that prevented concrete work. Documenting these multi-day events requires daily weather records for each affected day.

This is where the practical burden gets heavy. A contractor claiming 30 weather delay days over the course of a project needs 30 days of weather data, each showing conditions that exceeded the contractual threshold. Each day may need to be cross-referenced against the schedule to show critical path impact.

Weather documentation covering an entire date range in a single, structured package simplifies this process compared to assembling individual data requests day by day.

What Happens When You Don’t Document

The consequences of inadequate weather delay documentation are straightforward and expensive. A time extension request gets denied because the conditions can’t be verified against the contractual threshold. Liquidated damages accrue for each day past the contracted completion date. The project is completed late, and the financial responsibility falls on the contractor, not because the delay was the contractor’s fault, but because the documentation wasn’t there.

Courts and arbitration panels consistently enforce contractual notice and documentation requirements. A valid delay claim can be weakened or lost entirely when notice and documentation provisions aren’t followed.

Building a Strong Weather Delay Claim

Here’s a practical framework for documenting construction weather delays.

Before the project starts, identify the nearest official weather stations and establish a baseline for normal weather at the project location. Know your contract’s definition of adverse weather and its notice requirements.

During the project, maintain daily weather logs at the site, noting temperature, precipitation, wind, and work impact. When weather prevents or delays work, issue written notice within the contractual timeframe, even if you’re not sure yet whether the delay will affect the critical path.

For each weather delay day, obtain archived observation data from NOAA/NWS stations that supports your site observations. This data should include hourly conditions, precipitation amounts, temperatures, wind speeds, and any active NWS alerts or warnings.

When submitting a delay claim, package your weather documentation with the updated project schedule showing critical path impact. Include daily site logs, archived weather observation data, NWS alerts, and a clear narrative connecting the weather conditions to the specific work activities that were delayed.

The Cost of Getting It Right

For a contractor working on a project with $5,000/day in liquidated damages, even a few undocumented weather delay days represent significant financial exposure. A full month of unsupported weather delays could mean $150,000 or more.

Compared to those numbers, the cost of obtaining structured weather data for each delay day is small. The weather data exists in NOAA’s archives. The practical challenge is getting it into a format that’s organized, consistent, and ready to include in a delay claim package.

The Bottom Line

Weather is an unavoidable factor in construction. When it causes delays, the contract determines what documentation is required. Maintaining consistent records throughout the project, including both site observations and archived weather station data, simplifies the process if schedule extension requests become necessary.