What actually belongs in a daily site diary

A daily site diary is one of the oldest pieces of site record-keeping, and one of the easiest to let slide into a bare attendance register — who was on site, what the weather was doing, not much else. That's a missed opportunity, because a genuinely detailed diary is often the single most useful document a site produces when something later needs reconstructing: a delay claim, a dispute over what was agreed on site on a given day, or the lead-up to an incident.

What a thin diary misses

A diary entry that reads as a normal working day with all trades on site tells you almost nothing six months later when a question arises about what was actually happening that afternoon. Was a particular area accessible? Had a specific delivery arrived? Was a subcontractor working in a location relevant to a later dispute? None of that is answerable from a thin entry, even though capturing it at the time would have taken barely any extra effort.

• –Who was on site — by trade and approximate numbers, not just a headcount
• –Weather conditions, particularly anything that affected work — heavy rain, high wind, low temperatures
• –Deliveries received and any that were expected but didn't arrive
• –Key visitors — client representatives, inspectors, designers attending site
• –Any instructions given verbally on site, even informally, that affected the work
• –Anything unusual — a near miss, a delay, an access restriction, a change to the planned sequence of work

Why verbal instructions matter most

The single most valuable category, in practice, is capturing instructions given informally on site — a client representative asking for a change verbally during a site walk, a design query resolved on the spot rather than through the formal instruction process. These moments happen constantly on a live project and are exactly the kind of thing that gets disputed later, precisely because there's no formal paper trail unless someone wrote it down at the time. A diary entry noting who said what, and when, is often the only contemporaneous record that exists of an informal but genuinely significant decision.

How this connects to inspection and toolbox records

A site diary shouldn't try to duplicate formal inspection records or toolbox talk logs — those deserve their own dedicated records with their own level of detail. But a diary entry can usefully cross-reference them: noting that an inspection happened and where its record lives, rather than trying to recreate the inspection's content inside the diary itself. The diary's job is to be the daily narrative thread that ties everything else together, not to replace the more detailed records sitting alongside it.

A worked example

A dispute arises months after practical completion over whether a client representative verbally instructed a change to a finish specification during a site visit. Neither party has a formal written instruction. The site diary from that day, if it recorded the visit and noted what was discussed, becomes genuinely decisive evidence — not because it's a perfect record of the conversation, but because it's a contemporaneous one, written before either party had a reason to remember the exchange in a way that favoured their own position.

Who should actually be writing it

A diary is only as good as the person writing it being genuinely present and paying attention — a diary filled in retrospectively at the end of the week from memory loses most of its value, because the specific detail that makes it useful is exactly what fades fastest. It's worth treating the diary the same way as any other time-sensitive record: written at the time, or as close to it as practically possible, by whoever's actually on site that day rather than reconstructed later by someone who wasn't.

Common mistakes

• –Recording only attendance and weather, missing the informal instructions and decisions that actually get disputed later
• –Writing entries at the end of the week from memory rather than at the time
• –Duplicating the content of formal inspection or toolbox talk records instead of cross-referencing them
• –Treating the diary as a formality with no real audience, rather than a genuine evidential record
• –Leaving gaps on quieter days, on the assumption that nothing worth recording happened
• –Not keeping diaries accessible and organised once a project finishes, when they're most likely to actually be needed