Construction Daily Report: What to Include (+ Template)

Many general contractors require subcontractors to submit a daily report form before they sign off on the day's work. But even when no one is asking for it, a complete daily report is one of the cheapest forms of protection a sub can carry. When a delay claim hits, when a GC disputes your change order, or when an inspector questions what was on site last Tuesday — your daily reports are the contemporaneous record that answers the question.

This guide breaks down exactly what belongs in each section of a construction daily report, with notes on how to fill each one out so the record is actually useful. At the end you'll also find how to file these digitally so they're searchable and ready when you need them.

What is a construction daily report?

A construction daily report is a dated record of everything that happened on a job site on a given day. General contractors call it a daily report; subcontractors and field software often call it a site log or daily log. The content is the same: who was on site, what was built, what arrived, who visited, and what went wrong or was delayed.

Most GCs have their own daily report forms. Many also have their own project-management portals where subs submit them. Fill out whatever the GC requires — and keep your own record too. The GC form manages the project; your record protects you.

The 8 sections every daily report should have

1. Project identification and date

The header ties the report to a specific project and day. At minimum: project name, project number or address, date, and the name of the person filing the report. If you have a contract number or GC-assigned document number, include it. This sounds obvious but matters in disputes — a stack of reports with no header is nearly useless.

2. Personnel on site

List everyone your company had on the job that day: name or classification (foreman, journeyman, apprentice, laborer), hours worked, and what area or task they were assigned to. This section:

• Supports labor billing on time-and-material work and change orders — you can tie hours to scope
• Demonstrates adequate staffing if a delay claim arises against your schedule
• Gives you a record of actual vs. planned manpower you can review later

Don't just write a headcount. "4 workers on site" is much weaker than "Foreman J. Reyes (8h, rough-in Building A), 2 journeymen (8h ea., panels 2A and 2B), 1 apprentice (8h, conduit pull 1st floor)."

3. Work performed

Describe what your crew actually completed that day. Use location references that match the drawings — building, floor, room number, gridline. "Installed 180 LF of 2-inch EMT conduit, Building A, 3rd floor, Rooms 301–312" is usable evidence. "Continued conduit work" is not.

Also document work that was planned but could not be performed, and why. "Unable to start trim-out in Suite 205 — suspended ceiling grid not installed by others" is a contemporaneous record of a delay you did not cause. That entry, dated and filed the day it happened, is far more credible than raising it for the first time at closeout.

4. Equipment on site

List major equipment — boom lifts, excavators, welding machines, compressors, generators. Note rental equipment separately with start and end dates. If equipment sat idle due to access issues, weather, or delays caused by other trades, record that explicitly. Idle equipment time is a recoverable cost in many delay and disruption claims — but only if you documented it at the time.

5. Materials received and stored

Log all deliveries with quantities, vendor, and where materials were stored on site. Note any damaged or short shipments and how you handled them. This section serves two purposes: it creates a chain of custody for materials, and it supports stored materials billing on your pay applications — the GC or owner needs to see that material was delivered and is on site before they'll pay for it.

Also note long-lead items that were expected and did not arrive if that affected your schedule.

6. Visitors and inspections

Record every visitor to the site: owner's representatives, GC superintendents, architects, engineers, city inspectors. For inspections, note the result — passed, failed, partial — and what was inspected. If an inspector flagged an issue, document the specific item and the required corrective action. If the issue was caused by another trade's work or a design conflict, say that.

An inspection that passes without documentation is still just your word. An inspection that fails without documentation is a liability.

7. Safety observations

Document safety toolbox meetings: date, topic, and attendance. Note any incidents, near-misses, or hazards — even those involving other trades. If you reported an unsafe condition to the GC or owner, record that you did and when. Safety documentation is both a legal requirement on many projects and a liability shield when incidents are investigated.

8. Delays, disruptions, and issues

This is the most important section and the one most subs skip entirely. Any time your work is delayed or disrupted by something outside your control, you need a real-time record:

• Areas not accessible or not ready for your trade
• Missing or late information — RFI responses, shop drawing approvals, design clarifications
• Other trades blocking your work area
• Late or incorrect material deliveries caused by others' scope changes
• Schedule changes communicated by the GC
• Weather conditions that stopped or slowed work (note times and impact, not just "rain")

The reason to document this in real time — not at the end of the month, not when you're preparing a change order — is credibility. A delay documented the day it happened is contemporaneous evidence. A delay summarized weeks later is a reconstruction, and reconstructions lose to contemporaneous records in almost every dispute.

Daily report template: a section-by-section reference

Use this as a checklist when filing your report each day. Each section maps to one of the eight areas above.

What makes a daily report legally defensible

Filling out a report is not the same as filling it out well. A few practices that separate useful records from ones that get dismissed:

• Specificity over summaries. "Rain from 7 AM to 10:30 AM, standing water in the excavation, underground rough-in stopped for 3.5 hours" is evidence. "Weather delay" is not.
• File it the same day. Contemporaneous means you wrote it while memory was fresh. If you're filling in reports on Friday for Monday through Thursday, you've already degraded their evidentiary value.
• Be consistent. A log kept every single working day is far harder to challenge than one with gaps. Gaps invite the question of what happened on the missing days.
• Attach photos. A photo with an embedded timestamp of the flooded excavation, the blocked work area, or the delivered material is stronger than words alone.
• Don't editorialize. "Concrete pour delayed 4 hours because GC did not have pump truck on site as scheduled" is a factual statement. "GC completely mismanaged the concrete pour" is an opinion that will be attacked in any proceeding.

Who writes it, and when

Both questions have the same answer: the person who was on site, that same day. A field record written by someone who wasn't there — or written the following week from memory — keeps the format but loses most of what makes it worth keeping.

That is a staffing question as much as a paperwork one. In BuildWorkPro, company admins, managers, members, and field crew can all create site logs, and the Field Crew role exists for exactly this: an on-site worker can write the day's record without getting access to bids, pricing, or billing. Make the log part of the end-of-day routine for whoever closes out the site, and it gets written by the person who actually watched the day happen.

Once it's written, a manager can mark the entry reviewed — a second set of eyes, and a filterable status so nothing sits unchecked. That review step is what turns a pile of individual notes into a record the company stands behind.

What to leave out

Two things belong nowhere near a daily report, and both are easy to get wrong under pressure.

Arguments about who is at fault. Beyond the editorializing point above, this matters most when a directive arrives verbally. Record that a verbal directive was given, who gave it, and what it covered — then follow up in writing through the proper channel. The log is a factual record of what happened; the case for who owes whom belongs in a formal notice, where it carries weight and gets a response.

Blank days. A missing entry on a day when something went wrong is worse than a thin one. "Rained all day, no work performed — site flooded east of the utility trench" is a complete record of a day nothing got built. An empty day says either nothing happened or nobody was tracking, and you don't get to choose which one a reader assumes months later.

Using site logs in BuildWorkPro

In BuildWorkPro, site logs are a dedicated field module — not an afterthought tacked onto project notes. Each log is tied to a specific project and date. You add personnel on site, write your notes, and tag the entry by type: Progress, Issue, Delay, Safety, Delivery, or Inspection.

The detail page lets you fill in Work Performed, Materials Received, Visitors on Site, and Issues as distinct fields — the same sections this template covers. Attach photos directly to the log entry. A manager can mark each log reviewed once it's been checked.

The tag is the part people skip, and it's the part that pays. Adding one costs two seconds on the day you write the entry. Six months later, when you need every day the work was held up to support a schedule extension request, it's the difference between a filter and an afternoon of reading:

• Delay entries become the timeline behind an extension claim — every day the work was held up, and why.
• Safety entries are the documented record if an incident is questioned later.
• Inspection entries capture what was inspected, by whom, and the result.
• Issue entries are your running log of problems — which answers a GC who says a problem was never raised.

You can filter the timeline or table view by project, tag, or reviewed status, and search by title or notes. That's what keeps a year of daily entries navigable instead of turning it into an undifferentiated wall of text.

When a delay or disruption rises to the level of a scope change, you can create a change order directly from the log — the field record becomes the paper trail behind the cost. For teams also using time tracking, crew hours tie to the same project and date, so labor and field activity are always in sync. See the site logs documentation for a full walkthrough.

If you want the broader picture on daily documentation habits and making logging a consistent crew routine, our construction site log best practices guide covers the discipline side — what to do when, who should own it, and why paper logs fall short.