What Evidence Do You Need for a Construction Delay Claim?

What is construction delay claim evidence?

Construction delay claim evidence is the set of site, commercial, programme, and communication records used to explain and support a delay event.

It should help answer:

What caused the delay?
When did it start?
When did it finish?
Which works were affected?
Who or what caused the delay, if known?
Was notice given?
Was the programme affected?
Was labour affected?
Was plant affected?
Were materials, deliveries, or subcontractors affected?
What cost impact occurred?
What evidence was captured at the time?

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

1. Delay notice records

Delay notice records help show that the delay was identified and communicated.

A useful delay notice record should include:

notice date
delay event date
project name
recipient
delay cause
affected works
likely time impact
likely cost impact, if known
evidence available at the time
reference number or email trail

The notice does not need to prove the full claim by itself. Its job is to create a clear record that the delay was notified in line with the project or contract process.

Need to create a structured notice quickly? Use the free Construction Delay Notice Generator.

2. Site diary and daily records

Site diaries and daily records help show what was happening on site at the time of the delay.

Useful daily records may include:

weather
labour on site
plant on site
activities planned
activities completed
work areas affected
access restrictions
instructions received
delays observed
deliveries
inspections
incidents or constraints

A site diary is helpful background evidence, but it is often not enough by itself. The delay should also be recorded as a specific event with cause, time, affected works, labour, plant, and evidence.

For related guidance, read Site Diary vs Delay Record: What You Need to Prove a Claim.

3. Photos and videos

Photos and videos help show physical site conditions, access problems, weather impacts, incomplete preceding works, idle plant, affected work areas, and completed or changed work.

Good photo evidence should include:

date
time
location
short description
affected activity
reason the image matters

Weak photo evidence is a folder of images with no explanation. Strong photo evidence is attached to a delay record that explains what each image shows.

For example:

Photo taken at 9:35am showing blocked access to northern trench. Excavation crew and 20t excavator unable to proceed until access reopened at 1:30pm.

The image supports the record because it is connected to time, location, cause, and impact.

4. Instructions, RFIs, emails, and correspondence

Instructions and correspondence help show what was communicated, requested, changed, delayed, approved, or disputed.

Keep:

site instructions
superintendent instructions
client emails
head contractor directions
RFI submissions
RFI responses
drawing issue dates
design clarifications
meeting minutes
programme direction emails
stand-down instructions
access restriction notices

These records are useful because they help establish the timeline. They show when information was requested, when it was received, when work was stopped, and when decisions were made.

Where possible, link each communication to the affected activity. An email is stronger when the delay record explains how it affected the works.

5. Programme impact records

Programme impact records help show how the delay affected planned work, sequencing, milestones, or completion.

Useful programme evidence may include:

current accepted programme
lookahead programme
short-term programme
programme updates
marked-up programme extracts
activity IDs
affected work sequence
critical path notes, if relevant
resequencing records
mitigation notes
recovery programme notes

The programme record should explain the link between the delay event and the affected activity.

A weak programme note says:

Delay affected programme.

A stronger note says:

Late RFI response delayed stormwater installation activity SW-240 from 18 June to 20 June. This pushed back backfill and pavement preparation in Zone C. Updated two-week lookahead attached.

Programme impact is often the part that gets missed. Site teams do not need to perform a full delay analysis on the spot, but they should record which planned activity was affected.

6. Labour impact records

Labour impact records show which workers were affected, how long they were affected, and whether they were stood down, redirected, or made less productive.

Record:

worker type or role
number of workers affected
names or crew reference, if required
planned activity
delay cause
start and finish time
standby duration
redirected work, if any
hourly or daily rate, if costed
timesheets or allocation records
supervisor notes

Need to estimate labour standby cost? Use the free Labour Standby Cost Calculator.

For related guidance, read Labour Standby Cost: How to Calculate Labour Sitting Idle on Site.

7. Plant impact records

Plant impact records show which equipment was delayed, idle, underused, or required because of the delay.

Record:

plant item
quantity
plant ID or supplier
planned activity
delay cause
start and finish time
idle duration
rate
rate basis
owned, hired, wet hire, or dry hire status
hire docket, invoice, or internal rate sheet
operator record, if relevant

Need to estimate idle plant cost? Use the free Plant Downtime Cost Calculator.

For related guidance, read Plant Downtime Cost: How to Calculate Idle Plant During a Delay.

8. Cost and dayworks records

Cost records help show the financial impact of the delay.

Depending on the delay, useful cost evidence may include:

labour standby calculations
plant downtime calculations
dayworks dockets
material cost records
supplier invoices
subcontractor charges
remobilisation costs
supervision time
delivery costs
disposal records
hire extension costs
evidence/admin time, where relevant and supportable

Dayworks records are useful when labour, plant, and materials need to be recorded on a time-and-material basis.

Need to create a dayworks record? Use the free Dayworks Docket Generator.

9. Weather, access, and site condition evidence

Weather, access, and site condition records help support delays caused by physical conditions on site.

Useful evidence can include:

weather reports
site photos
videos
access maps
exclusion zone records
traffic management records
flood or water pooling photos
safety stand-down notes
inspection records
geotechnical or ground condition records

The evidence should show why the affected work could not proceed. A weather report by itself may not be enough if it does not connect to the actual work area and activity.

For weather-specific guidance, read Construction Weather Delay Letter: What to Include and What Evidence to Keep.

Example: evidence chain for a blocked access delay

A subcontractor’s drainage crew is unable to start excavation because access to the workfront is blocked.

A strong evidence chain may include:

Evidence type: Example

Delay notice: Notice sent to head contractor on the day of the delay

Site diary: Daily note showing crew and plant were on site

Photos: Images showing blocked access at 7:30am and 10:30am

Correspondence: Email confirming access restriction

Labour record: Five-person crew on standby for 3.5 hours

Plant record: 8t excavator idle for 3.5 hours

Programme record: Two-week lookahead showing drainage activity planned that day

Cost record: Labour standby and plant downtime calculation

No single record does everything. Together, they explain what happened, why it mattered, and what impact it had.

Common mistakes with construction delay claim evidence

Common mistakes include:

relying only on a site diary
failing to send or save delay notices
recording delays too late
using vague wording
missing start and finish times
not identifying affected works
not connecting photos to delay records
failing to record labour standby
failing to record plant downtime
missing programme impact
not saving emails, RFIs, or instructions
leaving cost evidence disconnected from the delay event

A delay claim is weaker when the evidence is scattered, vague, or created after the fact.

Construction delay claim evidence checklist

Before relying on a delay record, check whether you have:

[ ] Delay notice record
[ ] Site diary or daily record
[ ] Clear delay cause
[ ] Start and finish time
[ ] Affected works
[ ] Location on site
[ ] Photos or videos
[ ] Emails, RFIs, instructions, or meeting notes
[ ] Programme or lookahead evidence
[ ] Labour impact record
[ ] Plant impact record
[ ] Material or delivery impact record, if relevant
[ ] Cost calculation
[ ] Dayworks docket, if relevant
[ ] Weather or access evidence, if relevant
[ ] Notes explaining the event in plain language

Use the free EOT Claim Readiness Checker

Need to check whether your delay record is ready for an EOT claim? Use the free EOT Claim Readiness Checker.

DelaySolve’s EOT Claim Readiness Checker helps identify gaps in notice timing, evidence, programme impact, and delay records before you rely on them to support an extension of time claim.

How DelaySolve helps with construction delay evidence

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. Log the delay on site. 2. Record the cause, time, location, and affected works. 3. Add labour and plant impact. 4. Attach photos, videos, emails, RFIs, or instructions. 5. Keep cost and evidence connected to the same delay event. 6. Review the record later for notices, EOTs, dayworks, variations, or claim discussions.

The value is not just capturing more information. It is keeping the right information connected.

FAQs

What evidence is needed for a construction delay claim?

Useful evidence includes delay notices, site diary records, photos, videos, emails, RFIs, instructions, programme records, labour records, plant records, cost records, dayworks dockets, and weather or access evidence where relevant.

Is a site diary enough evidence for a delay claim?

A site diary can support a delay claim, but it is usually not enough by itself. A stronger record also includes delay notices, photos, programme impact, labour and plant impact, correspondence, and cost evidence.

Why are photos not enough by themselves?

Photos are stronger when connected to a dated delay record explaining what the image shows, where it was taken, what work was affected, and why the delay occurred.

What programme evidence should be kept?

Keep accepted programmes, short-term lookaheads, programme updates, marked-up extracts, activity references, resequencing notes, and records showing which planned activity was affected.

Should labour and plant be recorded separately?

Yes. Labour standby and plant downtime are different impacts. Record them separately, then link both to the same delay event.

When should delay evidence be captured?

Delay evidence should be captured while the delay is happening or as soon as possible after it occurs. Records created at the time are usually more useful than reconstructed notes created weeks later.