Every contract's delay terms, captured where they belong

The Head Contract setup now carries the parameters that govern delay notices, EoT claims and liquidated-damages exposure. Set them once at contract creation, and the terms live on the contract itself, not in your head or a spreadsheet on the side. The problem we're chipping away at A delay event lands on site and the clock starts. You have a fixed number of days to issue the Notice of Delay, a separate window to lodge the formal EoT claim with the superintendent, and a liquidated-damages rate ticking against you for every day past practical completion. Today that all lives in the contract PDF and in people's memory. The notice periods are buried in clause 34. The LD rate is something half-remembered from tender. Two builders running identical jobs can carry very different risk simply because one CA remembers the terms better than the other. That is not a system, it is luck. The first step to fixing it is getting those terms out of the PDF and into structured fields on the contract record. That is what shipped. Who this is for Contract administrators, commercial managers and project managers running head contracts under AS4000, AS2124, NZS3910 or any SoP/CCA regime where the delay terms matter and a missed notice window can cost a legitimate claim. What changed: the notice periods Open any head contract and you will find a new Notices & Contract Administration section. NoD Notice Period (days) — Calendar days from a delay event within which the Notice of Delay must be issued. Typically clause 34 under AS4000 or clause 10.3 under NZS3910. The form references the clause so you are not guessing. EoT Notice Period (days) — Calendar days within which the formal extension-of-time claim must reach the superintendent. What changed: the exposure Before / After Why it matters now, and what's coming Deep Space · Construction runs better here · Published 1st June 2026