TL;DR
Get business pricing on tools and workshop supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Weather and delay logs improve scheduling when they capture conditions promptly and connect each event to a specific activity, actual work impact, and schedule effect. Track causes separately, support entries with field evidence, and use recurring patterns to adjust calendars, durations, sequencing, and contingency plans.
A rainy Tuesday does not automatically cost your project a full day. The crew may lose two hours waiting for the trench to drain, then shift to indoor work and finish the shift productively. If your daily report only says “rain delay,” you lose the detail that helps explain what happened and plan the next pour, excavation, or crew move.
Weather and delay logs turn jobsite disruptions into information teams can use. They help you see which work is weather-sensitive, how much time an event actually affected production, and whether the schedule absorbed the hit or moved. That detail matters during the current job and when you build the next schedule.
This guide shows you what to record, how to connect a field event to the schedule, and how to use patterns without treating last year’s weather as a promise. You’ll also see how to keep entries useful when rain, equipment trouble, and access problems land on the same shift.
Record the time, site area, condition, affected activity, actual work impact, observer, and supporting evidence while the shift is underway.
Separate weather observations from schedule consequences; a weather event does not automatically equal a full lost workday.
Trace each disruption through condition, activity, impact, schedule effect, and mitigation.
Record overlapping causes such as weather, equipment trouble, labor, and access on separate timelines.
Use recurring activity-level patterns to refine calendars, durations, sequencing, and contingencies, while treating past weather as evidence rather than a guar…
FIELD GUIDE / PROJECT CONTROLS
How to Use Weather and Delay Logs to Improve Project Scheduling
Turn jobsite disruptions into scheduling evidence. Record what happened, connect it to the work affected, and use the schedule logic to understand whether time was recovered, float was consumed, or completion moved.
Record the shift while the details are fresh
A clear entry lets someone reconstruct what happened later without guessing what “lost time” meant.
Pin down the event
Record date, shift, site area, start and end times, observed conditions, measurement, and data source or observer.
Name the activity
Use the schedule name or ID. Note the crew and equipment affected, plus whether work stopped, slowed, or moved.
Show what happened next
Attach photos, station data, daily reports, or supervisor notes. Record work completed, mitigation, and any recovery step.
- Condition and source, such as rainfall, temperature, wind, or snow
- Actual hours stopped or reduced—not an assumed full shift
- Labor, equipment, access, and location effects
- Visible correction history that preserves the original entry
Use the five-link chain
Field facts explain the event; schedule logic tests what it changed.
Wind stops a lift for two hours. Record the affected pick, the crew and equipment, and the actual stoppage window.
If the lift has float and finishes next morning without disrupting follow-on work, the completion date may hold. If it controls steel erection and crews are waiting, even a shorter stoppage can push later work.
Track the task’s constraint, not just the forecast
Conditions affect activities differently. Record what made the specific work unsafe or impractical and what the crew could still do.
Wet access can stop haul trucks
“Rain from 9:10 to 10:25 a.m. softened the north access road; concrete trucks could not reach the footing pour.” Add observed site conditions and the applicable project limits.
Another crew may keep producing
Excavation may pause while electricians rough in conduit inside. Record each activity separately so the schedule review sees both the stoppage and the work that continued.
A 12-person grading crew lost 90 minutes when overnight rain left the pad too soft for haul trucks. Two operators then moved to drainage work.
Illustrative field entry / Record lost production and productive reassignmentBuild one timeline when delays overlap
Separate entries reveal which constraint drove each part of the interruption and whether another issue would have stopped work anyway.
Record each cause, start and end time, affected work, and the counterfactual: would production have stopped if the other issue had not occurred? Keep weather, equipment, labor, access, inspection, and owner changes distinguishable.
Use recurring patterns as evidence
Compare actual conditions and delays with baseline assumptions to improve the next schedule.
Adjust seasonal assumptions
Review recurring weather-sensitive work windows and refine working calendars for the site and season.
Plan for actual constraints
Use activity-level patterns to revisit durations, sequencing, protection, and alternate work locations.
Prepare a recovery response
Set realistic buffers and options for crews, access, and resources. Past weather is evidence, not a guarantee.
Make records consistent and reviewable
Shared definitions make weekly totals meaningful across crews and seasons.
Agree on “rain day”
Clarify whether it means measurable rain or a shift when planned work cannot proceed. Define “stoppage” and “lost hours” too.
Keep field facts clear
Use contract definitions and notice requirements when assessing entitlement. Observations alone do not establish responsibility or compensable time.
Use tools with judgment
Mobile reports, station data, forecasts, and dashboards can help collection. Check distance, site conditions, calendars, and schedule logic before drawing conclusions.
Record the event while the details are still fresh
Weather and delay logs improve scheduling when you record each event close to when it happens, with the time, location, affected activity, duration, and work impact. A clear entry lets someone reconstruct the shift later without guessing what “lost time” meant. Add who observed the condition and what evidence supports the entry.
Keep the record concrete. “Rain from 9:10 to 10:25 a.m. softened the north access road; the concrete truck could not reach the footing pour” tells a better story than “weather delay.” Include whether work stopped completely, slowed down, or moved to another task. If the crew changed locations, note where it went and when.
For example, a foreman might report that a 12-person grading crew lost 90 minutes after overnight rain left the pad too soft for haul trucks. The crew then moved two operators to drainage work. That entry records both the lost production and the work that continued, giving the scheduler a more honest picture than marking the entire day as lost.
Use the same basic fields every day so entries line up over weeks and across crews. Record date and shift, site area, condition and source, affected activity, start and end times, labor and equipment effects, work performed, mitigation, and supporting photos or notes. Make a correction visibly if you discover an error; preserve the original record and explain the update.
Popular right now
De'Longhi Magnifica Evo Fully Automatic Espresso Machine with Manual Milk Frother, Silver
KitchenAid Classic Series 4.5-Quart Tilt-Head Stand Mixer, Onyx Black
Dyson V8 Cyclone Cordless Vacuum
As an affiliate, we earn on qualifying purchases.
Connect the weather to the work it actually stopped
A weather log records conditions; a delay log records how an event affected work. To improve a schedule, connect the two at the activity level. Rain can stop earthwork while interior framing continues, and high wind can halt crane picks while crews complete ground-level work. A date alone cannot explain that difference.
Start with the work’s requirements and the conditions at the work area. Note whether the surface became too soft, visibility dropped, wind exceeded a safe operating limit, or temperatures affected a specified material or process. Use actual observations and applicable project rules. Don’t label an entire shift a weather loss just because the rain gauge collected water.
Take a wet morning on a commercial site. The excavation crew may wait for the trench to drain, while electricians rough in conduit inside a dry building. A useful entry separates those outcomes: excavation paused from 7:30 to 10:00 a.m.; indoor electrical work continued; two laborers helped clear a safe path to the work area. The schedule review can then assess the excavation activity without erasing the indoor production.
Define terms such as “rain day,” “work stoppage,” and “lost hours” before the season gets busy. One crew might use “rain day” for any measurable rain, while another means a shift when a planned task cannot proceed. Consistent definitions make weekly totals meaningful. When contract documents define adverse weather or notice requirements, follow those terms for contract administration and keep field observations clear and separate.
Use this five-step chain to show the schedule impact
Weather and delay logs explain a schedule impact when they trace five links: condition, affected activity, work impact, schedule effect, and mitigation. This chain gives the scheduler enough detail to test what changed. It also helps a superintendent explain why a disruption mattered—or why the crew recovered the time.
- Record the condition. Note what happened, where, when, and how you measured or observed it.
- Name the activity. Use the schedule name or ID when possible, such as “Place east footing concrete.”
- Measure the work impact. Capture the actual hours stopped or reduced, crew and equipment affected, and work completed.
- Check the schedule effect. Identify whether the activity had float, was on the critical path, or disrupted the next operation.
- Record the response. Note resequencing, added resources, protection, cleanup, or other recovery steps.
Suppose wind stops a crane pick for two hours. If the lift has float and the crew completes it the following morning without affecting follow-on work, the completion date may hold. If the same lift controls steel erection and the concrete crew is already waiting on that sequence, even a shorter stoppage could push later work. The log should record the facts; the schedule logic shows the consequence.
Update the schedule through your normal process and keep a record of the version used in the review. An entry that says only “two hours lost” cannot show whether the team consumed float, shifted work, or changed a milestone. A short note on the activity relationship makes the disruption much easier to review later.
Separate weather from equipment, labor, and access delays
A delay log is more useful when each cause has its own entry, even when two or more causes overlap. Weather, equipment trouble, labor shortages, inspections, access restrictions, and owner changes can affect the same work window. Recording them as one general “delay” hides which constraint drove the stoppage and what the team could have controlled.
Use a timeline when causes overlap. Say rain closes a haul road at 8:00 a.m., then a loader develops a hydraulic problem at 9:15. Record each start and end time, the affected work, and whether the loader issue would have stopped production even if the road had stayed open. Avoid claiming that every lost hour came from the first event listed.
For instance, a paving crew may lose an hour waiting for a truck after a gate closes during a storm. The storm may have affected access, but the truck shortage adds a separate constraint. Your report can show both conditions and the time each one affected delivery. That gives the project team a fair basis for discussing the sequence and recovery options.
A weekly review can flag overlapping causes for closer schedule analysis. Compare the event timeline with crew reports, equipment records, inspection logs, and the current schedule. The log can support an analysis or a notice, but it does not decide responsibility or prove entitlement by itself. Contract language, notice deadlines, project facts, and schedule logic still matter, so involve the appropriate project staff when those questions arise.
Build a weather record people can verify
A credible weather entry states what conditions affected the site and where the information came from. Record relevant measurements—such as rainfall, temperature, wind, or snow—along with the source and its location. Pair those numbers with site observations, because a nearby station may not reflect the conditions at a shaded cut, exposed roof, or muddy access road.
For example, an airport station several miles away reports light rain, but a storm cell leaves standing water on your east laydown area. Note the station reading and distance, then describe the puddling and attach a timestamped photo. The site condition explains why delivery access changed; the station data adds useful context without pretending to measure the exact conditions under every crew’s boots.
Preserve daily reports, photos, supervisor notes, weather data, and schedule updates in an orderly record. Write entries promptly and identify the observer. If someone corrects a time or measurement later, keep the first entry and document the correction. A clean trail helps the team review the event months after the muddy tire tracks have dried.
Mobile field-reporting tools can help crews capture conditions, photos, labor, equipment, and delay events during the shift. Some systems can associate a record with an activity or dashboard, reducing manual collation. Still, check automated summaries against field notes and schedule logic. A software label cannot establish that weather caused a delay, and it cannot replace contract requirements or a careful activity-level review.
Turn repeat disruptions into better schedule assumptions
Historical logs help you improve future schedules by showing where your assumptions differed from actual jobsite conditions. Review events by season, site area, and activity rather than relying on a single total of “bad weather days.” Repeated soft subgrade after storms may point to a drainage or access constraint; repeated heat slowdowns may affect a different set of tasks and work hours.
Imagine three months of reports show that the south excavation loses production after heavy rain, while interior rough-in keeps moving. That pattern gives the next planner a reason to schedule sensitive earthwork earlier in a dry window, build in time for access recovery, or plan an alternate task for the crew. The logs turn jobsite disruptions into information teams can use to plan more realistically.
Compare actual start and finish dates with the baseline schedule and note the assumptions behind the activity durations and calendar. Did the work start in the expected season? Did crews face conditions the plan did not account for? Did resequencing protect the milestone? Use those answers to adjust calendars, durations, sequencing, seasonal plans, and contingency strategies where the evidence supports a change.
Do not copy last year’s delay count into next year’s schedule as a guarantee. Weather varies, and each site has different drainage, exposure, access, and work rules. Use history as one input, alongside forecasts, the contract calendar, site knowledge, and current schedule logic. That gives your plan a grounded allowance without treating the past as a forecast.
Use the weekly review to find a practical recovery move
A weekly review turns individual log entries into decisions about the work ahead. Compare reported impacts with the current schedule, look for activities that lost float or now threaten a handoff, and decide whether the crew can resequence safely. The review should produce a clear next action, not just a longer list of delay codes.
Suppose rain keeps the foundation crew off a west pad for part of Monday, but the crew can move to east-side formwork. The superintendent and scheduler can check whether that swap protects the next concrete placement, whether materials and inspection timing allow it, and what work will need to return to the west pad. Note the choice and its result so the next review can tell whether it recovered time.
Useful recovery options depend on the task and site. You might protect an exposed area, move crews to indoor work, change a delivery sequence, add a shift if allowed, or keep a weather-sensitive task out of a forecast risk window. Every option has costs: a resequence can create congestion, extra labor can strain supervision, and a longer shift can raise fatigue concerns. Record the tradeoff that shaped the decision.
Close the loop by checking the next update. Did the mitigation keep the milestone? Did the crew lose more time than expected? A concise note answers those questions and helps the next planning meeting focus on actual results. When your reports show both the disruption and the response, teams can improve the plan without confusing a weather event with an automatic full-day loss.
Frequently Asked Questions
What should a weather and delay log include?
Record the date and time, site location, observed conditions and data source, affected activity, work stopped or reduced, duration, and labor or equipment impacts. Add mitigation steps and evidence such as timestamped photos, daily reports, or supervisor notes. A short entry should let someone understand what happened without standing beside you on the jobsite.
Does a rainy day count as a full day of delay?
Not by itself. Record the actual time and work affected, including tasks that continued or shifted. A wet morning may stop excavation while indoor work proceeds, so the schedule effect depends on the activity and its relationship to later work.
What is the difference between a weather log and a delay log?
A weather log records site conditions, such as rainfall, temperature, or wind. A delay log records events that affected work and their schedule consequences. One daily report can include both, as long as the conditions and work impacts stay distinguishable.
How do you decide whether weather caused a schedule delay?
Compare the observed conditions with the activity’s requirements and the applicable project or contract criteria. Then record the specific work impact and check the schedule logic, including float, critical-path status, and recovery options. Weather data alone does not establish the schedule effect.
How can old logs improve a future schedule?
Review repeated impacts by season, site area, and activity, then compare them with the assumptions in the baseline schedule. If reports repeatedly show rain slowing one access route or heat reducing production on a particular task, you can adjust sequencing, durations, calendars, or contingency plans. Past patterns help you plan; they do not guarantee future conditions.
Can a delay log prove a contractor is owed extra time or money?
A log can support a schedule analysis or contract discussion, but it does not decide entitlement or compensation by itself. The contract, notice requirements, project facts, and schedule analysis all matter. Keep the record timely and factual, and route contract questions through the project’s established process.
Conclusion
Write each log entry so another person can follow the chain from the condition to the affected work, hours lost or recovered, and schedule result. That record helps you make better decisions during the job and gives future planners evidence they can use.
Next shift, replace “rain delay” with the times, task, site condition, and recovery move. Months later, that small detail can be the difference between a schedule built on memory and one built on what your crew actually faced.
