Daily Construction Report: What to Include (Template + Example)

November 15, 2026

GanttMaster

Plan Smarter. Execute Faster.

Interactive Project Management Tool, real-time collaboration.

⭐ 4.8 Rating • Trusted by modern teams worldwide

At the end of a long day on site, the daily report is the last thing anyone wants to write. It is also one of the most useful documents a project produces. Weeks later, when someone asks why the slab pour slipped, who approved the extra outlet, or whether the drywall delivery really arrived short, the answer is usually sitting in a daily report, or it is missing because nobody wrote one.

This guide explains what a daily construction report is, what to include, how to write one in about fifteen minutes, and how to keep the record useful. You will also find a template you can copy and an illustrative example. It is written for superintendents, foremen, site engineers, and small contractors, and most of it applies just as well to any field team that does physical work in changing conditions, such as facility maintenance or clinic renovations.

What is a daily construction report?

A daily construction report (also called a daily log, site diary, or daily field report) is a short written record of what happened on site during one working day. It captures who was there, what work was done and where, what arrived, what got in the way, and what is planned next.

It serves three audiences at once:

  • The project team today. The project manager, estimator, and office staff get a factual picture of progress without driving to site.
  • The client or owner. A steady stream of clear reports builds trust and cuts down on "what is going on out there?" calls.
  • Everyone later. When there is a question about a delay, a change, a payment, or a defect, the daily report written on the day carries far more weight than anyone's memory.

Why daily reports matter

  • They protect your schedule. Weather stoppages, late deliveries, and waiting on decisions are easy to forget and hard to prove after the fact. Written down the same day, they support a time extension request.
  • They support changes and payments. Extra work, verbal instructions, and site conditions that differ from the drawings are easier to price and agree on when they were recorded when they happened.
  • They reveal patterns. Read a week of reports together and you can see a trade that is always short-staffed, equipment that keeps sitting idle, or an area where rework keeps coming back.
  • They improve handovers. If the superintendent is off for a day, the person covering can read yesterday's report and know exactly where things stand.

What to include in a daily construction report

Your contract or company may require specific fields, so check those first. Beyond that, most good daily reports cover the same ground.

1. Project details

Project name and number, site address, date, report number, and the name and role of the person writing it. Numbering reports in sequence makes it obvious if a day is missing from the file.

2. Weather and site conditions

Record the conditions, but more importantly, record their effect on the work. "Rain" says little. "Heavy rain from 10:00 to 13:30, excavation stopped, crew moved to formwork prep" tells the full story.

3. Labor on site

Each trade or subcontractor present, the number of workers, and the hours worked. Note no-shows and late starts, because a short crew often explains slow progress.

4. Work performed

This is the heart of the report. Describe each activity with its location (level, grid line, room, or zone) and, where you can, the quantity completed. "Installed 40 m of 100 mm drainage pipe, grid C3 to C7" is a record. "Worked on drainage" is not. Separate change work from base contract work.

5. Equipment

Equipment on site, hours used, and idle time with the reason. A rented machine waiting half a day for a delivery is a cost, and the report is where that cost becomes visible.

6. Materials and deliveries

What arrived, how much, from which supplier, the delivery ticket number, and the condition on arrival. Note short, damaged, or wrong deliveries on the day they arrive.

7. Delays and issues

What was affected, when it started and stopped, the cause, and who was told. Open questions to the designer, pending client decisions, and access problems belong here too. If there were no delays, write "No delays today" rather than leaving the section blank.

8. Safety

Toolbox talk topics, inspections, near misses, and incidents, following your company's safety procedures. Again, write "No incidents" when that is true.

9. Visitors, inspections, and instructions

Inspectors, client visits, consultants, and any instructions given on site, especially verbal ones. Record who said what and when.

10. Photos

Progress photos, problem areas, and deliveries, each with a short caption and location. A photo with "Level 2, east corridor, ceiling grid complete" is far more useful than a folder of unnamed images.

11. Plan for tomorrow

The work, crews, equipment, and deliveries expected next day. This turns the report from a backward-looking record into a short planning tool.

12. Sign-off

Name, role, and the time the report was completed.

How to write a daily report in 15 minutes

  1. Take notes during the day, not after. Jot down delivery times, delays, and visitors as they happen. A few words on your phone at 10:15 beat trying to remember at 17:30.
  2. Photograph as you walk. Take photos on your site walks and name or caption them while you still remember where they were taken.
  3. Use the same template every day. A fixed structure means you fill in blanks instead of composing from scratch, and nothing gets skipped.
  4. Write facts, not opinions. "Electrician arrived 09:40, scheduled for 07:00" is a fact. "Electrician was lazy" is an opinion that helps nobody.
  5. Be specific about location and quantity. Grid lines, levels, rooms, meters, and counts make the record useful.
  6. Send it the same day. A report finished on time is worth more than a perfect one written three days later.

Daily construction report template

Copy this structure into a document, a form, or a spreadsheet:

  • Project / Job no. / Date / Report no. / Prepared by
  • Site hours: start and finish
  • Weather: conditions, and impact on work (what stopped, from when to when)
  • Labor: trade or company, number of workers, hours, notes
  • Work performed: activity, location, quantity, percent complete, base or change work
  • Equipment: item, hours used, idle hours and reason
  • Materials and deliveries: item, quantity, supplier, ticket no., condition
  • Delays and issues: description, start and end time, cause, who was notified
  • Safety: toolbox talk topic, inspections, near misses, incidents
  • Visitors and instructions: name, company, purpose, instructions given
  • Photos: number, location, caption
  • Plan for tomorrow: activities, crews, equipment, deliveries
  • Sign-off: name, role, time

Example: a filled-in daily report

The example below is illustrative, written for a fictional small retail fit-out, to show the level of detail that makes a report useful.

  • Project: Corner bakery fit-out, Job 24-117, Report no. 18, prepared by the site supervisor
  • Site hours: 07:00 to 16:30
  • Weather: Dry, cool. No impact on work (all work indoors).
  • Labor: Drywall contractor, 4 workers, 8 hours. Electrician, 2 workers, 8 hours. Plumber, 1 worker, arrived 10:30 instead of 07:00.
  • Work performed: Drywall boarding on the kitchen partition complete (about 60%). Electrical first fix in the front-of-house area complete. Plumber started rough-in for the hand wash sinks, about 30% done.
  • Equipment: Scissor lift, 6 hours used, 2 hours idle waiting for ceiling access.
  • Materials: 40 sheets of moisture-resistant board delivered, ticket 5582, 3 sheets with damaged corners, set aside and supplier notified.
  • Delays and issues: Sink location in the prep area unclear on the drawings. Question sent to the designer at 11:00, plumber moved to the other sinks meanwhile. Late plumber start reduced rough-in progress.
  • Safety: Toolbox talk on ladder use. No incidents.
  • Visitors and instructions: Owner visited at 14:00 and asked for one extra double socket behind the counter. Recorded as a possible change, pending price.
  • Photos: 6 taken (kitchen partition, electrical first fix, damaged boards, prep area sink wall).
  • Plan for tomorrow: Finish kitchen partition boarding, continue plumbing rough-in, electrician to start the back-of-house area.

Notice that a reader who was not on site can tell what moved, what did not, why, and what decisions are still open.

Common mistakes to avoid

  • Leaving sections blank. A blank field looks like an oversight. "None" or "No delays" is a statement of fact.
  • Writing at the end of the week. Details fade fast. Write the report on the day.
  • Vague descriptions. No location, no quantity, no times. These are the reports that cannot answer questions later.
  • Unlabeled photos. Without a caption and location, a photo proves very little.
  • Reports that go nowhere. If issues in the report never become actions in the schedule, the same problem shows up again tomorrow.

Connecting daily reports to your schedule in GanttMaster

The daily report records what happened. The follow-through (the open question, the late delivery, the extra socket, tomorrow's work) belongs in your project plan, where the whole team can see it. GanttMaster is a project management app for iPhone and iPad that helps with that part on site:

  • Start the day from the Today view. See the project tasks due today alongside your own daily tasks, and set reminders, for example to write the report before you leave site.
GanttMaster Today view showing project tasks and personal tasks for the day
Example project: the Today view with project tasks and personal tasks.
  • Keep issues on the task they affect. Each task has its own comments, so the conversation about "prep area sink location" stays with that task, and the team gets notified about new comments and updates.
GanttMaster task comments tab with a team conversation on a single task
Example project: a conversation on a single task.
  • Link photos and reports to tasks. Add file links on a task that point to the day's photo folder or the report document, so the evidence sits next to the work.
GanttMaster file links tab for adding a file description and link to a task
Example project: adding a file link to a task.
  • See the knock-on effect on the Gantt chart. When a delay hits one task, the Finish-to-Start, Start-to-Start, and Finish-to-Finish dependencies show which tasks follow it, and bar colors show task status at a glance.
  • Turn recurring issues into risks and costs. Log a repeating problem in the risk register with likelihood, impact, mitigation, owner, and due date, and record expenses such as extra equipment rental against the project budget.
  • Plan tomorrow as tasks. Turn the "plan for tomorrow" section into tasks and subtasks assigned to a user, a team, or both.
GanttMaster Gantt chart on iPad with task bars and dependency arrows
Example project: the Gantt chart with dependency lines on iPad.

There is no per-user pricing, so foremen, subcontractor leads, and office staff can all be on the project without counting seats. GanttMaster is free to download with a 1-week trial, then $5.99 a month or $34.99 a year.

A daily construction report does not need to be long. It needs to be written every day, specific about what happened and where, and connected to the actions that follow. Fifteen minutes at the end of the day can save hours of arguing a month later.

GanttMaster logo

Plan it on your iPhone or iPad

Full disclosure: we make GanttMaster, an iPhone and iPad app with FS/SS/FF dependencies, tasks and subtasks, checkpoint tasks, a Today view with reminders, team assignment, risk and budget tracking, and no per-user pricing. It is free to download with a 1-week trial, then $5.99/month or $34.99/year.

Download on the App Store