Construction daily report template (Excel + PDF)
A clean, field-ready daily report covering labor, equipment, materials, work performed, delays, safety, and visitors — built by a preconstruction manager who’s read thousands of them. Below the download: a full guide to filling it out so the record actually protects you.
Everything a daily report should capture
Labor & equipment
Every company on site, trade, headcount, and hours — with totals that calculate themselves in the Excel version — plus equipment used or sitting idle.
Conditions & deliveries
Weather AM/PM, temperature, site conditions, and materials delivered — the context that explains schedule and productivity later.
The record that protects you
Work performed, delays and issues, safety activity, and visitors — the entries that win disputes months after everyone’s memory fades.
The daily report is the project’s memory
Every construction dispute eventually comes down to the same question: what actually happened, and can you prove it? Schedules get debated, delay claims get filed, pay applications get challenged, and “we had a full crew out there” meets “no you didn’t.” The side with contemporaneous daily reports wins those arguments overwhelmingly more often than the side reconstructing events from memory and text messages.
In seven years of preconstruction across GC and subcontractor work, I’ve watched daily reports settle six-figure delay disputes — and I’ve watched their absence lose them. A same-day entry that says “concrete crew idle 7:00–11:30, waiting on RFI-023 answer for grid D, reassigned to site cleanup” is evidence. A recollection offered eight months later is a story. That’s the whole reason to fill one of these out every single working day, whether the day was dramatic or completely boring.
The boring days matter more than you’d think: an unbroken run of reports is what makes the dramatic ones credible. If reports only exist for days you later needed leverage, opposing counsel will notice — and so will an arbitrator.
How to fill out every section properly
Ten fields, and the specific way each one protects you when it’s written right.
Project, report # & date
Number reports sequentially and never skip or reuse a number — gaps get a record challenged. One report per calendar day, including no-work days (“no work performed — [reason]”). Those no-work entries are gold in weather-delay claims.
Weather & site conditions
AM and PM separately, with temperature. “Rain” is weak; “steady rain 6:30–10:00, standing water in the grid D excavation, pour postponed” ties weather to a consequence — the backbone of weather-delay documentation.
Labor on site
Every company, not just your own forces: trade, headcount, hours, and where they worked. Labor hours support pay apps and T&M billing — and defeat the back-charge claim that says nine workers when your uncontested report says three.
Equipment on site
Used and idle. An excavator sitting four days behind a design hold is a quantifiable delay-damage line item — but only if the idleness was recorded while it was happening.
Materials delivered
What arrived, quantity, from whom. Your receipt trail for stored-materials billing, your defense in a shortage dispute, and your timestamp when a late delivery cascades into a schedule slip.
Work performed today
Specific, located, quantified: “formed and poured footings F-12 to F-18, grid D, ±34 CY” beats “concrete work.” A scheduling expert reconstructs the project from these entries — make them reconstructable.
Delays / issues
What stopped, when, why, what it’s waiting on, and what the crew did instead — naming the RFI or drawing revision. Extra work spotted here isn’t a note, it’s money: price it as a change order while it’s fresh.
Safety
Toolbox talks, inspections, incidents, near-misses, corrective actions. Even “ladder safety talk, 23 attendees, no incidents” builds the run-safe pattern that matters if OSHA visits or an injury claim lands.
Visitors / inspections
Owner reps, architects, inspectors, testing agencies — who, when, and anything they directed. Verbal field direction recorded same-day has started (and won) many change order conversations.
Signature
Whoever watched the day happen signs it — usually the super or foreman. An unsigned report is a draft; a signed one is a record.
What a good entry looks like
Same day, two ways. The left column is what most daily reports say; the right column is what wins disputes:
| Section | Weak entry | Strong entry |
|---|---|---|
| Weather | Rain | Steady rain 6:30–10:00 AM, 54°F. Standing water grid D excavation; footing pour postponed to Wed. |
| Labor | Concrete crew on site | BR Concrete — 6 workers, 8 hrs, footings grid D. Ace Electric — 3 workers, 8 hrs, rough-in Level 1. |
| Work performed | Concrete work | Formed footings F-12 to F-18, grid D. Rebar inspected & passed, 2:15 PM, City of Alpharetta. |
| Delays | Waiting on answers | Crew idle 7:00–9:30 waiting on RFI-023 (grid D dimension conflict, S-201 Rev 2 vs Rev 3). Reassigned to washout relocation. |
| Visitors | Owner came by | Owner’s rep (J. Martinez) on site 1:00–1:45; directed adding a floor drain at Rm 114 — flagged for pricing as CO. |
Notice the strong column keeps referencing documents — the RFI, the drawing revision, the change order. That cross-referencing is what turns a stack of daily reports into a coherent project record. It’s also exactly what construction document management does automatically when the documents live in one system.
Four ways daily reports go wrong
Backfilling on Friday
A week of reports written in one sitting reads exactly like what it is. Time-stamps, consistency, and same-day detail are what make the record contemporaneous — the legal word for “credible.”
Vague entries
“Worked on Level 2” protects nobody. If a stranger couldn’t reconstruct the day from your entry, neither can the scheduling expert defending your delay claim in two years.
Only filing on bad days
Reports that exist only when something went wrong look manufactured, because they were. The unbroken daily habit is what gives any single report its weight.
Keeping it in a truck
A daily report nobody can find is a daily report that doesn’t exist. File them in one organized, searchable place per project — a binder if you must, a document management system when the stack gets serious.
Daily report vs. daily log vs. field report
You’ll hear construction daily report, daily log, daily construction report, and field report used almost interchangeably — and for practical purposes they’re the same document: the dated record of a day on site. Where teams draw a distinction, “daily log” usually means the superintendent’s running diary (sometimes more informal), while “daily report” implies the structured, distributed version that goes to the office and often to the owner. This template works as either: it’s structured enough to distribute and fast enough to fill out as a log. Whatever your contract calls it, check the reporting clause — many contracts specify what the daily record must include and how often it’s submitted, and this template covers the standard requirements.
Made by a contractor, not a content farm. Keaton Bandhoesingh, Founder of Planroom — preconstruction manager across three construction firms with $100M+ directly awarded. This template is the format his own field teams use: complete enough to hold up in a dispute, short enough that a super actually fills it out. Read the story →
Good to know
What is a construction daily report?
A dated record of everything that happened on site that day — who worked, what got done, what was delivered, what went wrong, and who visited. Filed consistently, daily reports become the project’s memory: they support pay apps, defend delay claims, and settle “that never happened” arguments with a time-stamped entry.
What should a daily report include?
At minimum: project and date, weather and site conditions, labor by company/trade/headcount/hours, equipment on site (used and idle), materials delivered, work performed, delays or issues, safety activity, and visitors or inspections — with a signature. That’s exactly the structure of this template.
Should I use the Excel or PDF version?
Excel if you fill it out on a laptop or want labor-hour totals calculated automatically; PDF if the field fills it out by hand on a clipboard. Many teams print the PDF for the field and transcribe into Excel for the record — the format is identical.
Who fills out the daily report?
Whoever actually watched the day happen — usually the superintendent or foreman. The weakest daily reports are written by someone in the office reconstructing events secondhand.
How long should we keep daily reports?
At least through the applicable statute of repose in your state — commonly 6–10 years after completion — because latent-defect and delay claims can surface long after closeout. Storage is cheap; keep them all, organized by project. (General information, not legal advice.)
Do daily reports actually matter legally?
Contemporaneous project records are consistently among the most persuasive documentation in delay and change disputes — a same-day entry carries weight that reconstructed testimony doesn’t. That’s also why keeping them organized and findable matters as much as writing them. (General information, not legal advice.)
What about photos?
Take them, reference them in the report (“photos 047-01 to 047-06, grid D excavation”), and store them with the report. A dated photo tied to a dated entry is about as strong as field documentation gets.
When the paperwork outgrows the spreadsheet
Templates are genuinely enough for many crews. When you’re chasing signatures and versions across email, that’s when software earns its keep — Planroom’s daily report software files these from a phone in minutes — alongside your change orders, document management, submittals, and RFIs for $149/mo flat, no contract.
More included templates: change order · change order log · transmittal · submittal log · RFI — or see all templates.
Grab the template. It’s yours.
Excel and PDF, no email gate, yours forever. From a contractor who actually uses it.
Download the template →