“Rain” is a weather observation, not a delay record. A useful entry identifies the condition, the affected activity and location, the time lost, the crew or equipment affected, and the action taken. That detail helps the project team separate ordinary weather from a documented impact.

Record the condition and the source

Note the time the condition began and ended, measured or observed conditions, and the source of any weather data. Add jobsite-specific facts such as standing water, frozen ground, unsafe wind exposure, or restricted access.

  • Temperature and precipitation
  • Wind speed or observed wind effect
  • Ground and access conditions
  • Start and end times
  • Weather source

Explain the actual impact

State which planned activities could not proceed and why. Identify the location, crew, equipment, and duration affected. If some work continued, distinguish it from the work that stopped. This makes the record more credible than a blanket statement that the entire project was delayed.

  • Scheduled activity affected
  • Reason the condition prevented work
  • Crew hours lost or reassigned
  • Equipment idled
  • Recovery or mitigation steps
  • Work that continued

For a practical companion to this section, see Daily report writing guide.

Connect the daily record to notice and schedule

The daily log supports facts, but it may not satisfy contractual notice. Review the contract for notice deadlines, required recipients, weather-day definitions, schedule obligations, and supporting documentation. Send required notice separately and reference it in the log.

Use photos that prove impact

Photograph the relevant condition and its effect on the work. Include a wide view for location and closer views for detail. Captions should identify what the image shows and why it matters.

Weather is not the same as delay

Rain on the weather report does not automatically establish a delay. The record must show how the condition affected a scheduled activity. For example, light rain may have no effect on interior work but may stop roofing, excavation, painting, or crane operations. Describe the activity, the threshold or safety concern, and the duration of the impact.

If a crew moves to productive alternate work, record that mitigation. If access remains blocked after the rain stops, document the continuing ground or site condition separately.

Example of a useful weather-delay entry

Heavy rain began at 12:45 p.m. and continued through 3:20 p.m. Water accumulated at the east material gate and prevented the forklift from reaching the staging area. The four-person exterior crew stopped unloading at 1:05 p.m. and moved to indoor layout work until 2:30 p.m. The final fixture delivery remained on the truck and was rescheduled for the following morning. Photos 4 through 7 show the access route and standing water.

This example connects the weather to location, activity, labor, mitigation, delivery effect, timing, and photos. It gives a reviewer facts to evaluate instead of asking them to infer impact from a weather icon.

Records to keep with the daily log

Preserve the project schedule or look-ahead plan that identifies the affected work. Keep the formal notice, weather data source, site photos, correspondence, delivery records, and any direction about suspension or recovery. If the contract defines normal weather or weather-day allowances, retain the baseline used for comparison.

Related construction documentation resources

Continue building a connected field-to-office process with these related resources:

Common questions

Frequently asked questions

Does rain automatically count as a construction delay?

No. The record should connect the weather to a scheduled activity, location, duration, and actual operational impact.

What photos help document a weather delay?

Capture the overall site condition, the affected access or work area, and close details that show why the activity could not proceed.

Does a daily log satisfy contractual notice?

Not necessarily. Follow the contract for notice timing, recipients, content, and required supporting documents.

Write the impact, not just the forecast.

Record what could not proceed, where the interruption occurred, how long it lasted, and what the crew did next. Follow the contract separately for any required notice.