What Is a Daily Report in Construction? The Document That Wins Delay Claims
A daily report — sometimes called a daily log, daily field report, or site diary — is the contemporaneous record of everything that happened on a construction site on a given day. It's filled out by the superintendent or foreman and captures crew counts, weather, work performed, deliveries received, visitors to the site, issues encountered, and anything else consequential.
The daily report's primary audience is the office (project management, ownership, and the owner's rep), but its most valuable use comes later — when a project ends up in a delay claim, a back-charge dispute, or an insurance claim. Because it's written contemporaneously at the end of each day, it has evidentiary weight that reconstructed records don't. Courts, arbitrators, and adjusters all give daily reports significant credibility for this reason.
A well-structured daily report captures:
Standard daily report fields
- Date, project name, superintendent name
- Weather — temperature high/low, precipitation, wind, any weather that affected work
- Crew counts by trade — number of workers present from each sub, plus any GC self-performed labor
- Hours worked — start time, stop time, break periods; critical if overtime or shift work is in play
- Work performed — what each trade actually did on the site, by location
- Deliveries received — what materials arrived, in what quantity, signed for by whom
- Equipment on site — rental equipment, owned equipment, idle time
- Visitors — owner reps, architect, engineers, inspectors, anyone not normally on site
- Inspections — what was inspected, by whom, with what result
- Safety incidents — any injuries, near-misses, or safety observations
- Issues and delays — anything that stopped work or slowed it down, and the duration
- Photos — key site conditions, progress, issues
- Superintendent signature confirming the day's record
Weather documentation gets its own category because weather delays are one of the most common types of excusable delays on construction schedules. A contract typically gives the contractor a time extension for unusual weather — weather beyond the normal expectations for the project location and time of year. Proving that weather was unusual requires evidence, and the daily report is the evidence.
Good weather documentation notes the actual conditions (3" rain from 10 AM to 2 PM, high winds 20-30 mph all day, freeze overnight with 6:30 AM temperature of 18°F) rather than the generic label ("rainy," "cold"). Some contractors include reference to the nearest NOAA weather station readings, which tie the daily report to an independent meteorological record.
A daily report that says "weather delayed work" proves nothing. A daily report that says "concrete pour scheduled for foundation footings cancelled due to 2.3\" rain measured at site from 8 AM to 11 AM, per NWS station KABC reading" proves a weather delay and supports a time extension claim.
Crew count documentation — how many workers each trade had on site — supports claims in a few ways. If a trade was supposed to have 12 workers on site but only sent 6, and the project fell behind, the undersized crew may be the reason. If the GC had to add workers to accelerate, the daily report documents when and how many.
For delay claims that depend on whether the contractor had adequate resources applied, crew count history over weeks or months becomes one of the evidence streams. A consistent pattern of undersized crews undermines a contractor's claim that they were adequately resourced; strong crew numbers support it.
The "work performed" section is where the daily report is most useful for quantifying progress. Generic entries like "continued framing" are less useful than specific ones: "framed east wall of Suite 201, from column line 4 to column line 7, full height; installed studs at 16\" OC, sheathing partial."
Specific entries let you reconstruct what happened in a room, on a floor, or on a phase. If a dispute arises about whether specific work was done by a certain date, the daily reports for the weeks leading up to that date can reconstruct the picture. Vague entries don't support the reconstruction.
When work stops or slows for any reason, the daily report should document: what stopped, why, when (start time and end time), who was affected, and what the impact was. An RFI-driven delay might read: "Electrical rough-in on 3rd floor stopped at 10:30 AM pending response to RFI-147 regarding conduit routing through fire-rated wall. Resumed 2:15 PM after response received. 2.5 hours lost; affected crews redeployed to 2nd floor where possible, but 1.5 worker-days of 3rd floor progress lost."
Notice the specificity. The cause (RFI-147, with its own paper trail), the time (trackable), the impact (quantified in lost worker-days). A daily report entry like this feeds directly into a time impact analysis.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Photos
Photos attached to the daily report are strong evidence. Modern practice uses geotagged, time-stamped photos taken on the superintendent's phone and attached to the daily report in the construction management platform. The location and timestamp data become part of the record.
Categories of photos worth taking daily: general site progress (from consistent angles to show progression over time), specific work in progress (so quality and sequence are documented), issues or damage (before and after), unusual conditions (weather impact, equipment breakdown, visitor activity), deliveries and stored materials.
The daily report is typically the superintendent's responsibility. On larger projects, the general superintendent delegates to area superintendents or foremen for specific floors or trades, with the general superintendent consolidating at end of day.
On smaller projects, the single superintendent covers it all. Either way, the person doing the daily report should be present on site, watching the work — not reconstructing the day from notes at the end of the week. Contemporaneous writing is what gives the document its evidentiary weight.
Construction management platforms now handle daily reports digitally — tablet-based entry in the field, integrated photo attachments, automated weather pulling from API feeds, automatic distribution to project management and ownership. The logs tie into the rest of the project documentation stream (RFI log, submittal log, pay applications) so cross-references are clickable.
Digital daily reports have largely displaced handwritten logs on projects above a certain scale. For small projects, paper or spreadsheet logs still work. Either way, the content is what matters — digital isn't inherently better if the content is weak.
Downstream uses of daily reports
- Pay application support — crew counts and work performed feed the pay app's progress percentages
- Delay claim evidence — daily reports are the primary record of what happened each day
- Back-charge support — if the GC did work that was a sub's responsibility, the daily report documents who was there (and wasn't)
- Safety claims and insurance — injury reports and near-miss documentation feed claim files
- Warranty disputes — post-occupancy issues can be traced back to installation conditions documented in the daily report
- Owner communications — the daily report often feeds weekly project reports to ownership
The daily report is one of the construction industry's highest-leverage documents. The effort to fill it in properly is small per day; the value aggregates over the life of the project and becomes decisive in any dispute. Specific, contemporaneous entries with photos and crew counts are worth their weight; vague summaries leave money on the table when claims arise. Superintendents who treat the daily report as their primary defensive document rather than as an administrative burden protect both themselves and their companies.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts