How to Write a Construction Daily Report (With a Free Template)

A construction daily report is a same-day written record of what happened on a job: who was on site, what work got done and how much, what equipment ran, what the weather did, and anything that slowed the work down or changed it. Write it before the crew leaves, keep the format the same every day, and use quantities, locations and times instead of general descriptions.

That's the short version. The rest of this guide covers what goes in each section, how to word entries so they hold up months later when someone is reading them across a table, and a template you can copy straight into a notes app, a spreadsheet or a printed form.

Why the daily report matters more than it feels like it does#

At 4:30 in the afternoon the daily is the last thing a foreman wants to do. It feels like paperwork for the office. It is, but it's also the only record of that day that was written by someone who was there, on that day.

Here is where it gets used:

• Payroll and job cost. Hours and cost codes on the daily back up the timecards. When a PM asks why the forming code is over budget, the dailies are where you look.
• Change orders. Extra work that wasn't in the scope gets priced from what the daily says you did. "Hand-dug around unmarked utility, 4 laborers, 2.5 hrs" is billable. "Ran into some issues" isn't.
• Delay and weather claims. If you ever ask for time or money because of rain, a late delivery or another trade in your way, the daily is your evidence that it happened and how much it cost you.
• Disputes. Records written at the time generally carry more weight than anyone's memory a year later. That cuts both ways: a vague or missing daily helps whoever is on the other side.
• Production tracking. Units installed per day, by crew, is how you find out whether the estimate was right and how you bid the next one.

None of that works if the report says "worked on site, good day."

What to include in a construction daily report#

Most good dailies have the same dozen sections. Some jobs add more (a DOT job will have its own forms, a federal job may require specific contractor quality control reports), but this is the base.

Job info and shift times#

Put the job number on every report, not just the name. Two jobs called "Riverside" will happen eventually. Record the actual shift start and end, not the scheduled one. If the crew was on the clock at 7:00 but couldn't get on the pad until 8:15 because the gate was still locked, the shift starts at 7:00 and those 75 minutes go in the delay section.

Weather#

Record weather every day, including nice days. A stack of dailies that only mentions weather when it rained looks selective, and it gives you nothing to compare against when you need to show that a given week was unusual.

A practical approach is to log conditions at two or three fixed times, say 7:00, noon and 3:00, plus anything that changed the work. Note ground conditions too: "standing water in footing excavations, pumped 1.5 hrs before forming" tells a reader much more than "rain overnight."

Manpower and hours#

List every person on your crew, their classification (laborer, operator, finisher, journeyman, apprentice), hours worked and the cost codes those hours went to. For subs, a company name and headcount is usually enough unless your contract asks for more.

On prevailing-wage jobs the classification matters. The daily should match what's on the certified payroll, and payroll staff will thank you for catching a mismatch on day one instead of at the end of the month.

If your crew's time is already in a time-tracking app by cost code, the daily doesn't need to repeat every punch. Reference it, and make sure the two agree.

Equipment#

Track each piece of equipment by unit number: hours operated, hours on site but idle, and why it was idle. "Excavator #14 on site 8 hrs, operated 3 hrs, idle 5 hrs waiting on locate" is the sentence that supports a standby claim. A list of machines with no hours doesn't.

Rented equipment should be noted with the rental company and the date it arrived or went off rent. Off-rent calls that never got made are a quiet budget leak on a lot of jobs.

Work completed#

This is the core of the report, and it's where most dailies go soft. Every line should answer four questions: what task, where, how much, and in what unit.

The numbers in that table are examples, but the pattern is the point. If the office can't turn your work-completed line into a quantity per hour, it's not specific enough.

Materials and deliveries#

Record what arrived, from which supplier, the ticket number, the time, and whether it was complete and undamaged. Short or damaged deliveries should be photographed before anything is moved. If the concrete truck showed up 50 minutes late and your finishers stood around, write the arrival time and the batch time from the ticket.

Delays and problems#

A delay entry needs five things:

1. What happened (cause).
2. When it started and when it ended, or "ongoing."
3. What work and which people or equipment were affected.
4. Who you notified, how and when (call, text, email to the PM or GC super).
5. What you did about it (moved the crew to other work, sent people home, waited).

Then carry it forward. If the RFI on the wall embed layout is still open the next day, it goes on the next daily too, and the one after that. A delay that appears on one report and then disappears looks like a one-day problem, even if it held up the wall for two weeks.

Changes and extra work#

When someone gives direction in the field, write down who, when and exactly what they said. "Owner rep (name) directed at 10:20 to raise top of wall elevation 4 inches at gridline C; crew re-formed 32 LF" is the start of a change order. A verbal direction that never got written down is often a fight later.

Most contracts have their own written notice requirements and deadlines for changes and claims. A line in the daily is usually not a substitute for formal notice under the contract, so check the notice clauses on each job and get the PM involved the same day.

Visitors and inspections#

Inspectors, engineers, owner reps, the GC's safety person, utility locators: name, company, time on site, what they looked at and what the result was. A passed rebar inspection with the inspector's name and the time can save a lot of back and forth if a question comes up after the pour.

Safety#

Note the toolbox talk topic and who attended, any first aid cases, incidents or near misses, and the corrective action taken. Follow your company safety program and your competent person's direction on what gets documented where. The daily is not the official injury log.

Under federal OSHA, many employers are required to keep injury and illness records on OSHA Forms 300, 300A and 301, and 29 CFR 1904.39 requires employers to report a work-related fatality to OSHA within 8 hours, and an in-patient hospitalization, amputation or loss of an eye within 24 hours. State-plan states can have their own rules. Who handles those reports is a company decision, so make sure every foreman knows who to call. Then note in the daily that the call was made and when.

Photos#

Take progress photos at roughly the same spots each day so they can be compared. Then take extra photos of anything unusual: a damaged delivery, water in an excavation, another trade's materials blocking your work area, an existing condition that doesn't match the drawings.

A photo with no context is half a record. Each one should be tied to the report, with the date, time, location on site and one line about what it shows. Most phones stamp the date and time in the file's metadata, but a caption still helps the person reading it six months from now.

Sign-off#

The person who wrote the report signs and dates it. If a super reviews the foreman dailies, they sign as reviewer. Don't let the office edit a submitted daily without a note of what changed and who changed it. Silent edits undermine the whole record.

Free construction daily report template#

Copy this into a notes app, a shared document or a spreadsheet, or print it. Delete sections that don't apply to your trade, but keep the order the same every day so reports are easy to compare.

CONSTRUCTION DAILY REPORT

Job name:                         Job #:
Date:                             Report #:
Written by:                       Title:
Shift start (actual):             Shift end (actual):

WEATHER
  7:00   Conditions:          Temp:      Wind:
  12:00  Conditions:          Temp:      Wind:
  15:00  Conditions:          Temp:      Wind:
  Precipitation (type / start / end):
  Ground conditions:
  Weather impact on work (crew, hours, tasks affected):

MANPOWER (own crew)
  Name / classification      Hours     Cost code(s)
  1.
  2.
  3.
  4.
  5.
  6.
  Total crew hours:

SUBCONTRACTORS / OTHER TRADES ON SITE
  Company / trade            Headcount     Work area

EQUIPMENT
  Unit # / description       Hrs operated   Hrs idle   Idle reason
  1.
  2.
  3.
  Rentals delivered or called off rent today:

WORK COMPLETED
  Task / location                          Quantity    Unit    Cost code
  1.
  2.
  3.
  4.

MATERIALS AND DELIVERIES
  Supplier / ticket #    Material    Time arrived    Complete? Damage?

DELAYS AND PROBLEMS
  Cause:
  Start time:            End time (or ongoing):
  Crew / equipment affected and hours lost:
  Who was notified, how, when:
  Action taken:
  Carried forward from earlier report? (Y/N, report #):

CHANGES / EXTRA WORK / FIELD DIRECTION
  Direction given by (name, company):      Time:
  What was directed:
  Work performed and hours:
  PM notified? (Y/N, time):

VISITORS AND INSPECTIONS
  Name / company       Time in / out      Purpose / result

SAFETY
  Toolbox talk topic:                 Attendees:
  Incidents / near misses / first aid:
  Corrective actions:
  Reported to (name, time):

PHOTOS
  Photo #   Location on site   What it shows

NOTES FOR TOMORROW
  Open items, material needed, inspections scheduled:

SIGN-OFF
  Written by (signature):                     Date:
  Reviewed by (signature):                    Date:

How to write a daily report that holds up later#

Format matters less than habits. These are the ones that separate a useful daily from a box-checking one.

Write it the same day, on site#

Jot notes through the day: arrival times, delivery tickets, when the inspector showed up. Finish the report before the crew leaves. Reports written on Friday for the whole week are guesses, and they usually read that way. Same-day reports also catch problems while you can still do something about them.

Use numbers, times and locations#

Every entry should give someone who wasn't there enough to picture it. Use gridlines, stations, room numbers, or "east side of building B." Use times, not "this morning." Use quantities with units. The table in the work-completed section above is the standard.

Keep opinions out#

Write what happened, what you saw and what people said. Leave out blame, guesses about intent and sarcasm. If something is your judgment ("subgrade appeared too wet to compact"), say that it's an observation and note what it was based on.

Carry open items forward#

Unresolved delays, open RFIs, waiting on inspection, missing materials: they stay on the daily every day until they're closed. When an item closes, write when and how.

Make it fast enough to actually get done#

A 40-field form that takes 30 minutes will get skipped or half-filled on the days that matter most, which are the bad days. Keep the daily to what you'll actually use. If the foreman is already logging crew hours by cost code in a time app, pull those in instead of re-typing them.

This is also where voice tools help. In Emerald Field OS, for example, the foreman holds one button at the end of the day and talks for about a minute, in English or Spanish. The AI drafts the crew hours by cost code, production quantities, equipment, delays, safety notes and the daily report, and nothing saves until the foreman reviews and confirms it. Whatever tool you use, the rule is the same: a person who was on site checks the record before it becomes the record.

Common daily report mistakes#

These are the ones that show up over and over when someone pulls a stack of dailies to support a claim or answer a question about a job.

1. Copy-paste reports. Tuesday's report is Monday's report with the date changed. It undermines every other report in the stack.
2. No quantities. "Continued pipe install" for 15 days in a row tells nobody how far along the job is.
3. Weather only on bad days. Selective weather records are easy to challenge.
4. Delays that appear once and vanish. Carry them forward until they close.
5. Hours that don't match payroll. The daily says 6 people for 8 hours, the timecards say 7 people for 9.5. Somebody has to reconcile it, and it should be the foreman the same day, not the payroll clerk two weeks later.
6. Unlabeled photos. A folder of 200 photos with no dates, locations or captions is close to useless.
7. Office edits with no trail. A changed report with no record of who changed it and why is a credibility problem.
8. No sign-off. Somebody has to stand behind it.

Paper, spreadsheet or app#

Any of these can produce a good daily. The format is less important than whether it gets filled out the same day, every day, with specifics.

If you go with an app, look for a few things: it saves entries offline and syncs later, it ties hours to cost codes so the daily and payroll agree, it attaches photos to the report automatically, and it keeps an audit trail when someone edits a submitted report. You can see how the field side of Emerald Field OS handles dailies, time and job cost on the product overview, and the pricing page lists what each plan includes.

A quick example#

Here's what a short daily looks like for a hypothetical site utility crew. The names and numbers are made up for the example.

Job: Hillcrest Commons Site Utilities   Job #: 2614   Date: Thu
Written by: (foreman name)   Shift: 6:30 - 15:30

Weather: 6:30 clear 41F calm / 12:00 clear 58F wind SW 10 / 15:00 clear 60F
Ground: dry, firm. No weather impact.

Manpower: 1 foreman, 1 operator, 3 laborers. 9.0 hrs each, 45.0 total.
  Cost codes: 02-610 storm pipe 36.0 hrs / 02-100 traffic control 9.0 hrs

Equipment: Excavator #14 operated 7.0 hrs, idle 1.5 hrs (waiting on pipe
  delivery). Loader #6 operated 5.0 hrs.

Work completed:
  Laid 120 LF 15-inch RCP storm, CB-4 to CB-5, bedding and backfill to 1 ft
  over pipe. Set CB-5 structure.

Deliveries: Precast supplier ticket 55102, 8 sticks 15-inch RCP, scheduled 7:00,
  arrived 8:35. Complete, no damage.

Delays: Pipe delivery 95 min late. Excavator idle 1.5 hrs, laborers moved to
  CB-5 base prep. Texted PM 7:20 and 8:40.

Inspections: City inspector (name on card) 13:10, checked bedding CB-4 to CB-5,
  passed.

Safety: Toolbox talk on trench sloping and spoil pile setback, all 5 attended.
  No incidents.

Photos: 6 (pipe in trench at CB-5, delivery ticket, bedding before backfill).

Open items: Need 2 more sticks of 15-inch RCP for CB-5 to CB-6, ordered.

Signed: (foreman name)

That took a few minutes to write and answers almost any question someone could ask about that day: what got built, how long it took, why the excavator sat, who knew about it, and that the work passed inspection. For trench work like this, OSHA's excavation rules live in 29 CFR 1926 Subpart P, and the crew's competent person decides on protective systems; the daily just records that the talk happened and who attended.