Skip to content
Construction

Construction Daily Report: What to Record, With an Example (2026)

What a construction daily report should record, a filled-in example with crew hours and delays, a 10-minute routine, and the mistakes to avoid.

By Ryan Kramer, founder of Wisegrid. Last updated November 2026.

A construction daily report is a short record, written every working day, of what happened on a job site: the weather, who was there and for how long, what work was done, what was delivered, who visited, and anything that went wrong. The superintendent or site lead usually writes it before leaving the site.

Daily reports feel like paperwork until something is disputed. Then they are often the only written record of what really happened on a given day: whether rain stopped work, when a delivery arrived short, or when the owner asked for extra work. This guide covers what to record, a filled-in example, a 10-minute routine for writing one, and the mistakes that make reports useless when you need them.

Key takeaways

– Write it every working day, on the day. A report written a week later is far weaker evidence.

– Record facts, not opinions: times, counts, hours, locations and names.

– Crew hours by company are the core of the report. They support job costing, subcontractor bills and delay claims.

– Every delay, problem or owner request gets a follow-up, such as a request for information or a change order request.

– Photos make a report much stronger when each one has a date, a location and a one-line caption.

What is a construction daily report?

A construction daily report is the job’s diary, kept in a standard format so anyone can read it later. It answers five questions about one day: what was the weather, who was on site, what got done, what arrived, and what went wrong.

Owners, lenders and public agencies often require daily reports in the contract. The National Park Service’s daily report form, for example, asks for weather and ground conditions, workers and hours for the prime contractor and each subcontractor, equipment, deliveries, visitors, inspections, tests, safety events and unforeseen problems, with photos attached. Even when no one requires them, contractors keep daily reports because they protect the business in billing, scheduling and disputes.

What should a construction daily report include?

Keep the same sections every day, in the same order, so reports are quick to write and quick to search. These are the sections most contractors and public agencies use:

Section What to record
Date and report number One report per working day
Weather Conditions, high and low, ground
Crew on site Company, workers, hours, area
Equipment What was used, hours, any idle time
Work completed Activity, location, quantity
Deliveries What arrived, what was short or damaged
Visitors and inspections Who came, why, and the result
Safety Incidents, near misses, toolbox talks
Delays and issues What happened, impact, follow-up
Photos Date, location and a caption each

If you only have time for three things, record crew hours by company, work completed by location and anything that stopped or slowed the work. Those three are what you will need months later.

Construction daily report example

A two-story office fit-out on a Tuesday. Rain held up the framing crew for the first two hours. The table shows everyone on site and the hours they were there; the bold row is the crew affected by the weather.

Company Workers Hours Area
General contractor 3 24 Site-wide
Framing subcontractor 6 48 Level 2
Electrical subcontractor 4 32 Level 1
Plumbing subcontractor 2 12 Level 1
Total 15 116

The same report lists the day’s problems and what happens next for each one. This is the part of the report that pays for itself:

Issue Impact Follow-up
Rain, 7:00 to 9:00 a.m. Framing started 2 hours late Weather noted, photos taken
Drywall delivery 40 sheets short Level 2 board-up moves a day Supplier promised Thursday
Duct hits beam, grid C-4 Ductwork stopped in one room Request for information (RFI) 14
Owner asked for an extra outlet Not started Change order request 6

What this tells you: 12 of the framing crew’s 48 hours (6 workers × 2 hours) were spent waiting out the rain. If the framing subcontractor later bills for standby time, or you ask the owner for a weather extension, this report is your proof. The grid-line problem and the owner’s request each became a numbered document the same day, so neither can turn into a “we never agreed to that” argument. Our guides to the request for information (RFI) process and to change orders cover what happens next.

How to write a daily report in 10 minutes

A daily report should not take an hour. This routine keeps it to about 10 minutes for a superintendent on a mid-size job:

  1. Start the report in the morning. Fill in the date, the weather and the planned work before the day gets busy.
  2. Count the crews at mid-morning. Note each company, the number of workers and where they are working. Ask foremen for their hours at the end of the day.
  3. Take photos as you walk the site, and caption each one with the location before you forget. Our guide on how to inspect construction work covers what to look at.
  4. Log deliveries when they arrive. Check them against the purchase order and the approved items on your submittal log, and note anything short or damaged.
  5. Write down issues as they happen, with the time. Each one gets a follow-up: a phone call, an RFI, a change order request or a note for tomorrow.
  6. Record work completed by location and quantity at the end of the day, such as “Level 2, east wing, 1,200 square feet of drywall hung.” Those quantities back up the percent complete you bill on your schedule of values.
  7. Read it once and send it to the project manager before you leave the site.

Daily report vs daily log: is there a difference?

In practice, most contractors use “daily report” and “daily log” for the same thing. When people do separate them, the daily log is the running list of everything that happened, often kept as notes through the day, and the daily report is the cleaned-up summary sent to the project manager, owner or lender. Some contracts also require a separate quality control report or inspector’s report. Whatever you call it, keep one official version per day.

Common daily report mistakes

  • Writing it days later. Memory fades, and a report written after the fact is easy to challenge.
  • Vague entries. “Framing ongoing” tells no one anything. “Framing, Level 2 east wing, 6 workers, walls 80% stood” does.
  • Opinions and blame. “The electrician is useless” helps no one in a dispute. Record what happened and when.
  • Leaving out bad days. Days with no work because of weather or a missing inspection are exactly the days you need on record.
  • Hours that do not match timesheets. Crew hours in the report should agree with what lands in your timesheet template and in your construction job costing.
  • Issues with no follow-up. A problem noted and never acted on looks worse than a problem not noted at all.
  • Photos with no captions. Fifty pictures of drywall are useless without a date and location.

From spreadsheet to a shared daily log

Many superintendents fill in a spreadsheet or a word processing file every day and email it to the office. It works, but the reports pile up as separate files. When someone asks how many days the framing crew lost to weather in March, or how many hours the electrician worked last month, someone has to open thirty files and add them up by hand.

In Wisegrid, the daily log is one shared sheet per job, with a row for each company on site each day and a row for each issue. Because it is one grid, you can filter by company, add up hours by week, or count weather days in seconds. Crew hours can feed the job’s job costing template, and open issues can show on the construction project dashboard. The owner can view the log for free. It does not replace a site walk or a photo app; it gives the facts one home. Use the free labor cost calculator to turn crew hours into cost.

FAQ

Who writes the construction daily report?

The general contractor’s superintendent usually writes it, because they are on site all day. On larger jobs, an assistant superintendent or project engineer may draft it for the superintendent to review. Subcontractor foremen often keep their own daily reports for their crews and share them with the general contractor.

How long should you keep construction daily reports?

Keep them at least as long as your contract requires and until any warranty period and time limit for claims has passed. These periods vary by contract and state, so ask your lawyer or insurer for a rule that fits your business. Storing them digitally in one place makes long retention cheap and searchable.

Can daily reports be used as evidence?

Yes. Daily reports are often used in delay claims, payment disputes and injury claims, because they were written at the time by someone on site. That is why they should be factual, written on the same day and never changed afterward. If you need to correct one, add a dated note instead of editing the original.

Should a daily report include photos?

Yes, when you can. A photo with a date, location and short caption is the strongest support for anything in the report, from work completed to damage and delays. Take a few wide shots of each work area every day, plus close-ups of anything unusual.

Is there a free construction daily report template?

Wisegrid does not have a daily report template page yet. The sections in the table above are a complete starting point: put them as columns in a spreadsheet, one row per company per day. For crew hours, the timesheet template already has the columns you need.

Sources


Give every site day one home

Log crews, hours and issues on a shared Wisegrid sheet, and share it with the owner for free. Start with the timesheet template, the job costing template and the construction project dashboard.

Start free → · RFI guide → · Inspection guide →


About the author Ryan Kramer is the founder of Wisegrid, a higher-capacity work management grid built around a 1,000,000-cell-per-sheet limit, date-triggered automations with run history, and cross-sheet reporting. He writes about the project management documents teams actually keep updated. More from Ryan →