Quick summary: the five delay records to keep
These five construction delay records work best when they are connected to the same delay event.
Summary table (shown as a list because the blog body does not support table blocks yet):
- Delay notice : What it proves: the delay was identified and communicated. Capture: cause, date, location, affected works, likely impact, supporting evidence.
- Daily delay record : What it proves: what happened on site each day. Capture: start and finish time, affected activity, daily notes, photos, instructions.
- Labour standby record : What it proves: which workers were held up. Capture: labour roles, quantity, duration, reason delayed, rate if relevant.
- Plant downtime record : What it proves: which equipment was idle. Capture: plant item, downtime duration, rate, operator impact, reason delayed.
- Dayworks or cost record : What it proves: the commercial impact of the delay. Capture: labour, plant, materials, notes, evidence, sign-off or review status.
A site diary can support these records, but it should not be treated as a complete delay record by itself. A useful delay record explains the cause, impact, evidence, and cost connection in a way someone else can understand later.
Why construction delay records matter
Construction delay records matter because delays are much harder to prove after the fact.
A site team may remember that access was blocked, plant was left idle, or a crew was stood down. But weeks later, that memory is not enough. A useful record needs dates, times, locations, affected works, affected labour, affected plant, instructions, photos, videos, notes, and any cost impact.
For subcontractors, the commercial issue is simple: if the delay is not recorded properly, it becomes harder to explain what happened and harder to support the cost later.
A good delay record should answer five questions:
- What caused the delay?
- When did it start and finish?
- Which works were affected?
- Which labour, plant, or materials were impacted?
- What evidence supports the record?
The following five records give subcontractors a practical structure.
1. Delay notice
A delay notice records that a delay event has occurred and that it may affect time, cost, programme, or progress.
The exact notice requirements depend on the contract, but the practical record should be clear, dated, and specific. A vague message saying “we were delayed on site” is weak. A stronger notice explains the cause, location, affected work, timing, and available evidence.
This record proves that the delay was identified and communicated at the time, rather than reconstructed later.
A delay notice should usually include:
- project name
- date of notice
- date and time the delay started
- location on site
- cause of delay
- affected works
- whether labour or plant was affected
- likely time or cost impact, if known
- evidence available at the time
- reference to any instruction, access issue, weather event, delivery issue, or design issue
Example only: use this as a drafting guide, not legal advice. Check your contract requirements before sending formal notices or claims.
We notify you that works were delayed on [date] at [location] due to [cause of delay]. The affected works include [affected works]. Labour and plant were impacted from [start time] to [finish time / ongoing]. Supporting records include [photos/videos/site instruction/emails/dockets]. Further details will be provided as the impact becomes clearer.
The delay notice does not need to contain every final cost or claim detail immediately. Its job is to create a clear record that the delay was identified and communicated.
For a deeper breakdown, read: Construction Delay Notice Template: What to Include Before You Send One.
Relevant supporting asset: Construction Delay Notice Generator.
2. Daily delay record
A daily delay record captures what actually happened on site while the delay was active.
This is different from a general site diary. A site diary might say what work happened across the day. A delay record should focus specifically on the delay event: what was stopped, what was slowed, who was affected, and what evidence was collected.
This record proves the day-by-day site impact of the delay.
A daily delay record should include:
- delay title or reference
- project and location
- date
- start and finish time, or “ongoing”
- delay cause
- affected activity
- workers affected
- plant affected
- materials affected
- instructions received
- photos, videos, or documents attached
- notes from supervisor or foreman
- whether the delay continued from a previous day
This record is especially important for multi-day delays. A delay that starts on Monday and continues until Thursday should not rely on one note written at the end of the week. Each day should show what was affected and whether the impact changed.
For example, a blocked access delay might affect excavation on day one, concrete preparation on day two, and subcontractor sequencing on day three. A daily record keeps that progression clear.
3. Labour standby record
A labour standby record shows which workers were held up, for how long, and why they could not proceed with planned work.
This matters because labour costs can become vague very quickly if they are not recorded properly. It is not enough to say “crew delayed”. The record should show the labour type, quantity, duration, and affected activity.
This record proves the labour impact of the delay.
A labour standby record should include:
- labour role or trade
- number of workers affected
- start and finish time
- hourly rate or agreed standby rate, if applicable
- work they were meant to perform
- reason they could not proceed
- whether they were fully stood down or partially affected
- supervisor notes
- evidence supporting the delay
A stronger labour standby record might say:
Four formworkers were held on standby from 7:00am to 10:30am because access to the work area was blocked by others. Planned works could not proceed. Photos of the blocked access and supervisor notes are attached.
That is far more useful than:
Formwork crew delayed.
The goal is not to overcomplicate the record. The goal is to make the labour impact clear enough that someone reviewing it later can understand what happened without needing the supervisor to explain everything from memory.
Relevant supporting asset: Labour Standby Cost Calculator.
4. Plant downtime record
A plant downtime record shows which equipment was idle during the delay and what impact that had.
Plant downtime is often missed because the machine is still on site and the cost can feel less visible than labour. But idle plant can be a real commercial impact, especially when excavators, loaders, cranes, trucks, pumps, or specialist equipment are held up.
This record proves the plant or equipment impact of the delay.
A plant downtime record should include:
- plant or equipment type
- quantity
- asset name or identifier, if available
- start and finish time
- hire rate, hourly rate, or internal rate
- operator impact, if relevant
- reason the plant could not work
- affected activity
- photos or videos showing the issue
- whether the plant was fully idle or partially utilised
A useful record might say:
One 14T excavator and operator were idle from 8:15am to 12:00pm due to late approval of excavation area access. The excavator remained on site and could not be reassigned. Photos, supervisor notes, and access correspondence are attached.
This creates a clearer link between the delay event and the cost impact.
Relevant supporting asset: Plant Downtime Cost Calculator.
5. Dayworks or cost record
A dayworks or cost record connects the delay to the labour, plant, materials, notes, and supporting evidence that may need to be reviewed commercially.
This is where many delay records fall apart. The site team may know what happened, and the commercial team may know a cost has been submitted, but the connection between the event, resources, evidence, and cost is often weak.
This record proves how the delay event connects to commercial impact.
A useful dayworks or cost record should include:
- delay or work event reference
- date
- labour involved
- plant involved
- materials involved
- time impact
- cost rates
- supervisor notes
- evidence attachments
- instruction or cause of delay
- sign-off status, if required
- whether the record is open, submitted, disputed, or closed
The point is not just to calculate a number. The point is to create a defensible record that explains where the number came from.
A dayworks docket is stronger when it is linked back to the delay record that caused it. Labour, plant, and material costs should not sit in isolation. They should be connected to the delay event, evidence, and site notes.
Relevant supporting asset: Dayworks Docket Generator.
Construction delay records should work together
The strongest construction delay records are connected.
A delay notice says the delay happened.
A daily delay record explains what happened on site.
A labour standby record shows which workers were affected.
A plant downtime record shows which equipment was idle.
A dayworks or cost record connects the impact to a commercial value.
Individually, each record is useful. Together, they create a much stronger picture.
For example, if wet weather prevents works from proceeding, the record should not stop at “weather delay”. A stronger record would show:
- the weather condition
- when works stopped
- which area was affected
- which crew was held up
- which plant was idle
- photos or videos of site conditions
- any direction or instruction received
- whether work resumed later that day
- whether a delay notice was sent
- what cost impact followed
This is the difference between a general note and a commercially useful delay record.
Common mistakes that weaken construction delay records
The most common delay record mistake is recording too little, too late.
Other common mistakes include:
- writing vague notes like “held up on site”
- failing to record start and finish times
- not naming the affected activity
- grouping all labour together without roles or quantities
- forgetting idle plant
- relying only on photos without explaining what they show
- not linking costs back to the delay event
- waiting until the end of the week to recreate the record
- treating a site diary as enough evidence by itself
- not checking contract notice requirements
A useful record does not need to be perfect. It needs to be clear, timely, and specific enough for someone else to understand later.
Construction delay record checklist
Before closing or submitting a delay record, check whether it includes:
- delay cause
- date and time
- site location
- affected work activity
- labour affected
- plant affected
- materials or fixed costs affected
- photos, videos, emails, or instructions
- daily notes if the delay continued
- delay notice status
- cost impact, if known
- supporting dayworks or cost record
- person responsible for the record
- current status: open, submitted, reviewed, or closed
If several of these are missing, the record may still be useful internally, but it will be weaker for commercial review.
How DelaySolve helps keep delay records connected
DelaySolve helps subcontractors log delays, cost labour and plant impact, attach evidence, and keep a structured delay record across live projects.
Instead of keeping delay notices, photos, labour notes, plant costs, and dayworks dockets in separate places, DelaySolve is designed to keep the record connected to the delay event.
That matters because the commercial value of a delay record depends on the full picture: what happened, what it affected, what it cost, and what evidence supports it.
You can also use the free tools to support specific parts of the workflow:
- Construction Delay Notice Generator
- Plant Downtime Cost Calculator
- Labour Standby Cost Calculator
FAQs
What is a construction delay record?
A construction delay record is a structured record of a delay event on site. It should explain what caused the delay, when it happened, which works were affected, what labour or plant was impacted, and what evidence supports the record.
Is a site diary enough to prove a construction delay?
A site diary can help, but it is usually not enough by itself. A delay record should go further by recording the cause, affected works, time impact, labour impact, plant impact, cost impact, and supporting evidence.
What evidence should support a construction delay record?
Useful evidence can include photos, videos, emails, site instructions, delivery records, weather records, supervisor notes, labour records, plant records, and programme impact notes. The best evidence is connected directly to the delay event.
Should every delay have a notice?
Not every site issue will need a formal notice, but any delay that may affect time, cost, programme, or entitlement should be checked against the contract requirements. If formal notice is required, the record should be clear, dated, and supported by evidence.
What is the difference between a delay record and a dayworks docket?
A delay record explains the delay event. A dayworks docket records labour, plant, materials, notes, and costs that may need to be submitted or reviewed. A strong dayworks docket should be linked back to the delay or instruction that caused the cost.
When should a delay record be created?
A delay record should be created as soon as the delay is identified. The earlier the record is started, the easier it is to capture accurate times, affected resources, photos, notes, and instructions.
