If you're working under NEC4, your construction site diary isn't just good practice. It's the evidential backbone of every compensation event, every time extension, and every disputed penny at final account. Without it, you're guessing. And guessing loses money.
This guide covers everything a commercial team needs to know about site diaries: what they are, why they matter commercially, what to record, how to structure entries, and how to turn daily records into recoverable revenue. Each section links to a detailed spoke page where you can go deeper.
What Is a Site Diary?
A construction site diary is a contemporaneous, chronological record of daily events on a building or infrastructure project. It captures weather, labour, plant, materials, instructions received, delays encountered, visitors, safety observations, and anything else that deviates from the planned programme.
Think of it as the project's memory. People forget. Diaries don't.
The best site diaries aren't literary masterpieces. They're factual, specific, and written on the day. "Rain from 07:00 to 11:30, standing water in Excavation Zone 3, no piling possible until pump-out complete at 13:15" tells you everything. "Bad weather caused delays" tells you nothing.
Whether you call it a building site diary, a construction daily log, or just "the diary," the purpose is the same: create a record today that protects your position tomorrow. For a deeper look at entry structure and formatting, see our guide on how to write a site diary.
Why Site Diaries Matter Commercially
Here's the number that should keep every commercial manager awake. On a typical £50M infrastructure project with 3% variations, poor records mean roughly 40% of legitimate change goes unrecovered. That's £600,000 walking out the door because nobody wrote down what happened on a Tuesday in March. Six hundred grand. Gone.
Site diaries matter for three reasons:
1. They're your evidence for compensation events. Under NEC4, you can't notify a compensation event without knowing it happened. And you can't prove it happened without records. The eight-week time bar is absolute. Miss it, and the money's gone regardless of entitlement.
2. They protect your programme position. When the Project Manager challenges your revised programme submission, what do you point to? Your site diary. It's the primary evidence that delay actually occurred. No diary entries, no credible delay narrative.
3. They support final account negotiations. Final accounts are won and lost on records. I've sat across from client QSs who've rejected perfectly legitimate claims because the contractor couldn't produce contemporaneous evidence. The work happened. The money was spent. But without the diary, it's just your word against theirs.
On one £35M highways package in the North West, the commercial team recovered an additional £2.1M in compensation events between January 2023 and June 2024. That wasn't luck. The site engineers were writing proper diary entries that flagged weather disruption, late design information, and access restrictions, and the QS team reviewed them weekly. The diaries didn't just record history. They generated revenue.
Worked Example: How a Diary Entry Becomes a Compensation Event
Scenario: 12 March 2025, £28M Network Rail electrification package under NEC4 Option C. The site diary records: "Client utility diversion works ongoing in Section 4 (chainage 1200-1400). Our piling rig unable to access Grid K3-K8 as planned on Accepted Programme Rev 3. Rig and 4-person crew stood down from 07:30. Access expected to resume 14 March per verbal instruction from PM at 09:15."
What happens next:
- The QS reads this entry during the weekly diary review on 14 March
- This is a compensation event under clause 60.1(5): the Contractor is unable to access the working area as shown on the Accepted Programme
- The QS notifies the Project Manager under clause 61.3 on 14 March, within the 8-week time bar (awareness date: 12 March)
- The CE quotation under clause 62 includes 2 days of standing time for piling rig (£3,200/day) plus 4 operatives (£280/day each), plus the knock-on delay to the piling sequence
- Total CE value: £9,440 direct cost plus 1.5 days of critical delay
Without the diary entry? The QS might not have known about the access restriction until the next programme update meeting on 28 March. By then, 16 days have passed since awareness, and the event risks being absorbed into the noise. The diary turned a £9,440 recovery into a recorded, notified, and substantiated claim within 48 hours.
Worked Example: Weather Records That Pay for Themselves
Scenario: Week commencing 3 February 2025, £42M flood defence scheme under NEC4 Option A. The site diary records weather at 07:00, 12:00, and 17:00 each day:
Date 07:00 12:00 17:00 Rainfall (mm) Mon 3 Feb 4C, heavy rain 5C, drizzle 4C, overcast 18mm Tue 4 Feb 3C, sleet 2C, snow 1C, clear 12mm Wed 5 Feb -1C, frost 3C, clear 2C, clear 0mm Thu 6 Feb 2C, heavy rain 4C, rain 3C, drizzle 24mm Fri 7 Feb 5C, overcast 6C, clear 4C, clear 2mm The diary also notes: "Earthworks suspended Mon-Tue and Thu due to saturated formation. Piling continued all week (unaffected). 12 earthworks operatives redeployed to drainage works Mon/Tue; stood down Thu as drainage works also weather-dependent."
Result: The QS cross-references the diary weather data with Met Office records and the contract weather measurement data. The rainfall on Monday and Thursday exceeds the 1-in-10-year threshold at the nearest Met Office station, qualifying as a compensation event under clause 60.1(13). The CE quotation covers 2 lost days of earthworks production, standing time for plant, and the programme impact of pushing the earthworks critical path by 2 days. Total CE value: £47,600.
Without detailed weather records? The QS would need to reconstruct conditions from Met Office data alone, with no proof of actual site impact. "It rained" doesn't tell you earthworks stopped. The diary does.
What to Record in a Site Diary
The golden rule: if it happened on site today, write it down. If it was different from what was planned, write it down in detail.
At minimum, every entry needs:
| Category | What to Record | Why It Matters |
|---|---|---|
| Date and weather | Conditions at 07:00, 12:00, and end of shift. Temperature, wind, rainfall | Weather is a compensation event trigger under clause 60.1(13) |
| Labour | Numbers by trade, by subcontractor, hours worked | Proves resource levels for disruption claims |
| Plant and equipment | What was on site, what was working, what was idle | Standing time supports time-related cost claims |
| Work completed | Location, activity, quantities where possible | Progress evidence for programme updates |
| Instructions received | Who gave them, what they said, when | May constitute a compensation event under clause 60.1(1) |
| Delays and disruption | What stopped, when, why, impact on planned activities | Foundation for every CE notification |
| Visitors | Who visited, purpose, any instructions or comments | Client instructions can trigger CEs |
| Safety observations | Incidents, near misses, inspections | CDM 2015 compliance and RIDDOR reporting |
| Material deliveries | What arrived, quantities, condition, any rejections | Supply chain issues may trigger CEs |
| Photos | Progress, conditions, problems, before/after | Visual evidence is harder to dispute than text |
For a comprehensive breakdown with examples, see what to include in a site diary. We've also published site diary examples showing good and bad entries side by side.
If you want a ready-made format, grab our site diary template.
How to Write Effective Site Diary Entries
Most site diary entries fail not because they're empty, but because they're vague. "Groundworks ongoing in Area B" is technically true and commercially useless. Compare that with: "CFA piling rig 3 relocated to Grid J7-J12, Area B. 14 piles cast to design depth (18m). 2 piles abandoned at 12m due to unexpected rock head; RE notified verbally at 14:30, written confirmation to follow."
The second entry does three things the first doesn't: it records specific quantities, it flags a problem, and it documents communication. That's the difference between a diary and a tick-box exercise.
Three rules for good entries:
Be specific. Locations, grid references, quantities, times, names. "Section 3 chainage 450-520" not "along the road."
Record deviations. Anything different from the Accepted Programme gets detailed attention. The planned activities that didn't happen are often more important than the ones that did.
Write it today. A diary written on Friday afternoon covering Monday to Thursday is a fiction. Courts and adjudicators can tell. Write entries on the day, ideally before leaving site. If you absolutely can't, write them the following morning and note the delay.
Our full guide on how to write a site diary covers entry structure, language to use and avoid, and a step-by-step walkthrough. For teams managing daily task assignments alongside diary records, see the completion checklist that ties both processes together.
Site Diary vs Daily Allocation Sheet
This causes more confusion than it should. They're different documents with different purposes, and you probably need both.
A site diary records what happened: events, conditions, problems, progress. It's a narrative account of the day.
A daily allocation sheet records who did what: which operatives were assigned to which tasks, for how long, in which locations. It's a resource deployment record.
| Feature | Site Diary | Daily Allocation Sheet |
|---|---|---|
| Primary purpose | Record events and conditions | Record resource deployment |
| Who writes it | Site engineer, foreman, or site manager | Foreman or supervisor |
| Format | Narrative with structured fields | Tabular: names, tasks, hours, locations |
| Commercial use | CE evidence, delay narrative, compliance | Labour cost substantiation, productivity analysis |
| Contractual basis | Supports clause 61, 62, 63 claims | Supports Defined Cost records under clause 11.2(23) |
On well-run projects, these feed into each other. The allocation sheet tells you the resource input. The diary tells you the context and output. Together, they give you the full picture.
For a detailed comparison, see site diary vs allocation sheet. If you need the resource tracking document, we have a guide on daily allocation sheets and a downloadable allocation sheet template.
Site Diary vs Daily Report
Another common question. A site diary and a daily report overlap, but they serve different audiences and have different levels of formality.
A site diary is typically an internal contractor document. It's contemporaneous, factual, and written for the project team and commercial function.
A daily report (sometimes called a daily site report or construction daily log) is often a formal document submitted to the client, the Principal Contractor, or the project management team. It may include a narrative summary, progress photos, and KPI data.
Some organisations merge these into one document. That can work, but be careful: anything you submit to the client becomes disclosure. Keep your internal site diary honest and unfiltered. Your daily report might need to be more measured. I've seen too many projects where the combined document gets sanitised for the client's benefit, and the commercial team loses the unvarnished version they actually need at final account.
There's a distinction in who writes what, too. The foreman report covers gang-level detail that feeds into the broader diary. On a large project, the foreman's report and the engineer's site diary serve different levels of granularity, and you want both.
For more on when to keep them separate and when to combine them, see daily report vs site diary.
NEC4 Contracts and Site Diaries
Under NEC4, site diaries aren't just record-keeping. They're a contractual mechanism.
The contract doesn't explicitly require a "site diary," but it creates obligations that are practically impossible to meet without one. Consider these:
Clause 16 (Early Warnings). You must notify early warnings as soon as you become aware of a matter that could increase the Prices, delay Completion, or impair performance. Your diary is where you first spot the pattern. Three days of access restrictions don't look like much individually. Plotted in a diary over two weeks, they're clearly a compensation event.
Clause 61.3 (Notification Time Bar). You have 8 weeks from becoming aware of a compensation event to notify the Project Manager. "Becoming aware" is the trigger, and your diary is the evidence of when awareness crystallised. Without it, the PM can argue you knew earlier, and your notification is time-barred.
Clause 63 (Assessment of Compensation Events). CEs are assessed prospectively from the dividing date. Your diary provides the baseline data: what was happening before the event, what resources were deployed, what the programme looked like. Without contemporaneous records, your CE quotation is built on assumptions, and assumptions get challenged.
Clause 31/32 (Programme). Every programme revision should be supported by diary records showing why the programme changed. "Revised due to weather delays" means nothing without the diary entries proving which days were lost and what the impact was on the critical path. Your Accepted Programme is the contract baseline, and the diary is the evidence trail that tracks departures from it.
For the full picture on how site diaries support NEC4 commercial management, see our bridge post on site diaries and NEC4 compensation events. If your records aren't up to scratch, the consequences go beyond missed CEs; poor site records are a direct route to disallowed cost under Options C and D.
Legal and Compliance Requirements
Is a site diary a legal requirement? Not exactly. No UK statute mandates a "site diary" by name. But several regulations create duties that are virtually impossible to discharge without one.
The Construction (Design and Management) Regulations 2015 require the Principal Contractor to maintain records of workforce health and safety arrangements, site inductions, and incident reporting. A site diary is the natural home for this information.
The Building Safety Act 2022 introduced the "golden thread" of information for higher-risk buildings. While this primarily applies to residential buildings over 18 metres, it establishes a principle of contemporaneous record-keeping that's influencing commercial practice across the sector.
The Limitation Act 1980 sets the clock on contractual claims at 6 years (12 years for deeds). Your site records need to survive at least that long.
Adjudication and litigation. In disputes, contemporaneous records carry far more weight than witness statements prepared years after the event. Judges and adjudicators routinely prefer diary evidence over testimony because diaries are created in real time with no litigation in mind. The case of Costain Ltd v Bechtel Ltd [2005] is often cited for the principle that contemporaneous records are the "best evidence" of what actually happened.
So what's the practical answer? You don't have a legal obligation to keep a site diary. You have a legal and commercial obligation to maintain records that a site diary is the most efficient way to satisfy. Try explaining to an adjudicator why you didn't bother. See how that goes.
Retention: How Long to Keep Site Records
Most commercial managers know they need to keep records. Fewer know for how long. The answer depends on the contract form and the nature of potential claims.
| Scenario | Minimum Retention Period | Source |
|---|---|---|
| Standard contract (simple) | 6 years from completion | Limitation Act 1980, s.5 |
| Contract executed as deed | 12 years from completion | Limitation Act 1980, s.8 |
| Defects liability period active | Until DLP expires + 6 years | Contract terms + Limitation Act |
| Projects involving personal injury risk | 15 years (prudent) | Limitation Act 1980, s.11/14 |
| Higher-risk buildings (BSA 2022) | Lifetime of the building | Building Safety Act 2022 |
Don't just keep the diaries. Keep them accessible. A box of paper diaries in a warehouse in Widnes isn't much use when you need to respond to an adjudication notice in 7 days. Digital records are searchable. Paper records are not.
For detailed retention guidance including digital storage requirements and destruction protocols, see our guide on how long to keep site records.
Digital Site Diaries vs Paper Logbooks
Paper diaries still dominate on many UK construction sites. The supervisor grabs the A4 hardback from the site cabin, scribbles in it at the end of shift, and puts it back on the shelf. It works. Sort of.
The problem with paper isn't the writing. It's what happens after. Paper diaries sit in site cabins until someone asks for them, usually months later during a final account negotiation or a dispute. By then, pages are missing, handwriting is illegible, and nobody can find the diary from Phase 2 because the site cabin was returned to the hire company. I've personally spent an afternoon in a storage unit in Warrington looking for a missing diary. We found it. Behind a pallet of cable trays.
Digital site diary software solves the retrieval problem. Every entry is timestamped, searchable, and backed up. Photos are embedded rather than floating in a camera roll. Multiple team members can contribute without fighting over one physical book. Most site diary apps work offline too, syncing when connectivity returns, so there's no excuse on remote sites.
But digital tools introduce their own risks. If the operative can't use the interface, entries don't get made. The best tool is the one that actually gets used, every day, by every person who should be writing in it.
Gather's approach is different from most site diary apps. Instead of replacing the diary, Gather's AI agent reviews existing diary entries against contract terms and the project baseline, automatically flagging potential compensation events that humans miss. It doesn't matter whether the diary is digital or handwritten, provided it's captured. The AI does the commercial analysis that would otherwise take a QS 50 hours per month per project. If you're curious about how AI is changing construction workflows more broadly, that's a topic we cover in depth separately.
For teams evaluating digital options, the key questions are: Does it work offline? Can labourers actually use it? Does it integrate with your commercial workflow? And critically, does it help you find the money in the records, or just store them more neatly?
Common Mistakes That Cost Money
I've reviewed hundreds of site diaries across NEC3 and NEC4 contracts. The same problems come up on nearly every project, and honestly, some of them are painful to see.
1. Writing the diary days later. Friday afternoon catch-up sessions are not contemporaneous records. Adjudicators can tell when entries have been batch-written, and they discount them accordingly. Write the diary on the day. Every day. No exceptions.
2. Recording activities but not deviations. "Concrete pour Bay 4, 45m3" is fine for progress. But if the concrete arrived 3 hours late because the batching plant broke down, and that pushed the pour into overtime, that deviation is where the money is. Record what went wrong, not just what went right.
3. Using vague language. "Some delay due to weather" is useless. "Heavy rainfall from 06:00 to 10:30 (Met Office data confirms 28mm), standing water across the formation in Zone 2, excavation suspended, 8 operatives and 2 excavators stood down until 11:15" is evidence. One gets you paid. The other doesn't.
4. Not linking diary entries to contract events. Your diary should flag when something looks like it might be a compensation event. "Note: access to working area restricted by client works in Zone 5, possible CE under 60.1(5)" turns a passive record into an active commercial tool.
5. Only the foreman writes it. On a £30M project with 150 operatives across six work fronts, one person can't see everything. Multiple contributors, whether through a shared digital system or separate section diaries that are collated, give you complete coverage.
6. Ignoring weather data. Weather is one of the most common compensation event triggers under NEC4 clause 60.1(13), yet most diaries record it as "fine" or "rain." Record actual conditions: temperature, wind speed, rainfall duration and quantity. Cross-reference with Met Office data. This is the difference between a rejected and an accepted weather CE.
7. Not taking photographs. A photo with a timestamp and location tag is evidence that's almost impossible to dispute. Conditions, progress, problems, access restrictions: photograph everything. Storage is cheap. Losing a £200,000 claim because you can't prove the access road was flooded is not.
8. No weekly commercial review. The diary is only half the job. Someone from the commercial team needs to review entries every week, cross-referencing against the programme and contract. If the QS only reads the diary at final account, they'll find the evidence but miss the deadlines. Gather automates this review process, but even without software, a 30-minute weekly review catches most issues.
Site Diary Quick Reference
| Element | Best Practice | Common Failure |
|---|---|---|
| When to write | Same day, before leaving site | Friday catch-up (not contemporaneous) |
| Weather recording | Temperature, rainfall (mm), wind, conditions at 3 times daily | "Fine" or "Rain" |
| Labour records | Headcount by trade, by subcontractor, hours worked | Total headcount only |
| Delay recording | Activity affected, duration, cause, impact on programme | "Some delay occurred" |
| Instructions | Who gave it, when, what was said, written or verbal | Not recorded at all |
| Photos | Timestamped, geotagged, referenced in diary text | Separate camera roll, unlinked |
| CE flags | Note potential CE reference in diary entry | Left to QS to spot weeks later |
| Format | Structured fields with narrative section | Blank page, inconsistent format |
| Contributors | Multiple: foreman, engineer, supervisor | Single author per site |
| Storage | Digital backup, searchable, minimum 6 years | Paper in site cabin |
| Review frequency | Weekly by site QS for commercial opportunities | Only at final account |
For a printable version with tick-boxes, see the site diary completion checklist.
.webp)
