EOT notice time bars: the clause that quietly kills delay claims

What is an EOT time bar?

An extension of time clause gives you more time to finish when the job is delayed by something you're entitled to relief for — a variation, a principal-directed change, weather, latent conditions, whatever the clause lists. The time bar is the condition attached to it: notify the builder of the delay within a set window, in a set form, or lose the entitlement entirely.

That last part is the point. A well-drafted time bar doesn't just ask for notice — it makes notice a condition precedent to the claim. Miss the window and the claim isn't weakened; on the contract's own terms, it doesn't exist. And because liquidated damages run from the date for practical completion, an EOT you failed to claim converts directly into LDs you now owe.

Is there a statutory notice period?

No — and this surprises a lot of subcontractors. Security of Payment legislation sets statutory timeframes for payment claims, but there is no equivalent for EOT notices. The time bar itself lives in your contract — though in Victoria and Western Australia, statute can now step in when an unfair one bites (more on that below). Two consequences follow:

• Every contract is different. The standard forms are relatively generous — commonly in the region of 28 days from when you became (or should have become) aware of the delay. Bespoke head-contract pass-throughs routinely cut that to 10, 7 or 5 business days, and sometimes less.
• You can't rely on what the last job's contract said. The only way to know your window is to read the clause — which is exactly the sort of thing that gets missed at 9pm the night before signing, and exactly what a pre-signing review flags.

What actually voids a claim?

Time bar clauses fail claims on more than lateness. The usual tripwires:

• The window itself — counted from the delay event or from when you became aware of it, whichever the clause says. Awareness-based triggers start running earlier than people think.
• The wrong form. Verbal mention at a site meeting is not written notice. Many clauses require stated content: cause, affected activities, estimated delay.
• The wrong recipient or method. If the clause says notice to the superintendent by email to a nominated address, a text to the site foreman doesn't count.
• No follow-up particulars. Some clauses require an initial notice fast, then detailed particulars within a further window — two deadlines, not one.

Australian courts have repeatedly enforced clearly drafted time bars, even where the delay itself was genuine and the builder suffered no prejudice from the late notice. There are arguments dispute lawyers run against them — the prevention principle where the principal caused the delay, waiver or estoppel where the builder's conduct excused compliance — but those are expensive, uncertain, after-the-fact fights. Nobody prices a job planning to win one.

Can an unfair time bar be challenged?

In two states, yes — by statute. In Victoria (under s 13A of the SOP Act) and Western Australia (under s 16 of the SOP Act), decision-makers — adjudicators, courts, arbitrators and expert determiners — have statutory powers to declare strict contractual notice-based time bars "unfair" and ineffective if compliance was not reasonably possible or was unreasonably onerous. Victoria's power arrived with the SOP reforms of 15 April 2026; WA's sits in its 2021 Act. So don't abandon a legitimate variation, delay or time claim solely because a contractual notice window has expired, without evaluating statutory relief under these provisions.

Two things to keep straight about these powers:

• A declaration is claim-specific. It renders the time bar of no effect only for the particular claim being determined. The clause stays on foot as a valid contractual term for every other circumstance and future claim — it is not struck out of the contract.
• They are a safety net, not a plan. You have to persuade a decision-maker that compliance was not reasonably possible or was unreasonably onerous, claim by claim — and outside Victoria and WA there is no equivalent power at all. Notice served inside the window beats statutory relief every time.

What does good notice discipline look like?

1. Know your windows before the job starts. Extract every notice obligation from the executed contract — event, clause, period, how counted, served how. This is what SubSync does at project setup, and what the contract notices module tracks from then on.
2. Notify early and imperfectly rather than late and perfect. A short compliant notice of delay inside the window, with particulars to follow, beats a polished claim served a week after the bar came down.
3. Notify routinely, not selectively. Serving notices only when things turn hostile signals that your paperwork is tactical. Serving them every time makes it business as usual — and keeps every entitlement alive.
4. Keep the evidence attached. Site diaries, directions, photos, program impacts. The notice claims the entitlement; the records win it.
5. Watch the interaction with your payment rights. Delay costs claimed under Security of Payment still depend on the contractual entitlement existing — a time-barred EOT can undermine the money claim that follows it.

The pre-signing check

Before you sign, read the EOT clause against three questions: How long is the window and when does it start? Is notice a condition precedent? What form and content does it demand? If the answers are "5 business days, yes, and detailed particulars" — that's not a reason to walk away, but it is a term to price, a line worth putting in your departure schedule, and an obligation your site team needs to know about on day one. The clause sits alongside the other terms on our subcontract review checklist. Upload the subcontract and SubSync will flag the time bar, rate its risk and draft the departure — before it can cost you a claim.