What should a site diary contain?
At minimum: the date and weather, who was on site, what work was committed and whether it happened, why anything did not happen, deliveries and their times, plant and equipment, instructions received, and anything that stopped or delayed work. The reason a task did not proceed is the entry most diaries record badly and the one most often needed later.
Last reviewed 20 Nov 2026
Many contracts require a site diary without saying what goes in it, which leaves the question to whoever is keeping it. The honest test is not what looks thorough on the day. It is what somebody who was not there can establish from it eleven months later.
The entries almost every diary gets right
Date, weather, who attended, what was done. These go in because they are obvious, and because leaving them out looks like neglect. They are also the entries least often in dispute.
Weather deserves a note. The forecast is not evidence of anything; what fell on that site on that day is. Rainfall at set times through the day, with temperature and conditions, is a few seconds of work and it is the part a wet weather claim stands on.
The entry most diaries get wrong
The reason a task did not proceed, written as a sentence instead of chosen from a list.
A sentence cannot be counted. Three weeks of "waiting on materials", "material not on site" and "no material" are the same cause written three ways, and no amount of reading will turn them into a figure. The same three weeks recorded as a code can be counted in seconds, compared with last month, and set against a particular trade or supplier.
Use a short fixed list, keep it the same across projects, and allow a free-text note alongside the code rather than instead of it. The list has to be short enough that people use it consistently and stable enough that this month can be compared with last month.
The entries that decide a claim
What was committed against what happened, so a pattern of non-completion is visible rather than inferred. Whether a task sat on the chain that moves the completion date, recorded on the day rather than argued afterwards. Deliveries booked against deliveries arrived, with the turnaround between the gate and departure. Instructions received, from whom and when. Anything that stopped work, with the time it started and the time it resumed.
None of that requires knowing in advance which day will turn into an argument, which is the whole point of recording it that way.
What a diary cannot do on its own
A diary establishes what happened and when. It does not establish what that meant for the completion date, which is a programme question. Projects with good records and a stale programme end up roughly where projects with neither end up: the events are documented and nothing can be proven about their effect.
See it on a real record.
Walk around a project with five weeks of records on it, or download a blank Day Record and keep it yourself. Neither needs a sign up.
