Site Diary: The Complete Guide to Construction Site Diaries
A site diary is a daily written record of everything that happens on a construction project: who was on site, what work took place, what went wrong, and what changed. It is the single most important document you will produce on any contract, and most teams get it badly wrong.
If you are the commercial manager or QS on an NEC4 job, the site diary is not a site manager's admin chore. It is the record that notifies a compensation event inside the eight-week time bar, substantiates Defined Cost, and still stands at final account.
A diary written on the day is how you prove what happened. A Friday catch-up is not.
A construction site diary is a contemporaneous, chronological record of daily events on a building or infrastructure project. Weather, labour, plant, materials, instructions, delays, visitors, safety observations, and anything that departed from the Accepted Programme.
People forget. Diaries don't.
The commercial test is simple. Can a QS, six months later, rebuild the day well enough to notify a compensation event and price it? Rain from 07:00 to 11:30, standing water in Excavation Zone 3, no piling possible until pump-out complete at 13:15 does that. Bad weather caused delays does not.
Call it a building site diary or just the diary. The job is the same: write a record today that protects the commercial position tomorrow. For entry structure, see how to write a site diary.
Why Site Diaries Matter Commercially
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.
Site diaries matter for three reasons: they are the evidence for compensation events, they protect the programme position, and they support final account negotiations.
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" does not 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 weather, labour, plant, work completed, instructions, delays, visitors, safety, deliveries and photos.
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
If the diary is sitting in the cabin unread, the eight-week clock is already running. Rosie reads those entries against the contract so the commercial team sees the compensation event while the record is still warm.
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.
Clause 61.3. You have 8 weeks from becoming aware of a compensation event to notify the Project Manager. The diary is the evidence of when awareness crystallised.
Clause 31/32. Every programme revision should be supported by diary records showing why the programme changed. Your Accepted Programme is the contract baseline.
This causes more confusion than it should. They are different documents with different purposes, and you probably need both.
A site diary records what happened: events, conditions, problems, progress. It is 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 is 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.
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 is 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 have 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 is 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.
If you are coming from US terminology, see site diary vs daily log for how the UK and US terms map to each other.
Digital Site Diaries vs Paper Logbooks
Paper diaries still dominate on many UK sites. The supervisor grabs the A4 hardback from the site cabin, writes it at the end of shift, and puts it back on the shelf. It works. Until someone asks for Phase 2 in a hurry and the cabin has gone back to the hire company.
A digital site diary for NEC4 work does not have to replace the cabin habit. It has to make the record searchable when the QS is writing the quotation. Timestamped entries. Photos sitting with the words, not in a camera roll. More than one person contributing without fighting over one book.
The commercial question is not which app looks modern. It is whether the QS can find the access restriction from 12 March before clause 61.3 runs out. Offline capture still matters on remote sites. So does a format a site engineer will actually complete at 17:30.
Rosie does not replace the diary. She reads it against the NEC4 contract and the Accepted Programme, and flags the events a tired Friday review will miss.
Common Mistakes That Cost Money
I have 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 does not.
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 cannot 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 is almost impossible to dispute. Conditions, progress, problems, access restrictions: photograph everything. Storage is cheap. Losing a £200,000 claim because you cannot 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 will find the evidence but miss the deadlines. Gather automates this review process, but even without software, a 30-minute weekly review catches most issues.
Related Guides
This pillar page gives you the overview. The guides below go deeper on each topic.
Site diaries feed earned value tracking because progress and resource data are the raw inputs. For how a diary sits next to other daily records, see daily report vs site diary.
Legal and Retention
No UK statute requires a site diary by name. CDM 2015 and the Building Safety Act 2022 still make contemporaneous records expected professional practice. Under the Limitation Act 1980 keep records at least 6 years from completion, or 12 years if the contract is a deed. See record retention.
Site records, assured
See how Rosie reads a site diary against the contract
On a typical NEC4 project, thin diary records mean legitimate change goes unrecovered. The commercial team should review the diary every week against clause 60.1, not at final account.
A site diary is a contemporaneous daily record of what happened on site. On an NEC4 job it is how the commercial team proves a compensation event and prices Defined Cost.
Is a site diary a legal requirement in the UK?
No UK statute requires a site diary by name. However, the Construction (Design and Management) Regulations 2015 require records of health and safety arrangements, and the Building Safety Act 2022 requires a golden thread of information for higher-risk buildings. In practice, meeting these obligations without a site diary is extremely difficult. Most standard form contracts and adjudicators treat site diaries as expected professional practice.
Who should write the site diary?
On most projects, the site engineer or foreman writes the diary, with contributions from supervisors across different work fronts. On larger projects (over £10M or with multiple active areas), multiple contributors are essential because no single person can observe everything. The commercial team should review entries weekly to identify potential compensation events or claims triggers.
How often should a site diary be completed?
Every working day, without exception. Entries should be written on the same day, ideally before leaving site. Courts and adjudicators give significantly more weight to contemporaneous records (written on the day) than to entries reconstructed days or weeks later. If you miss a day, note the gap honestly rather than backfilling.
What is the difference between a site diary and a daily allocation sheet?
A site diary records events and conditions (what happened). A daily allocation sheet records resource deployment (who did what, where, for how long). The diary is narrative and contextual. The allocation sheet is tabular and quantitative. Both are needed for comprehensive commercial records, particularly under NEC4 where Defined Cost substantiation requires detailed resource records.
How long should I keep site diary records?
Under the Limitation Act 1980, the minimum is 6 years from project completion for simple contracts, or 12 years if the contract is executed as deed. For projects involving personal injury risk, 15 years is prudent. For higher-risk buildings under the Building Safety Act 2022, records should be retained for the lifetime of the building. See our detailed guide on record retention periods.
Can a site diary be used as evidence in adjudication?
Yes, and it is often the most persuasive evidence available. Adjudicators routinely prefer contemporaneous site records over witness statements prepared for the proceedings because diaries are created in real time without litigation in mind. The key requirements are that entries are genuinely contemporaneous, factual, and specific. Vague or retrospective entries carry little weight.
How do site diaries support NEC4 compensation events?
Site diaries provide the evidence chain for NEC4 compensation events at every stage: identifying that an event occurred, proving the date of awareness (critical for the 8-week time bar), substantiating the quotation with contemporaneous resource and disruption data, and supporting the assessment from the dividing date. Without diary records, CEs are difficult to notify on time and almost impossible to substantiate properly.
What should I do if I have fallen behind on site diary entries?
Start again today. Do not try to reconstruct the past from memory, because those entries will not be contemporaneous and will carry little evidential weight. Note the gap honestly ("No entries recorded 14-18 March due to site engineer absence") and ensure entries are maintained daily going forward. One week of missing records is recoverable. Three months of missing records during a critical programme period can cost you the entire commercial position on delayed works.
Should site diaries be digital or paper?
Both work if used consistently. Digital site diary software offers advantages in searchability, backup, photo integration, and multi-user access. Paper diaries are simpler and do not depend on connectivity or device availability. The critical factor is not the medium; it is the discipline. A paper diary written every day beats a digital system that nobody opens. For most Tier 1 contractors, digital is now standard because of the volume of data and the need for rapid retrieval during disputes.