Document a weather interruption by recording the local date and times, site conditions, work activities affected, and supporting records. Whether it qualifies for extra time depends on the contract and the schedule evidence. A wet or windy day alone does not establish an entitlement to an extension.
This guide covers the practical workflow for documenting weather delays: what to record, when to record it, what data sources to reference, and how to present the documentation in a format that aligns with typical contract requirements.
What Construction Contracts Require
Read the contract before using a weather log or preparing a delay notice. Check the applicable clause, notice recipient, deadline, weather definition and required schedule evidence. The following are questions to resolve, not standard terms that apply to every project.
Excusable delay provisions
Check what the agreement treats as excusable weather and how it measures an effect on completion. Do not assume that a weather interruption automatically qualifies for extra time or payment.
Notice requirements
Record the exact notice deadline and recipient in your contract. For example, FAR 52.249-10(b), when incorporated in a federal fixed-price construction contract, includes unusually severe weather and written notice within 10 days from the beginning of the delay unless extended by the Contracting Officer. That is an example, not a universal deadline.
Documentation requirements
Keep records of the weather, interruption times, affected activities and schedule status. Check which daily reports, notices and schedule updates the recipient requires.
Threshold definitions
If your contract specifies a weather allowance or threshold, retain its wording, units, reporting period and location. Avoid substituting a generic rainfall, wind or temperature threshold for the project requirements.
Understanding your contract's specific provisions is the starting point for building a defensible weather delay claim.
The Daily Documentation Workflow
Make entries as events occur when possible. If you reconstruct an entry later, show when you created it and identify the contemporaneous records used. Do not backdate an entry.
Maintain a daily weather log
Record the general conditions each day: precipitation (type and approximate amount), wind conditions, temperature range, and any conditions that prevented or limited work. Note the specific hours when work was suspended and the reason.
For a rain interruption, check rainfall totals for a past date and keep the reporting interval with the workday log.
Cross-reference with archived observation data
Record site observations and supporting weather data separately. A site instrument can provide a measurement; an airport observation describes that station. Note location, reporting interval, time zone and units, and explain differences rather than changing a log to match an external record.
Document the impact on scheduled activities
Identify the activity and describe what stopped, continued or resumed. Retain the relevant schedule version and activity references for the project team to assess any completion-date impact.
Photograph conditions when relevant
When safe, photograph relevant conditions and work areas. Preserve original timestamps and file references. A photograph records a particular view and time; it is not a wind-speed or rainfall measurement.
What should a weather-delay notice include?
Use your contract's required format. Identify the project, clause, event dates, affected activities, known impact, supporting records and any next update. Send it to the specified recipient within the actual deadline and retain delivery evidence. A daily log is an attachment, not a substitute for required notice.
Aligning Weather Data with Contract Thresholds
If your contract defines specific thresholds for excusable weather, your documentation should explicitly map the recorded conditions against those thresholds.
Contract specifies measurable criteria
Use the threshold actually written in the contract. If it requires a rainfall total for working hours at a named station, a midnight-to-midnight total for another location is not the same comparison. Check available weather values and reporting periods before quoting them.
Keep operational or manufacturer safety limits separate from the contractual test for an extension. A stop-work decision and a decision about compensable or excusable delay answer different questions.
Contract uses general language
If the contract uses language such as "unusually severe," identify the comparison method required for the project. Historical averages may provide context, but the relevant period, location and definition of a weather day need to match.
Do not simply subtract an average number of rainy days from the observed count and treat the difference as approved delay days. Keep the weather comparison separate from the assessment of work and schedule impacts.
How to Present Weather Delay Documentation
The format of your weather delay documentation affects how it is received. A disorganized pile of daily logs and weather printouts creates work for the reviewer and invites challenges. A structured presentation is more persuasive.
Organize by date
Each claimed delay day should have its own entry showing the date, the recorded weather conditions (temperature range, precipitation, wind, visibility), the contract threshold it exceeded, the activities affected, and the schedule impact.
Include the data source
Identify the provider and source location, reporting period, time zone and retrieval date. A location-based compilation should be labeled as such. StormRecord uses Visual Crossing weather compilations and available regional records; see the source methodology.
Summarize the totals
After presenting the individual days, summarize the total number of delay days claimed, organized by category if applicable (rain days, wind days, temperature days). Compare against the contract's weather allowance if one exists.
Reference the critical path
Retain the schedule activities, dependencies and relevant schedule version. The project team should assess completion-date effects, available float and other concurrent interruptions under the applicable contract.
Common Weather Delay Documentation Mistakes
Several common mistakes weaken weather delay claims.
Retroactive documentation
Late entries can omit important context. Identify them as retrospective and reference the original records used rather than presenting them as contemporaneous observations.
Relying only on site logs without objective data
Keep both the site account and supporting observations. An external rainfall total can be independently reviewed for its own location and period; it does not convert a site description into an instrument measurement.
Failing to provide timely notice
Follow the notice provisions in the applicable agreement. Keep the notice, recipient, delivery date and acknowledgement with the relevant entry; the log itself may not satisfy a notice requirement.
Claiming every rain day
Record whether precipitation actually interrupted a named activity and during which hours. Do not count all rainy days automatically as extension days.
Ignoring the critical path
Record impacts on all affected work, then have the project team assess any effect on completion. A log should not automatically classify days as entitled or ineligible.
Frequently Asked Questions
The contract defines the test for relief. Record the interruption, relevant weather, required notices and affected schedule activities. Neither a generic weather threshold nor the log alone establishes an extension.
Keep site observations, interruption times and work impacts, then attach relevant supporting weather records. Use the free construction weather delay log to organize the entry; follow your contract separately for notice and schedule requirements.
Station archives can provide available measurements for the station and reporting period. NWS warnings describe an identified hazard for an area; they are not confirmation at every property. Regional storm reports add separate location and time context. Compare sources in the weather-records guide.
Available archives can support a later review, but coverage and corrections vary. Date the reconstructed entry honestly and identify the photos, site records or other evidence supporting the work-impact account.
There is no single number of weather-delay days appropriate to every project. Use the project location, season, activities, schedule and the contract's allowance or comparison method. Days above an average are not automatically approved extensions.
Ask the project team what analysis is required. Disputed conditions or a site-specific reconstruction may call for a qualified weather specialist; contractual or schedule questions need the appropriate project professionals.
The Bottom Line
A useful record connects a dated site account, supporting weather information, attachment references and affected activities. Keep required notices and schedule assessments with it. Documentation helps a reviewer understand the facts; it does not decide the outcome.
Keep the version of each weather record you relied on and its retrieval date. Archives can publish corrections or later reports, and some measurements may be missing. A later lookup can differ from the file originally saved.
This article is provided for informational purposes only and does not constitute legal or contractual advice. Contract provisions and documentation requirements vary by agreement.
Published by StormRecord.
StormRecord does not provide legal or contractual advice. Contract provisions and documentation requirements vary by agreement.