How to Write a Construction Site Diary: Step-by-Step Guide

Here's the frustrating part: most site teams already know this. They've got templates, apps, even training packs. And yet the diaries still come out vague, late, and commercially useless. I've reviewed thousands of them. The problem is almost never the template. It's the writing.

This guide walks you through how to maintain a site diary that actually holds up under scrutiny, step by step. Not what to include (that's covered in our what to include in a site diary guide), but how to write each entry so it's clear, defensible, and worth the 20 minutes it takes.

Why the Way You Write Your Diary Matters More Than the Template

I've reviewed thousands of site diary entries across dozens of NEC4 contracts. The pattern is always the same. Teams use a perfectly good template, tick every box, and still produce records that are commercially useless.

Why? Because there's a gap between recording information and writing useful records. "Concrete pour, Bay 3" tells you something happened. "Poured 45m3 C40/50 to Bay 3, deck slab level 2, started 07:30, completed 14:15, 2-hour delay waiting for pump (supplier issue, notified PM verbally at 09:00)" tells you enough to defend a compensation event two years later.

Under NEC4, poorly written diary entries create three specific risks:

1. Time-barred compensation events. Clause 61.3 gives the Contractor 8 weeks from the date they became aware of an event to notify the Project Manager. If your diary doesn't record when you first became aware, you can't prove you notified within the time bar. I've seen a £180,000 CE rejected because the diary entry said "delay to steelwork" with no date of awareness.
2. Disallowed costs. Under NEC4 clause 11.2(26), costs can be disallowed if records don't support them. Vague diary entries are the fastest way to get legitimate costs thrown out during assessment.
3. Weak final account positions. On a £35M highways package I worked on, the commercial team had 14 months of daily diaries. Barely any of them mentioned weather conditions, plant standing time, or subcontractor attendance numbers. The final account negotiation took 9 months longer than it should have because every disputed item required the team to reconstruct events from memory.

The solution isn't a better template. It's better writing. And it takes about 20 minutes a day.

Step 1: Write at the End of Every Shift, Not the Next Morning

This sounds obvious. Nobody does it.

On a £22M water treatment project in Yorkshire, the site team had a policy of completing diaries "by 10am the following morning." Within three weeks, entries had drifted to lunchtime. By month two, Friday's entry was being written on Monday. By month four, the commercial manager was writing weekly summaries from memory and calling them daily records.

The fix is simple: your diary entry is the last task of every shift. Not the first task of tomorrow. Not something you catch up on when it's quiet. The last thing you do before you leave site.

Here's why this matters commercially. Memory degrades fast. Research on eyewitness testimony shows that recall accuracy drops by roughly 30% after 24 hours. On a busy construction site with dozens of concurrent activities, that 30% is exactly where your compensation events live. The detail you forget overnight is the detail that proves your claim.

Practical tip: Set a daily alarm for 30 minutes before shift end. That's your diary time. Protect it like you'd protect a meeting with the client.

Step 2: Start with the Context, Not the Activity

Most diary entries jump straight to what happened. That's backwards. Start with the conditions that shaped what happened.

Weak opening:

Continued drainage works in Zone B.

Strong opening:

Weather: Heavy rain from 06:00 to 10:30, 18mm recorded at site gauge. Ground conditions: standing water across Zone B access track, plant unable to reach excavation face until 11:00. Wind: 25mph gusting to 35mph, tower crane stood down 08:00-12:00 per crane operator's decision.

The strong version takes 90 seconds longer to write. It saves you hours during a weather-related compensation event assessment because you've already recorded the evidence.

Context means three things, in this order:

1. Weather. Temperature, rainfall (measured, not guessed), wind speed, visibility. If you don't have a site weather station, get one. They cost under £200 and they remove arguments about whether it actually rained.
2. Site conditions. What state was the working area in when the shift started? Was access restricted? Were there standing instructions affecting work?
3. Resources available. How many people from each trade were on site? Which plant items were operational? What materials were delivered?

Record the context before you record the work. Every single time. Skip this step and your whole entry loses its commercial backbone.

Step 3: Describe Activities with Enough Detail to Reconstruct the Day

Here's my test for whether a diary entry has enough detail. Could someone who wasn't on site that day read your entry and draw a rough sketch of what happened, where, and in what sequence? If not, you haven't written enough.

That doesn't mean writing an essay. It means being specific.

The "just right" column follows a pattern: what (specific activity), where (location reference), how much (quantity), when (time), and outcome (completed, partially complete, or blocked).

Use the same structure for every activity and your entries become scannable. A commercial manager reviewing six months of diaries can find what they need in minutes rather than hours.

Step 4: Record What Didn't Happen and Why

This is the step that separates good diary-keepers from excellent ones. Most people record what they did. Few record what they couldn't do.

On every project I've worked on, the most commercially valuable diary entries are the ones that say "X was planned but couldn't proceed because Y." These entries are the raw material for early warnings, compensation event notifications, and delay analysis.

Examples of what to record:

• "Planned to start rebar fix to pile caps PC-07 to PC-12. Unable to proceed, design information for reinforcement detailing not received (RFI #0034, submitted 12 Feb, still outstanding at shift end)."
• "Subcontractor ABC Electrical did not attend site. 4 operatives expected per programme. No advance notice given. Phoned their contracts manager at 08:30, no answer."
• "Tower crane stood down 09:15 to 14:00 due to wind speed exceeding 38mph. 3 concrete pours postponed (Bays 7, 8, 9). Pump on standby, demurrage charge applies."

Each of these entries documents a disruption with enough detail to support a notification. The third one alone could be worth tens of thousands of pounds in a compensation event for adverse weather under clause 60.1(13), provided the weather data meets the threshold compared against the 10-year Met Office averages.

The rule: If something was programmed to happen today and it didn't, your diary must say what it was, why it didn't happen, and what the knock-on effect is.

Step 5: Capture Instructions, Decisions, and Conversations

Verbal instructions happen on every construction site, every day. How many get written down? Almost none.

Under NEC4, the Project Manager's instructions can create compensation events. But if the only record of that instruction is your memory, you're relying on the PM agreeing with your recollection months later. They won't.

When you receive a verbal instruction, direction, or decision on site, record it like this:

14:20 - Instruction from [Name], [Role]: "Stop excavation in Zone D pending utility survey results." Confirmed this constitutes a change to the Works Information. PM agreed to issue formal instruction by end of day. [Your name] present, also witnessed by [Name], Site Supervisor.

Three things matter here:

1. Who gave the instruction (name and role, not just "the PM said")
2. What was said (as close to verbatim as you can manage)
3. Who witnessed it (always try to have a witness present for significant instructions)

Follow up verbal instructions with a confirmatory email or CEN the same day. Your diary entry is the backup evidence, not the primary notification. But when the formal trail goes quiet, and it will, your diary is the only record that proves the instruction happened.

Step 6: Use Photographs as Evidence, Not Decoration

Photos in a site diary aren't there to make the entry look professional. They're evidence. Treat them accordingly.

Every photograph needs three things:

1. A written description in the diary entry explaining what the photo shows and why it matters
2. A location reference tied to the drawing or grid reference
3. A timestamp (use your phone's automatic timestamp, don't rely on manual dating)

Bad photo practice: 47 photos of "general progress" with no descriptions, taken from the same spot every day.

Good photo practice: 6 targeted photos showing specific conditions, each with a diary note explaining context. "Photo 1: Standing water at grid intersection G7/4, measured depth 150mm at 08:00. Access to pile cap PC-19 prevented. Photo taken facing north."

On one project, a single properly described photograph of water ingress through a temporary works seal saved £140,000 in a dispute about whose responsibility the damage was. The photo had a diary entry linking it to the specific failure, the time it was discovered, and the instruction given to make it safe. Without the diary context, it would have been just another photo in a folder of thousands.

Step 7: Close Out with a Forward Look

End every diary entry with two things:

1. Status summary. Where does the day's work leave you relative to the programme? Are you ahead, on track, or behind? Be honest, not optimistic.
2. Tomorrow's planned activities. What's programmed for the next shift? This creates continuity between entries and makes it immediately obvious when planned work gets disrupted.

Example close-out:

End-of-day status: Drainage works Zone B now 2 days behind programme due to weather delays (cumulative). Structural steel erection on programme. Concrete pours for Level 3 deck rescheduled from Wednesday to Friday pending crane availability.

Planned for tomorrow (15 March 2025): Resume drainage trench excavation Zone B (weather permitting). Continue rebar fix to transfer beams TB-04 to TB-06. Concrete pour Bay 10 (booked 08:00, Hanson, 32m3 C40/50). Anticipated delivery of precast stairs units 3 and 4 (confirm with logistics by 16:00 today).

This forward look does something subtle but powerful. It creates a chain of evidence. If tomorrow's diary says "precast stairs not delivered, supplier delayed," you can trace back to today's entry showing the delivery was expected. That chain is exactly what you need for a disruption claim under NEC4.

Worked Example: A Complete Diary Entry

Here's what a properly written site diary entry looks like for a real working day on a £28M residential development under NEC4 Option A.

Date: Tuesday 18 March 2025
Project: Riverside Quarter Phase 2, Manchester
Author: J. Thompson, Senior Site Engineer
Shift: 07:00 to 17:30
Weather: Overcast, dry. Temp 8C at 07:00, rising to 12C by 14:00. Wind: 10-15mph SW. No precipitation.

Resources on site:

• Main contractor: 14 operatives (4 steel fixers, 3 joiners, 2 banksmen, 2 labourers, 1 site engineer, 1 site manager, 1 SHEQ advisor)
• ABC Scaffolding: 6 operatives (erecting scaffold to Block C south elevation)
• DEF M&E: 3 electricians (first fix Level 2 Block A)
• Tower crane TC-01: operational from 07:30
• Excavator (20T): standing, no work available (drainage design outstanding)

Activities completed:

1. Rebar fix to transfer beam TB-04, Block B. Started 07:30, completed 15:00. Ready for inspection. Requested checking engineer attendance for Wednesday AM (emailed WSP at 15:15, ref TB04-INSP).
2. Formwork to columns C14-C16, Block A ground floor. Completed and ready for pour.
3. Scaffold erection Block C south elevation: reached Level 3 (of 5). On programme.
4. First fix electrical Block A Level 2: 4 of 12 apartments completed. DEF report they're 1 day behind due to late containment delivery last week.

Work not completed / disruptions:

• 20T excavator standing all day. Drainage design for Phase 2 external works not received. RFI #0089 submitted 28 Feb, now 18 days outstanding. This is the third consecutive week of standing time. Excavator daily rate: £450. Cumulative standing cost: £6,750 (15 days). Potential CE: client design information not provided in accordance with the Accepted Programme (clause 60.1(3)). Verbal discussion with PM (S. Adams) at site meeting 10:00. PM acknowledged delay but has not issued instruction. CEN to be submitted today.

Instructions and decisions:

• 10:00, weekly site meeting. PM (S. Adams) instructed additional fire stopping survey to Block A Levels 1-2 before fit-out continues. Not in the Works Information. Confirmed this verbally as a change. PM to issue formal instruction. Noted in meeting minutes (ref WM-025).
• 14:30, PM requested we accelerate scaffold to Block C to allow cladding contractor access by 28 March (2 days earlier than programmed). Advised PM this would require weekend working and additional scaffolders. Awaiting formal instruction and confirmation of cost recovery.

Photographs: 4 photos taken, uploaded to project folder /2025-03-18/.

• Photo 1: TB-04 rebar complete, pre-inspection (facing east)
• Photo 2: 20T excavator standing, Zone D (drainage area). Shows no works in progress
• Photo 3-4: Scaffold progress Block C south elevation, Level 3

End-of-day status: Block A structural on programme. Block B rebar 1 day ahead. Block C scaffold on programme. External drainage 3 weeks behind due to outstanding design (tracked via RFI #0089). Standing plant costs escalating.

Planned for tomorrow (19 March 2025): Checking engineer inspection TB-04 (AM, subject to confirmation). Concrete pour columns C14-C16 (PM, 8m3 C32/20, booked with Hanson). Continue scaffold Block C. Chase RFI #0089 with design team.

That entry took about 20 minutes to write. It captures three potential compensation events, records a PM instruction that changes the scope, documents standing plant costs with daily rates, and creates a forward-looking chain for tomorrow's entry.

Twenty minutes. That's the cost. The value, if even one of those CEs proceeds, is measured in tens of thousands of pounds.

Common Mistakes That Undermine Your Diary

1. Writing opinions instead of facts

"The subcontractor's work was poor quality" is an opinion. "Subcontractor XYZ installed 12 linear metres of drainage pipe at incorrect falls. Measured gradient: 1:120. Specified gradient: 1:80. Defect raised, ref DEF-0045" is a fact. Opinions get challenged. Facts get accepted.

2. Copying and pasting yesterday's entry

Stop doing this. I've seen it more times than I can count. Monday's entry gets copied to Tuesday with minor tweaks. By Friday, the diary reads like a template rather than a record. The problem? When entries look identical, adjudicators and contract administrators treat them as unreliable. They assume you weren't really recording what happened.

3. Forgetting to record who was on site

Labour records are the foundation of cost-based claims under NEC4 Options C, D, and E. If your diary doesn't record how many people from each trade were on site each day, you can't substantiate Defined Cost when it matters. On a £40M rail electrification package, a contractor lost £320,000 in a CE assessment because their diaries recorded activities but never labour numbers. The PM assessed the CE at their own rates, which were 40% lower.

4. Not recording weather when nothing went wrong

"Weather fine, no impact" still needs recording. Why? Because when you do claim for a weather event under clause 60.1(13), you need to demonstrate the weather on the affected day was exceptional compared to the norm. If you've only recorded weather on bad days, you've got no baseline for comparison, and the PM will notice.

5. Waiting until the end of the week

This one makes me genuinely angry. A Friday catch-up session produces entries that read like summaries, not records. They lack times, quantities, and the small details that make diary entries credible. If you can't write daily, you shouldn't be the person responsible for the diary. Hand it to someone who will.

Quick Reference: The 7-Step Diary Writing Process

Site Diary Writing Checklist

Use this as a daily prompt until the process becomes automatic. For a downloadable version, see our site diary template. For a full end-of-project review, use the completion checklist.