The Daily Site Diary: What to Record, and Why It Wins Disputes

Short answer: Record weather with times, labour by company and trade, plant with operating and standing hours, work progressed by area, deliveries, visitors and inspections, instructions received, delays with start and finish times and causes, and safety events. Write it on the day, sign it, and make sure it agrees with your timesheets. Its value is entirely in being contemporaneous.

Why the diary is the first document requested

When a job goes to a dispute — a delay claim, a defect argument, a disputed daywork account, an HSE investigation — the first request is almost always for contemporaneous records. Not the programme, not the correspondence. The diary.

The reason is simple. Correspondence is written by people who already know there is an argument. A diary is written by someone recording a Tuesday. That difference in motive is precisely what makes it persuasive, and it is why a diary started after the trouble began is worth so little.

There is a corollary worth internalising: a diary you keep properly protects you against claims as often as it supports yours. A subcontractor claiming they were delayed by your attendance is answered by a diary showing their four operatives were on site and working every day of the period.

What goes in

Weather, with times

Not "rain". Rain from when to when, and what it stopped. Weather is the most common delay cause and the easiest to verify independently, which cuts both ways: a diary claiming a washout on a day the Met Office recorded as dry destroys the credibility of every other entry.

Record temperature where it matters — concrete pours, mortar, resin, roofing membranes all have working limits, and a record of the temperature at the time of the decision is what justifies stopping.

People, by company and trade

Numbers on site, broken down: your own operatives by trade, each subcontractor by company with their numbers, staff, visitors. This is the entry that reconciles against timesheets, and the one that answers most attendance disputes.

Record who should have been there and was not. An absent subcontractor gang is a fact worth two lines on the day and worth a great deal at the account.

Plant, working and standing

Item by item, with hours. Separate operating hours from standing hours and record why anything stood. Plant standing is either your cost or someone else's, and the diary entry made on the day is what decides which.

Work progressed, by area

Specific: which activity, which area, how far it got. "Blockwork" is not a record. "Blockwork to gable, grid B to D, to first lift" is.

This is the entry that builds the as-built programme. If your diary is specific enough about location and activity, you can reconstruct actual progress from it months later — which is exactly what a delay analysis requires and what most contractors cannot do.

Deliveries and materials

What arrived, from whom, quantity, and condition. Note short deliveries and damage on the day. A delivery note signed clean cannot later be argued to have arrived damaged.

Visitors and inspections

Who came, from where, what they looked at, what they said. Building control, the client's representative, the designer, an HSE inspector, a scaffolding inspection. Instructions given verbally during these visits are the single most commonly lost commercial record on a construction site.

Instructions received

Every direction, including verbal ones. Who gave it, when, what it was, and — critically — whether you have confirmed it in writing. Most standard forms require verbal instructions to be confirmed in writing within a set period to be effective. The diary entry is your prompt to send that confirmation, and your evidence that the instruction was given if you did not.

Delays and disruption

The entry that earns the diary its keep. For each event: what happened, when it started, when it finished, which activity it affected, how many people and how much plant were affected, and what was done to mitigate it.

Mitigation matters more than contractors expect. A record showing the gang was redeployed to another area rather than sent home is what distinguishes a well-managed delay from an inflated claim.

Safety events

Inductions carried out, toolbox talks given, near misses, first aid, any dangerous occurrence, and any enforcement contact. Note that a RIDDOR-reportable event has its own statutory reporting obligation and its own deadline — the diary is a record, not a report.

Anything unusual

Neighbours, access problems, deliveries turned away, services struck, a road closure, an unexpected discovery. Today's oddity is next year's key fact, and you cannot know which one in advance.

What makes an entry hold up

Contemporaneous. Written on the day. A week of entries written on a Friday is visible to anyone reading it — the language flattens, the times get rounder, the detail thins.

Attributed. One named author per day, who could be asked what they saw.

Specific. Times, locations, numbers, names. Specificity is what makes an entry checkable, and checkable is what makes it believed.

Consistent. The diary must agree with timesheets, delivery notes, daywork sheets and plant returns. A single unexplained inconsistency invites the other side to test every other entry.

Unamended, or visibly amended. Correcting an error is fine; correcting it invisibly is not. A record that can be silently rewritten after the event has no evidential value at all, which is the fundamental problem with the shared spreadsheet.

Where paper diaries fail

The traditional site diary is a hardback book in the site cabin. It has one genuine advantage — it is obviously sequential and hard to alter — and several serious weaknesses:

• It exists in one copy, in one place, and gets rained on, lost, or left in a cabin that goes back to the hire company.
• It cannot be searched. Finding every entry mentioning a grid reference means reading a year of pages.
• It has no photographs, which are now the most persuasive record available.
• Nobody in the office sees it until it matters, so nobody notices it has not been written for three weeks.

The shared spreadsheet solves distribution and creates a worse problem: no author, no timestamp, and full retrospective editability. As evidence, it is weaker than the book it replaced.

What a good digital diary does differently

Three properties matter, and only three:

It is written on site, on the day, by the person who was there — which means it has to work on a phone, in a cabin, with no signal, in under five minutes.

Entries carry their own provenance — author, time written, and an audit of any later amendment, so a correction is visible as a correction.

It reconciles automatically with the other records. If labour on site comes from the same clock-in data as the timesheets, the diary and the payroll cannot disagree, and the most common credibility attack disappears.

ScopeKit keeps a signed daily site diary for every live site — weather, hours, operatives, inductions, delays and the rest — recorded on site from a phone, with photographs attached and the labour figures drawn from the same records that produce timesheets. The entry is signed and timestamped, and amendments are audited rather than silent.

A five-minute daily habit

At the end of each day, before leaving site:

Weather and any weather impact, with times.

Numbers on site, by company.

Plant, and anything that stood.

What progressed, by area.

Deliveries in.

Anyone who visited, and anything they said.

Any delay: start, finish, cause, effect, mitigation.

Any safety event.

Sign it.

Five minutes a day. It is the cheapest insurance on the job, and the only record whose value comes entirely from having been written before anybody needed it.

Related reading

• Dayworks explained — the sheets your diary must reconcile with.
• RIDDOR reporting guide — when a diary entry also triggers a statutory report.
• Awaab's Law repair timescales — evidencing attendance against a statutory clock.
• The ScopeKit field app — diaries, forms and photos captured on site, offline.