Extensions of time and delay,
claimed when the cause happens.

An extension of time (EOT) is the contractual mechanism that moves a job's completion date when a delay arises from a cause the contract says is not the builder's to absorb. The residential building contract sets a completion date or a method of calculating one, and the builder is bound to it. The EOT clause is the machinery that keeps that date honest when the job is delayed by weather beyond the allowance, by the client, by a variation or by an authority, so the date the builder is measured against reflects the delays that were never theirs.

The definition has two working parts. The cause must qualify, meaning it appears in the contract's list of allowable causes, and the claim must be made the way the contract prescribes, which usually means written notice within a defined window of the delay arising. A real delay from a qualifying cause, claimed late or not at all, is commonly no entitlement. That makes the EOT unusual among contract mechanisms; it is lost more often by silence than by argument.

Why it matters

The completion date is where a residential contract keeps its teeth. Finish late without an approved EOT and the contract's remedies for the owner, liquidated damages where the contract states them or a possible claim for general damages where it does not, run against the builder from the date the contract still shows. Every day of delay therefore ends up on one side of a ledger, moved onto the contract date by an approved EOT or carried silently by the builder. The date also controls when the job reaches practical completion, which is where final payments, possession and the defects liability period all hinge. A builder who does not manage the date is managing everything else against the wrong baseline.

An EOT lives at the junction of the contract and the programme. The contract supplies the entitlement, the qualifying causes and the notice machinery; the construction schedule supplies the evidence of what the delay actually did, because a cause only earns days if it delayed work on the critical path. That is why builders who keep a baseline and track real progress against it find EOT claims straightforward to quantify, while builders whose programme is a start-of-job artefact end up arguing about days they cannot demonstrate. The applied discipline of building a schedule that survives its first delay is covered in the residential construction scheduling guide.

The machinery matters before site start as well. Clients reasonably expect paperwork, variations and final pricing locked before a job begins, and in practice these are often still being finalised late in pre-construction, sometimes because of the client's own scope changes. A start date that moves for those reasons is delay like any other, and the same disciplines of cause, notice and record apply to it.

The most common misunderstanding about EOTs is that an approved extension carries payment with it. It does not, by itself. The EOT answers one question, what date the builder must now finish by. Whether the builder is compensated for the cost of the delay is a separate question, and the contract answers it separately; some contracts attach cost recovery to some causes and not others, and many residential contracts are silent or restrictive. The clause is read for both answers, never one.

The cost is real whichever way the clause answers. A job that runs four weeks longer consumes four more weeks of preliminaries, the supervision, site facilities, fencing, amenities and insurances that are priced by duration rather than by quantity of work. An EOT without cost recovery means the builder wears that consumption; an unclaimed EOT means the builder wears it and the damages exposure as well. Understanding extended preliminaries as a genuine cost, not an accounting abstraction, is what makes builders take the time side of delay seriously.

Running the other way sits the owner's remedy for late completion. Where the contract states liquidated damages, they commonly accrue at the stated rate for each day or week beyond the contract completion date; where it does not, general damages may be open to the owner on ordinary contract principles. Both are described here as mechanisms only. How they apply, whether a stated rate is enforceable and how they interact with the EOT clause are questions of contract interpretation in a specific jurisdiction, and a builder facing them should take legal advice on the actual document. Approved EOTs are the builder's structural defence, because every day legitimately moved onto the contract date is a day damages cannot run against.

The operator's observation is that builders lose EOTs twice. The first loss happens when the cause happens. The relationship is good, the client is friendly, the delay is only a few days, and sending a formal notice feels petty, so the days get absorbed to keep the peace. The second loss happens months later when the job is running late for ordinary reasons and the builder claims the whole history in one letter. By then the notice windows have mostly closed, the evidence is thin, and a claim that would have read as routine paperwork in week nine reads as an excuse in week thirty. The same days, claimable once, are now lost at both ends.

The discipline that prevents both losses is boring, which is the point. A short written notice inside the window every time a qualifying cause arises, whether or not the builder ever intends to press it hard, and a diary entry on the day describing what happened and what stopped. Builders who run this as habit find the end of the job uneventful; the completion date moved as the job moved, in increments everyone saw at the time, and there is nothing to relitigate. Builders who save it up are negotiating their entitlement at the moment their leverage is weakest.

The evidence rule is just as unglamorous. The site diary written on the wet day beats the weather bureau printout produced six months later, every time. The printout proves it rained in the region; the diary proves the site was closed, the slab was under water, the concreter was stood down and the frame carrier was called off. Delay arguments are decided on contemporaneous records, entries and photographs dated at the time, not reconstructed afterwards from memory and public data. The builder with the diary is describing what happened; the builder without it is asking to be believed.

Where software fits the workflow

The contemporaneous record only exists if writing it is easier than skipping it, which is a workflow problem rather than a legal one. In VIABUILD the ViaSite daily diary is filled in on site as part of the supervisor's day, with dated photos attached to the entry, so the record of the wet day, the stood-down trades and the closed site is created at the time and filed against the job without anyone deciding to build an evidence trail. The judgement about what to claim and when remains the builder's; the software's contribution is that the diary the claim stands on was already written.

EOT machinery in Australian residential building is a creature of the contract, operating inside each state and territory's domestic building framework. The points below are labelled by evidence class. Requirements differ by jurisdiction and change over time, so confirm the current source before relying on any of them, and treat this whole page as general information rather than legal advice.

• Legislation. Domestic building contract legislation in the states and territories commonly requires a residential contract to state a completion date or a method of calculating one, and jurisdictions regulate aspects of how the build period is expressed and adjusted. The specific requirements differ by jurisdiction and no clause-level detail is asserted here; confirm the current position with your state or territory regulator.
• Industry best practice. Standard-form residential contracts published by HIA and Master Builders carry EOT clauses maintained against each jurisdiction's legislation, with defined qualifying causes, notice requirements and timeframes. Using a current edition is the simplest way to inherit workable delay machinery, and the clause in the edition you signed is the one that governs.
• Common practice. Build periods are commonly set with an allowance for anticipated wet weather and holidays already inside them, and many contracts state the weather allowance. Delay inside the allowance is priced into the job; the EOT machinery exists for delay beyond it. Knowing where that line sits in your contract is the first question of every weather claim.
• Common practice. Delay machinery matters before site start. Approvals such as the construction certificate or its local equivalent, and clients whose own changes are still moving late in pre-construction, commonly shift start dates, and contracts differ in how they treat commencement delay. The same notice and record disciplines apply from the day the contract is signed, not the day the slab is poured.
• Professional recommendation. Liquidated damages, general damages and any contested EOT are contract interpretation questions with real money attached. Positions on them should be taken on legal advice about the specific contract and jurisdiction, not on general references, this page included.

Illustrative only, not a benchmark. Two builders hit the same wet fortnight at slab stage, each losing six working days on the critical path beyond the allowance their contracts carry. The first builder's supervisor writes the diary each affected day, site closed, concreter stood down, pump cancelled, with photos of the flooded excavation, and a written EOT notice goes to the client inside the contract's window claiming six days. The client, looking at dated photographs of their own underwater site, approves it in a week. The completion date moves six days, the programme is rebaselined, and nobody ever discusses it again.

The second builder absorbs it, because the job is early and the relationship is warm. Seven months later the job is running three weeks late, partly for reasons that were the builder's own, and the builder now claims the wet fortnight along with every other delay since, supported by a weather bureau printout. The notice windows have closed, the printout does not show what the site actually lost, and the claim lands as an excuse rather than a record. Whether any of it survives is now a legal question, and the owner is counting days against a completion date that never moved. Same rain, same six days, opposite endings.

Extension of time or EOT (the contractual mechanism that moves the completion date for qualifying delay), qualifying cause (a cause of delay the contract lists as claimable), notice window (the defined period after a delay arises within which written notice must be given), delay costs (the money question the contract answers separately from the date), liquidated damages (a stated rate the contract applies for late completion), wet weather allowance (the anticipated weather already inside the build period), contemporaneous record (evidence created at the time of the event, not reconstructed later), critical path (the sequence of tasks that sets the finish date). Definitions for the wider vocabulary live in the construction glossary.

The diaries, notices and photographs this page keeps returning to are documents, and what a builder's systems do with documents is its own subject; the next reference is construction intelligence.

• Your state or territory's building regulator and fair trading body, for the current domestic building contract requirements on completion dates, build periods and delay in your jurisdiction.
• Housing Industry Association , publisher of standard-form residential building contracts whose EOT clauses are maintained against each jurisdiction's legislation.
• Master Builders Australia , publisher (through its state and territory associations) of standard-form residential building contracts.