The daily site diary template that takes 6 minutes

What a good daily site diary records and why each item matters, how diaries decide delay and claim disputes, digital versus paper, and a worked example entry.

The short version

The daily site diary is the least glamorous document in construction and the one most likely to save you money years after the job finishes. It is a contemporaneous record: written on the day, about the day, by someone who was there. That is precisely what gives it weight when a delay claim, a defect allegation or a final account argument lands on the table long after everyone's memory has faded. A good diary takes about six minutes at the end of the day. A missing diary can take six months of expensive argument to work around.

The trap is treating it as a chore to be minimised. "Wet. Bricklayers on site. No problems" is technically a diary entry and practically worthless. The difference between that and an entry that wins a dispute is knowing what to record and why each item earns its place.

What a good daily diary records, and why each item matters

Weather, and what it stopped

Record the actual conditions morning and afternoon, and, crucially, what they prevented. "Rain from 11:00, external blockwork stopped 11:00 to 14:30, gang redeployed to internal partitions" is evidence. "Rain" is not. Weather is the most common ground for extension of time claims on UK contracts, and those claims stand or fall on whether anyone recorded what the weather actually did to the work. A general observation that it rained can be countered; a same-day note that a specific activity stopped for a specific window cannot easily be.

Labour on site

Numbers, trades and employer: "4 bricklayers (J Smith Brickwork), 2 groundworkers (ABC Civils), 1 electrician (Voltside)." This is your defence when a subcontractor later claims they had eight operatives on site through March, and your evidence when you are the one claiming disruption because a trade failed to turn up. Head counts also anchor productivity arguments: if the diary shows the gang that was priced never materialised, the programme slippage explains itself.

Plant and equipment

What was on site, working or standing, and why if standing. "Telehandler standing all day, awaiting repair to hydraulics, fitter booked for tomorrow" matters twice: it supports a claim for standing time if the fault sits with a supplier, and it defends you against one if it does not. Hired plant costs money whether it moves or not, and the diary is where the story of every standing day lives.

Deliveries and materials

What arrived, from whom, complete or short, accepted or rejected. Short and late deliveries are a classic root cause of delay that becomes invisible six months later unless someone wrote it down on the day. "Roof trusses delivered 13:40, 2 damaged, rejected and photographed, replacement promised Thursday" is the kind of line that later connects a two-week roof delay to its actual cause.

Delays, disruption and stoppages

The heart of the diary. Any event that stopped or slowed work: access not available, drawings awaited, prior trade incomplete, services strike, inspection failed, statutory undertaker no-show. Record the time lost and who or what caused it, factually and without editorial. Under most standard UK contract forms, entitlement to time or money depends on notices backed by records, and the diary is the record layer everything else is built on.

Instructions and visitors

Who came to site and what they said. Verbal instructions are the classic dispute seed: the architect who said "carry on and we will paper it later" in March has a different recollection in November. "AI visit 10:15, verbal instruction to proceed with revised door schedule, confirmation requested" protects everyone, including the person who gave the instruction. Log every visitor with a time: client, consultants, building control, HSE, delivery reps. Visitor entries also quietly prove the site was open, working and managed on any given day.

Progress, and photographs of it

Two or three sentences on what actually moved: "Plots 14 and 15 first lift complete. Plot 16 slab poured 09:30, cube samples taken. Second fix started Block A level 1." Paired with dated photographs, this becomes an unarguable timeline of the build. Photographs are the diary's best friend, provided they can be tied to a time and place; our lessons on adding a photo to a record properly and GPS and timestamp settings that hold up in court cover exactly how to make a site photo evidentially solid rather than just a picture.

Health, safety and anything unusual

Near misses, accidents, toolbox talks delivered, unsafe conditions found and actioned. These have their own formal reporting routes, but a diary line cross-referencing them keeps the day's full story in one place.

How diaries win delay and claim disputes

Construction disputes are usually decided on records, not recollections. Adjudicators, arbitrators and judges consistently give more weight to contemporaneous documents than to witness statements written years later with a lawyer's help, for the obvious reason: the diary was written before anyone knew there would be a dispute, so it had no side to take.

Picture a typical final account argument. The subcontractor claims six weeks of prolongation caused by late access. The main contractor's diaries, kept daily, show the access dates, the actual labour on site each day, the weather windows, and three weeks in the middle where the subcontractor had full access and two operatives instead of the six they had promised. Against that, the subcontractor offers a claim narrative assembled eighteen months later. It is not a fair fight. Now reverse it: if the diaries are missing, thin or plainly written up in batches after the fact, the well-documented claim wins instead, whatever really happened.

Three qualities give a diary that power. It is contemporaneous: written that day, not reconstructed on Friday for the week. It is consistent: kept every working day including the boring ones, because gaps invite the suggestion that entries were made selectively. And it is factual: what happened, when, who was there. Opinions, blame and speculation weaken it. The entry that says "ABC Civils are useless" helps nobody; the entry that says "ABC Civils attended with 2 of the 5 operatives confirmed on Friday's call" ends arguments.

Digital versus paper diaries

A paper diary in a duplicate book is better than nothing, and courts have accepted them for a century. But paper has failure modes that matter more as projects get bigger: handwriting that cannot be read, pages that go missing, one physical copy that lives in a site cabin, no photographs attached, and no way to prove when an entry was actually written. Backdating a paper diary is trivially easy, and everyone in a dispute knows it.

A digital diary kept in a field app closes those gaps mechanically. Entries carry a genuine timestamp, photographs attach directly to the day with their own time and location data, the record syncs off the device so it cannot be lost with the site cabin, and everyone who needs the diary can read it without waiting for the book to be photocopied. Dropdowns and templates also make the six-minute promise real, because weather, labour and plant become quick selections rather than prose. The one discipline digital does not remove is the human one: it still has to be done today, about today. The format for a fast, complete entry is exactly what our daily report lesson teaches, and the habit of writing it daily is covered from a different angle in how to keep a site diary that protects you.

A worked example entry

The following is an illustrative example, not a record of a real project, showing what six minutes of typing looks like when the headings above are followed.

Project: Orchard Park, Phase 2. Date: Tuesday 14 April. Author: R. Onsite, Site Manager.

Weather: Dry, overcast am. Heavy rain 13:00 to 15:30. External render to plots 21 and 22 stopped 13:00, not resumed; gang moved to beading and internal prep.

Labour: 5 bricklayers + 1 labourer (J Smith Brickwork), 3 renderers (FaceFix), 2 electricians (Voltside), 2 groundworkers (ABC Civils), 1 site manager, 1 forklift driver.

Plant: Telehandler in use am, standing from 13:00 (rain). 3t excavator working plot 25 drainage all day. Tower scaffold to plot 22 inspected, tag signed.

Deliveries: Windows for plots 19 and 20 arrived 08:15, checked complete, stored in compound. Drainage fittings expected today NOT delivered; supplier advises Thursday. Plot 25 drainage will stand down Wednesday pm if not received.

Delays/instructions: Rain stoppage as above, 2.5 hours lost to render programme. AI (T. Draws) visited 10:30, verbal instruction to swap ironmongery spec on plot 19 front doors; written confirmation requested by email 11:05.

Progress: Plot 21 render first coat complete to rear elevation. Plot 25 drainage runs 60 percent complete. First fix electrics complete plot 18, ready for inspection tomorrow am.

HSE: Toolbox talk delivered 07:45, working at height, 12 attendees signed. One near miss: unsecured board on plot 22 scaffold, fixed immediately, logged in near miss register ref NM-041.

Photos: 6 attached: render progress x2, rejected fittings shortage note, plot 25 trench x2, scaffold tag.

Nothing in that entry took thought a site manager was not already having at 4pm. It simply got written down while it was still true.

Making it stick

The diary habit survives on rhythm, not willpower. Fix the slot, last fifteen minutes before leaving, same time every day, and treat the entry as part of closing the site rather than admin on top of it. Use a template so the headings prompt the memory. Attach the day's photos while you still know what they show. Then make sure the entry actually leaves the device: a diary trapped on an unsynced tablet is one dropped phone away from not existing, which is why the end-of-day sync check belongs in the same ritual.

Six minutes a day, every day, for the length of a project is a trivial cost. The first time a diary entry from two years ago quietly kills a six-figure claim, it becomes the best-paid six minutes on the job. The training library has the short lessons that turn this from a good intention into the way your site simply runs.