Extension of Time Claims: Turn Your Programme into Evidence

An extension of time (EOT) claim is a builder's formal request, under the contract, for more time to reach practical completion because a qualifying event delayed the work. Forensic programme analysis supports the claim by showing, from the programme and site records, what happened, when, and how it moved the completion date.

You know how it usually goes. Three weeks of rain, a late design change, an authority connection that slips, and the site loses time. A letter goes out saying the job was delayed and asking for twenty days. The superintendent comes back with a rejection: no critical path impact shown, the programme has not been updated since award, and the notice was late. Meanwhile liquidated damages are building up against a date you already know you cannot hit.

The delay was real. The claim failed because it was an opinion, not evidence. The programme is what turns one into the other.

What does a superintendent need to see in an EOT claim?

Contracts word it differently, but most standard forms used in Australia ask the same questions before time is granted. Your claim has to answer each one clearly.

  • A qualifying cause. The event has to be one the contract allows time for, such as a variation, a late instruction or a defined weather event, and not something within your control.
  • Notice in time. Most contracts set a short window to notify and some bar the claim if you miss it.
  • Actual delay to completion. A delay to one activity is not enough. You need to show it delayed the critical path and the date for practical completion.
  • The extent of the delay. The days claimed have to be measured from the programme, not estimated.
  • Records that agree. Diaries, RFIs, instructions and photos should tell the same story as the programme.
Five-step flow from a delay event to notice, programme update, critical path impact and lodging an extension of time claim
Each step builds on the one before. A claim lodged without an updated programme skips the step that proves the delay.

This is general information, not legal advice. Your contract sets the actual notice periods, time bars and claim requirements, so read it early and get legal input where the stakes are high.

How does forensic programme analysis support your claim?

Forensic programme analysis looks at the programme and the records to establish what caused the delay and how much time it cost. It starts from a baseline the superintendent has accepted, or at least received, and works forward from there.

  • Status the programme. Update progress to the point just before the delay event, so the analysis starts from where the job actually was.
  • Model the event. Add the delay to the activities it affected, with logic that reflects how the work really depends on it.
  • Compare completion dates. The difference in the forecast completion date is the time the event cost, provided the delay sits on the critical path.
  • Test the result against the records. Site diaries, instructions, delivery dockets and dated photos should confirm the sequence the analysis shows.

Some claims are prepared as the delay happens; others are reconstructed later from the as-built record. Either way, the analysis is only as strong as the critical path in the programme it starts from. Which technique fits depends on the records you hold; see delay analysis methods.

Multi-storey concrete frame under construction with formwork and props on the upper floors
On a busy structure, several delays can overlap. The analysis has to show which ones actually moved completion.

That is why the analysis needs someone who understands both the programme logic and how the job is built on site. A delay that looks critical on screen may have been absorbed by float, and a delay that looks minor may have pushed the structure cycle back a full floor.

Why do capable builders still lose EOT claims?

It is rarely because the delay was not real. Your PM and CM know what held the job up. Claims fail on the programme and the paperwork behind them.

  • The programme has not been updated since award, so there is no reliable starting point for the analysis.
  • The contract programme was never accepted, or it differs from what the site is building.
  • Logic is broken or forced with hard constraints, so the critical path on screen is not the real one.
  • Notices were late, vague or did not name the cause and the likely effect on completion.
  • The claim asks for total days without showing causation, or ignores delays the builder caused at the same time.
Bar diagram comparing a delay absorbed by float on a non-critical activity with a delay on the critical path that moves completion
A delay inside float does not move completion. Only a delay on the critical path supports a claim for more time.

Each of these is fixable, but most are far easier to fix during the job than after it. A programme kept current is the cheapest EOT insurance a builder has.

What records should you keep from day one?

The strongest claims are built on records kept as a habit, not gathered after a dispute starts. Agree with your PM and site team what gets kept and where.

  • The contract programme as submitted and any acceptance, with its Basis of Schedule.
  • Regular programme updates, fortnightly or monthly, saved as separate versions.
  • Site diaries, RFIs and responses, instructions and variations, with dates.
  • Weather records, delivery dockets and dated photos of the affected areas.
  • Copies of every notice and the correspondence that followed.
Two engineers in hard hats reviewing work in a basement excavation with scaffolding behind them
Site walks, dated photos and diaries are often what confirm when an activity actually started and finished.

The move from tender programme to contract programme is the right moment to set this up, because it fixes the baseline every later claim will be measured against.

 

FAQs

What is the difference between an EOT and a delay costs claim?

An EOT moves the date for practical completion and protects you from liquidated damages for that period. Delay costs are the money you claim for the extra time on site. Many contracts treat them separately, and an EOT does not automatically mean costs are paid.

How long do you have to notify a delay?

It depends on your contract. Standard forms set short notice periods and some include time bars that remove entitlement if notice is late. Check the clause at the start of the job and set up a process so notices go out on time.

Does any delay entitle a builder to more time?

Under most contracts, no. The event has to be a qualifying cause and it has to delay the work in a way that affects the date for practical completion, which usually means the critical path.

Should a builder outsource EOT programme analysis?

If your PM and CM are running the job and the programme has not been kept current, an experienced planner can rebuild the starting point, model the events and test them against the records faster than a stretched site team. Your team still supplies the facts; the planner turns them into evidence.

Who offers forensic programme analysis and EOT support in Australia?

FeelDX is an Australian project controls specialist firm with a construction background that provides forensic programme analysis and EOT support for builders, along with programme status updates, construction programmes, Basis of Schedule and 3D and 4D visualisation that shows how the delay affected the sequence.

How does FeelDX support your EOT claim?

FeelDX combines planning and visualisation so you can show how the job is being built, how long it will take and what it looks like, and reduce risk before it turns into a dispute. For an EOT, that means turning your programme and records into evidence: what happened, when, what was affected and whether it hit the critical path. Where it helps the superintendent follow the argument, a 3D or 4D sequence can show the delay in context. See our project controls services and planning and visualisation technology.

  • Planning Lead. Once you give the go-ahead, a Planning Lead is assigned and introduced, so you know who you are working with.
  • Kick-off. A short meeting with your PM or CM on the delay events, notices issued, contract requirements and the records available.
  • High-level WBS and delay windows. The first hold point: you confirm the programme structure and the periods to be analysed before the detail is built.
  • First draft with review time. The analysis arrives with enough time for your team to review and challenge it before the claim or response is due.

Send us your contract programme, the latest update and the notices issued so far, and we will come back with our view of the critical path impact and a proposed approach and timeline.

Talk to FeelDX.
📞 1800 FEELDX (1800 333 539) | 🌐 www.feeldx.com