Extension of time (EOT)
An extension of time (EOT) is a formal move of the contractual completion date where a delay is caused by something the contract does not hold the contractor responsible for. It protects the contractor from damages for finishing late.
In practice for trades
An extension of time answers one question: whose fault was the delay. Where the cause is a relevant event under the contract, such as late information, a variation instructed mid-job, exceptional weather or a client-caused delay, the completion date moves and liquidated damages cannot be charged for that period. Where the cause is the contractor's own resourcing or sequencing, it does not.
The critical thing trades get wrong is assuming an extension of time brings money with it. It does not. It buys time and protects you from damages. Recovering the cost of standing around for three weeks is a separate loss and expense claim, argued on different grounds, and one does not automatically follow the other.
Extensions of time are won on records, not arguments. A dated site diary showing when the information was requested, when it arrived and what the site was doing in between is worth more than any letter written afterwards. Notify in writing as soon as the delay is apparent, because most contracts require prompt notice and late notice is the easiest ground to refuse on.
Worked example
A job due to finish 14 June is held up three weeks waiting on a client decision about a kitchen. With a granted EOT the completion date moves to 5 July, and liquidated damages of £200 a day cannot be charged for those 21 days, saving £4,200. The cost of the idle labour is claimed separately, if at all.
Related terms
- Site diary: the contemporaneous record an EOT claim stands or falls on
- Variation in construction: instructed changes that are a common ground for an extension
- Practical completion: the milestone the extended date is measured to
Evidence it in FieldHive
Keep the dated daily record that an extension of time claim rests on, covering delays, instructions and who was on site, with the Site Diary Generator.
Site Diary Generator→


