Skip to content

Construction administration guide · By Yes AI

How to track EOT notices and contract time bars

Published 6 min read

Extension of time claims can fail on paperwork: a notice that went in late, went to the wrong person or left out the program. This guide shows how to build a time-bar register from your contracts, using a published government contract as the worked example. It is general information, not legal advice.

Quick answer

Read the extension of time clause in each head contract and subcontract at award, record every notice step and its deadline in a register, and log the start of each delay on the day it is identified. Under the ACT Government's modified GC21 contract, for example, an initial notice is due within 7 days of the delay starting and the claim within 28 days, updated every 28 days. Other contracts differ. This is general information, not legal advice.

Project manager and contract administrator reviewing a printed construction program with a delay marked in red pen

What is a time bar in a construction contract?

A time bar is a clause that makes an entitlement, such as more time or more money, depend on a notice given within a set period. The consequence of missing it is set by the contract. In the ACT Government's modified GC21 (Edition 2), if the initial notice of delay is given later than 7 days after the delay starts, the contractor's extension of time entitlement is reduced by one day for each day the notice is late. Other contracts treat late notice differently, so the consequence has to be read from each contract you sign, including subcontracts you issue.

How do you build the register from the contract?

Do this at award, while the contract is fresh, and have a second person check it. The register entry for each contract should capture what triggers a notice, what it must contain, who receives it, how it must be sent and when updates are due. Record the clause numbers so anyone can check the source. Where a subcontract allows a longer notice period than the head contract for the same kind of event, note the gap, because a subcontractor's late notice can leave too little time to notify upstream.

  • Notice trigger: when a delay starts, or when the contractor becomes aware of it.
  • Deadlines for the initial notice, the claim and any updates.
  • Required contents, such as cause, steps to minimise and program evidence.
  • Recipient and method: the named representative and the notice address in the contract.
  • Any rule on concurrent delays or days that do not count.

What does a worked example look like?

Clause 50 of the ACT modified GC21 gives a contractor an extension of time if it is delayed by a cause beyond its control, the delay is to an activity on the critical path of the current contract program and work is proceeding in accordance with that program. The initial notice, due within 7 days, must set out the cause, the steps to minimise the delay and the relevant facts, with a copy of the program verified as current at the start of the delay. The claim must be submitted within 28 days of the start of the delay and updated every 28 days while it continues.

Hypothetical example: a consultant's late RFI response holds up a slab pour, and the delay is logged on day 0. Under GC21-style terms the initial notice is due by day 7 and the claim by day 28, with updates every 28 days after that. Whether those are calendar or business days is a question for the contract's definitions.

Why do delays get noticed too late?

A delay can go unnoticed until the program slips, weeks after the event that caused it. The cause often sits in a document nobody has read closely: an RFI response that changes a detail, an approval that arrived late, a site diary note about a crane breakdown. A weekly review of RFI responses, diary entries and correspondence for possible delay events catches most of these while the notice period is still open. The review should log each possible event with a start date for the project manager to confirm or dismiss.

What changed for time bars in Victoria in 2026?

Victoria's Building and Plumbing Commission says amendments to the Security of Payment Act took effect on 15 April 2026. Under them, a notice-based time bar affecting payment, an extension of time that affects payment, or release of a performance security may be found unfair by an adjudicator, court, arbitrator or appointed expert if compliance is not reasonably possible or would be unreasonably onerous. The BPC says the changes apply to all construction contracts from that date, including contracts entered into earlier, subject to transitional provisions. Treat this as a possible argument in a later dispute. Keep giving notices on time, and take legal advice on any Victorian contract.

Where does software fit in EOT administration?

Software can extract the notice clauses from each contract at award into the register, scan RFI responses, diary entries and emails for possible delay events, track every deadline and draft the initial notice with the facts and program attached for the contract administrator to review. It cannot decide whether a delay is on the critical path, whether the cause is beyond your control or whether to make a claim. Those decisions belong to the project manager, the planner and the contract administrator, who also sign and send the notice.

Example fields for an EOT register entry

FieldWhat to recordHypothetical entry
Delay eventShort description and source documentLate RFI response holds up level 3 slab pour
Start dateDate the delay began, confirmed by the project managerDay 0
Initial notice dueDeadline from the contract clauseDay 7 (clause 50.1.3 in the GC21 example)
Claim dueDeadline from the contract clauseDay 28, then updates every 28 days
Program evidenceProgram version verified at the start of the delayProgram revision current on day 0
Sent to and howRecipient and method the contract requiresNamed representative, by the contract notice method
StatusDrafted, sent, acknowledged, assessedInitial notice sent, claim in preparation

Practical checklist

  • Every head contract and subcontract has its time-bar clauses logged at award, with clause numbers.
  • Possible delay events from RFIs, site diaries and correspondence are reviewed at least weekly.
  • Each delay event has a start date confirmed by the project manager on the day it is identified.
  • Notices go to the recipient and by the method the contract specifies, with proof of delivery filed.
  • Ongoing delays have their update dates in the register until the delay ends.
  • A construction lawyer has reviewed the register template against your usual contract forms.

Common questions

Do subcontractor EOT claims need the same register?

Yes. Record incoming notices and claims from subcontractors with the same fields, because a subcontractor's delay may become your own claim upstream. Check that your head contract periods leave you enough time to pass a subcontractor's notice on, since they may be shorter than the periods in your subcontracts.

Can the principal extend time even if we miss the notice?

Some contracts give the principal a discretion. The ACT modified GC21 says the principal may extend a completion date at any time and for any reason, but in its absolute discretion and without any obligation to do so. Do not plan around a discretion; give the notice on time.

Does wet weather count as a delay?

That depends on the contract. Some allow time for inclement weather beyond an allowance and some exclude it. Whatever the contract says, record the weather in the site diary on the day and keep Bureau of Meteorology observations from the nearest station, so the evidence exists if a claim is available.

Are time bars always enforced?

Not always, and the answer depends on the contract, the facts and the state. Victoria's 2026 amendments allow some notice-based time bars to be found unfair. Courts and adjudicators may take different views elsewhere. Get legal advice on a specific dispute and keep giving notices on time.

Can software decide whether a delay is on the critical path?

No. Critical path analysis needs the current program, the planner's judgement and knowledge of what is happening on site. Software can attach the right program version and highlight affected activities, but the planner or project manager makes the call and records the reasoning.

Sources and further reading

Continue planning

Plan the next improvement to your project administration

Describe the document workflow, project systems and handover causing delays. We can discuss a bounded admin pilot and the checks your project team needs. Keep contracts, personal records and confidential project files out of this enquiry.