Construction Daily Report: What to Include, a Template and How to Make It Defensible
By Kush Agarwal, President and CEO, YelloSKYE. Published .
Executive Summary
- The Question: What goes in a construction daily report, and how do you write one that is quick to fill in and still stands up months later?
- The Answer: Record labour, plant, materials, work done, delays, instructions and events, each tied to a location and written as fact on the day. Back the words with dated images of the same places, so readers can check rather than trust.
- The YelloSKYE Angle: Construct IQ adds drone, 360° and fixed-camera captures that DEX keeps on a day-by-day timeline, so a daily report can point to what the site actually looked like.
A construction daily report is the signed, same-day record of what happened on site: who was there, what equipment worked, what arrived, what was built and where, what held the work up, and what instructions were received. It is short, routine and easy to neglect, yet it is often the only contemporary account of a given day when a delay, a variation or a payment is questioned later.
This guide sets out what to include, gives a template you can adapt, lists the gaps that most often weaken a daily report, and explains how visual capture from Construct IQ can make reports quicker to write and harder to dispute. For how the daily report fits alongside issues, inspections and the rest of the site routine, see our guide to construction field management.
Who reads a daily report, and for what
A daily report is written by one person but read by many, often long after the day it describes. Knowing who will rely on it explains why each field matters.
| Reader | What they use it for | When |
|---|---|---|
| Project manager | Spotting slippage and resource gaps before they reach the programme | Same day or next morning |
| Planner | Updating actual start and finish dates and productivity rates | Weekly |
| Commercial team | Checking daywork, variations and progress payment claims | Monthly |
| Owner or owner's representative | Understanding progress and the cause of any delay | Weekly or monthly |
| Health and safety lead | Following up incidents and near misses | Same day |
| Claims or dispute specialist | Rebuilding what happened on a disputed day | Months or years later |
The last reader is the one most teams forget. Writing with them in mind, someone who was never on site and has only the report to go on, produces better reports for everyone else too.
Daily report template
The table below is a working template. Copy the first two columns into your form or software and use the example entries as a guide to the level of detail that holds up.
| Section | What to record | Example entry |
|---|---|---|
| Header | Project, report number, date, shift start and finish, author | Report 214, 07:00 to 17:30, written by the site manager |
| Weather | Conditions at start, midday and end, and any work stopped as a result | Heavy rain 11:00 to 13:30; external brickwork stood down for 2.5 hours |
| Labour | Headcount by trade and by employer, including supervisors | Formwork subcontractor 14, rebar subcontractor 9, main contractor 6 |
| Plant | Major equipment on site, hours worked, any breakdowns or idle time | Tower crane 9.5 h; mobile pump idle all day awaiting pour release |
| Deliveries | Materials received, quantities, and anything rejected with the reason | 22 t rebar for level 5; 3 precast stairs rejected for chipped nosings |
| Work done | Activities by location and quantity, using gridlines, levels or zone names | Level 4 slab, grids C to F: bottom mat fixed, sleeves 60% placed |
| Delays and disruptions | What stopped or slowed, where, for how long, and the cause | Level 4 pour moved to tomorrow: revised sleeve drawing received 14:00 |
| Instructions and information | Site instructions, drawings, RFI answers received, with reference numbers | SI-087 received from the structural engineer; RFI-142 answered |
| Inspections and tests | Inspections held, by whom, result; tests taken | Level 4 reinforcement inspected, three items to correct before release |
| Visitors | Name, organisation and purpose, especially consultants and authorities | Building authority inspector, drainage inspection, passed |
| Health and safety | Incidents, near misses, toolbox talks, notable observations | Near miss at hoist gate; gate interlock repaired the same afternoon |
| Visual record | Links to the day's captures for the places mentioned | 360° walk of level 4; fixed-camera images of the north core |
| Sign-off | Name, role, signature and time submitted | Signed 18:10 |
A good report fits on one or two screens. Length is not the goal; precision is. "Level 4 slab, grids C to F, bottom mat fixed" is more useful than a paragraph about a productive day.
Writing entries that hold up
Name the place every time
Every activity, delay and delivery should carry a location: a level, gridline, room number or zone. Without it, the entry cannot be matched to the programme, to a payment claim or to an image. Agree a location system at the start of the project and use it everywhere.
Separate cause from effect
A delay entry needs three parts: what was affected, for how long, and why. "Pour postponed" tells a reader almost nothing. "Level 4 pour postponed one day because the revised sleeve drawing arrived at 14:00" tells them who caused the delay and which activity it hit. That distinction is what a delay analysis later depends on.
Record what did not happen
Idle plant, crews stood down, deliveries that did not arrive and inspections that were cancelled are all evidence. They are also the items most often left out, because nothing visible happened.
Write facts, not opinions
"The subcontractor is slow" is an opinion and invites argument. "Formwork crew of 14 on site; planned 20" is a fact anyone can check. Keep commentary for meetings and correspondence.
Submit it the same day
A report written three days later from memory is weaker evidence and usually less accurate. Same-day submission, with a time stamp, is the single habit that does most to make a daily report credible.
Gaps that weaken a daily report
| Gap | What it costs later | How to close it |
|---|---|---|
| Work described in general terms | Progress cannot be tied to the programme or a payment claim | Require a location for every activity |
| Delays logged without cause | Responsibility for lost time cannot be assigned | Make cause a required field for every delay |
| Reports missing for weekends or quiet days | Gaps appear exactly when someone asks what happened | Submit a short report for every calendar day the site is open |
| Subcontractor headcounts copied forward | Labour records lose credibility for every other day too | Take counts at a set time from the gate or attendance record |
| Photos kept on personal phones | Images are lost when the person leaves the project | Upload to one shared, dated record the same day |
| Different formats from different sites | Leadership cannot compare projects | Use one template across the portfolio |
| Reports signed but never read | Problems recorded on site do not reach decision-makers | Review the week's reports in the project meeting |
How visual capture makes reports faster and more defensible
A written report describes; an image shows. The two together are much stronger than either alone, and visual capture can also take some of the writing burden off the site manager.
Link rather than describe
Instead of describing the state of a floor in detail, the report can state the essential facts and link to the 360° walk or drone capture of that area taken the same day. The reader sees the condition directly. A 360° walk of the active floors takes minutes and covers every room on the route.
Fill the hours between reports
A daily report captures one person's view at the end of the shift. Fixed cameras record selected zones at set intervals through the day, so questions about when a crew arrived, when a crane stopped or when a delivery was unloaded can be answered from timestamped images. In our fixed-camera construction monitoring use case, combining fixed cameras with scheduled drone flights and DEX gave project teams up to 80 per cent fewer site visits, because zones could be reviewed remotely.
Give the week a measurable baseline
A weekly drone flight produces a measurable map of the whole site against which a week of daily reports can be checked. On our aerial progress capture project, that routine replaced hours of manual reporting: site managers saved more than 15 hours a week. DEX keeps every capture on one timeline that can be scrolled day by day, so the report for any date can be read next to what the site looked like.
Make disputes shorter
When a daily report says level 4 was ready for the pour and a dated image shows the deck with sleeves missing, the record speaks for itself, whichever way it points. For payments, captures timed to the billing cycle let the project manager, contractor and owner review the same evidence; our contractor billing dispute use case shows that workflow. Our guide to construction dispute documentation covers how daily reports and images combine into a claim record.
| Capture | What it adds to the daily report | Typical rhythm |
|---|---|---|
| Phone photos | Close-ups of specific events, defects and deliveries | As events happen |
| 360° walk | Complete view of every room on the active floors | Daily or at trade milestones |
| Fixed camera | Timestamped activity in priority zones through the day | Continuous, at set intervals |
| Drone flight | Measurable view of the whole site and external works | Weekly or fortnightly |
From daily reports to the bigger picture
Daily reports are raw material. Each week, the planner should use them to update the programme with actual dates, the commercial team should check them against daywork sheets and claimed quantities, and the project manager should read the delay entries for patterns: the same cause recurring, or the same zone always behind. Monthly reports to the owner then summarise what the daily reports already prove.
If your reports are written in field software, export them in a standard format so they survive a change of tools. On YelloSKYE projects, the capture data travels into the tools a team already uses for its daily records, with Procore, Autodesk Construction Cloud and MS Project all supported through APIs and standard file formats. The construction documentation checklist shows where daily reports sit within the full project record.
Next steps
- Agree one daily report template for every site, using the sections above.
- Set a location system (levels, gridlines, zones) and require it in every entry.
- Make delay cause a required field.
- Require same-day submission for every day the site is open, including quiet days.
- Move site photos off personal phones into one shared, dated record.
- Add regular visual capture, such as weekly drone flights and 360° walks of active floors, and link it from the report.
- Read the week's reports in the project meeting, so problems recorded on site reach the people who can act.
Frequently asked questions
What should a construction daily report include?
At minimum: the date and shift, weather and its effect on work, labour by trade and employer, plant on site and whether it worked, materials delivered, work done by location, delays with their causes, instructions received, inspections and tests, visitors, and safety events. Each entry should name a place on site, and the report should be signed and dated the same day.
Who is responsible for writing the daily report?
The main contractor's site manager or superintendent usually writes and signs it, with input from foremen and trade supervisors. Subcontractors often keep their own daily records too, and owners' representatives may keep a separate diary. Contracts sometimes state who must keep daily records and who must receive them, so check yours.
What is the difference between a daily report, a daily log and a site diary?
In practice they are the same record under different names. Some teams use 'daily log' for a quick running record and 'daily report' for the formal version sent to the project manager or owner. What matters is that one agreed format is used every day and kept with the project records.
Are daily reports used as evidence in disputes?
Yes. Because they are written at the time, daily reports are often the main source for working out what happened on a given day in a delay claim, a variation dispute or a payment disagreement. How much weight they carry depends on the contract and the legal system, and on whether they are complete, consistent and supported by other records such as photos.
How long should construction daily reports be kept?
Keep them at least until all claims, final accounts and defects periods have closed, and longer if your contract or local limitation periods require it. Many organisations keep them for the life of the asset, because they help explain later problems. Store them where the whole project team can retrieve them after site staff move on.