How to Write a Construction Daily Report: A Step-by-Step Guide for the Field
To write a construction daily report, record the day in a fixed order: project and date, weather, manpower and hours by company, work performed by location with quantities, equipment, deliveries, delays with start and stop times, safety items, visitors and inspections, and photos. Write it the same day, use specific numbers and locations, state facts without opinion, and keep the same structure every day so anyone can compare reports across the job.
If you want the definition and the reasons daily reports matter, start with our guide on what a construction daily report is. This article is the practical how-to: the order, the level of detail, and sample text.
Before you start: set up the report once
Most bad daily reports come from a blank page every evening. Set these up at the start of the job so the daily part is only the day's facts.
- Project header: project name, number, address, owner, and report number sequence.
- Company list: every subcontractor and sub-tier expected on site, with the foreman's name and phone number.
- Location language: agree on how you name areas (Level 2, gridlines C to F, Building B east wing). Use the same names the drawings use.
- Schedule activity names: if your schedule has activity IDs, keep a short list handy so work performed can reference them.
Step 1: Record the weather, every day
Write the conditions at start of shift, midday and end of shift: temperature, precipitation, wind, and ground conditions. Record good weather too. "Clear, 62 F at 7:00 AM, 71 F at 2:00 PM, no impact to work" is a baseline that makes a later weather claim believable.
When weather affects work, write the impact in hours and crews: "Rain from 10:15 AM to 12:40 PM. Roofing crew (6) stood down 2.5 hours. Exterior framing (4) moved to interior Level 1." For more detail see our guide to weather delay documentation.
Step 2: Log manpower and hours by company
List every company on site with headcount and hours. Break out trade when one sub has more than one crew.
| Company | Trade | Workers | Hours | Area |
|---|---|---|---|---|
| ABC Concrete | Concrete | 6 | 48 | Level 2 deck, C to F |
| Northline Electric | Electrical | 4 | 32 | Level 1 rough-in |
| General contractor self-perform | Carpentry | 3 | 24 | Stair 2 blocking |
Totals matter. If the schedule assumed 10 electricians and 4 showed up for a week, the daily reports are where that pattern becomes visible. See construction manpower tracking.
Step 3: Describe work performed with location and quantity
This is the heart of the report. Each line should answer: what, where, how much, and who.
- Weak: "Concrete work on second floor."
- Strong: "ABC Concrete placed 38 CY of 4,000 psi on Level 2 deck, gridlines C to F, 7:30 AM to 11:45 AM. Pump truck on site 7:00 AM to 12:15 PM."
Compare planned to actual when they differ: "Installed 140 LF of interior framing on Level 3 versus 200 LF planned. Ductwork in the corridor ceiling blocked sequence. Second day of this condition."
Step 4: Equipment and deliveries
Note equipment on site, whether it worked, sat idle, or was down, and why. Idle equipment costs money and often signals a delay worth recording.
For deliveries, log the supplier, material, quantity, ticket number, and condition. Write down rejections and short shipments the same day: "Received 12 of 16 storefront frames from Coastal Glass, ticket 44817. Four frames back-ordered, supplier says Thursday."
Step 5: Delays, issues and open questions
For every delay record cause, start and stop time, affected crews, and whether it continues tomorrow. Keep writing it daily until it is resolved. A delay mentioned on day one and then dropped looks like a one-day problem in a claim review. See daily reports for delay claims.
Also log open items that could become delays: pending RFIs, missing information, access conflicts, failed inspections. Reference the RFI number when there is one.
Step 6: Safety
Record pre-task plans completed, any incident or near miss, and corrective actions assigned. If nothing happened, say so: "No incidents or near misses reported." Our pieces on incident reporting and near-miss reporting cover what to capture.
Step 7: Visitors, inspections and instructions
Log who came on site, when, and why: owner's rep, architect, inspector, testing agency. Record inspection results. Write down verbal direction from the owner or design team and confirm it in writing: "Owner's rep J. Patel directed relocation of the Level 1 floor box at room 112 to the north wall. RFI to follow."
Step 8: Photos
Attach dated photos tied to the entries above: the pour, the delay condition, the damaged delivery, the inspection tag. Caption each one with location. See construction photo documentation for a simple routine.
Step 9: Review and submit
Read it once as if you were a stranger reading it in three years. Fix vague words, add missing times, sign it, and submit it. If you must correct a submitted report, issue a revision and keep the original.
Sample daily report text
Project: Riverside Middle School Addition, Report #142, Tuesday Weather: 7 AM 48 F overcast. 1 PM 57 F light rain 1:10 PM to 2:30 PM. Site muddy at east lot. Manpower: ABC Concrete 6 (48 hrs), Northline Electric 4 (32 hrs), Summit Mechanical 5 (40 hrs), general contractor 3 (24 hrs). Total 18 workers, 144 hrs. Work: ABC placed 38 CY slab on grade, Wing B classrooms 104 to 108. Northline pulled feeders to panel LP-2. Summit set 2 rooftop curbs, Wing A. Delays: Rain stopped east lot grading 1:10 PM to 2:30 PM. Excavator idle 1.3 hrs. RFI 087 (door hardware at 106) still open, day 4. Safety: 4 pre-task plans received. No incidents or near misses. Visitors: City inspector passed under-slab plumbing at Wing B, 8:20 AM.
Want a blank version to start from? Download the free daily report template.
The faster way: capture during the day
The real fix for late, thin reports is capturing information as it happens instead of at the end of the day. That is the idea behind Cascade. Cascade is SMS-first field intelligence for general contractors and subcontractors: superintendents and foremen text in their day, along with their subs, and Cascade builds the daily report. It covers: Daily reports, manpower and hours by sub, photos, toolbox talks, pre-task plans (JHA), safety incidents and corrective actions, project + schedule planning, automatic sub reminders, analytics and plain-English answers. Subcontractor access is free, and teams see 95%+ sub daily report compliance.
Onboarding and integration are free, and you can run a one-month pilot on the general contractor plan with no contract lock-in. We beat Raken, Procore and ACC on price, guaranteed. See how it works by text.
Frequently asked questions
How long should a construction daily report take to write?
For a superintendent on a mid-size job, 10 to 20 minutes if notes are captured during the day. It takes much longer when the report is reconstructed from memory at 6 PM, which is why capturing entries as things happen matters more than the form you use.
When should a daily report be written?
Same day, before you leave the site. Many subcontracts and specs require submission by a set time the next morning, such as 9:00 AM. Reports written days later carry less weight if they are ever used as evidence.
Who should write the daily report on a construction project?
The general contractor's superintendent usually writes the project daily report. Each subcontractor foreman should also submit a daily report for their own crew, which the superintendent rolls up into the project record.
What if nothing happened on site that day?
Write a report anyway. Record the weather, that no crews worked, and why. A 'no work' day with a reason protects you later when someone asks why the schedule slipped.