Almost every substantial construction project experiences delay, and the question of who bears its consequences is the most persistently contested issue in the industry. When completion slips, the contractor faces liquidated damages unless entitlement to more time can be established; the employer faces cost and lost use unless it can be resisted. The stakes are considerable and the analysis is genuinely difficult.
An extension of time claim is the mechanism through which a contractor seeks relief from those damages by demonstrating that delay was caused by an event for which the contract allocates risk to the employer. Understanding how such claims succeed — and, more often, why they fail — is essential knowledge for anyone delivering construction in the UAE.
What entitlement actually requires
A successful extension of time claim rests on establishing several things together, and weakness in any one is usually fatal. There must be a delay event for which the contract places risk on the employer. That event must have caused delay to the completion date, not merely to some activity that had float available to absorb it. The contractual notice requirements must have been complied with. And the whole must be demonstrated by evidence rather than asserted.
The causation requirement defeats more claims than any other. A genuine employer-risk event that delayed a non-critical activity gives rise to no entitlement to time, because the completion date was never affected. This is why the programme, and specifically the critical path, sits at the centre of every serious delay analysis.
Methods of delay analysis
Several established techniques exist for demonstrating the effect of delay events on completion, and the choice between them can materially affect the result. The appropriate method depends on the quality of the available records, the nature of the project, and what the contract or the tribunal expects.
- Impacted as-planned — delay events are inserted into the original baseline programme to model their theoretical effect. Simple, but criticised for ignoring what actually happened.
- Time impact analysis — events are modelled against an updated programme at the time each occurred, producing a prospective view widely regarded as robust where good records exist.
- As-planned versus as-built — the planned and actual programmes are compared to identify where and why divergence occurred, retrospectively.
- Collapsed as-built — delay events are removed from the as-built programme to show when completion would have occurred without them.
The problem of concurrent delay
Concurrency arises where two delays occur in the same period, one at the employer’s risk and one at the contractor’s, each independently capable of delaying completion. It is among the most contested concepts in construction law, and approaches to it differ across jurisdictions and between commentators.
The practical consequence on most projects is that concurrency, where established, tends to affect the relationship between time and money — a contractor may secure relief from liquidated damages while facing greater difficulty recovering prolongation costs for the same period. Because the analysis is fact-specific and the governing contract and law determine the outcome, concurrency claims reward meticulous records and careful, early advice.
Records win claims
Underlying every successful claim, and absent from most failed ones, is contemporaneous evidence. Delay claims are proved with programmes that were genuinely updated, site records that show what was actually happening, correspondence that notified events when they occurred, and resource records that demonstrate impact. Reconstructed narratives assembled long afterwards rarely persuade.
The discipline this demands is unglamorous and constant: maintain the programme properly, update it honestly, issue notices promptly, and keep records as though they will one day be scrutinised — because on any project that ends in dispute, they will be. Projects that treat this as routine control work are in an incomparably stronger position than those that treat claims as something the commercial team addresses at the end.
Delay claims are not won by argument at the end of a project. They are won by the programme discipline and record-keeping practised throughout it.
Key takeaways
- 1Entitlement requires an employer-risk event, proven critical-path causation, compliant notices, and evidence.
- 2The choice of delay analysis method can materially affect the outcome and depends on records and context.
- 3Concurrent delay is contested and typically affects time and cost entitlement differently.
- 4Contemporaneous programmes, notices, and site records are what ultimately determine claim outcomes.
Frequently asked questions
What is the difference between an EOT and a prolongation cost claim?
An extension of time adjusts the completion date and provides relief from liquidated damages; a prolongation claim seeks the additional cost of the extended period. They are related but distinct, and entitlement to one does not automatically confer the other.
How soon must a delay event be notified?
Contracts impose specific, and typically short, notice periods. Because late notification can defeat an otherwise valid claim, prompt notice on becoming aware of a potentially delaying event should be treated as standard practice.
Is this legal advice?
No. This is general guidance on how delay claims work in practice. Entitlement depends on your specific contract, the governing law, and the facts, and specific professional and legal advice should be taken on any actual claim.
