Rain Delay Documentation: The Complete Guide for Civil Contractors

March 2026 · 11 min read

Rain is the most common cause of construction delays. It is also the most commonly under-documented. Writing "rain day" in your daily log is not documentation — it is a note. It tells a claims reviewer nothing about how much it rained, what work was affected, how long the site was down, or whether the delay was excusable under your contract.

The difference between a rain delay claim that succeeds and one that fails is almost never whether the rain actually happened. Everyone knows it rained. The difference is whether the contractor can prove the rain was unusually severe, that it impacted critical path work, and that proper notice was given — all supported by contemporaneous records created on the day it happened, not weeks later when someone decided to file a claim.

This guide shows you how to turn rain events into defensible delay claims. What to record, how to measure impact, and how to build evidence packages that hold up in disputes. If rain also caused property damage or equipment loss, you will need separate insurance documentation — see our guide on construction documentation for insurance claims.

Why Rain Delay Claims Fail

Most rain delay claims fail for one of three reasons. Understanding these failure points is the first step to avoiding them.

1. The Contract Provisions Were Not Followed

Every construction contract has specific provisions governing weather delays. These provisions define what qualifies as an excusable weather delay, how many rain days are already built into the schedule, and what notice requirements must be met. Contractors who do not read and follow these provisions to the letter lose their claims before the evidence is even reviewed.

2. The Records Are Inadequate

A daily log that says "rained all day, no work" is not adequate documentation for a delay claim. It does not state how much rain fell, when it started and stopped, which activities were affected, what crews did, or how long the site remained unworkable after the rain stopped. Claims reviewers, mediators, and judges need specifics. Vague records produce vague claims, and vague claims get denied.

3. There Is No Impact Correlation

Rain alone does not create an excusable delay. The rain must impact critical path activities. If it rained on Tuesday but the only scheduled work was interior electrical rough-in on the third floor, the rain did not delay the project. Contractors who document rain without connecting it to specific schedule impacts are documenting weather, not delays.

What Your Contract Says About Rain Delays

Before you can document rain delays effectively, you need to understand how your contract defines them. Not all rain days are created equal in the eyes of a construction contract.

"Adverse Weather" vs. "Unusually Severe Weather"

This is the distinction that matters most in rain delay claims. Most contracts do not grant time extensions for ordinary rain. Rain is expected. It is built into the project schedule. What contracts typically allow extensions for is unusually severe weather — rainfall that exceeds what a reasonable contractor should have anticipated based on historical data for the project location.

Some contracts use the term "adverse weather" more broadly, but even then, the contractor usually must demonstrate that conditions exceeded normal expectations. The bar is not "it rained." The bar is "it rained significantly more than historical averages predicted for this location and time period."

How Contracts Define Excusable Rain Days

Most well-drafted construction contracts establish a baseline for expected rain days using historical weather data — typically NOAA 10-year averages for the nearest reporting weather station. The contract may specify a monthly allowance of anticipated rain days or a total allowance for the project duration.

For example, a contract might state: "The contractor has included 8 anticipated weather days per month based on 10-year NOAA averages for the project location. Time extensions for weather delays shall only be considered for weather days exceeding this allowance." Under this provision, the first 8 rain days each month are on the contractor. Only rain days beyond the allowance are potentially excusable.

Some contracts go further and define what constitutes a "rain day" — for instance, any day with measurable precipitation exceeding 0.10 inches, or any day where precipitation prevents work for more than 50% of the scheduled shift. Know your contract's definition. It determines what counts.

Notice Requirements

This is where many contractors lose their rain delay claims entirely. Most contracts require written notice of a delay event within a specific timeframe — commonly 48 to 72 hours, though some allow up to 10 or 14 days. The notice must typically be directed to a specific person (the owner's representative, the project manager, or the architect) and must be in a specified form.

Missing the notice deadline can forfeit your right to claim the delay regardless of how well-documented the rain event was. If your contract says 72-hour notice and you send notice on day five, the owner can reject the claim on procedural grounds alone. Set a system — flag every potential delay event the day it happens, and send notice immediately.

The Rain Delay Documentation Checklist

Every rain event on your project should be documented with the following information, captured the day it occurs. This is not a claim form — this is what your daily report should contain every time rain affects the site. For general best practices on writing daily reports that hold up in disputes, see our guide on how to write a construction daily report.

Precipitation Amounts

Record how much rain fell, when it started, and when it stopped. "It rained" is useless. "Rain began at 5:45 AM, steady through 11:30 AM, intermittent until 1:15 PM, total accumulation approximately 1.8 inches" is documentation. If you have a rain gauge on site, use it. If not, note your estimate and cross-reference with the nearest NOAA weather station data after the fact.

Impact on Specific Activities

Which work was affected by the rain, and which was not? Be explicit. "Earthwork grading at Lot 12-15 halted due to saturated subgrade. Structural steel erection at Building A suspended due to wet conditions on elevated deck. Interior drywall finishing at Building C continued unaffected." This level of detail shows that you assessed the rain's actual impact on each active work activity rather than writing off the entire day.

Site Conditions

Rain impact often extends well beyond the rain event itself. Document the conditions that prevent work from resuming: standing water in excavations, saturated soil that cannot support equipment, impassable access roads, flooded laydown areas. These conditions are the reason recovery time exists — and recovery time is often where the real schedule impact lies.

Crew Disposition

What happened to your crews? Were they sent home at the start of the shift? Did they arrive and then get sent home after two hours? Were they reassigned to covered work? Were they kept on standby? Each scenario has different cost and schedule implications. Document the headcount, the trades affected, and the decision made — including the time the decision was made.

Equipment Status

Record which equipment was idle, which was relocated to protected areas, and which continued operating. A crane sitting idle costs money. A dozer that cannot operate on saturated soil costs money. An excavator relocated to a covered staging area costs money. This information feeds directly into the cost component of a delay claim.

Recovery Time

This is the most frequently underdocumented element of rain delays. The rain stops at noon, but when does work actually resume? If the soil needs 48 hours to dry before earthwork equipment can operate without rutting the subgrade, that is two additional days of delay from a single rain event. Document when rain stopped, when work resumed, and what conditions had to be met before resumption was possible.

Photos

GPS-tagged, timestamped photos are the strongest evidence in any delay claim. Photograph flooded excavations, saturated soil, standing water on access roads, idle equipment, impassable haul routes, and any other condition that demonstrates why work could not proceed. Take photos during the rain event and again the following day to document lingering conditions. A digital daily report tool like BuildLog automatically embeds GPS coordinates and timestamps in every photo, creating evidence that is difficult to dispute.

How to Measure and Prove "Unusually Severe Weather"

Proving that rain was unusually severe — not just inconvenient — is the threshold for most excusable weather delay claims. Here is how to build that proof.

NOAA Historical Data Comparison

The National Oceanic and Atmospheric Administration (NOAA) maintains historical precipitation data for thousands of weather stations across the United States. Pull the data for the station nearest to your project site. You need monthly precipitation totals and the number of days with measurable precipitation for the past 10 years.

10-Year Averages for Your Project Location

Calculate the 10-year average monthly rainfall and average number of rain days per month for your project location. This becomes your baseline — what a reasonable contractor should have anticipated. Present this data in a table: month, 10-year average precipitation, 10-year average rain days, actual precipitation during your project, actual rain days during your project.

Any month where actual rainfall exceeds the 10-year average is a candidate for unusually severe weather. The greater the variance, the stronger the claim. If the 10-year average for April is 3.8 inches and your project site received 7.2 inches, that is a compelling data point.

Threshold Documentation in Your Contract

If your contract specifies a rain day allowance, compare actual rain days against the allowance month by month. Produce a running tally: "Through April, the contract allows 32 rain days; actual rain days to date: 47; excess: 15 days." This running count, supported by daily logs that document each rain day individually, is the backbone of your time extension request.

Building the Rain Delay Evidence Package

When it is time to file a rain delay claim, you need to assemble your documentation into a coherent evidence package. If you have been documenting properly all along, this is an assembly exercise, not a research project.

Daily Logs with Specific Precipitation Data

Your daily reports are the primary evidence. Filter them to show every day where rain or rain-related conditions affected work. Each entry should already contain precipitation amounts, impact descriptions, crew disposition, equipment status, and recovery time — because you documented all of that on the day it happened.

Corroborating NOAA Records

Pull official NOAA weather data for every rain day you are claiming. Your daily log says 1.8 inches; the NOAA station two miles away recorded 1.6 inches. This corroboration strengthens your records. If there is a discrepancy, note it and explain it — localized storms can produce significant variation over short distances.

Photo Documentation Timeline

Organize your GPS-tagged photos chronologically. For each rain event, include photos from the day of the rain showing active conditions and photos from subsequent days showing lingering impacts. A photo of standing water in an excavation at 7 AM the day after rain stopped is powerful evidence that the site was not workable despite clear skies.

Crew and Equipment Impact Reports

Summarize the labor and equipment impacts across all rain delay days. Total crew-hours lost, equipment idle time, and subcontractor impacts. This feeds into the cost component of your claim and demonstrates the magnitude of the delay beyond just calendar days.

Schedule Impact Analysis

This is the critical path correlation. Show which rain delay days impacted activities on the critical path and how the cumulative delay pushed the project completion date. A simple comparison of as-planned versus as-built schedule, with rain delay days highlighted on the critical path, is often sufficient for time extension requests. More complex claims may require a formal schedule analysis by a claims consultant.

Common Mistakes in Rain Delay Documentation

Even contractors who understand the importance of rain delay documentation make these mistakes. Avoiding them is the difference between a claim that succeeds and one that stalls in review.

Documenting Rain but Not Impact

"Rain from 6 AM to 2 PM, approximately 1.2 inches." That is good weather documentation. It is not delay documentation. Without a description of which activities were affected, which crews were idle, and how the rain altered the day's planned work, you have documented a weather event but not a delay event. Every rain entry in your daily report must connect the weather to its impact on work.

Missing the Notice Deadline

If your contract requires 48-hour written notice of delay events, a daily report entry alone may not satisfy that requirement. You may need to send a separate formal notice letter to the owner's representative within the contractual timeframe. Check your contract. Set reminders. A legitimate 20-day rain delay claim can be denied entirely because notice was sent on day four instead of day two.

Not Tracking Recovery Days

The rain stopped on Tuesday afternoon. Work resumed on Thursday morning. What happened on Wednesday? If your log for Wednesday says "clear skies, crews mobilizing, preparing to resume grading" without explaining that the subgrade was still saturated and needed 24 hours to dry, you have a gap in your delay narrative. Document every recovery day with the same rigor as the rain day itself — what conditions existed, what testing or inspection was done, and why work could not yet resume.

Failing to Distinguish Between Rain Days and Rain Impact Days

It rained for 15 minutes during a lunch break and accumulated 0.03 inches. Is that a rain day? Technically, yes — there was measurable precipitation. Did it impact any work? No. Claiming it as a delay day undermines the credibility of your entire claim. Be honest and precise. Claim only the days where rain or its aftereffects actually prevented or delayed scheduled work. A credible claim with 18 well-documented impact days is far stronger than a padded claim with 30 days that includes days with negligible impact.

Frequently Asked Questions

How many rain days should I expect on a construction project?

The number of expected rain days depends on your project location and time of year. Most contracts define expected rain days using NOAA 10-year historical averages for the nearest weather station. A 12-month project in Atlanta might have a contract allowance of 95 to 110 rain days, while a project in Phoenix might only allow 25 to 35. Rain days exceeding the contract allowance are potentially claimable as excusable delays, provided you can demonstrate the rainfall was unusually severe and that it impacted critical path activities.

What is the difference between a rain day and a rain impact day?

A rain day is any day where measurable precipitation occurs at the project site. A rain impact day is a day where rain or its aftereffects actually prevented or delayed scheduled work. These are not the same thing. It might rain for 20 minutes during lunch with zero impact on operations. Conversely, a half-inch of rain on Monday might make the site impassable until Wednesday, creating two rain impact days from one rain day. For delay claims, rain impact days are what matter. Your documentation needs to record not just precipitation but its specific effect on scheduled work.

How do I prove rain was "unusually severe" for a delay claim?

Compare actual rainfall during your project to historical averages for the same location and time period. Pull NOAA historical precipitation data for the nearest weather station covering the past 10 years. Calculate monthly average rainfall and average rain days per month. Then compare actual monthly rainfall against those averages. Present this as a side-by-side table — expected versus actual, by month — with your daily logs providing the day-by-day detail behind the numbers.

What is the notice requirement for rain delay claims?

Most construction contracts require written notice of a delay event within 48 to 72 hours, though some allow up to 10 or 14 days. Missing the notice deadline can forfeit your right to claim the delay, even if it was legitimate and well-documented. Check your contract for the exact notice period, who must receive notice, and what form it must take. BuildLog's timestamped daily reports serve as contemporaneous documentation supporting your formal notice.

Should I track rain delays even if I do not plan to file a claim?

Yes, always. You cannot predict at the start of a project whether you will need to file a delay claim. If a project runs late and rain was a contributing factor, you need documentation going back to day one. Contemporaneous records created in real time are far more credible than records reconstructed after the fact. Daily logging of weather conditions and work impact takes minutes per day. Reconstructing six months of weather delay history costs thousands in consultant fees and produces weaker evidence. Document every rain event as if you will need it.