On this page
- Step 1: Fill in the header and the weather
- Step 2: Record manpower by company
- Step 3: Describe the work performed by area
- Step 4: Log equipment, deliveries, visitors and inspections
- Step 5: Write delays as they happen
- Step 6: Record directions, conversations and changes
- Step 7: Safety, photos and tomorrow
- Worked example: a rain day
- Common mistakes
- How os.construction handles it
- FAQ
A good daily construction report records, the same day, the facts someone will need later: weather, manpower by company with hours, work performed by area, equipment, deliveries, visitors and inspections, delays with cause and times, directions received, safety items, photos and tomorrow’s plan. Write facts, times, counts and names, not opinions, and finish it before you leave site.
The daily log feels like paperwork on the day you write it. It becomes important on the day someone asks what happened: a delay claim, a disputed change, a back charge, an injury, a payment argument. By then memory is no help, and the report is what’s left. Our post on why daily logs are financial documents covers where those numbers end up. This one is about writing the report itself.
Step 1: Fill in the header and the weather
Project, date, report number, author. Then weather, twice: morning and afternoon, with sky, temperature, wind and any precipitation. Add ground and site conditions if they matter (standing water, frozen ground, mud on the haul road). Note whether weather stopped or slowed work, and which work. “Rain” alone doesn’t show that anything was affected.
Step 2: Record manpower by company
For every company on site, record the headcount and hours worked, and the trade or crew. If your company tracks labor against cost codes, note the area or cost code too. Count your own forces as well as subs. Many superintendents start from yesterday’s list and correct it, since most days look like the day before.
Step 3: Describe the work performed by area
Say what each crew did and where: “Framing, L2 east, gridlines 4–7: top track and studs complete, started door openings”. Where you track quantities, record them (cubic yards placed, linear feet installed). Specific locations matter because the question months later is usually about one area.
Step 4: Log equipment, deliveries, visitors and inspections
- Equipment: what’s on site, and hours operating and idle. Idle equipment on a delay day is a cost someone may need to prove.
- Deliveries: supplier, what arrived, who received it, and anything short or damaged.
- Visitors: name, company, purpose, time in and out.
- Inspections: inspector, scope, result, and any correction notice.
Step 5: Write delays as they happen
This is the entry that matters most later, and the one most often written badly. For each delay or disruption, record:
- What happened and what caused it.
- When it started and ended, or that it’s continuing.
- Who and what was affected: crews, headcount, equipment, areas.
- Who you told, and when.
A delay entry written the day it happens, with times and names, is the start of any time extension request. Check your contract’s notice requirements as well; the daily report is a record, not usually a substitute for formal written notice.
Step 6: Record directions, conversations and changes
When someone gives the field a direction that changes the work, write down who, what, when, and what it led to: an RFI number, a T&M ticket number, a change event. Phone calls that changed the plan go here too. Cross-referencing record numbers is what lets someone connect the report to the paperwork later.
Step 7: Safety, photos and tomorrow
Note the toolbox talk topic and who attended, any incidents or near misses (and that they were reported through your incident procedure), and any safety violations issued. Take photos with locations in the caption. Then write tomorrow’s planned work and crews, and sign or complete the report.
Worked example: a rain day
Daily report #87. Project: two-storey office building. Author: superintendent.
Weather. AM: overcast, 52°F, light wind, light rain from 9:15. PM: steady rain, 49°F, about 0.6 in. by 3:00 pm. Site: standing water at the area C slab subgrade; haul road muddy but passable.
Manpower.
| Company | Trade | Workers | Hours | Notes |
|---|---|---|---|---|
| GC (own forces) | Supervision, labor | 3 | 24 | |
| Concrete sub | Concrete | 6 | 24 | Sent home 11:00, see delay |
| Framing sub | Framing | 8 | 64 | L2 east, interior, unaffected |
| Electrical sub | Electrical | 4 | 32 | L1 rough-in |
| Total | 21 | 144 |
Work performed. Framing: L2 east, gridlines 4–7, top track and studs complete; started door openings. Electrical: L1 rooms 104–110, rough-in boxes and conduit. Concrete: set edge forms at area C until 11:00.
Equipment. Telehandler: 6 h operating. Concrete pump: ordered for today’s pour, cancelled at 8:40, no charge per supplier. Skid steer: on site, 0 h (idle all day, rain).
Deliveries. 10:30, drywall supplier: 120 sheets 5/8” Type X to L2, received by GC laborer, no damage.
Inspections and visitors. Pre-pour inspection for area C, scheduled 8:00, postponed by inspector due to rain; rescheduled for the next dry day. Owner’s rep on site 1:00–1:45 pm, walked L2.
Delays. Rain stopped the area C slab-on-grade pour. Pour scheduled 7:30 am, cancelled 8:40 am after the inspector postponed. Concrete crew (6) continued forming until 11:00, then sent home. Subgrade will need to be checked for moisture before rescheduling. Told the PM 8:45 am and the owner’s rep in person at 1:00 pm. Pour and inspection to be rescheduled; area C slab is on the current look-ahead for this week.
Directions and changes. None today.
Safety. Toolbox talk 7:00 am: slips and falls on wet surfaces, 19 attended. No incidents. Mud on the L1 stair entry; laborer assigned to clean and set mats.
Photos. 6 photos: area C subgrade at 8:30 and 2:00 pm, L2 east framing progress, drywall delivery.
Tomorrow. Framing L2 east (8). Electrical L1 (4). Concrete: re-check area C subgrade with the sub’s foreman at 7:00 am; pour only if subgrade and inspector allow.
Compare the delay entry with the version that often gets written: “Rain. No pour.” That one says nothing about times, crews, equipment, the inspection, or who was told, which is everything someone will need if the pour slips the schedule.
Common mistakes
- Skipping quiet days. A day with no entry is a day you can’t show anything about.
- Writing it later. Reports reconstructed at the end of the week miss times and names.
- Opinions instead of facts. “Electrician slow again” helps nobody; “Electrical, 4 workers, 8 h, rooms 104–110 rough-in” does.
- Weather without impact. Say which work it stopped and for how long.
- No cross-references. If a direction became an RFI or T&M ticket, put the number in.
- Copying yesterday without correcting it. Copied manpower that’s wrong is worse than none.
The free daily log checklist lists every item above, and the printable daily construction log gives you a one-page form.
How os.construction handles it
The Daily Log is one page per day with sections for weather, manpower, notes, visitors, deliveries, equipment, accidents, phone calls, delays, quantities, safety violations, scheduled work and more. Copy from previous day brings yesterday’s manpower forward, Complete Day locks the entries until someone reopens it, and each day exports to PDF or CSV. It runs in a phone’s browser and needs a connection; offline capture is planned. The daily reports walkthrough shows a completed day, and construction daily log software covers what to look for in any daily log tool.
FAQ
What should be included in a daily construction report?
The date, project and author; weather in the morning and afternoon; manpower by company with headcount and hours; work performed by area and trade; equipment on site and its hours; deliveries; visitors and inspections; delays with cause, times and who was affected; directions received and the RFI or T&M ticket they led to; safety items; photos; and the next day's planned work.
Who writes the daily construction report?
Usually the general contractor's superintendent, sometimes with input from foremen or an assistant superintendent. Many subcontracts also require each sub to keep and submit its own daily reports.
When should the daily report be written?
The same day, before leaving site, including quiet days. A report written days later from memory is weaker evidence and usually missing detail. Notes during the day make the end-of-day write-up quick.
How detailed should a daily report be?
Detailed enough that someone who wasn't there could tell what happened: which crews worked where, what stopped work and for how long, who gave which direction. Facts, times, counts and names, not opinions.
How long should daily reports be kept?
At least through the end of the job and as long as claims, warranty issues or audits could arise afterward. Your contract, insurer and legal counsel set the actual retention period.
Share this article