Site Diary vs Delay Record: What You Need to Prove a Claim

What is a construction site diary?

A construction site diary is a daily record of general site activity, conditions, labour, plant, visitors, deliveries, incidents, inspections, and progress.

A useful site diary may include:

• date and weather
• work areas active that day
• labour and plant on site
• subcontractors present
• deliveries
• inspections
• incidents or safety notes
• general progress notes
• instructions received
• delays or disruptions observed

Site diaries are valuable because they create a contemporaneous record. They help show what was happening on a specific date, who was on site, and what general conditions existed.

The limitation is that many site diaries are written as broad daily notes. They may say that work was delayed, but not explain the delay clearly enough for a commercial team to price, review, or rely on later.

What is a delay record?

A delay record is a specific record created to document a delay event and its impact on planned work.

A proper delay record should answer:

• what caused the delay?
• when did it start?
• when did it finish, or is it ongoing?
• where did it happen?
• which works were affected?
• which labour, plant, materials, or subcontractors were affected?
• was the programme impacted?
• what cost impact may have occurred?
• what evidence supports the event?
• was a notice, instruction, RFI, email, or dayworks docket created?

A delay record should be more structured than a site diary note. It should be written so someone who was not on site can understand the issue later.

Site diary vs delay record: the practical difference

A site diary and delay record may describe the same event, but they do different jobs.

Record type — Main purpose — What it usually proves — Main weakness

Site diary — Records general site activity for the day — What happened on site, who was present, general conditions — Often too broad to explain commercial impact

Delay record — Records a specific delay event and its impact — Cause, timing, affected works, resource impact, evidence — Weak if not created while the delay is happening

A site diary might say:

Excavation delayed due to access issue.

A stronger delay record would say:

Excavation at the northern trench was delayed from 9:30am to 1:30pm because access was blocked by incomplete service relocation works. One excavator, two dump trucks, one roller, and a four-person crew were affected. Photos were taken at 9:35am and 12:10pm. Email from site supervisor confirming access restriction attached.

The second record is much more commercially useful because it explains time, cause, location, resources, and evidence.

Why a site diary may not be enough for a claim

A site diary may not be enough for a claim because it often records the event without enough detail about delay impact, cost impact, or supporting evidence.

A claim-support record usually needs more than proof that something happened. It needs to explain how the event affected the works.

For example, if a site diary says “weather delay”, the commercial team may still need to know:

• what work was stopped?
• what area was affected?
• what time did the delay start and finish?
• which crew was stood down?
• what plant was idle?
• were photos taken?
• was a weather record kept?
• was a notice issued?
• did the delay affect the programme?

Without those details, the site diary may support the background story but not the full commercial position.

This is general information only and not legal advice. Contract requirements vary, so check the relevant contract before sending formal notices or claims.

What should be captured when a delay happens?

When a delay happens, capture the delay as a separate event, even if it is also mentioned in the site diary.

At minimum, record:

• project name
• date
• time the delay started
• time the delay finished, if known
• location on site
• delay cause
• source of the delay, if known
• affected activity or workfront
• labour affected
• plant affected
• materials or deliveries affected
• instruction, RFI, email, or notice reference
• photos, videos, or other evidence
• likely time impact
• likely cost impact, if known
• notes from the supervisor or foreman

Do not rely on a single vague note. A delay is easier to explain later when the record is specific and dated.

Example: site diary note vs delay record

Here is the difference in practice.

Weak site diary note — Strong delay record

“Crew delayed waiting for access.” — “Drainage crew delayed from 7:00am to 10:45am because access to the southern workfront was blocked by scaffold exclusion zone. Crew of five and one excavator stood idle. Photos attached. Access reopened after confirmation from site supervisor at 10:40am.”

“Rain affected works.” — “Concrete preparation works in Zone B stopped from 11:20am due to heavy rain and water pooling. Crew was redirected to housekeeping until 1:00pm. Photos and weather record attached.”

“Late drawings.” — “Stormwater installation could not proceed because revised drawing SW-104 had not been issued. RFI-038 remained open. Two-person crew and 8t excavator affected for full morning shift.”

The stronger version does not need to be beautifully written. It needs to be clear, specific, and supported.

Common mistakes with site diaries and delay records

The most common mistake is treating a site diary as a complete delay record.

Other mistakes include:

• recording the delay days later from memory
• writing vague notes like “held up” or “delayed”
• missing start and finish times
• not naming the affected workfront
• failing to record labour and plant impact
• not attaching photos or videos
• keeping evidence separate from the delay note
• failing to reference instructions, emails, RFIs, or notices
• mixing several delay events into one general note
• not updating the record when the delay continues into another day

A site diary can support a delay record. It should not be the only record when the delay may affect time, cost, or entitlement.

Site diary and delay record checklist

Use this checklist when a delay occurs:

• [ ] Add the general event to the site diary
• [ ] Create a separate delay record
• [ ] Record delay start time
• [ ] Record delay finish time, if known
• [ ] Identify the delay cause
• [ ] Identify the affected work area
• [ ] List affected labour
• [ ] List affected plant
• [ ] Attach photos or videos
• [ ] Attach instructions, emails, RFIs, or weather records
• [ ] Note likely programme impact
• [ ] Note likely cost impact
• [ ] Link the record to any delay notice, dayworks docket, or claim file

The best workflow is not site diary or delay record. It is both, with each one doing its own job.

How DelaySolve helps keep better delay records

DelaySolve helps subcontractors log delays, cost labour and plant impact, attach evidence, and keep a structured delay record across live projects.

The practical workflow is:

1. Record the delay while it is happening. 2. Capture the cause, time, location, and affected works. 3. Add labour and plant impact. 4. Attach photos, videos, instructions, or emails. 5. Keep the record ready for commercial review.

A site diary may show the background. DelaySolve helps create the structured delay record that explains the impact.

For related guidance, read Site diary and EOT notices for tier 1 civil subcontractors or visit the DelaySolve free tools hub.

FAQs

Is a site diary the same as a delay record?

No. A site diary records general site activity for the day. A delay record documents a specific delay event, including cause, timing, affected works, labour, plant, cost impact, and supporting evidence.

Can a site diary support a delay claim?

A site diary can support a delay claim, but it is usually stronger when combined with delay notices, photos, programme records, labour records, plant records, instructions, and other evidence.

What should a delay record include?

A delay record should include the date, time, location, cause, affected work, labour impact, plant impact, programme impact, cost impact, and supporting evidence.

Should every delay go in the site diary?

Yes, important delays should usually be recorded in the site diary. But if the delay may affect time, cost, dayworks, a variation, or a claim, it should also be recorded separately as a structured delay event.

Why are start and finish times important?

Start and finish times help show the duration of the delay. Without duration, it is harder to calculate labour standby, plant downtime, or programme impact.