The construction daily report is the most written and least read document on any project. It gets completed under duress at the end of an eleven hour day, filed somewhere nobody looks, and then, once every few years, becomes the most important piece of paper in a six figure argument.
Most of them would not survive that moment. Here is what separates the ones that do.
The test that matters
There is one useful question to ask of any daily report: could a stranger reconstruct that day from it in three years, without asking anyone what it meant?
Not could you reconstruct it. You will have left, or forgotten, or be the person whose recollection the other side is challenging. A stranger: an adjudicator, a new project manager, a solicitor, an auditor.
Apply that test to last Tuesday’s report on your current job. If it says “works progressing, weather poor, 12 operatives”, it fails. Twelve operatives doing what, where? Weather poor enough to stop what, from when?
What a defensible daily report contains
| Section | Weak version | Defensible version |
|---|---|---|
| Weather | “Wet” | Conditions with times, and what they stopped: “Heavy rain from 11:20, pour to gridlines 4 to 7 abandoned” |
| Labour | “12 operatives” | By trade and number, against work areas: “6 groundworkers, plots 12 to 15; 4 steel fixers, core; 2 labourers” |
| Plant | “Excavator on site” | What was there, what it did, what stood idle and why. Standing time separated. |
| Progress | “Works progressing” | What was achieved, by location, in terms someone off site can follow |
| Deliveries | Often omitted | What arrived, what was rejected and why, what did not turn up |
| Instructions | Often omitted | Anything the team was told to do differently, by whom, and when |
| Delays | “Slow day” | The event, the time lost, and specifically what it prevented |
| Health and safety | “Nil” | Near misses, incidents, toolbox talks, and inspections with who attended |
| Visitors | Often omitted | Who came, when, and why. This settles “we were never told” arguments. |
The three failures that recur everywhere
Adjectives instead of facts. “Poor”, “slow”, “difficult” and “ongoing” are the four most common words in construction daily reports and none of them evidences anything. Replace every adjective with a number, a time, a location or a name.
Batching. Reports written on Friday for the whole week converge on generic summaries, because that is all memory retains. They also lose their status as records made at the time, which is the entire source of their evidential value. A thin entry made daily is worth more than a detailed one made weekly.
Silence on bad days. The instinct to under-record when things go wrong is understandable and catastrophic. The days you would rather not write about are the days the report is for. A record that goes quiet whenever there is trouble reads, later, as either careless or deliberate, and neither helps you.
What to stop writing by hand
Here is the part most guidance avoids: a large share of what goes into a daily report has already been communicated, in writing, hours before anyone sits down to write it.
The delivery was confirmed in the group chat with a photo of the ticket. The obstruction was flagged in a voice note. The instruction from the contract administrator came by email at 09:15 and was relayed to the gang immediately. The weather that stopped the pour was complained about by four people in real time.
Asking a site manager to type all of that out again at seven in the evening is not a records policy, it is a duplication policy, and duplication is what people quietly stop doing when the job gets busy. Which is precisely when you need the record most.
So the honest answer to “what should we stop writing by hand?” is: anything the site has already said somewhere else. The job is to capture and structure that, not to re-key it.
Daily report or site diary?
People use the terms interchangeably and it rarely matters, but there is a distinction worth knowing. “Daily report” is the more common phrasing in North American practice and tends to mean a structured form submitted upward. “Site diary” is the traditional UK term and carries more of a sense of a continuous personal record kept by the person running the site.
Evidentially, the diary tradition is the stronger one, because a continuous narrative kept by an identifiable person is harder to attack than a form somebody completed. The best version is both: the structure of a form, with the completeness and continuity of a diary.
How to tell if yours is good enough
Pick a week from six months ago, at random, and read it as though you were the other side’s expert looking for holes. Ask:
- Is there an entry for every working day, including the quiet ones?
- Can I tell where the works physically were at the end of that week?
- Can I reconcile the labour recorded against any daywork sheets or applications from the same period?
- Are the bad days recorded with the same detail as the good ones?
- Is anything in there that was clearly written later than the day it describes?
Most projects fail on the first and the second. Those two are the ones worth fixing first, and neither requires more writing, only more consistency.
Construction Metric produces this report every evening from the messages, photos and voice notes the team already sends, so the entry exists on the days nobody had time. Read a full sample, or see how it compares to a daily report app.