Construction Daily Report: What to Include, Why It Matters, and How to Do It Right
The construction daily report is the most consistently undervalued document on a job site. GCs who treat it as a bureaucratic checkbox lose disputes they should win. GCs who treat it as a contemporaneous legal record — written the same day the work happened — routinely use it to support delay claims, defend against defect allegations, and justify change order pricing. This guide covers what belongs in a daily report, how to structure it, and how to turn a routine field habit into a powerful project management tool.
What Is a Construction Daily Report?
A construction daily report (also called a daily field report, superintendent's log, or daily log) is a written record of everything that happened on a job site on a given day. It is prepared by the superintendent, project manager, or both — ideally before they leave the site — and it documents conditions, activities, personnel, equipment, and events.
The critical attribute is timing: a report written the day the work occurred is a contemporaneous record. A report reconstructed from memory two weeks later is not. Courts and arbitrators treat contemporaneous records as significantly more credible than reconstructed accounts — which is why daily reports written consistently and completely are a GC's best defense in any project dispute.
The 8 Core Sections of a Daily Report
Project name, number, date, report number, and the name of the person preparing the report. Report numbers should be sequential — gaps in the sequence are a red flag in disputes that suggests reports were created retroactively.
Temperature (high/low), precipitation type and amount, wind, humidity, and ground conditions. Document weather at multiple points in the day if conditions changed. This matters for:
- •Concrete placement temperature requirements (ACI 305/306)
- •Rain delays and productivity loss claims
- •Excusable delay documentation under force majeure provisions
- •SWPPP compliance events (precipitation triggers)
List each trade/subcontractor on-site that day, number of workers, foreman name, and hours worked. Format that works:
Total manpower count is your productivity baseline. A project that suddenly shows 40% fewer workers than scheduled is a schedule problem you need to address — and document — immediately.
List major equipment present, including idle equipment. Idle equipment documents standby costs in delay claims. Equipment breakdowns should be noted with the time discovered, impact on work, and resolution.
This is the substantive section — a description of what each trade accomplished that day, by location and quantity where possible. The standard to reach for:
Record every visitor: owner's rep, architect, engineer, building inspector, testing lab, manufacturer's rep, lender's inspector. Note what they observed, any comments made, and any inspection results (pass/fail, hold points). An inspection that happened but wasn't documented didn't happen in a dispute.
This is the most legally sensitive section. Document:
- •Any work stoppage and the cause (owner-directed, weather, material shortage, trade conflict)
- •Verbal directives from the owner or architect (with their name, time, and exact substance)
- •Unforeseen conditions encountered (subsurface, concealed conditions)
- •Safety incidents or near-misses (see Section 8)
- •Material deliveries — on time, late, or damaged
- •Outstanding RFIs that are impacting work (with RFI number and days outstanding)
A verbal directive documented in that day's daily report is far stronger than a memo written three weeks later saying "on [date], the owner verbally directed us to..."
Record toolbox talk topics, any safety incidents or near-misses, first-aid events, and OSHA 300 log entries triggered. Even "no incidents" should be stated explicitly — it shows the safety program was active. Document any safety violations observed and corrective action taken.
Daily Report as Legal Record
The daily report's legal weight comes from one property: it was written the day the events occurred. In construction disputes — delay claims, change order disputes, defect allegations, liquidated damages defenses — the side with the better contemporaneous record almost always prevails.
- • When a delay started and what caused it
- • That an owner-directed change was given verbally
- • That an inspection passed (or failed) on a specific date
- • That a sub was undermanned relative to schedule
- • Weather impact on a specific day's productivity
- • That a defect condition was observed and reported
- • Work sequence and the order trades were on-site
- • Delay claims without contemporaneous documentation
- • Verbal directives you can't prove were given
- • Weather day claims with no weather records
- • Productivity loss claims with no baseline data
- • Defect disputes where work sequence is unclear
- • Sub back-charges you can't support with dates and facts
Superintendent vs. PM Daily Reports
Large projects often run two parallel logs — a superintendent's daily field report focused on field conditions, manpower, and physical work, and a PM's daily or weekly log focused on administrative events, correspondence, and decisions. They serve different purposes:
| Aspect | Superintendent's Log | PM's Log |
|---|---|---|
| Primary focus | Field conditions, work performed, manpower | Decisions, correspondence, change events |
| Frequency | Every day work is performed | Daily or weekly, per project size |
| Key entries | Weather, manpower counts, work performed, site events | Owner directives, RFI status, submittal log, cost events |
| Legal use | Delay, productivity, defect, incident claims | Change order disputes, scope disputes, notice requirements |
5 Best Practices for Construction Daily Reports
-
1.
Write it the same day — no exceptions. A report written the following morning is still reasonably contemporaneous. A report written Friday covering the whole week is not. Build the daily report into end-of-day routine; it takes 10–15 minutes when done daily and hours when reconstructed later.
-
2.
Be specific about quantities and locations. "Poured Level 3 deck, Grid A–H, 420 CY, 7:15 AM–2:30 PM, mix design 4000 PSI, ticket numbers 1842–1861" is useful. "Poured concrete" is not. Specificity is what makes a daily report credible and defensible.
-
3.
Document verbal directives immediately. When the owner's rep walks the site and says "move that wall two feet" — write it in the daily report that day. Follow up with a written RFI or change order request, but the daily report is your contemporaneous record of when the directive was given.
-
4.
Never leave the weather section blank. Even if conditions were perfect, write "clear, 72°F, no precipitation." Blank weather sections in daily reports are a red flag suggesting the report was completed retroactively. Weather data is also independently verifiable — your records should match NOAA historical data for the site location.
-
5.
Tie daily reports to your job cost tracking. When a report shows a delay, that day's cost should be captured in a separate cost code so you can quantify the financial impact. The daily report proves the delay happened; the cost record proves what it cost. Both are required to support a claim.
Field Documentation That Connects to Cost
SheetIntel links daily field activity to job cost codes — so when a delay shows up in your daily report, the cost impact is already captured and ready to support a change order or claim.
Get Early Access →