Daily construction report template

The daily construction report is written for a reader you hope never shows up: the person reconstructing, two years from now, why the job finished eleven days late. Everything in the template below is there because it can be counted, dated or contradicted.

The report a superintendent files in four minutes at 3:45 pm and the report that supports a delay claim are the same document. It just has to be built out of facts instead of a paragraph.

The header carries the weather because the weather is evidence

Weather is not small talk on a daily log. A rain delay you can point to on the 2nd of September, in a report written on the 2nd of September, is worth more than any weather service printout you produce later, because yours says what the rain actually stopped.

File a report on days when nothing happened. A gap in the log is the gap the other side's claim gets argued through, and "no work, site shut for the storm" is one line.

Count the crews, do not describe them

"Full crew on site" is not a number and cannot be added up. Eighteen workers across four trades can be, and a month of those rows answers questions about productivity that no amount of narrative will.

Count what you see when you walk it. Estimating from the sign-in sheet is how a log records twelve workers on a day nine showed up.

Work performed is organized by area, not by trade

Trades already have a row in the manpower table. The work section answers a different question: what changed in the building today.

Write it by area, in the order a person would walk them. "Dock apron, bays 1 to 6: placed and finished 240 cubic yards, screeded by 11:00, saw cuts started at 14:00." A reader can stand in bay 3 next week and check that against what is there.

Two other things belong in this section. Anything that got covered up (underslab plumbing, in-wall rough-in, waterproofing behind a substrate) gets a line, because after today nobody can see it without demolition. And anything that reached a hold point, meaning work that cannot proceed until an inspection passes.

A delay is only a delay if it has times

The line worth writing carefully looks like this:

Steel erection stopped 10:15 to 13:40, grid D to F. Crane could not lift in sustained wind measured above the erector's limit. Five workers idle, 3 hours 25 minutes.

Cause, area, clock times, headcount, duration. "Weather delays this morning" has none of them and is worth nothing when the schedule analysis happens.

Log the small ones too. A late concrete truck that costs forty minutes reads as trivial on the day and becomes a pattern when it shows up eleven times in a month.

Deliveries, inspections and visitors are one line each

Deliveries: what arrived, from whom, and whether it was accepted. Rejected material needs a line explaining why, on the day it was rejected.

Inspections: who inspected, what, and the result. A failed inspection with the correction required, written that afternoon, prevents an argument about when the crew was told.

Visitors: anyone on site who does not work there. The owner's representative, the architect, the fire marshal, the insurance inspector. A name and a time. When someone later says they raised a concern on site, the log either supports it or does not.

A filled example, from a day that never happened

Date: Wednesday, September 2, 2026. Harbor Point Logistics Center, Phase 2. Prepared by J. Reyes, superintendent. Weather: rain until 10:30, then overcast. 54 to 61 F. Working hours 6:30 to 15:30.

Manpower: 18 workers across concrete (8), steel (5), electrical (3) and plumbing (2).

Work performed:

• Dock apron, bays 1 to 6: placed and finished 240 cubic yards. Screeded by 11:00, saw cuts started 14:00.
• High bay, grid C to F: steel erection resumed 13:40 after the wind delay. Four bays set.
• Level 1 north: electrical rough-in continued in the office build-out. No walls closed.
• Restroom core: underslab plumbing complete and photographed before backfill. Ready for inspection Thursday.

Delays: steel erection stopped 10:15 to 13:40, grid D to F, sustained wind above the erector's limit. Five workers idle, 3 hours 25 minutes.

Deliveries: two loads of rebar accepted at 07:20. One load of anchor bolts rejected at 13:10, wrong diameter, supplier notified same day.

Inspections: none. Underslab plumbing inspection requested for Thursday.

Visitors: owner's representative on site 09:00 to 09:45, walked the dock apron.

Write what happened, not what you thought of it

Opinions about a subcontractor's performance. Record the hours and the output instead. "Crew was slow" helps nobody and reads badly when the log is produced in a dispute.

Safety incident details. Log that an incident occurred and that the incident report was filed. The details belong in that report, under whatever process your safety program requires.

Tomorrow's plan. A daily report is a record of a day. Planning belongs in the look-ahead schedule, and mixing them means a reader cannot tell what happened from what was intended.

Photos with no area attached. A photo of rebar is worth something if the caption says which bay and what time.

Sitewise covers the walk that produces those photos, on iPhone and iPad: capture, dictate a note that transcribes on the phone, sketch on the image, and every frame carries its own timestamp and, when location is on, a GPS pin, offline if the site has no signal. Exporting the day gives you a PDF or DOCX with the photos and captions in capture order, ready to attach to whatever system holds your logs. It is not a scheduling or budgeting tool and does not replace one.

The photo half of the log has its own rules, and the photo documentation guide covers what to shoot before something gets covered up.

A daily log is worth what its worst month is worth. Twenty good entries and eight blank days leaves you arguing about the eight, so the habit that matters is filing the boring ones.