Most people use "daily log" and "site diary" interchangeably. They're wrong. There's a difference, and it matters commercially. We'll cover that distinction in a moment.
What's the Difference Between a Construction Daily Log and a Site Diary?
Short answer: a construction daily log is one entry. A site diary is the collection of all entries across the life of a project.
Think of it this way. Your site diary is the book. The daily log is one page in that book. Every day produces a new log entry. String them together chronologically and you've got a site diary.
Why does this matter? Because when a Project Manager asks "show me your site diary for the period 14 March to 28 March," they're asking for 15 consecutive daily logs. If three of those days have no log entry, you've got three days with no contemporaneous record. Under NEC4, that's three days where you can't prove what happened, who was on site, or what instructions were given.
I've seen this exact scenario on a Network Rail GRIP 6 package worth around £28M. The Contractor had solid daily logs for four days out of every five. The fifth day, typically Fridays, had nothing. When a compensation event spanning a Friday needed evidencing, the Project Manager assessed it based on available records only. The Contractor lost roughly £65,000 in that single assessment because Friday's disruption simply didn't exist on paper.
For a deeper look at how daily logs, daily site reports, and foreman reports fit together, those guides break down each document type in detail.
What Goes in a Construction Daily Log
Every construction daily log should capture the same core fields, completed the same way, every single day. Consistency beats eloquence. A terse but complete log is worth ten times more than a beautifully written one with gaps.
Here's what belongs in every entry. For a comprehensive breakdown of each field, see our what to include in a site diary guide.
Date, Time, and Shift Information
Record the date, the day of the week, the shift type (day or night), and the actual start and finish times. Not the planned times. The actual times.
This sounds trivial until you're in a delay analysis six months later and need to prove whether Saturday 22 March was a planned working day or overtime. If the log doesn't say, you'll argue about it for weeks.
Weather Conditions
Record temperature (morning and afternoon), rainfall (duration and intensity, not just "rain"), wind conditions, and ground state. Under NEC4 clause 60.1(13), weather compensation events require comparison against 10-year averages at the nearest weather station. "Wet" isn't evidence. "Heavy rainfall, 14mm estimated over 3 hours, waterlogged formation level, earthworks suspended at 10:45" is evidence.
Labour On Site
Record headcount by trade, not just a total number. Note which subcontractor each gang belongs to, the hours each trade worked, and any standing time with the reason.
Labour records are the backbone of disruption claims. Under clause 63.1, assessment of compensation events is based on the effect on Defined Cost. Labour is typically 60 to 70 per cent of Defined Cost on a civils package. If you can't break it down by trade, you can't prove which trades were disrupted.
Your daily allocation sheet handles the detailed breakdown. The daily log captures the summary as a cross-check.
Plant and Equipment
List every piece of plant on site, whether it was working or standing, and what it was doing. Standing plant with a reason ("360 excavator idle 09:00 to 14:30, awaiting Client design information for retaining wall foundation") is a Defined Cost record waiting to happen.
Materials Delivered and Used
Record deliveries with quantities, any rejected materials and why, and what was actually consumed. Did the ready-mix arrive on time? Was any concrete wasted because of a late design change? This supports cost reconciliation and evidences waste caused by changed methods.
Work Completed and Progress
Describe what was done, where on site, and how it compares to the Accepted Programme. Be specific: "Poured 45m3 concrete to base slab zone 3, grid lines A-D/1-4" not "concrete works progressed."
Instructions Received
This is where daily logs pay for themselves commercially. Any instruction from the Project Manager, Supervisor, or Client representative could be a compensation event under clause 60.1(1). Record who gave the instruction, what it said, when it was given, and whether it was verbal or written.
I've watched entire CE claims fail because the instruction wasn't recorded on the day it was given. The Contractor notified the CE three weeks later but had no contemporaneous record of the instruction itself. The Project Manager simply denied giving it.
Delays and Disruptions
If anything stopped or slowed work, record it: what happened, which activities were affected, how long it lasted, and any knock-on effect on other work fronts. This is your contemporaneous delay record. Try doing a retrospective delay analysis without it. You can't. It's guesswork.
Health and Safety
Log safety observations, near misses, incidents, toolbox talks, and any CDM-related matters. Beyond the legal requirements, safety records demonstrate a well-managed site, which strengthens your credibility in any dispute.
Visitors
Who visited, when they arrived, who they met, and what was discussed. Particularly important when the Project Manager or Client's representative visits and gives verbal instructions.
Photographs
Photos with timestamps, locations, and descriptions of what they show. A photo without context is just a picture. A photo captioned "Standing water on formation level zone 4, preventing piling operations, 09:30 on 18 March 2025" is evidence.
Construction Daily Log Template
Here's a practical template structure you can adapt. This isn't a form to photocopy; it's a framework for what your daily log system should capture.
| Field | What to Record | Example |
|---|---|---|
| Project name and number | Contract reference | ABC Highways, NR/2024/0847 |
| Date and day | Full date with day of week | Monday 17 March 2025 |
| Shift and hours | Type, actual start/finish | Day shift, 07:00 to 17:30 |
| Weather (AM) | Temp, conditions, ground | 8°C, overcast, light drizzle, ground soft but workable |
| Weather (PM) | Temp, conditions, ground | 11°C, dry, moderate wind (SW), ground drying |
| Labour summary | Trade, number, hours | Steel fixers x6 (10.5hrs), labourers x4 (10.5hrs) |
| Plant on site | Equipment, status | CAT 320 excavator (working, drainage zone 2), 8T dumper (idle AM, fuel delivery delayed) |
| Materials delivered | Item, quantity, supplier | Ready-mix concrete, 3 loads (24m3), Hanson |
| Materials used | Item, quantity, location | 24m3 concrete placed, base slab zone 2 |
| Work completed | Activity, location, quantity | Excavated 120m of drainage trench, zone 2, to formation level |
| Instructions received | Who, what, when, format | PM issued email instruction 09:15 to relocate temporary compound. Verbal confirmation on site at 10:00 |
| Delays/disruptions | Event, cause, duration, impact | Drainage trench excavation suspended 13:00 to 15:30 (2.5hrs), uncharted BT duct found at 1.2m depth. Zone 2 drainage programme delayed. Notified PM verbally, formal CE notification to follow |
| H&S observations | Incidents, near misses, talks | Toolbox talk on excavation safety. Near miss: unsecured scaffold board zone 1, corrected immediately |
| Visitors | Name, organisation, time | J. Smith (NR Project Manager), 11:00 to 13:30 |
| Photographs | Reference, description, location | Photos 0847-0317-01 to 06: uncharted BT duct in drainage trench zone 2, depth 1.2m |
| Completed by | Name and role | A. Williams, Section Engineer |
Worked Example: A Daily Log That Saved £210,000
This one's anonymised but based on an actual project I was involved with.
Project: £35M highway improvement scheme, NEC4 Option C, West Midlands.
Date: Wednesday 18 June 2025.
What the daily log recorded:
The section engineer's log for 18 June noted: "PM's representative visited site at 10:15. During walkover of earthworks area 3, verbally instructed Contractor to re-profile embankment batters from 1:2 to 1:3 gradient due to updated geotechnical assessment. Instruction given by R. Jenkins (Client's site rep) to S. Patel (site agent). Confirmed this changes the Accepted Programme earthworks quantities by approximately 4,200m3 additional cut. Photos 0621-0618-01 to 03 show current batter profile for reference."
What happened next:
The Contractor notified a compensation event under clause 61.3 on 19 June, within 24 hours. The CE quotation referenced the daily log entry as contemporaneous evidence of the instruction. The Project Manager initially queried whether a formal instruction had been given. The daily log, with the named individuals, the time, the specific instruction, and the photographs, made the instruction undeniable.
The assessment: 4,200m3 additional earthworks at the tendered rates, plus 2 weeks additional programme time for the earthworks section. Total assessed value: £210,000.
Without the daily log: If the section engineer had written "PM rep visited site, discussed earthworks" or simply hadn't recorded the visit, the Contractor would have been relying on memory and email trails. The Client could have argued the instruction was a suggestion, not a formal change. I've seen that exact argument succeed on three separate projects.
Five Common Daily Log Mistakes
1. Writing the log days after the event
It's not a daily log if you write it on Friday afternoon covering Monday to Thursday. Contemporaneous means on the day. Courts and adjudicators treat retrospective records with significantly less weight than same-day entries. If your section engineers are batching their logs, they're creating a liability, not a record.
2. Recording what was planned instead of what happened
"Drainage works continued as programme" tells you nothing. What actually happened? How many metres were laid? Was it ahead or behind programme? Did anything go wrong? A daily log should capture reality, even when reality is boring.
3. Headcount without trade breakdown
"42 operatives on site" is almost useless for a disruption claim. "12 steel fixers, 8 shuttering joiners, 6 concrete finishers, 4 banksmen, 12 general labourers" is a record you can use. The trade breakdown links directly to Defined Cost categories and makes your CE quotations defensible.
4. Missing the instruction that triggers a compensation event
Someone on the Client's side tells your site agent to do something differently. Your site agent does it. Nobody writes it down. Three weeks later, you're trying to notify a compensation event but you can't prove when the instruction was given. Under clause 61.3, the 8-week time bar runs from the date the Contractor became aware. If you can't evidence awareness, you can't evidence timeliness.
5. No photographs, or photographs without context
A photo of a flooded excavation is worthless without a date, location, and description. A photo captioned "Zone 4, pile cap excavation flooded due to overnight rainfall, 07:15 on 22 March 2025, work suspended pending pump-out" is a piece of evidence. Always caption your photos in the daily log.
Construction Daily Log vs Daily Site Report vs Foreman Report
These three documents overlap but serve different purposes. Here's how they fit together.
| Document | Who Writes It | Primary Purpose | Level of Detail | Frequency |
|---|---|---|---|---|
| Construction daily log | Section engineer or site agent | Comprehensive site record covering all activities, weather, labour, plant, instructions, delays | High: covers everything on site | Daily, end of shift |
| Daily site report | Project manager or site manager | Summary for management and Client reporting, often formatted for external distribution | Medium: highlights and exceptions | Daily or as required |
| Foreman report | Trade foreman or gang leader | Activity-level record for a specific work front or trade | Very high for that trade, but narrow scope | Daily, per gang or work front |
The daily log is the backbone. The daily site report summarises it for management. The foreman report feeds detail into it from each work front. On a well-run site, the section engineer compiles the daily log using foreman reports as source material and adds instructions, visitors, weather, and safety observations.
Don't rely on just one of these documents. Each serves a different audience and a different commercial purpose. Together, they create a record that's very hard to challenge.
Why Daily Logs Matter Under NEC4
Under NEC4, the Contractor has specific obligations to keep records (clause 52.2 in some options), and the consequences of poor records are severe.
Three commercial reasons your daily logs need to be bulletproof:
1. The 8-week time bar (clause 61.3). The Contractor must notify compensation events within 8 weeks of becoming aware. Your daily log is the evidence of when you became aware. If you didn't record an instruction on 5 March, but you notify the CE on 28 April, the Project Manager can argue you were aware before 5 March and you're time-barred.
2. Compensation event assessment (clause 63). Assessment is based on the effect on Defined Cost and the impact on the programme. Both require contemporaneous records. No daily log means no evidence of actual Defined Cost. The Project Manager makes their own assessment, and I can promise you it won't be generous.
3. Disallowed cost (clause 11.2(26) in Options C and D). Cost that the Project Manager decides is not justified by the Contractor's records is Disallowed Cost. It comes straight off your pain/gain share. On a £50M Option C contract with a 50/50 share ratio, £200,000 of disallowed cost because of poor daily logs costs you £100,000 off your share. That's real money lost because someone didn't spend 20 minutes at the end of each day filling in a log.
Who Should Complete the Construction Daily Log
The short answer: someone who was on site all day, has enough seniority to understand what they're recording, and will actually do it every day.
On most UK construction sites, that's the section engineer or site agent. On smaller projects, it might be the site manager. On larger programmes with multiple work fronts, each section engineer completes a log for their area, and the project team consolidates them.
Don't give this job to the most junior person on site. I've seen projects hand daily log responsibility to a trainee quantity surveyor who'd never run a project. They recorded what they could see but missed the commercial significance of half of it. A foreman saying "we couldn't start the pour until 11 because the pump was on the wrong side of the exclusion zone" is just a delay to them. To an experienced engineer, it's a potential CE if the exclusion zone was a Client constraint not in the original Works Information.
The person completing the log doesn't need to write like Shakespeare. They need to capture facts, be specific, and do it every single day without fail. That last bit is the hard part.
Digital vs Paper Daily Logs
Paper daily logs still exist on UK construction sites. I won't pretend they don't. But they're a liability.
| Paper Log | Digital Log | |
|---|---|---|
| Completion time | 20 to 30 minutes per entry | 10 to 15 minutes with templates and dropdowns |
| Photo integration | Separate, needs cross-referencing | Embedded with automatic timestamps and geotags |
| Searchability | Flip through a lever arch file | Keyword search across months of records |
| Legibility | Depends on handwriting (good luck reading a site agent's notes in January) | Always readable |
| Backup | One copy, vulnerable to loss, damage, or "disappearing" before adjudication | Cloud-stored, time-stamped, tamper-evident |
| CE notification speed | Manual review required to spot potential CEs | AI-powered tools can flag potential compensation events automatically |
| Audit trail | None unless you photocopy everything | Full edit history with timestamps |
The direction of travel is obvious. But here's what really matters commercially: a digital log with a full audit trail is significantly harder to challenge in adjudication than a handwritten notebook where pages could theoretically be added or removed. I've had opposing counsel in an adjudication suggest exactly that about paper records. You don't want to be in that position.
.webp)
