Weather Documentation for Civil Contractors: What Your Logs Need

Published: February 2026 | Category: Delay Claims Defense

Weather is the single most common cause of excusable delay claims on civil construction projects. Rain, extreme cold, high winds, and their aftereffects — muddy ground, frozen soil, standing water — can shut down a site for days or weeks. But you can only claim a weather delay if you documented the weather when it happened.

Most contractors know this in theory. In practice, weather documentation is incomplete, inconsistent, or missing entirely. Here’s what your daily logs actually need.

The Four Weather Data Points

Every daily log on a civil project should capture these four conditions, regardless of whether work was impacted:

Field	What to Record	Why It Matters
Temperature	Actual temp at site (e.g., “28°F at 7am”)	Proves conditions prevented concrete work, asphalt paving, or paint application
Rain	Yes/No, plus intensity if relevant	Establishes rain days for weather delay calculations
Wind	Estimated speed or description (e.g., “15 mph gusts”)	High winds stop crane operations, roofing, and elevated work
Site Condition	Free text (e.g., “muddy”, “frozen ground”, “standing water in excavation”)	Documents the aftereffects of weather that prevent work even after the rain stops

Key insight: Recording weather on clear, productive days is just as important as recording it on delay days. A complete weather record across the entire project period shows the pattern — not just the exceptions.

Why “It Rained” Isn’t Enough

In a delay claim, you need to prove three things about weather:

The weather actually occurred. Your daily log with temperature, rain, wind, and site condition data serves as contemporaneous proof.
The weather was abnormal. Claims analysts compare your records against historical weather data (NOAA, weather stations). You need enough data points across the project to show the abnormality.
The weather impacted the critical path. This is where your log description matters. Document what specific work was prevented, what crews were affected, and what the schedule impact was.

A log entry that says “Rain delay” satisfies none of these. A log entry that says “Heavy rain starting 6:30am, 42°F, site access road flooded, concrete pour for Section B foundation postponed, 12-person crew sent home at 8am” satisfies all three.

Site Conditions: The Forgotten Weather Data

Many contractors document rain and temperature but forget site conditions. This is a critical gap because site conditions often persist for days after the weather event:

Muddy ground — prevents excavation, grading, and heavy equipment operation for days after rain
Frozen soil — prevents earthwork even on clear, cold days
Standing water — fills excavations, prevents foundation work, creates safety hazards
Saturated subgrade — fails compaction tests even after the surface dries

If your logs only show rain on Tuesday but no site condition data on Wednesday through Friday, you can only claim one rain day — not four impact days.

Building a Weather Record for Claims

The strongest weather documentation for delay claims follows these practices:

Record weather every single day. Not just on bad days. The pattern matters.
Record at the same time each day. Consistency builds credibility.
Include photos. A GPS-tagged photo of a flooded excavation is worth more than any written description.
Flag claim-relevant days. Tag the entry with a delay category (weather) so you can filter and export later.
Don’t round or approximate. “About 40 degrees” is weaker than “38°F at 7:15am.”

From Daily Weather Records to Delay Defense Pack

When a weather delay claim is filed, your claims team or attorney needs a structured summary of all weather-affected days. Manually compiling this from individual logs is tedious and error-prone.

BuildLog’s Delay Defense Pack automatically compiles a weather records table across all claim-relevant reports: date, temperature, rain, wind, and site condition in a single tabular view. This is exactly what claims analysts need to perform weather delay calculations.

Weather Documentation, Built Into Every Daily Log

BuildLog tracks temperature, rain, wind, and site conditions with every report. Flag weather delay days, take GPS-tagged photos, and export Delay Defense Packs with structured weather records.

Book a Demo

Conclusion

Weather delay claims live or die on the quality of daily weather documentation. The four data points — temperature, rain, wind, and site condition — need to be recorded every day, not just on delay days. And the description needs to connect weather to impact: what work was prevented, what crews were affected, what the schedule consequence was.

Start documenting weather conditions in every daily log today. The claim that depends on those records might be filed six months from now.