Construction Superintendent Daily Report: What to Include (2026 Guide)
A construction superintendent's daily report is the single most important document produced on a job site. It is the contemporaneous record of what happened, who was there, what conditions existed, and what decisions were made. When a delay claim surfaces 18 months after the fact, when an OSHA inspector asks for documentation, or when an owner disputes a change order — the daily report is what the superintendent reaches for.
Yet most superintendent daily reports are incomplete. They capture the basics — weather, crew counts, maybe a sentence about progress — and miss the 12 other data points that matter most in disputes, claims, and safety investigations. This guide covers the 16 items every superintendent should document daily, why each one matters, and how to capture them in under 5 minutes.
Why Superintendent Daily Reports Matter More Than You Think
The daily report serves three distinct purposes, and most superintendents only think about the first one:
- Project communication. Keeping the office informed about field progress. This is the obvious purpose.
- Legal protection. Creating a contemporaneous record that holds evidentiary weight in delay claims, disputes, and litigation. Courts give significant weight to records created at the time events occurred.
- Safety defense. Documenting compliance activities, hazard observations, and corrective actions that demonstrate good faith during OSHA inspections.
The difference between a superintendent who wins a $400,000 delay claim and one who loses it is almost always documentation. Not who was right — who can prove it.
Key principle: If it's not in the daily report, it didn't happen. This is how attorneys, judges, arbitrators, and inspectors view site documentation. The daily report is not a chore — it is your evidence.
The 16 Items Every Superintendent Must Document
1. Date, Time, and Weather Conditions
Record the date, the time you arrived on site, and detailed weather conditions: temperature, precipitation type and amount, wind speed and direction, and ground conditions. "Rainy" is not sufficient. "Continuous rain from 6 AM to 2 PM, 1.2 inches accumulated, standing water in excavation areas" is defensible documentation.
Weather is the foundation of delay claims. A contractor who records "rain" for 30 days has weak evidence. A contractor who records specific conditions, start/stop times, and impact on specific activities has a claim that holds up under scrutiny.
2. Workforce Headcount by Trade
Document every worker on site, broken down by trade and employer. Include your own crew and every subcontractor's crew. Record the number of workers, the trade (carpenter, iron worker, electrician, laborer), and the employer name.
This data proves manpower deployment during acceleration claims, demonstrates subcontractor staffing deficiencies, and provides evidence of crew size during productivity disputes.
3. Subcontractor Crews and Activities
Beyond headcount, record what each subcontractor crew was working on and where. "ABC Electric — 4 workers — pulling wire in Building A, 2nd floor" is far more useful than "Electricians on site." When a subcontractor claims they were delayed by your work, your daily report should show exactly where their crew was and what they were doing.
4. Work Completed (Tied to Schedule)
This is where most daily reports fail. Describing work in general terms ("poured concrete", "set steel") is not enough. Tie each activity to the project schedule. Reference the schedule activity ID or description: "Poured slab-on-grade for Building B, grid lines 4-8 (Activity 2340) — 180 CY placed."
When your daily report ties directly to your CPM schedule, you can trace delay impacts with precision. Without this connection, schedule analysis becomes speculation.
5. Equipment on Site
List major equipment on site and its status: operating, idle, or down for repair. Include equipment hours where applicable. This documentation supports equipment cost claims and proves utilization during extended overhead claims.
6. Material Deliveries
Record every material delivery: what was delivered, the quantity, the supplier, and whether it was accepted or rejected. Note any shortages, damage, or discrepancies from the purchase order. Late or defective material deliveries are a leading cause of construction delays.
7. Safety Observations and Incidents
Document your safety walkthrough observations: hazards identified, corrective actions taken, PPE compliance, and any near-miss incidents. If an incident occurs, record the details immediately — who was involved, what happened, what actions were taken, and who was notified.
This documentation is critical for OSHA defense. Inspectors look for evidence that the contractor was actively monitoring and addressing hazards. A daily report with consistent safety observations demonstrates the "good faith" that reduces penalties.
Capture All 16 Items in Under 5 Minutes
BuildLog lets superintendents speak their daily report, snap GPS-tagged photos, and submit — even without cell service. AI-assisted analysis flags safety concerns and documentation gaps automatically.
Start Free Trial8. Site Visitors and Inspections
Record every visitor: owner representatives, architects, engineers, inspectors (building code, OSHA, environmental), utility company workers, and any other non-crew personnel. Document their arrival and departure times, the purpose of their visit, and any directives or observations they communicated.
This is especially important for owner-directed changes. If the owner's representative verbally directs additional work, your daily report is the contemporaneous record that establishes the direction was given.
9. Delays and Their Causes
This is the most legally valuable section of the daily report. When work is delayed, document the cause with specificity: what activity was affected, what caused the delay, who is responsible, how long the delay lasted, and what crews or equipment were impacted.
"Concrete pour delayed" is worthless. "Concrete pour for Activity 2340 (Building B slab) delayed 4 hours. Ready-mix trucks arrived at 6:00 AM but Acme Plumbing had not completed underground rough-in in grid lines 6-8. Concrete crew (6 workers) and pump truck stood by idle from 6:00 AM to 10:00 AM" is a defensible record.
10. Change Order Work
Document any work performed under a change order or potential change order. Include the change order number (if issued), a description of the work, the labor and equipment used, and materials consumed. If the work has not yet been authorized by change order, document it as "directed work pending change order" with the name of the person who directed it.
11. RFIs Submitted or Answered
Record any Requests for Information submitted to the design team and any RFI responses received. Include the RFI number and a brief description. Unanswered RFIs are a common cause of delays, and your daily report should create a contemporaneous record of when information was requested and when (or if) it was received.
12. Photos with GPS Tags
Take photos daily. Minimum 5-10 photos covering: overall site conditions, specific work areas, safety conditions, delivered materials, and any problems or unusual conditions. Photos should be GPS-tagged and timestamped automatically. They should be attached directly to the daily report, not stored in a separate folder that nobody organizes later.
13. Schedule Variances
Note any activities that are ahead of schedule or behind schedule. Record the variance in days and the reason. This ongoing record of schedule performance is invaluable for delay analysis — it shows when the project first began to fall behind and identifies the driving causes.
14. Quality Issues Observed
Document any quality deficiencies observed in your own work or subcontractor work. Record the issue, the location, the responsible party, and the corrective action required. Photographic evidence is critical here.
15. Upcoming Work (Next Day Plan)
A brief note about planned activities for the next working day. This serves two purposes: it communicates plans to the office, and it creates a baseline to measure the next day's actual progress against. When planned work doesn't happen, the comparison between plan and actual reveals delays that might otherwise go undocumented.
16. Special Remarks
Any unforeseen conditions, unusual events, or observations that don't fit neatly into another category. Differing site conditions, utility conflicts, unexpected soil conditions, third-party impacts, noise complaints — anything that affected or could affect the project.
How Long Should a Superintendent Daily Report Take?
| Method | Time per Report | Completeness | Legal Value |
|---|---|---|---|
| Paper forms | 15-25 minutes | Low — handwriting limits detail | Medium — hard to read, no photos |
| Spreadsheets / email | 15-20 minutes | Medium — inconsistent format | Medium — no timestamps, no GPS |
| Enterprise PM software | 10-15 minutes | High — but requires internet | High — if completed consistently |
| Voice-to-text field app | 3-5 minutes | High — voice captures more detail | Very high — GPS, timestamps, audio backup |
The real metric is not how long the report takes — it's whether your superintendent completes it every single day. A 3-minute report completed 250 days a year is infinitely more valuable than a 20-minute report completed 60% of the time. Consistency is everything.
Common Mistakes That Destroy Report Value
- Writing reports days later from memory. A daily report written three days after the fact is not a contemporaneous record. Courts treat delayed documentation with skepticism. Write the report the same day, ideally at the end of the work day while details are fresh.
- Using vague language. "Work progressed" and "weather was bad" have no evidentiary value. Use specific quantities, times, locations, and causes.
- Skipping days. Gaps in the daily report record raise questions. If a critical event occurred during a gap, opposing counsel will argue that the absence of a report means the event didn't happen — or that the report was fabricated after the fact.
- Not tying work to the schedule. Daily reports that describe work in general terms cannot be used for forensic schedule analysis. Reference schedule activities by name or ID.
- Storing photos separately from reports. Photos in a camera roll or shared drive, disconnected from the daily report, lose their context. Attach photos directly to the report entry for that day.
- Ignoring subcontractor activities. Your daily report should document what every crew on site was doing, not just your own. Subcontractor delay claims are won and lost based on what the general contractor's daily report shows.
How BuildLog Simplifies Superintendent Daily Reports
BuildLog is construction daily report software built for the superintendent standing on a job site, not the project manager sitting in an office. It handles the entire daily report workflow:
- Voice-to-text input — speak the report instead of typing. The app transcribes the voice recording and keeps the original audio as an evidentiary backup.
- GPS-tagged photos — every photo is automatically tagged with GPS coordinates and a timestamp. Photos attach directly to the daily report.
- Offline functionality — works without internet. Everything is stored locally and syncs when connectivity returns. No lost reports on remote sites.
- AI-assisted safety analysis — flags potential safety concerns, documentation gaps, and recurring issues in your reports on demand.
- Professional PDF exports — clean, branded reports with embedded photos, timestamps, and GPS data. Ready for clients, inspectors, or attorneys.
A superintendent opens the app, speaks the day's report covering all 16 items, takes photos, and submits. The entire process takes 3-5 minutes. No training required. No forms to fill out. No internet required.
Your Daily Report Is Your Best Defense
BuildLog captures all 16 items by voice, with GPS-tagged photos and automatic transcription. Works offline. Exports professional PDFs. AI analysis flags safety gaps before they become violations.
Start Free TrialFrequently Asked Questions
What should a construction superintendent include in a daily report?
A construction superintendent daily report should include 16 key items: date and weather conditions, workforce headcount by trade, subcontractor crews on site, work completed tied to schedule activities, equipment on site and hours used, material deliveries received, safety observations and incidents, site visitors and inspections, delays and their causes, change order work, RFIs submitted or answered, photos with GPS tags, schedule variances, quality issues observed, upcoming work for next day, and any special remarks or unforeseen conditions.
How long should a superintendent daily report take to complete?
A well-structured superintendent daily report should take 10-15 minutes using paper or spreadsheets, or 3-5 minutes using a dedicated field reporting app with voice-to-text input. If your reports consistently take longer than 15 minutes, your process has too much friction and your team will eventually stop completing them.
Are construction daily reports legally required?
While no federal law requires daily reports specifically, OSHA requires documentation of safety training, inspections, and incidents. Most construction contracts also require daily logs as a contract obligation. Beyond legal requirements, daily reports serve as contemporaneous evidence in delay claims, disputes, and litigation — making them effectively mandatory for any contractor who wants legal protection.
What is the difference between a daily log and a daily report?
The terms are often used interchangeably. A daily log typically refers to a chronological record of site activities, while a daily report is a more structured document that includes workforce counts, weather, deliveries, and progress tied to the schedule. In practice, the best approach combines both: a structured format that captures all required data points while allowing free-text narrative for context.
Can I use voice-to-text to create daily superintendent reports?
Yes. Voice-to-text is increasingly common for field reporting. Apps like BuildLog let superintendents speak their daily report instead of typing, which is significantly faster and captures more detail. The best tools transcribe the voice recording and keep the original audio attached as a backup record. This is especially useful on active job sites where typing on a phone screen is impractical.