Every commercial project has daily reports. Most of them are useless.
Not because the supers aren’t filling them out — they are. Not because the data isn’t being captured — it is. The reports are useless because the data being captured isn’t the data that protects the project when something goes sideways.
A daily report that exists to satisfy a contractual obligation and a daily report that holds up under dispute look almost identical from a distance. The difference shows up six months later, when an attorney is reading them and asking specific questions about who was on site, what the conditions were, what work was performed, and what was being communicated to whom.
Here’s what a useful daily report actually contains, why each piece matters, and what most reports miss.
Why Daily Reports Matter More Than They Look
A daily report is contemporaneous documentation. That phrase means more than it sounds like.
In any construction dispute — delay claims, change order disputes, defective work allegations, injury investigations — the question of “what actually happened on site that day” is the central evidentiary question. The party with reliable, dated, contemporaneous records has a fundamentally stronger position than the party trying to reconstruct events from memory and emails.
Daily reports are the spine of that record. Done well, they create a continuous timeline of conditions, manpower, work performed, and communications that is admissible in court, supports change order pricing, and rebuts retroactive accusations of poor performance.
Done poorly, they are paperwork that takes time and protects nobody.
What a Working Daily Report Captures
A daily report doesn’t need to be long. It needs to be specific. The fields that actually matter:
Date, Project, and Author
Obvious. Often wrong. The report needs the actual calendar date (not a “week ending”), the project identifier, and the name of the person who completed the report. If the report was edited after the fact, that needs to be visible in the record — software-based daily reports usually capture this; paper reports usually don’t.
Weather Conditions
Not just “sunny.” Specific high and low temperatures, precipitation, wind conditions, and any weather event that affected work. If the crew lost two hours waiting out a storm, that goes on the report — with start and stop times.
Weather documentation is one of the highest-leverage fields on a daily report. Weather-related delays are a frequent component of schedule claims, and a project with rigorous weather documentation can support a delay claim that a project without it cannot.
Manpower by Trade
The number of workers from each subcontractor on site that day, by trade, with names and crew compositions where possible. “5 electricians on site” is useful. “Smith Electric — 1 foreman (R. Smith), 3 journeymen, 1 apprentice — installing rough-in north wing Level 2” is dramatically more useful.
Manpower data supports productivity claims, validates progress against the lookahead, and provides the basis for any constructive acceleration claim if the project later requires additional manpower to recover schedule.
Work Performed
Specific descriptions, by location, of what work was completed. “Continued framing” is not specific. “Framed top track and studs, gridline 5-8, Level 2 north corridor — approximately 70% complete by EOD” is specific.
The standard for specificity: a project manager reading the report a year from now should be able to reconstruct what happened that day at a level that supports schedule analysis and progress verification.
Equipment on Site
Major equipment present and operating: cranes, forklifts, telehandlers, scissor lifts, concrete pumps, generators, anything billable. For owner-furnished equipment, note utilization. For rented equipment, note arrival and departure dates.
Equipment documentation supports cost claims, equipment damage disputes, and any later question about whether the right resources were on site.
Materials Delivered
Who delivered what, when, by whom. Quantities and any issues with the delivery (damaged material, short shipments, wrong product). Supports procurement records, material claims, and any dispute about whether the right material was on site to support the schedule.
Visitors and Inspections
Anyone on site who is not part of the regular construction team: owner representatives, architect or engineer, building inspector, fire marshal, OSHA compliance officer, third-party testing agency, neighbors, other contractors visiting for coordination.
For inspections specifically: who, what was inspected, what was the result, any deficiencies noted, follow-up required. An inspection that passed without a written documentation in the daily report can become a dispute ten months later when a deficiency is alleged and there’s no record of when the work was actually inspected.
Safety Events
Any safety incident, near miss, first aid event, recordable injury, or safety inspection. If a hazard was identified and corrected, the corrective action goes in the report.
Safety documentation is reviewed during OSHA inspections and is essential for any defense of a safety-related citation. The report doesn’t need to be lengthy; it needs to be present.
Communications
This is the field most reports miss most consistently.
Verbal communications with significant content — instructions to subs, agreements with the owner’s representative, decisions made in field meetings, notices issued — should be summarized in the daily report with the substance of what was communicated, who was present, and what was agreed.
Email and written communications don’t need to be replicated; they exist independently. But verbal communications without contemporaneous documentation are practically impossible to prove later. A field decision that comes up in a dispute six months from now is dramatically stronger if it appears in a contemporaneous daily report than if it depends on memory.
Conditions Encountered
Anything that affected work that day that isn’t expected: subsurface conditions different from those shown in the geotech, existing conditions that don’t match the drawings, scope items discovered to be missing or in conflict, equipment failures, material defects, deliveries that didn’t arrive.
Encountered conditions documentation is the foundation of any change order claim or differing site conditions claim. Without it, the contractor’s notice obligation under the contract is harder to satisfy.
Photos
Date-stamped, location-tagged photos of work in progress, completed work, deliveries, conditions, and any item documented elsewhere in the report.
Photos are the most underused leverage on a daily report. They’re easy to capture on a phone and they create unambiguous evidence of conditions that words alone struggle to convey. A photo of subsurface conditions found during excavation does more for a differing site conditions claim than three paragraphs of description.
What Most Reports Miss
Across hundreds of commercial projects, the same gaps show up consistently.
Verbal communications that aren’t captured. A super tells a subcontractor’s foreman to relocate a wall to accommodate a discovered structural condition. The conversation happens at 9am on a Tuesday. By the time the change order is being priced six weeks later, the only documentation is an email from Friday. The Tuesday conversation is what the contractor needs to point to. It’s nowhere.
Encountered conditions that get fixed without being documented. The crew finds out the floor slab is 1/2 inch lower than the drawings show in a critical area. The framers adjust their layout to compensate. The condition is fixed in the field, the project moves on, and the discovery never appears in writing. When the floor finishes don’t match the architectural intent and the question of “when did this discrepancy first appear” comes up, the answer should be “Tuesday May 12, daily report, with photos.” Often, it’s “I think the framers found it sometime in May, I’m not sure exactly when.”
Inspections passed without documentation. A fire alarm rough-in is inspected and approved verbally by the AHJ inspector. Weeks later, a deficiency is identified that should have been caught at rough-in. The contractor’s defense — that the work passed inspection — depends on documentation of the original inspection. If the daily report shows “Fire Marshal Wilson on site, fire alarm rough-in inspected Level 2 — approved,” the position is strong. If it shows nothing, the position depends on memory.
Subcontractor delays that aren’t called out. A sub commits to start work on a specific date and doesn’t show up. The GC absorbs the delay, recovers schedule by other means, and never documents the missed commitment. Later, when the same sub disputes a backcharge or claims they were impacted by the GC’s coordination failures, the absence of contemporaneous documentation of their performance becomes a problem.
Work performed without specific location. “Framing continued” tells you nothing about what specifically was done. When progress measurement, schedule analysis, or productivity claims come into the picture, location-specific work descriptions are essential. Reports that lack this specificity are essentially diaries — they capture activity but don’t support analysis.
How to Get the Crew to Write Reports That Actually Work
The daily report quality problem isn’t usually the report format. It’s the discipline of how the report is completed and reviewed.
Reports get completed on the day they cover, not the next morning. A report written Wednesday for Tuesday’s work loses fidelity. Memory degrades quickly on construction sites. The end-of-day discipline of completing the report before leaving the trailer is the single biggest factor in report quality.
Reports get reviewed weekly by the project manager. The PM should be reviewing the daily reports against the schedule, the change order log, and the RFI log every week. Patterns get flagged: a sub showing reduced manpower, weather days that should have triggered notice, encountered conditions that need formal change order treatment. Without this review, the daily report becomes a write-only system.
Reports get backed up off the project. A construction management platform that captures daily reports and stores them centrally is dramatically more reliable than paper reports stored in the trailer. If the trailer floods, gets vandalized, or the binder gets misfiled at project closeout, paper reports can disappear. Cloud-based reports persist.
Reports get integrated with other documentation. Daily reports, RFIs, submittals, change orders, and meeting minutes should reference each other and connect into a single project record. A daily report that mentions an encountered condition should reference the RFI that documents the formal notice. An RFI that mentions a field condition should reference the daily report and photos that document the condition.
A Note on Software
Most commercial GCs are using a project management platform that includes daily reports — Procore, Buildertrend, Fieldwire, or others. The platform doesn’t matter as much as the process. A team using paper reports with discipline produces stronger documentation than a team using a sophisticated platform without discipline.
If you’re choosing a daily report tool, the features that actually matter are: ease of completion in the field on a phone, integration with photos, cloud storage with audit trail, and ability to reference other project records. Anything beyond that is a feature; the four above are necessities.
The Bottom Line
A daily report is the most important document on most construction projects, and it’s the document most often produced as an afterthought. The teams that win disputes, support change orders, and defend against retroactive claims aren’t the teams with the most aggressive lawyers. They’re the teams whose daily reports tell a coherent, dated, specific story of what happened on the project.
Build the discipline. Your future self will thank you.
Jobsite Blog covers field documentation from the GC and superintendent’s perspective. If you have a specific documentation challenge, reach out through our contact page.