How to Write a Construction Daily Log (Free Template & Best Practices)

A construction daily log is the single most useful record on a job site, and the one most often done badly. Done well, it protects your programme, your costs and your position in a dispute. Done as an afterthought, it's a pile of scrawled notes nobody can search when it matters.

Here's what a daily log needs to cover, why each part earns its place, and a structure you can start using on your very next shift.

Why the daily log matters more than it gets credit for

Most site teams treat the daily log as paperwork. In practice, it's the only contemporaneous record of what actually happened on site — and contemporaneous records carry far more weight than a reconstruction written weeks later from memory. When a delay claim, variation dispute or defects argument lands on your desk, the daily log is usually the first document everyone reaches for.

What to record every day

1. Weather and site conditions

Temperature, rainfall, wind, and anything that affected workability. Weather is one of the most common grounds for an extension of time claim, so this entry alone can be worth thousands down the line.

2. Labour and plant on site

Headcount by trade, subcontractor crews present, and major plant and equipment in use or idle. This builds your productivity record and supports any claims around resource-related delay.

3. Deliveries and materials

What arrived, what didn't, and anything short-shipped or damaged on arrival. Materials delays are easy to forget by Friday if you don't log them the day they happen.

4. Visitors and inspections

Client reps, consultants, inspectors, and anyone else on site who isn't part of your crew — with the reason for the visit. This matters more than most site managers expect when a dispute turns on who knew what, and when.

5. Delays and disruptions

The specific activity affected, the cause, and your estimate of the time impact. Vague entries like "lost time due to weather" are far weaker than "concrete pour to Grid C-D postponed 4 hours, rainfall from 7–11am."

6. Instructions and RFIs

Any verbal or written instruction received on site, and any request for information raised, with who it went to and when. Verbal instructions are exactly the kind of thing that gets disputed later if there's no record.

7. Safety incidents and near-misses

Even minor ones. A near-miss log that's actually kept up to date is one of the better leading indicators a site can have.

A simple daily log structure

1. Header: Project name, date, day number, logged by.
2. Weather: Conditions, temperature, any workability impact.
3. Labour & plant: Headcount by trade, equipment on site.
4. Progress: What was completed against the programme.
5. Deliveries: Materials received, outstanding, or rejected.
6. Visitors: Who attended and why.
7. Delays: Activity, cause, estimated time impact.
8. Instructions & RFIs: What was issued or requested, and to whom.
9. Safety: Incidents, near-misses, toolbox talks held.
10. Photos: Dated and tied to the relevant entry above.

The problem with paper and spreadsheets

Paper diaries get left in the site office, filled in from memory two days later, and are nearly impossible to search when a claim surfaces six months on. Spreadsheets are searchable but disconnected — nobody links a delay entry back to the actual activity it affects, so the programme never reflects what really happened on site.

The most useful version of a daily log is one that's quick enough to fill in from the field in real time, and structured enough that a delay entry automatically shows up against the affected activity on your schedule — rather than living in a separate document nobody revisits.