Extension of Time Claim: What Site Teams Need to Record Before the Claim Is Prepared

Quick summary: what site teams should record for an extension of time claim

Site teams do not need to prepare the full extension of time claim, but they do need to capture the records the claim may rely on.

Summary table (shown as a list because the blog body does not support table blocks yet):

• Delay cause : What it helps show: why the delay happened. Capture: event, instruction, access issue, design issue, weather event, delivery issue, or other cause.
• Date and duration : What it helps show: when the delay happened. Capture: start date, start time, finish time, whether it is ongoing.
• Affected works : What it helps show: what could not proceed. Capture: activity, location, trade, sequence, blocked area, planned work.
• Programme impact : What it helps show: whether the delay affected planned progress. Capture: planned activity, next activity affected, critical sequence, revised sequencing notes.
• Notice record : What it helps show: whether the delay was communicated. Capture: notice date, recipient, subject, reference, supporting detail.
• Evidence : What it helps show: what supports the record. Capture: photos, videos, emails, instructions, drawings, delivery records, weather records.
• Labour and plant impact : What it helps show: what resources were affected. Capture: crew details, plant items, standby time, downtime, reassignment notes.

The strongest extension of time records are specific, dated, and connected. A vague site diary note is usually weaker than a structured record that explains the cause, timing, affected work, and evidence.

What is an extension of time claim?

An extension of time claim is a request for more time because a delay has affected the planned completion or progress of construction works.

In construction, an EOT claim is usually connected to contract requirements. Those requirements can vary widely. Some contracts require formal notices within strict timeframes. Others require specific details about delay cause, programme impact, mitigation, and supporting evidence.

This article does not explain legal entitlement. It focuses on the practical site records that help the project or commercial team understand and support the delay later.

A useful extension of time record should answer these questions:

• What caused the delay?
• When did the delay start?
• Is the delay still ongoing?
• Which works were affected?
• Did the delay affect the programme or sequence?
• Was notice given?
• What evidence supports the delay?
• Which labour, plant, or subcontractor resources were affected?

Why site records matter before the claim is prepared

Site records matter because the facts are clearest while the delay is happening.

By the time an extension of time claim is prepared, the site team may have moved on, the work area may have changed, and the detail may be harder to reconstruct. Photos may be missing. Instructions may be buried in emails. Labour and plant impacts may be estimated instead of recorded.

A strong site record helps the commercial team avoid relying on memory.

For example, a weak record might say:

Delayed due to access issue.

A stronger record would say:

Excavation works at Gridline B were delayed from 7:15am to 11:40am because access to the work area was blocked by stored materials. The excavation crew and one 14T excavator were unable to proceed. Photos were taken at 7:20am and 10:05am. Site instruction SI-024 was received at 11:10am confirming the area would be cleared.

The stronger record gives the delay a cause, location, timeframe, affected work, affected resources, and supporting evidence.

That is the difference between a general site note and a record that may help support an extension of time claim.

1. Record the cause of the delay

The cause of delay should be recorded clearly and specifically.

This is the starting point for any extension of time claim record. If the cause is vague, the rest of the record becomes harder to assess. Do not just write “delayed by others” or “held up”. Record what actually happened.

Common delay causes include:

• blocked site access
• late design information
• late approval
• client instruction or change
• weather stand-down
• unavailable work area
• late material delivery
• preceding trade not complete
• authority or inspection delay
• plant breakdown
• safety exclusion zone
• change in construction sequence

The record should explain the cause in plain language.

Better wording:

Works were delayed because access to the work area was blocked by stored materials from another contractor.

Weaker wording:

Access issue.

The site team does not need to decide legal responsibility in the site record. It should avoid guessing or blaming. The job is to record the observable facts.

2. Record the start time, finish time, and duration

An extension of time record should include when the delay started, when it finished, and whether it continued across multiple days.

Time is often where delay records become weak. If the record only says “delayed today”, it is difficult to understand the duration or the programme effect. A clearer record shows the actual time impact.

Record:

• date the delay started
• start time
• finish time, if known
• whether the delay is ongoing
• whether the delay continued from a previous day
• whether works restarted fully or partially
• any periods where work was resequenced or partially productive

For example:

Delay started at 6:45am when the crew arrived and could not access the work area. Access was restored at 1:20pm. Excavation restarted at 1:45pm after the area was checked and plant was repositioned.

For multi-day delays, keep a daily record. Do not rely on one summary at the end of the week.

A three-day delay should show what happened on each day, what changed, and whether the affected works remained the same.

3. Record the affected works

The affected works should be described in enough detail that someone reviewing the record later understands what could not proceed.

This should be practical and site-specific. Avoid writing only the broad trade or package name. Record the actual activity, area, and planned work.

Capture:

• activity affected
• work area or location
• trade or crew affected
• planned sequence
• what could not proceed
• whether any alternative work was possible
• whether the delay affected follow-on trades or activities

Weak wording:

Concrete works delayed.

Better wording:

Concrete pour preparation for footing F3 in Zone 2 was delayed because formwork inspection approval had not been received. Steel fixing was complete, but pour preparation could not proceed.

The stronger record explains the specific activity and why the work was affected.

This matters because an extension of time claim usually needs more than proof that something happened. It needs a clear connection between the delay event and the work that was affected.

4. Record whether the programme or sequence was affected

Programme impact should be recorded as soon as the site team can see that planned progress or sequencing may be affected.

The site team does not need to produce a full delay analysis. But it should capture what was planned, what could not happen, and what the immediate sequencing impact was.

Useful programme notes include:

• planned activity for the day
• activity that could not proceed
• next activity affected
• follow-on trade affected
• whether the delayed work was resequenced
• whether resources were moved elsewhere
• whether the delay affected a milestone or handover
• whether the impact continued into the next day

Example:

The planned excavation in Zone 2 could not proceed on 14 June. The crew was moved to minor preparation works in Zone 1 after 11:00am, but the main excavation activity remained incomplete. This affected the planned blinding works scheduled for the following morning.

This type of note gives the commercial or planning team something useful to assess later.

Avoid overstating the programme impact on site if it is not yet clear. Use careful wording:

• “may affect”
• “appears to affect”
• “requires review by the project team”
• “follow-on activity may be impacted”

5. Record the notice position

The notice record should show whether the delay was communicated, when it was communicated, and what information was included.

For many contracts, formal notice requirements matter. The site team should not assume the commercial team will know about the delay automatically. If the issue may affect time or cost, it should be escalated and recorded promptly.

Record:

• whether a delay notice was sent
• date and time sent
• who it was sent to
• subject line or reference
• method of communication
• summary of what was notified
• attachments or supporting evidence
• whether further details were promised

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 at [location] were delayed on [date] due to [cause]. The affected works include [activity]. The delay started at [time] and remains [ongoing / resolved at time]. We are continuing to record the time, labour, plant, and programme impact and will provide further details as they become available.

If a notice has not been sent, the record should still note that the issue has been escalated internally for review.

For more detail on notice wording, check out our article here : Construction Delay Notice Template: What to Include Before You Send One.

6. Record supporting evidence

Supporting evidence should be collected while the delay is visible and before the site condition changes.

Evidence is stronger when it is linked to the delay record. A photo sitting in a camera roll is less useful than a photo attached to a record explaining what it shows, when it was taken, and which delay it supports.

Useful evidence can include:

• photos of blocked access, conditions, or incomplete preceding works
• videos showing site conditions or work area restrictions
• emails or instructions
• site directions
• revised drawings
• delivery records
• weather records
• inspection records
• meeting notes
• subcontractor correspondence
• daily site diary entries
• labour and plant records

Each evidence item should answer:

• What does this show?
• When was it captured?
• Where was it captured?
• Which delay does it support?
• Why does it matter?

A photo caption might say:

Photo taken at 7:20am on 14 June showing stored materials blocking excavation access to Zone 2. This supports delay record DR-014.

That is far stronger than an unnamed image with no context.

7. Record labour and plant impact

Labour and plant impact should be recorded separately so the time and cost effect is clear.

A delay can affect time without creating a major resource cost. It can also create resource costs even if the programme effect is still being assessed. The record should separate these issues.

For labour, capture:

• labour role or trade
• number of workers affected
• start and finish time
• whether workers were idle, partially productive, or reassigned
• planned task
• reason work could not proceed
• supervisor notes

For plant, capture:

• plant or equipment type
• quantity
• asset ID or item name, if available
• operator impact
• start and finish time
• whether plant was fully idle or partially used
• hire rate or internal rate, if relevant
• reason it could not proceed

Example:

Three pipe layers and one excavator operator were held on standby from 6:45am to 10:30am while access to the trench area was blocked. One 14T excavator remained idle during the same period. The crew was partially reassigned after 10:30am, but the planned trenching activity did not proceed.

This makes the difference between delay duration, labour cost, and plant downtime easier to review.

For a broader record structure, read: 5 Construction Delay Records Every Subcontractor Should Keep.

8. Record mitigation or resequencing attempts

Mitigation records show what the site team did to reduce the delay impact.

This does not need to be complex. It should simply record whether the team tried to work around the issue, resequence works, move resources, or continue with partial productivity.

Capture:

• alternative work attempted
• resources moved to other activities
• areas made available
• partial productivity achieved
• instructions requested
• approvals chased
• temporary works or access solutions considered
• why mitigation was not possible, if relevant

Example:

Crew was moved to Zone 1 preparation works from 11:00am to 1:30pm. This provided partial productivity, but the planned Zone 2 excavation remained delayed because access was not restored until 1:20pm.

This type of note helps show that the delay was managed actively, not just observed.

9. Keep the record updated if the delay continues

Ongoing delays should be updated daily.

A delay that continues over multiple days can change in cause, impact, resources, and evidence. A single record created at the end of the delay is usually weaker than daily updates.

Each day, record:

• whether the delay is still active
• what changed since the previous day
• whether the affected work changed
• whether labour or plant impact changed
• whether any instructions or approvals were received
• whether further notice or update was sent
• whether works restarted or remained blocked

For example:

Delay continued on 15 June. Access to Zone 2 was restored at 9:15am, but excavation could not restart until 12:00pm due to inspection sequencing. One excavator and two crew members were affected. Updated photos and supervisor notes attached.

Daily updates create a clearer timeline for the commercial team.

Common mistakes that weaken extension of time records

The most common mistake is waiting until the claim is being prepared before gathering the evidence.

Other common mistakes include:

• using vague notes like “delay by others”
• not recording start and finish times
• failing to identify the affected activity
• not recording whether the delay was ongoing
• relying only on a site diary
• taking photos without captions or context
• not recording labour and plant impact separately
• not recording programme or sequencing impact
• not keeping daily updates for multi-day delays
• not checking formal notice requirements
• overclaiming programme impact before it has been reviewed

A site record should be factual. It should not try to argue the full claim. Its job is to preserve the facts clearly enough that the claim can be assessed later.

EOT site record checklist

Before relying on site records for an extension of time claim, check whether the record includes:

• delay cause
• date and start time
• finish time or ongoing status
• site location
• affected works
• affected trade or activity
• programme or sequencing impact
• delay notice status
• photos or videos
• emails, instructions, or approvals
• labour affected
• plant affected
• mitigation or resequencing attempts
• daily updates for multi-day delays
• person responsible for the record
• current status of the delay

If several of these items are missing, the record may still be useful, but it is likely weaker for EOT review.

Use the free EOT Claim Readiness Checker

DelaySolve’s free EOT Claim Readiness Checker helps you review whether a delay record has the basic information usually needed before an extension of time claim is prepared.

It can help identify gaps around:

• notice timing
• delay cause
• dates and duration
• affected works
• programme impact
• evidence
• labour and plant records

Use it as a practical record check, not as legal advice.

How DelaySolve helps with EOT-ready delay records

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

For EOT-related delays, the value is keeping the site record connected. The delay cause, notice record, daily updates, labour impact, plant impact, and evidence should not sit in separate places with no clear link between them.

DelaySolve is designed to help site and commercial teams keep that record clearer from the start.

FAQs

What is an extension of time claim in construction?

An extension of time claim is a request for additional time because a delay has affected planned construction progress or completion. The contract usually sets out the requirements for notices, evidence, timing, and assessment.

What should site teams record for an EOT claim?

Site teams should record the delay cause, date, start and finish time, affected works, programme or sequencing impact, notice status, supporting evidence, labour impact, plant impact, and any mitigation or resequencing attempts.

Is a site diary enough for an extension of time claim?

A site diary can support an extension of time claim, but it is usually not enough by itself. A stronger delay record should connect the site diary entry to the delay cause, affected works, evidence, programme impact, and resource impact.

When should an EOT delay record be created?

An EOT 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, photos, instructions, affected resources, and programme notes.

What evidence supports an extension of time claim?

Useful evidence can include delay notices, site diary entries, photos, videos, emails, site instructions, revised drawings, delivery records, weather records, inspection notes, labour records, plant records, and programme impact notes.

Should site teams decide whether a delay gives entitlement to an EOT?

Site teams should usually avoid deciding entitlement in the site record. Their job is to record the facts clearly. The contract, project manager, commercial team, or legal adviser may then assess whether the records support an extension of time claim.