I've used some version of this checklist on every project since 2014. It started as a laminated card in my site folder. The version below has been refined across dozens of NEC4 contracts and hundreds of diary reviews. It works because it's short enough to actually use, and specific enough to catch the entries that cost you money when they're missing.
For the full picture on site diaries and how they fit into your NEC4 commercial management, start with our pillar guide.
Why You Need a Checklist (Not Just Training)
Training teaches people what to record. That's necessary. But it doesn't solve the real problem.
The real problem is that site engineers write diary entries at 5:45pm after a ten-hour day on a wet site, and they forget things. Not because they're careless. Because they're human. A checklist catches the gaps that fatigue, habit, and routine create.
Here's what I've seen across hundreds of diary reviews:
- 72% of diary entries on a typical project are missing at least one commercially significant field
- Weather duration is the most commonly omitted detail (recorded as "rain" with no hours or intensity)
- Visitor names are skipped in roughly 60% of entries where site meetings or inspections occurred
- Photograph references are missing from 45% of entries that describe physical site conditions
These aren't guesses. They're patterns from reviewing diaries across NEC4 Option C and Option A contracts on infrastructure projects ranging from £3M to £80M.
A written checklist reduces incomplete entries by roughly 40% in the first month. A digital validation layer, like Gather's AI diary review, pushes that closer to 95%. But even a printed card taped to the site cabin wall beats no checklist at all.
The Complete Site Diary Checklist
Run through this checklist after writing your diary entry, before you submit or sign off. Every item is a yes/no question. If the answer is "no" and the item applies to that day, go back and fix it.
Section 1: Core Identifiers
| # | Check | Why It Matters |
|---|---|---|
| 1.1 | Date recorded (including day of week)? | Weekend working has commercial implications for prolongation |
| 1.2 | Shift type noted (day/night/split)? | Delay analysis requires clarity on which shift was affected |
| 1.3 | Start and finish times recorded? | Proves actual working hours against the Accepted Programme |
| 1.4 | Site/location/section identified? | Multi-section projects need location-specific records |
| 1.5 | Author name and role stated? | Evidential weight depends on who wrote it |
Section 2: Weather and Conditions
| # | Check | Why It Matters |
|---|---|---|
| 2.1 | Weather type recorded (rain, wind, frost, etc.)? | Baseline for clause 60.1(13) weather compensation events |
| 2.2 | Duration of adverse weather noted (hours, not just "morning")? | "Rain" without duration is commercially useless |
| 2.3 | Impact on work stated (stopped, restricted, or unaffected)? | Connects weather to programme impact |
| 2.4 | Ground conditions described? | Waterlogged vs workable determines whether delay was weather-caused |
| 2.5 | Temperature recorded (or at minimum: above/below freezing)? | Critical for concrete pours, earthworks, and surfacing |
Section 3: Labour
| # | Check | Why It Matters |
|---|---|---|
| 3.1 | Total headcount recorded? | Basic resource record for programme reconciliation |
| 3.2 | Breakdown by trade (not just a single number)? | Disruption claims require trade-specific evidence |
| 3.3 | Subcontractor gangs identified separately? | Defined Cost attribution needs clear allocation |
| 3.4 | Any standing time recorded with reason? | Idle labour costs must be linked to a cause |
| 3.5 | Overtime or extended hours noted? | Acceleration and prolongation claims need this data |
Section 4: Plant and Equipment
| # | Check | Why It Matters |
|---|---|---|
| 4.1 | Major plant on site listed? | Proves Defined Cost for plant-heavy compensation events |
| 4.2 | Plant utilisation noted (working/idle/standby)? | Standing time claims need contemporaneous records |
| 4.3 | Any breakdowns or plant off-hire recorded? | Affects programme analysis and Defined Cost |
| 4.4 | New plant arrivals or departures noted? | Establishes the resource profile against programme |
Section 5: Materials
| # | Check | Why It Matters |
|---|---|---|
| 5.1 | Key material deliveries recorded? | Tracks Defined Cost and flags supply chain issues |
| 5.2 | Any rejected materials or quality issues noted? | May trigger a compensation event or early warning |
| 5.3 | Material shortages or late deliveries recorded? | Evidence for delay claims if the cause is a Client risk |
Section 6: Work Completed and Progress
| # | Check | Why It Matters |
|---|---|---|
| 6.1 | Activities completed today described? | Measures progress against Accepted Programme |
| 6.2 | Quantities recorded where applicable? | Cost reconciliation and interim valuations |
| 6.3 | Any work out of sequence noted? | Changes to planned sequence may indicate disruption |
| 6.4 | Progress described against programme section/activity? | Links diary to the programme for delay analysis |
Section 7: Instructions and Communications
| # | Check | Why It Matters |
|---|---|---|
| 7.1 | Any instructions received today recorded? | Every instruction could be a compensation event |
| 7.2 | Who gave the instruction (name and role)? | Only the Project Manager can instruct under NEC4 |
| 7.3 | Was the instruction verbal or written? | Verbal instructions need confirming in writing |
| 7.4 | Does any instruction change the Works Information? | If yes, it's likely a compensation event under clause 60.1(1) |
| 7.5 | Has a compensation event notification been raised or flagged? | The 8-week time bar under clause 61.3 starts from awareness |
This is the section most people skip. And it's the one that costs the most money. I've reviewed projects where 15+ instructions were recorded in the diary over a three-month period, but only two compensation event notifications were raised. The rest were time-barred. That's not bad practice. That's leaving money on the table.
Section 8: Delays and Disruption
| # | Check | Why It Matters |
|---|---|---|
| 8.1 | Any delays today recorded? | Contemporaneous delay records beat retrospective analysis |
| 8.2 | Cause of delay stated? | Must link to a compensation event category |
| 8.3 | Duration of delay noted (hours or part-day)? | Quantifies impact for the time assessment |
| 8.4 | Which activities were affected? | Links delay to specific programme activities |
| 8.5 | Any knock-on effects on other trades or activities noted? | Disruption is about the ripple effect |
| 8.6 | Should this trigger an early warning under clause 15? | Early warnings aren't optional; they're a contractual obligation |
Section 9: Health, Safety, and Environment
| # | Check | Why It Matters |
|---|---|---|
| 9.1 | Any incidents or near misses recorded? | CDM and regulatory compliance |
| 9.2 | Safety observations noted? | Demonstrates proactive safety culture |
| 9.3 | Toolbox talks or briefings recorded? | Evidence of competence and communication |
| 9.4 | Any environmental issues (spills, dust, noise complaints)? | Protects against environmental liability |
Section 10: Photographs and Visual Evidence
| # | Check | Why It Matters |
|---|---|---|
| 10.1 | Photos taken of key activities or conditions? | Visual proof trumps written descriptions in disputes |
| 10.2 | Photos referenced in the diary text? | Unlinked photos are hard to locate months later |
| 10.3 | Before/after photos for changed conditions? | Critical for compensation event assessment |
| 10.4 | Photos of anything you'd struggle to describe in words? | Ground conditions, congestion, access restrictions |
Section 11: Visitors and Third Parties
| # | Check | Why It Matters |
|---|---|---|
| 11.1 | All visitors logged (name, organisation, purpose)? | Proves who was on site when decisions were made |
| 11.2 | Client/PM/Supervisor visits recorded? | Establishes what the Project Manager knew and when |
| 11.3 | Statutory inspections noted? | Compliance record for CDM and other regulations |
Section 12: Sign-Off
| # | Check | Why It Matters |
|---|---|---|
| 12.1 | Entry reviewed for accuracy before submission? | Errors in contemporaneous records undermine credibility |
| 12.2 | Any items from today that need following up tomorrow flagged? | Continuity between entries strengthens the narrative |
| 12.3 | Entry submitted/signed off within 24 hours? | Late entries carry less evidential weight |
The Red Flag Items: Five Checks You Must Never Skip
Not every checklist item carries equal weight. Skip the temperature on a mild day in July and nothing happens. Skip any of these five, and you risk real commercial damage.
1. Instructions received (7.1-7.5)
Every instruction that changes the scope, timing, or method of the works is potentially a compensation event. If you don't record it on the day it happens, the 8-week time bar clock is already running. On one HS2 enabling works package, the commercial team traced £420,000 in time-barred claims back to diary entries that said "PM visited site, discussed access changes" but didn't record what the instruction actually was.
2. Delays and their cause (8.1-8.3)
Retrospective delay analysis is expensive, adversarial, and far less convincing than a diary entry written at 6pm on the day it happened. An adjudicator will always prefer contemporaneous records over a forensic schedule analysis prepared two years later. Always.
3. Weather duration and impact (2.2-2.3)
"Rain" as a one-word weather entry has been the downfall of more compensation event claims than I can count. The difference between a successful and unsuccessful weather claim under clause 60.1(13) almost always comes down to whether the diary recorded duration and intensity, or just the existence of rain.
4. Labour breakdown by trade (3.2)
A single headcount number tells you nothing about disruption. If a Client instruction forced you to re-sequence works and your bricklayers stood idle while your groundworkers were doubled up, you need to show that in the diary. "42 operatives on site" doesn't do it. "12 groundworkers (6 diverted from Plot 4), 8 bricklayers (idle from 11:00, no access to Block C), 6 steelfixers..." does.
5. Photograph cross-references (10.2)
Photos without diary references become orphaned files. Diary descriptions without photos become unsubstantiated claims. The two need to link together. I've sat in adjudications where the Contractor had 4,000 site photos but couldn't match a single one to a specific diary entry. The photos existed. They proved nothing.
Worked Example: Before and After the Checklist
Here's a real diary entry (anonymised) from a £35M water treatment works under NEC4 Option C. I've run it through the checklist to show what's missing and why it matters.
Original entry (as submitted):
Tuesday 11 March 2025. Weather: Overcast, some rain. 38 operatives on site. Continued with concrete pour to bioreactor base slab (Area 3). Delivery of reinforcement for Phase 2 walls. PM visited at 14:00 to discuss programme. Photos taken. No incidents.
That reads fine at a glance. Most site engineers would sign it off and move on. Let's run the checklist.
| Check | Status | Issue |
|---|---|---|
| 1.1 Date (inc. day of week) | PASS | Tuesday 11 March 2025 |
| 1.2 Shift type | FAIL | No mention of day/night shift |
| 1.3 Start/finish times | FAIL | No times recorded |
| 2.1 Weather type | PASS | Overcast, rain |
| 2.2 Weather duration | FAIL | "Some rain" has no duration |
| 2.3 Impact on work | FAIL | Did the rain affect the concrete pour? |
| 3.1 Total headcount | PASS | 38 operatives |
| 3.2 Trade breakdown | FAIL | Just a total number |
| 5.1 Material deliveries | PASS | Rebar delivery noted |
| 6.1 Activities described | PASS | Concrete pour described |
| 6.2 Quantities | FAIL | No volume of concrete poured |
| 7.1 Instructions received | FAIL | PM visited to "discuss programme", but was anything instructed? |
| 7.2 Who gave instruction | PARTIAL | PM named by role, not name |
| 8.1 Delays recorded | UNKNOWN | Were there any? Entry doesn't confirm or deny |
| 10.1 Photos taken | PASS | "Photos taken" |
| 10.2 Photos referenced | FAIL | No detail on what photos show or where they're stored |
| 12.1 Reviewed for accuracy | UNKNOWN | No evidence of review |
Checklist result: 5 passes, 8 fails, 2 unknown. This entry would score roughly 35%.
Revised entry (after applying the checklist):
Tuesday 11 March 2025. Day shift, 07:00-17:30.
Weather: Overcast. Light rain 09:15-11:40 (approx 2.5 hrs). No impact on concrete pour (temporary shelter in place over Area 3). Ground conditions: soft in unpaved areas, no access restrictions.
Labour (38 total): 14 concrete gang (inc. 2 pump operatives), 8 steelfixers (Phase 2 wall rebar), 6 groundworkers (drainage run to MH7), 4 joiners (formwork strip Area 2), 3 electricians (cable containment), 2 banksmen, 1 site engineer. No standing time.
Plant: Concrete pump (working 08:00-16:00). 20T excavator (drainage, working). Telehandler (rebar offload, working 10:00-12:00, then standby).
Materials: 85m³ concrete delivered (4 loads, Hanson). 12T B500B rebar delivered (Phase 2 walls, Express Reinforcements). All materials accepted, no rejections.
Work completed: Concrete pour to bioreactor base slab Area 3 complete (85m³, as planned). Rebar fix to Phase 2 retaining wall progressing (estimated 40% complete, on programme). Drainage run MH6-MH7 continuing (12m laid today, 8m remaining).
Instructions/Communications: Project Manager [J. Thompson] visited site 14:00-15:15. Discussed programme for Phase 2 wall pours. PM verbally instructed revised pour sequence starting from south end rather than north end as shown in the Accepted Programme. This may constitute a change to the Works Information. Action: confirm instruction in writing and assess whether CE notification required under clause 61.3.
Delays: None today.
H&S: Toolbox talk (manual handling, concrete operations) delivered to concrete gang 06:45. No incidents or near misses.
Photos: 6 photos taken. Ref: SD-20250311-001 to 006. (001-002: concrete pour Area 3 in progress; 003: rebar delivery note; 004-005: drainage trench MH6-MH7; 006: PM site visit, programme discussion at site cabin).
Same day. Same project. The second version takes about eight minutes longer to write. But it's the difference between an entry that protects your commercial position and one that doesn't. That instruction about the revised pour sequence? If it turns out the south-to-north sequence costs an extra £45,000 in cranage and formwork redesign, the first version gives you nothing to claim against. The second version starts your CE trail.
The Checklist as a Printable Reference
For site teams who want a quick-reference card, here's the condensed version. Print it, laminate it, keep it in the site cabin.
| Category | Quick Checks |
|---|---|
| Core | Date + day. Shift type. Start/finish times. Location. Author. |
| Weather | Type. Duration (hours). Impact on work. Ground conditions. Temperature. |
| Labour | Total headcount. By trade. Subcontractors separate. Standing time + reason. |
| Plant | On site. Working/idle/standby. Breakdowns. Arrivals/departures. |
| Materials | Deliveries. Rejections. Shortages. |
| Progress | Activities done. Quantities. Against programme. Out of sequence? |
| Instructions | Any received? Who from? Verbal/written? Changes scope? CE needed? |
| Delays | Any today? Cause. Duration. Activities affected. Early warning needed? |
| Safety | Incidents. Near misses. Toolbox talks. Environmental issues. |
| Photos | Taken? Referenced in text? Before/after pairs? |
| Visitors | Names. Organisations. Purpose. Inspections. |
| Sign-off | Reviewed? Follow-ups flagged? Submitted within 24 hrs? |
Common Mistakes When Using a Checklist
1. Treating "N/A" as a valid answer for everything inconvenient
If no materials were delivered, write "No material deliveries today." Don't just skip the section. A blank field could mean nothing happened, or it could mean you forgot to record it. In a dispute, the other side will assume the latter.
2. Filling the checklist but not the diary
I've seen teams where the site engineer ticks the checklist boxes but the actual diary entry still says "38 operatives, work continued." The checklist is a verification tool, not a replacement for the diary itself. If the checklist shows you're missing weather duration, you fix the diary entry. You don't just tick "weather duration" and move on.
3. Only using the checklist on "interesting" days
The boring days matter more than you think. When a dispute arises over a two-week delay period, the adjudicator looks at every day, including the ones where nothing went wrong. Consistent, complete entries across ordinary days make your records credible when you need them for the extraordinary ones.
4. Not adapting the checklist to your contract
This checklist is built around NEC4 principles. If you're working under JCT or FIDIC, the commercial triggers are different. The instructions section, for example, needs to reflect whether you're dealing with Architect's Instructions (JCT) or Engineer's determinations (FIDIC) rather than PM instructions under NEC4. Adapt the checklist to match your contract form.
5. Stopping the checklist after the first month
Compliance always drops off. The first two weeks are perfect. By week six, it's back to "rain, 38 ops, work continued." Build the checklist review into your daily routine. Some commercial managers I've worked with make it part of the morning brief: "Yesterday's diary: did it pass the checklist?"
From Manual Checklists to Automated Validation
A printed checklist is a good start. But it relies on the person filling it in to be honest about their own gaps, and it can't cross-reference against the Accepted Programme, previous entries, or contract obligations.
That's where Gather comes in. Gather's AI diary review does what this checklist does, but automatically and at a level of detail no manual review can match:
- Completeness scoring: Every diary entry is scored against a validation framework. Missing fields are flagged before submission.
- Compensation event detection: Instructions and delays are automatically cross-referenced against NEC4 clause 60.1 categories. If a diary entry describes something that looks like a CE but no notification exists, Gather flags it.
- Programme alignment: Diary progress is compared against the Accepted Programme. If the diary says work is "on programme" but the programme shows critical path float being consumed, that contradiction gets surfaced.
- Pattern detection: Gather spots trends across weeks and months that no daily checklist can catch. Recurring weather impacts building toward a clause 60.1(13) claim. Gradual labour underdeployment suggesting disruption. Access restrictions that appear in four diaries but haven't triggered an early warning.
The manual checklist on this page will improve your diary quality immediately. Gather replaces the checklist entirely by building the validation into the diary process itself.
For more on how site diaries connect to NEC4 compensation events, see our bridge guide.
.webp)
