Below is a complete construction site diary template you can use immediately, with field-by-field guidance, NEC4-specific additions, and a worked example showing exactly how a well-completed diary protects your commercial position.
What a Good Site Diary Template Covers
Most free templates you'll find online are thin. They give you a date field, a weather box, and a comments section. That's not a site diary. That's a notepad.
A template worth using captures twelve categories of information. Miss any one of them and you'll regret it six months later when someone asks you to prove what happened on a Tuesday in October.
Here's what to include in a site diary at a minimum:
| # | Field | Why It Matters |
|---|---|---|
| 1 | Date and day | Establishes the record timeline. Sounds obvious, but I've seen diaries submitted without dates |
| 2 | Weather conditions | Directly feeds NEC4 clause 60.1(13) weather compensation events |
| 3 | Temperature and wind | Supports weather measurement data against the 1-in-10-year threshold |
| 4 | Shift times | Proves working hours for disruption and prolongation claims |
| 5 | Labour count by trade | Essential for valuing compensation events under clause 63 |
| 6 | Plant and equipment on site | Feeds Defined Cost calculations and demonstrates capacity |
| 7 | Materials delivered | Tracks supply chain performance and identifies delay causes |
| 8 | Work completed | Progress evidence. Links directly to the Accepted Programme |
| 9 | Work areas / locations | Pinpoints where activity happened for delay analysis |
| 10 | Instructions received | Every verbal or written instruction could be a compensation event |
| 11 | Visitors and inspections | Records who was on site and what they observed |
| 12 | Delays, disruptions, incidents | The raw material for every commercial notification you'll ever write |
| 13 | Photographs | Visual evidence. Worth more than ten paragraphs of description |
| 14 | Signature and author | Proves who wrote the entry and when |
The Template
Here's a construction site diary template structured for UK contractors working under NEC4. You can adapt it for JCT or FIDIC, but the NEC4 fields are the ones most teams miss.
Section A: Project and Date Information
| Field | Entry |
|---|---|
| Project name | [e.g., A303 Amesbury to Berwick Down] |
| Contract number | [e.g., HE-SW-2024-0847] |
| Contract form | [e.g., NEC4 ECC Option C] |
| Date | [DD/MM/YYYY] |
| Day of week | [e.g., Tuesday] |
| Report author | [Name and role] |
| Shift | [e.g., Day shift 07:00-18:00] |
Section B: Weather Conditions
Record weather at three fixed times: start of shift, midday, and end of shift. This isn't optional on NEC4 contracts. Clause 60.1(13) requires you to demonstrate that weather was "sufficiently adverse" compared to the weather measurement data defined in Contract Data Part One.
| Time | Conditions | Temp (C) | Wind (Beaufort) | Rainfall (mm) |
|---|---|---|---|---|
| 07:00 | ||||
| 12:00 | ||||
| 17:00 |
Cumulative rainfall (24hr): _____ mm
Compared to weather station threshold? Yes / No
Impact on planned work? Yes / No (if yes, describe in Section F)
Section C: Labour
List every person on site by trade. Don't just write "6 labourers." That's useless for a compensation event quotation. You need names and trades so you can price the Defined Cost accurately.
| Trade | Number | Names (or reference) | Hours worked | Activity |
|---|---|---|---|---|
Total labour on site: _____
Subcontractor labour included? Yes / No
Any overtime worked? Yes / No (if yes, record hours and reason)
Section D: Plant and Equipment
| Item | Quantity | Hours operated | Idle? (Y/N) | Reason for idle |
|---|---|---|---|---|
Plant standing time is a classic source of compensation event costs that teams forget to record. If a 45-tonne excavator sits idle for four hours because of a client instruction, that's roughly £400 in Defined Cost you can't claim without a diary entry.
Section E: Materials Delivered and Used
| Material | Quantity | Supplier | Delivery time | Condition on arrival |
|---|---|---|---|---|
Any rejected deliveries? Yes / No (if yes, describe reason and impact)
Section F: Work Completed
This is the most important section commercially. Describe what was done, where, and how it relates to the Accepted Programme.
| Work area / location | Activity description | Programme ref | Planned? (Y/N) | Completed? (Y/N) |
|---|---|---|---|---|
Does progress match the Accepted Programme? Yes / No
If behind programme, explain: _________________________________
Is an early warning required? Yes / No
Section G: Instructions, Variations, and Events
This is where most templates fail. They don't capture instructions at all, or they bury them in a general comments box where nobody finds them again.
| Time | From whom | Instruction / event description | Verbal or written? | Potential CE? | Action taken |
|---|---|---|---|---|---|
Any new compensation events identified today? Yes / No
Any early warnings to raise? Yes / No
Reference numbers: _______________
Section H: Visitors, Inspections, and Meetings
| Time | Name | Organisation | Purpose of visit | Outcome / comments |
|---|---|---|---|---|
Section I: Health, Safety, and Environmental
| Item | Details |
|---|---|
| Incidents / near misses | |
| Toolbox talks delivered | |
| Safety observations | |
| Environmental issues | |
| Permits to work active |
Section J: Photographs
| Photo ref | Time taken | Location | Description |
|---|---|---|---|
Minimum 5 photographs per shift. Aim for: one site-wide overview, one per active work area, one of any deliveries, one of any issues or instructions received.
Section K: Summary and Sign-Off
| Field | Entry |
|---|---|
| Summary of day | [2-3 sentences covering key progress and issues] |
| Key risks or concerns | |
| Actions for tomorrow | |
| Author signature | |
| Date/time signed | |
| Reviewed by |
How to Use This Template: Field-by-Field Guidance
Don't treat the template as a form to fill in at the end of the day. I've seen too many site engineers scribbling entries at 17:30 from memory, missing half the detail. Here's how to get it right.
Fill It In Throughout the Day
Carry the template (or better, an app) with you. Update it as things happen. The 09:15 entry about a client instruction is worth ten times more than a vague mention at 17:00 that "the PM came to site and asked us to change something."
Be Specific, Not Descriptive
| Bad entry | Good entry |
|---|---|
| "Worked on drainage" | "Installed 6nr 450mm dia. concrete pipes from MH-14 to MH-15, chainage 240-290, as per drawing DRG-C-401 Rev C" |
| "Rain stopped work" | "Heavy rain from 10:30. 22mm recorded by 14:00. Excavation in Area 3 suspended at 11:15 due to flooding. 4 operatives and 1 excavator stood down" |
| "PM visited" | "PM (J. Roberts) visited 14:30-15:45. Instructed change to retaining wall alignment at chainage 350-380. Verbal instruction, followed up by email ref CE-024. Potential compensation event under 60.1(1)" |
For more examples of well-written diary entries, see our dedicated guide.
Link Every Entry to a Programme Activity
Your Accepted Programme has activity references. Use them. When a commercial manager needs to demonstrate delay six months from now, they'll search by programme activity, not by "that thing we did near the river."
Flag Compensation Events in Real Time
Don't wait for the weekly commercial meeting to identify CEs. If an instruction changes the scope, write "Potential CE" in the diary entry that day. It makes the 8-week notification window under clause 61.3 much easier to manage.
Worked Example: A Completed Diary Entry
Project: M6 Junction 19 Improvement, NEC4 ECC Option C
Contract value: £28M
Date: Tuesday 15 April 2025
Author: Sarah Chen, Site Engineer
Shift: Day shift 07:00-18:00Weather:
- 07:00: Overcast, 8C, light breeze (Beaufort 3), dry
- 12:00: Heavy rain, 10C, moderate wind (Beaufort 5), 14mm recorded
- 17:00: Clearing, 9C, light breeze (Beaufort 3), total 24hr rainfall 19mm
Labour: 14 operatives (4 steel fixers, 3 concrete finishers, 2 banksmen, 3 general operatives, 2 site engineers). Full names on allocation sheet ref DAS-2025-04-15.
Plant: 2x 30T excavators (1 idle from 11:15 due to rain, 3.75hrs standing time). 1x concrete pump on standby from 12:00 (rain delay to pour).
Work completed:
- Rebar fixing to pile cap PC-07 completed (programme ref 4.2.3). On programme.
- Concrete pour to pile cap PC-06 delayed from 13:00 to 15:30 due to heavy rain. 18m3 placed before shift end. Remaining 12m3 rescheduled to 16 April.
Instructions received:
- 10:45: PM (D. Walsh) instructed relocation of temporary haul road from chainage 120 to chainage 180 to avoid clash with utility diversion. Verbal instruction, confirmed by email 11:20 (ref PM-INS-047). Potential CE under 60.1(1): change to Works Information.
Photographs: 8 taken. Refs PH-0415-001 to PH-0415-008. Include: rain conditions at 12:00, idle plant, haul road current alignment, pile cap PC-07 rebar completion.
Summary: Good progress on rebar programme despite weather disruption. Concrete pour delayed 2.5 hours. PM instruction to move haul road will require additional earthworks. Early warning to be raised re. haul road impact on programme activity 3.1.2.
Signed: S. Chen, 18:15, 15/04/2025
That's a diary entry you can build a compensation event from. Compare it to "concrete delayed, rain, PM visited" and you'll see why templates matter.
NEC4-Essential Template Fields
If you're working under NEC4, five fields in your site diary template aren't just nice-to-have. They're contractually critical.
| NEC4 requirement | Template field | Why |
|---|---|---|
| Compensation event identification (cl. 61.1) | Section G: Instructions and events | The Contractor must notify CEs. Your diary is where you first spot them |
| Early warning obligation (cl. 15.1) | Section F: Early warning flag | You must notify matters that could increase cost or delay Completion |
| Defined Cost records (cl. 52.2) | Sections C, D, E: Labour, plant, materials | These are the records you need to justify CE quotations |
| Programme updates (cl. 32.1) | Section F: Programme reference | Every activity must link to the Accepted Programme |
| Weather records (cl. 60.1(13)) | Section B: Weather at 3 intervals | Must compare against the weather measurement data in Contract Data |
Without these fields, your template is a generic notepad. With them, it's a commercial tool.
Common Mistakes with Site Diary Templates
1. Filling it in from memory at the end of the day
This is the most common mistake and the most damaging. By 17:30, you've forgotten the exact time of the PM's instruction, the specific rainfall at 11:00, and whether the idle plant was stood down at 11:15 or 11:45. Those details matter in a dispute.
2. Using one template for all contract types
An NEC4 diary needs different fields from a JCT or FIDIC diary. The weather recording requirements under clause 60.1(13) are specific to NEC4. The instruction-tracking format ties to clause 61.1 notification. If your template doesn't match your contract, you'll miss things.
3. Not linking entries to the Accepted Programme
"Worked on drainage" tells a commercial manager nothing. "Installed drainage run MH-14 to MH-15 per programme activity 5.3.1" lets them trace the entry directly to the programme, identify delay, and build a compensation event quotation. The difference is five extra words.
4. Treating photographs as optional
I've lost count of the projects where a dispute turned on photographic evidence. Five photographs per shift is the minimum. Date-stamp them. GPS-tag them if possible. A photograph of idle plant at 11:15 in the rain is better evidence than a paragraph describing it.
5. Storing completed templates in a shared drive nobody organises
Filling in the template is half the job. Filing it where someone can find it six months later is the other half. If your completed diaries live in a folder called "Site Stuff" on someone's laptop, they're as good as lost. Use a consistent naming convention: [Project]-[Date]-[Author].pdf.
For a full walkthrough of diary best practice, see our guide on how to write a site diary.
Printable vs Digital: Which Format Works Best?
| Factor | Paper / PDF template | Excel template | Digital app (e.g., Gather) |
|---|---|---|---|
| Speed of entry | Slow. Handwriting, then scanning | Moderate. Copy-paste from yesterday | Fast. Tap, dictate, photograph |
| Searchability | Zero. Try finding a handwritten entry from October | Basic. Ctrl+F works if you know which file | Full text search across all entries |
| Photo integration | Separate folder, hope they're labelled | Embedded but files become enormous | Automatic. Geotagged, timestamped |
| NEC4 CE flagging | Manual. Relies on the author spotting it | Manual. Maybe a dropdown column | Automatic. AI flags potential CEs |
| Cost | Free (print costs aside) | Free | Subscription |
| Commercial risk | High. Records get lost, handwriting is illegible, no backup | Medium. Files get corrupted, version control is messy | Low. Cloud-stored, audit trail, daily backups |
Paper templates work for small projects or as a backup. For anything over about £5M, the commercial risk of lost or incomplete records isn't worth the saving. I've seen a £2.1M compensation event fail because the site engineer's handwritten diaries were "not contemporaneous" in the adjudicator's view, when in reality they were just illegible.
Download Options
We've created a free downloadable version of this site diary template in PDF and Excel formats, pre-configured with all the NEC4 fields above.
Download the free site diary template (PDF and Excel, no email required for the basic version)
The downloadable version includes:
- Pre-formatted daily entry form (A4 printable)
- NEC4-specific fields highlighted in yellow
- Weather recording table with threshold comparison
- Instruction log with CE flagging column
- Weekly summary roll-up sheet (Excel only)
Want a version that fills itself in, flags compensation events automatically, and links to your Accepted Programme? That's what Gather does. The template above is a good starting point. Gather is what replaces it when you're ready.
Site Diary Template Checklist
Use this completion checklist before signing off each day's entry:
- Date, day, and shift times recorded
- Weather at three intervals with temperature and rainfall
- Every person on site listed by name and trade
- All plant recorded, including idle time and reasons
- Materials deliveries logged with supplier and condition
- Work described by location and programme activity reference
- Every instruction recorded with time, source, and CE flag
- Minimum 5 photographs taken, referenced, and described
- Early warning assessment completed (yes/no)
- Entry signed and timed by author
If you can tick all ten, your diary entry is audit-ready. Most teams consistently manage six or seven. The gap between seven and ten is where commercial value lives.
.webp)
