Extension of Time (EOT)

An extension of time — or EOT — is the contractor's formal mechanism for claiming additional time when events outside their control delay the project. The contract completion date isn't just a target. It's a legally binding obligation with financial consequences attached. Understanding how EOTs work, and managing them properly, is essential for every developer.

EOT events generally fall into a few categories. Weather delays are the most common — prolonged rain, extreme heat days, or storms that exceed historical Bureau of Meteorology averages for the region. Latent conditions come next: hitting rock, contaminated soil, or underground services that weren't shown on the survey. Then there are directed variations — when you change the scope, the contractor is usually entitled to more time as well as more money. Force majeure events like pandemics, natural disasters, or government-imposed shutdowns are rarer but can add months. Most standard Australian contracts (AS 4000, HIA, MBA) define qualifying causes explicitly in their EOT clauses.

The notice and assessment process is time-critical. Under most contracts, the contractor must give written notice within a set number of days of the delay event occurring — often 5 to 10 business days. Late notice can void the claim entirely, depending on the contract wording. The superintendent then assesses the claim, considers the cause, reviews any supporting evidence (site diaries, weather records, photos), and either approves days, rejects the claim, or approves a different number of days. The contractor can dispute the assessment, but that's a separate process.

Why should developers care about getting EOTs right? Because EOTs interact directly with liquidated damages. If the contractor finishes late without an approved EOT, they owe you LDs — a pre-agreed daily rate that compensates you for the delay. But here's the catch: if the contractor had a valid EOT claim that you failed to assess, or assessed incorrectly, those LDs may be unenforceable. Australian courts have consistently held that a principal who prevents the contractor from claiming time cannot then claim LDs. This is the "prevention principle," and it can wipe out your LD entitlement entirely.

EOTs also have direct cash flow consequences that developers underestimate. A longer construction period means extended holding costs — interest on your development finance keeps accruing, prelims keep running, and settlement income gets pushed back. On a leveraged project with $50,000 per month in holding costs, even a two-week extension costs $25,000. Multiply that across several EOT events and you're looking at a material hit to your development margin.

For developers running multiple projects, EOT tracking gets complicated fast. Each project has its own contract date, its own EOT register, and its own cumulative impact. Without a system that tracks days claimed versus days approved and recalculates the adjusted completion date automatically, things slip through the cracks. And those cracks cost money.

Smart developers also keep their own delay records independent of the contractor's claims. Site diary entries, weather logs, and photographic evidence give you the ammunition to properly assess (or challenge) EOT claims rather than relying solely on the contractor's version of events.