Free download — no email required

Construction daily report template

A daily report template with the ten fields that hold up later: weather, crew counts, work performed, deliveries, delays, safety, and photos. Free print-ready PDF, no email gate — and a walkthrough of why each field matters when a claim shows up two years after the pour.

Why do daily reports matter so much?

Because they are the only project document written the day things happened, by the person who watched them happen. Schedules get revised, meeting minutes get negotiated, memories get convenient — the daily report, filled out that evening, is the record courts, arbitrators, and insurance adjusters weight most heavily as contemporaneous evidence.

The practical test for every field is simple: if this project ends in a delay claim, a differing-site-conditions dispute, or a back-charge fight two years from now, what will we wish the super had written down today? The template below is that list, and nothing else — a report that takes 40 minutes stops getting filled out honestly by Thursday.

What goes in a construction daily report?

Ten fields. For each: what to record, and the dispute it settles later.

Date, project, report number

One report per project per day, numbered sequentially.

Why it holds up: A gap in the sequence is the first thing opposing counsel looks for. Consecutive numbering proves the record is a habit, not a reconstruction.

Weather

Conditions at start of shift and any change — temperature, precipitation, wind — plus hours lost to weather.

Why it holds up: Weather-delay claims live or die on contemporaneous records. “Rain, 10:30 to 2:00, concrete pour postponed” written that day beats any weather-service printout produced a year later.

Crew and manpower count

Headcount by trade or subcontractor, with hours worked.

Why it holds up: Manpower records prove acceleration, stacking, and loss-of-productivity claims — and disprove the sub who later says they “always had twelve on site.”

Work performed

What each crew actually did, where — by area, level, or gridline.

Why it holds up: This is the schedule’s reality check. When the as-built schedule gets disputed, the daily reports are the evidence of when each activity really started and finished.

Equipment on site

What equipment was on site, working or idle, and why if idle.

Why it holds up: Idle-equipment costs are a standard delay-damage component. “Excavator idle — waiting on utility locate” is a claim line item written in real time.

Deliveries and materials

What arrived, from whom, and its condition — note shortages and rejections.

Why it holds up: Ties the procurement record to the field record. A rejected delivery noted the day it happened settles the back-charge argument before it starts.

Delays and disruptions

Anything that stopped or slowed work: RFIs pending, trade stacking, access blocked, inspection failures.

Why it holds up: Most contracts require timely notice of delay. The daily report is where the paper trail starts — a delay first mentioned three weeks later reads as invented.

Safety — incidents, talks, inspections

Incidents and near-misses, toolbox talks held (with topic), inspections passed or failed.

Why it holds up: Connects the safety program to the daily record. If an incident surfaces later, the report shows what the site knew and did that day.

Visitors and inspections

Owner reps, inspectors, testing agencies — who, when, what they looked at.

Why it holds up: Establishes who observed conditions and when. “The inspector saw the rebar before the pour” only counts if it was written down that day.

Photos

Progress photos tied to the date and location — a few purposeful shots beat fifty random ones.

Why it holds up: Photos are the strongest contemporaneous evidence there is. Date-stamped progress photos have ended more disputes than any narrative paragraph.

Three habits that make the record defensible

Same day, every day

A report written Friday about Tuesday is a reconstruction. Fill it before leaving site — even a thin honest report beats a rich one written from memory. If nothing happened in a category, write “none”: it proves the field was considered, not skipped.

Facts, not fault

Write what happened, who was there, and what it affected — “drywall crew relocated to Level 2; Level 1 access blocked by plumbing rework” — and skip the editorial about whose fault it was. Reports get read aloud in depositions; anger ages badly, facts don’t.

Specific beats complete

Locations by gridline, quantities, times of day. “Poured 40 CY, area B2, 7:00–11:30” is evidence. “Concrete work ongoing” is filler that costs you credibility on the entries that matter.

Comparing daily-reporting tools? Raken built its product around this document — our honest take is in the Raken alternative page. For the safety side of the daily record, the toolbox talk library and the free JSA template pair with this one.

Or stop typing it at all

In Sympl · Project, the daily log drafts itself from the day’s activity — photos, weather, crew check-ins, T&M tickets — and the super reviews and submits instead of typing from memory at 6 pm.

  • Weather auto-pulled from the project location, timestamped
  • Photos with EXIF and GPS preserved, tied to the day
  • Agent-drafted log — the super edits, not authors

Frequently asked questions

What is a construction daily report?

A construction daily report (or daily log) is the one-page record a superintendent or foreman completes each working day: weather, crew counts by trade, work performed by location, equipment, deliveries, delays, safety activity, visitors, and photos. It is the project’s contemporaneous record of what actually happened.

Are daily reports required?

Usually by contract, not by regulation. Most commercial construction contracts require the GC to keep daily records, and many owner and CM agreements specify their contents. Even where nothing requires them, they’re the document that protects you in delay claims and disputes — which is reason enough.

Who fills out the daily report?

The person who watched the work: the superintendent on the GC side, the foreman for a self-perform crew or subcontractor. Delegating it to the office defeats the purpose — its value comes from being written by a firsthand witness, the same day.

Why are daily reports important in claims?

Because they are contemporaneous evidence — written at the time by someone with direct knowledge, before anyone knew there would be a dispute. In delay, disruption, and differing-site-conditions claims, consistent daily reports routinely outweigh schedules and recollections assembled after the fact.

How long does a daily report take to fill out?

With this template, ten to fifteen minutes at the end of the shift. If it takes much longer, the form has too many fields — completeness that kills the daily habit is worth less than a shorter record kept every single day.