How to Keep a Site Diary That Protects You: A Guide for UK Site Managers

Published 12 June 2026 | 5 min read | SiteTech Coach

SiteTech Coach is an independent training platform. We are not affiliated with, endorsed by, or sponsored by Trimble, Viewpoint, or any software vendor. Product names are used descriptively only.

The short version

A site diary is only worth keeping if it can stand up to scrutiny months or years later. A strong daily entry records the date, the weather, labour, plant, deliveries, delays, instructions received, and photos. A weak entry says "work continued as planned" and protects nobody. This article covers what a good entry contains, why thin diaries lose disputes, and a worked example you can copy on your next shift, whether you keep your diary on paper or in a site diary app.

What a good daily entry contains

Every entry should be completed the same day, while the detail is fresh. The core sections are the same on every UK site:

• Date and weather. Conditions in the morning and afternoon, temperature, wind, and rain. Note specifically whether the weather stopped or slowed any activity, and which one.
• Labour. Headcount by trade, split between your own team and each subcontractor. If a gang did not turn up, record it.
• Plant. What was on site, what was working, and what was standing. If a machine stood idle, write down why and for how long.
• Deliveries. What arrived, from whom, the condition it arrived in, and any shortages or rejections.
• Delays and disruptions. The cause, the duration, and the areas or activities affected. Be factual, not emotional.
• Instructions received. Any verbal instruction from the client team, architect, or engineer. Record who gave it, what was said, and what you did about it.
• Visitors. Who came to site and why.
• Photos. Reference the photos taken that day. A timestamped photo linked to the entry is far stronger than a loose image on a camera roll.

A complete entry like this takes about six minutes. That is the entire cost of the habit.

Why thin diaries lose disputes

Construction disputes are usually decided on contemporaneous records, meaning records made at the time, not reconstructed later. Adjudicators, quantity surveyors, and the courts give real weight to a diary that was clearly filled in day by day. They give almost none to a diary that was obviously written up in a batch the week before the hearing.

Here is the uncomfortable part. If your diary is thin and the other side's diary is detailed, their version of events tends to become the accepted version. Consider three common situations:

• Extension of time. You claim two weeks of weather delay. Without daily weather notes tied to specific activities, the claim rests on memory and regional weather data, and it usually gets cut down.
• Loss and expense. You claim for standing plant and unproductive labour. If the diary never recorded which machines stood and which gangs were disrupted, there is nothing to price from.
• Disputed instructions. The client's representative told you verbally to open up a completed area. Six months later nobody remembers saying it. A same-day diary note naming the person, the instruction, and the time is often the only evidence that exists.

A diary that says "work continued as planned" on the day a crane stood idle for four hours is worse than no diary at all, because it actively contradicts your own claim.

A worked example entry

Here is what a protective entry looks like in practice:

Thursday 11 June 2026. Plots 14 to 18. Weather: dry and overcast AM, heavy rain from 13:40, roofing stopped 13:40 to 15:10. Labour: own team 4 (1 SM, 1 engineer, 2 labourers); BrickCo 6 bricklayers; RoofRight 3 roofers; SparkServ 2 electricians. Plant: telehandler working all day; 13t excavator standing 08:00 to 12:00 awaiting revised drainage levels. Deliveries: 4 packs facing brick received 09:15, one pack damaged and rejected, supplier notified. Delays: drainage to Plot 16 held all morning awaiting engineer's revised levels, requested 9 June, received 12:05. Instructions: J. Carter (client's engineer) verbally instructed removal of two courses at Plot 15 north gable for inspection, 10:20, confirmed by email same day. Visitors: building control 11:00, Plot 14 pre-plaster inspection passed. Photos: 12 taken, refs 0611-01 to 0611-12, covering rejected brick pack, standing excavator, and Plot 15 gable before removal.

That entry took longer to read than it takes to write. Every line in it is a fact you would otherwise be trying to remember under pressure a year later.

Doing it in the software your team already uses

Most UK site teams now have a field management app on their phones or tablets, and almost every one of them includes a structured daily diary template with the sections above already built in. A site diary app for construction teams in the UK adds three things paper cannot: automatic timestamps, a named author on every entry, and photos attached directly to the day they belong to. The record syncs to the office the moment it is saved, so the commercial team can see delay and disruption evidence building in real time instead of discovering gaps at claim time.

The tool is not the hard part. The habit is. Six minutes at the end of every shift, every shift, is what wins disputes.

How SiteTech Coach teaches the workflow

SiteTech Coach exists to close exactly this gap. Our lessons teach the daily diary workflow, along with photo evidence, snagging, and inspections, on the field management software your teams already use. Each lesson takes under five minutes, works on any phone or tablet, and is written around real UK site scenarios like the worked example above, so site managers build the habit on a live job rather than in a classroom.

Want your whole team keeping diaries that protect you?

SiteTech Coach provides 30 practical lessons covering daily diaries, photo evidence, snagging, and inspections, all in plain language for UK site teams. Train at your own pace, on site, without pulling anyone off the job. Browse the training library