Esc

↑↓ move↵ openIndex · Pagefind

How to document weather delays so a time extension holds up

Rain, wind, cold and heat stop work on every job, but a weather day only becomes extra time if you can show the weather was unusual, that it stopped critical work, and that you gave notice. Here is what to record each day, how to tally lost days against the contract's allowance, and a worked example for one month.

Charley Forey6 min readFieldDaily logsScheduling
On this page
  1. Step 1: Read what the contract says about weather
  2. Step 2: Record the weather on site, twice a day
  3. Step 3: Record the impact, not just the weather
  4. Step 4: Tie it to the critical path
  5. Step 5: Tally lost days against the allowance each month
  6. Step 6: Give notice and request the time
  7. Worked example: one January
  8. Common mistakes
  9. How os.construction handles it
  10. FAQ

To document a weather delay, record the weather on site every day, record which work it stopped or slowed and for how long, show that the affected work was on the critical path, compare the lost days with the normal weather the contract or historical records allow for, and give written notice within the contract’s deadlines. “Rained today” proves nothing. “Rain from 7:10 am, 0.8 in. by noon; area C slab pour cancelled; 6 concrete workers sent home at 9:00” is the start of a time extension.

Weather is the most common delay on most jobs, and the most commonly lost argument. Not because the rain didn’t happen, but because the records show weather without impact, or impact without showing that the weather was any worse than the contract already expected.

Check your contractWhether weather days are excusable, how they’re counted, what notice is required and whether any cost is recoverable all depend on the contract. This post covers the records; the contract decides what they’re worth.

Step 1: Read what the contract says about weather

Before the first bad day, find:

  • Whether weather is an excusable delay, and whether it is only “abnormal” or “unusually severe” weather.
  • A weather allowance: some contracts or specifications list anticipated adverse weather days per month, sometimes with a definition of what counts as a lost day.
  • Notice requirements: how and when to notify, and whether each event needs its own notice or a monthly summary is enough.
  • How the schedule must show weather, for example through a weather allowance in the calendar of weather-sensitive activities.
  • Whether time is the only remedy. Many contracts give time but not money for weather. Some have a no damages for delay clause that limits cost recovery more broadly.

Step 2: Record the weather on site, twice a day

The superintendent’s daily report is the primary record. At least morning and afternoon:

  • Sky, temperature, wind, and precipitation with start and stop times and an amount if you have a rain gauge.
  • Ground and site conditions: standing water, mud, frozen ground, snow cover.
  • Conditions that matter for specific work, such as wind for a crane pick or temperature for a concrete pour or a roofing product.

Official station data is useful for comparison later, but it isn’t a substitute for what happened at your site. A storm can hit the site and miss the airport.

Step 3: Record the impact, not just the weather

For each weather event, record:

  1. Which activities were stopped or slowed, by name and location.
  2. Start and end times of the stoppage.
  3. Crews and equipment affected: companies, headcount, hours lost, idle equipment.
  4. What you did instead: moved crews to interior work, sent them home, protected work.
  5. After-effects: the days after the rain when the site was too wet for earthwork. These often count, but only if you record them as weather-caused.

Step 4: Tie it to the critical path

Weather that stopped only work with float usually doesn’t delay completion. For each lost day, note whether the stopped work was on the critical path or near it in the current schedule update. A weather day on interior finishes under a dry roof rarely supports an extension; a weather day on the foundation pour that controls the whole job usually does, subject to the contract.

Step 5: Tally lost days against the allowance each month

At the end of each month, list the days where weather stopped critical work, and compare the count with the allowance for that month from the contract, or with what’s normal from historical records if the contract has no allowance. Only the days beyond the allowance are usually the basis of a request. Keep the tally running, so the request is a summary of records already in place, not a reconstruction.

Step 6: Give notice and request the time

Notify in writing as the contract requires, often per event and with a request for the specific number of days once the month’s tally is known. Attach the daily reports, the tally and, if needed, the schedule fragment showing the critical work affected. If the time is disputed, the analysis methods in our posts on extension of time evidence and concurrent delay apply to weather like any other delay.

Lost weather days against the allowanceA bar chart for three months. January: allowance 4 days, actual lost critical days 7, so 3 days beyond the allowance. February: allowance 3, actual 2, none beyond. March: allowance 3, actual 5, 2 beyond. Only the days beyond the allowance are typically the basis of an extension request.LOST CRITICAL DAYS VS ALLOWANCE473235JAN: +3FEB: 0MAR: +2ALLOWANCEACTUAL LOST
Only days beyond the allowance usually support a request. Illustrative figures.

Worked example: one January

Illustrative exampleA made-up project, contract allowance and weather.

The contract: time only for weather delays beyond the anticipated adverse weather days in the specifications, which list 4 days for January. A day counts if weather or its after-effects stop critical work for at least half the working day.

The work: foundations and underground utilities, all on the critical path this month.

Date Site weather Work stopped Hours lost Critical? Counts?
Jan 6 Rain 0.9 in., from 6:30 am Footing excavation, area B 8 Yes Yes
Jan 7 Dry, standing water in footings Excavation (pumping only) 6 Yes Yes, after-effect
Jan 13 Rain 0.3 in., stopped 10:00 Started late 3 Yes No, under half day
Jan 14 Low 18°F, high 29°F Footing pour postponed, below the spec cold-weather limit 8 Yes Yes
Jan 20 Snow 3 in. All site work 8 Yes Yes
Jan 21 Snow cover, frozen ground Excavation 8 Yes Yes
Jan 22 Thaw, mud Underground plumbing 5 Yes Yes
Jan 27 Rain 1.2 in. Underground plumbing 8 Yes Yes
Jan 28 Light rain Interior: none; site work moved to rebar fab 0 n/a No

Lost critical days that count: 7. Allowance: 4. Request: 3 days. The PM gave notice of each event within the contract’s deadline, with the daily report attached, and at month end sent the tally with a request for 3 days, the daily reports for each counted date, and a note that January 13 was recorded but not counted.

A tally like this one shows the reviewer you’ve applied the contract’s rules yourself. Counting January 13 to get one more day would make them doubt the other seven.

Common mistakes

  • Weather without impact. “Rain” in the daily report with no work, times or crews named.
  • Impact without the critical path. A day lost on work with float rarely moves completion.
  • Ignoring the allowance. Asking for every rain day when the contract already expected four of them.
  • Missing after-effect days. The mud day after the storm is often a lost day too, if you recorded why.
  • Reconstructing at the end of the job. A year of weather rebuilt from airport data and memory is weak. A monthly tally from daily reports isn’t.
  • Late notice. Records don’t fix a missed notice deadline.
  • Asking for money by default. Many contracts give time only. Check before you price it.

The daily log checklist has the weather and delay fields to capture each day, and the schedule calendars post explains how weather allowances behave in the schedule itself. For the wider legal category, see force majeure and delay claims.

How os.construction handles it

The Daily Log has an Observed Weather Conditions section with time, sky, temperature, wind, ground and precipitation and whether it caused a delay, and a Delays section with the type, start and end, cost code and location. In the schedule, the Risk page keeps weather calendars by region and month and can tag weather-sensitive activities, as described in risk analysis. For what to look for in a daily log tool generally, see construction daily log software.

FAQ

Are weather delays excusable in construction?

Often, but usually only for weather that is abnormal for the place and time of year, and only when it actually delays the work that drives completion. Many contracts make such delays excusable for time but not compensable, meaning the contractor can get more time but not more money. Your contract's terms decide.

What counts as a weather delay day?

It depends on the contract. Commonly, a day counts when weather or its after-effects, such as mud or standing water, prevented work on activities that control the completion date for a significant part of the day. Some contracts define the threshold, for example in hours lost or rainfall amount; others leave it to the parties.

How do you prove abnormal weather?

Compare the weather you recorded on site with what is normal for that location and month. Many contracts state the expected number of adverse weather days per month; otherwise, historical records from a nearby official weather station are the usual reference. In the US, NOAA's National Centers for Environmental Information publishes historical climate data.

What should a daily report say about weather?

The conditions in the morning and afternoon, with sky, temperature, wind and precipitation, plus ground conditions. Then the impact: which activities were stopped or slowed, for how long, which crews and equipment were affected, and whether work was moved elsewhere. Weather without impact doesn't support a delay.

Can you get paid for weather delays?

Usually not, unless the contract says otherwise. Weather is commonly treated as a shared risk: the contractor gets time but bears its own cost. There are exceptions, such as when weather damage results from an owner-caused delay that pushed the work into a worse season, but those depend heavily on the contract and the facts.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Open file