Most engineers and contract administrators in Australia have worked on an AS 4000 contract. Far fewer have read the standard end to end — and that’s fine. The General Conditions run to dozens of densely cross-referenced clauses, and the parts you actually touch on a live job are a small slice of the whole.
This guide is that slice. What AS 4000 is, who the Superintendent is and why the role trips people up, how variations and progress claims actually work, how the state Security of Payment Acts sit over the top, and how AS 4000 compares to New Zealand’s NZS 3910. Written by a civil engineer who’s worked under both for 27 years.
If you’re a project manager, contract administrator, or engineer coming up to speed on an Australian contract, this is the cheat sheet. If you’ve crossed the Tasman from NZS 3910 work, the comparison section maps the concepts you already know onto their Australian equivalents.
What is AS 4000 in one sentence?
AS 4000-1997 is the General Conditions of Contract published by Standards Australia — the most widely used standard-form construct-only contract for building and civil engineering work in Australia. Principals, head contractors, and consultants across government and private projects reference it as the framework that governs how a contract is administered.
It is not the law. The various state and territory Security of Payment Acts are the law that governs your statutory right to progress payments and rapid adjudication. AS 4000 is the contract document parties choose to adopt to give structure to the commercial relationship — covering everything the legislation doesn’t, such as variations, extensions of time, defects liability, insurance and risk, programme, and completion.
A quick history
AS 4000-1997 succeeded the older AS 2124-1992, which you’ll still occasionally see referenced on legacy or amended contracts. Its companion form is AS 4902, the design-and-construct (D&C) version, used when the contractor carries design responsibility rather than building to the Principal’s design.
After nearly three decades, Standards Australia is working on a modernised edition — a draft AS 4000:2024 has been circulated for consultation. Until that lands and is adopted, AS 4000-1997 remains the operative standard, and the overwhelming majority of contracts you’ll administer today still reference the 1997 form (usually with project-specific amendments — see “What AS 4000 covers” below).
The parties — and the Superintendent
AS 4000 is built around three named roles. Getting them straight saves a lot of confusion.
The Principal is the party paying for the work — a government agency, developer, or any organisation commissioning construction.
The Contractor carries out the work and has the direct contractual relationship with the Principal.
The Superintendent is the contract administrator named in the contract. This is the role that carries the most nuance in AS 4000, because the Superintendent wears two hats. In some functions they act as the Principal’s agent (issuing directions, managing the Principal’s interests). In others — assessing claims, valuing variations, certifying payment — they must act as an independent certifier. Clause 20 requires the Superintendent to act reasonably and in good faith when performing those certifying functions. A Superintendent who behaves purely as the Principal’s advocate when they’re supposed to be certifying impartially exposes the certificate to challenge.
On larger jobs the Superintendent appoints a Superintendent’s Representative to handle day-to-day delegation on site — walking the works, attending site meetings, feeding decisions back up. The Superintendent stays formally responsible for what the Representative does.
A common confusion: people treat the Superintendent as just “the Principal’s person.” On the agency functions, fair enough — but on certification, the Superintendent’s independence is exactly what makes the contract administration defensible if it ends up in adjudication.
AS 4000 vs Security of Payment — contract vs law
This is the single most important distinction for anyone administering an Australian construction contract.
Every state and territory has Security of Payment (SOP) legislation — for example the Building and Construction Industry Security of Payment Act 1999 (NSW), Victoria’s 2002 Act, and Queensland’s Building Industry Fairness (Security of Payment) Act 2017. These Acts give a statutory right to progress payments and a fast, low-cost adjudication process to recover them.
The key point: the legislation overrides the contract where they conflict. A payment clause in AS 4000 — or in the Principal’s amendments — that tries to contract out of the statutory regime won’t hold. The statutory payment-claim and payment-schedule timeframes are set by the Act in your jurisdiction, and they differ state to state. So you always administer a payment under two sets of rules at once: AS 4000’s clause 37, and your state’s SOP Act. Where they differ, the Act wins.
(This mirrors the New Zealand picture, where NZS 3910 sits over the Construction Contracts Act 2002 — see our NZS 3910 guide.)
What AS 4000 covers
The standard has a recognisable structure.
General Conditions of Contract. The rules of engagement — definitions, the Superintendent’s role, security, the contractor’s obligations, time and programme, variations, payment, defects liability, insurance and risk, and dispute resolution. This is the part you reference most.
The Annexure (Part A and Part B). This is where AS 4000 gets project-specific. Annexure Part A records the project’s particulars — the parties, the defects liability period, the amount and form of security, the time for payment, liquidated damages rate, and so on. Annexure Part B lists the amendments — the clauses that have been deleted, added, or rewritten for this contract. Australian contracts are very often amended AS 4000, so Part B is the first thing to read: it tells you how far this contract departs from the standard form.
Schedules and attachments. The drawings, specifications, the bill of quantities or schedule of rates, and the programme — the project data the General Conditions reference but don’t define.
The mechanics every engineer needs to know
A quick reference for the parts you deal with weekly.
Variations (Clause 36)
A variation is a change to the work under the contract. Under AS 4000, the Superintendent directs variations under clause 36 — and importantly, only before the date of practical completion; the Contractor isn’t obliged to carry out a varied work direction issued after that point.
The process matters. Clause 36.2 lets the Superintendent ask the Contractor for estimates, and for detailed quotations, in response to a proposed variation. Clause 36.4 sets the order of precedence for valuing a variation — starting with any prior agreement on price between the parties, then agreed rates, then the Superintendent’s reasonable valuation. The cleaner the paper trail — written direction, agreed price, agreed time impact — the less likely a variation resurfaces as a dispute months later.
Progress claims and payment (Clause 37)
The monthly payment cycle runs under clause 37 and your state’s SOP Act:
- The Contractor submits a progress claim under clause 37.1 at the claim date in the Annexure.
- The Superintendent issues a progress certificate assessing the amount due. Under clause 37.2, if the Superintendent doesn’t issue the certificate within 14 days, the progress claim itself is deemed to be the progress certificate — i.e. the claimed amount stands. (Your SOP Act may impose its own, often shorter, response deadline — and that one is statutory.)
- The Principal pays the certified amount within the time set in the Annexure.
Miss the certificate window and you can find the full claimed amount deemed payable. It’s expensive and entirely avoidable.
Extensions of time (Clause 34)
Time and delay are dealt with under clause 34. The Contractor claims an extension of time (EOT) for a qualifying delay; the Superintendent assesses it. Watch the deadline from the other side: under clause 34.5, if the Superintendent doesn’t respond to an EOT claim within 28 days, the extension can be deemed allowed in full. EOT administration is where a lot of contracts quietly lose time — and money via delay costs and liquidated damages — through missed response windows.
Security and retention (Clause 5)
Clause 5 governs security — the Principal’s protection against contractor default. It’s typically provided as retention (a percentage withheld from each payment) or as unconditional bank guarantees to an agreed value, with the amount and form set in Annexure Part A. Security is usually reduced at practical completion and released after the defects liability period. As a domain rule, a contract uses one coherent security mechanism — don’t double up retention and guarantees for the same exposure.
Defects liability (Clause 35)
Clause 35 sets the defects liability period — the window after practical completion during which the Contractor must rectify defects, with the duration (commonly 12 months) recorded in the Annexure. Track it: the security release and final payment hang off the end of this period.
Common pitfalls
Patterns I’ve seen repeated across 27 years on civil works in Australia and NZ:
- Reading unamended AS 4000. Australian contracts are frequently amended via Annexure Part B. Administer the amended clauses, not the standard ones you remember.
- Forgetting the SOP Act sits on top. Following clause 37’s 14-day rule but missing the statutory payment-schedule deadline in your state can cost you the right to dispute the claim at all.
- Missed EOT responses. Let a clause 34 claim sit past 28 days and it can be deemed allowed in full.
- Treating the Superintendent as the Principal’s advocate. On certifying functions the Superintendent must act reasonably and in good faith (clause 20). A captured certificate is a challengeable one.
- Variations directed after practical completion. The Contractor isn’t bound to comply — get the timing right.
AS 4000 vs NZS 3910
For trans-Tasman firms, the concepts map across cleanly once you know the role names:
- Superintendent ↔ Engineer. Both administer the contract and certify payment; both owe duties of fairness in their certifying role.
- Annexure Part B (amendments) ↔ Special Conditions. The project-specific override layer.
- Security of Payment Acts ↔ Construction Contracts Act 2002. The statutory regime over the contract.
- Principal ↔ Principal, Contractor ↔ Contractor.
The biggest structural difference: NZS 3910 names four parties (Principal, Engineer, Engineer’s Representative, Contractor) and ties retentions to a default schedule, while AS 4000 centres on the Superintendent and leaves security amounts to the Annexure, negotiated per project. And in Australia the Security of Payment landscape is state-by-state, where New Zealand has a single national Act. If you run jobs under both standards, modern contract administration software should handle them in one place — see the comparison in our NZS 3910 guide.
AS 4000:2024 — what’s coming
Standards Australia has circulated a draft AS 4000:2024 to modernise the 1997 form — addressing areas the original didn’t anticipate and tightening points exposed by nearly three decades of case law. Until it’s finalised and adopted into Principals’ procurement templates, AS 4000-1997 remains the standard you’ll be working under, and existing contracts will continue to reference the 1997 edition regardless. Always check the front sheet and Annexure Part B for which edition and amendments apply.
Tools that help
You can run an AS 4000 contract on spreadsheets. Plenty of firms do — until the volume compounds. A single live contract generates dozens of variations, EOT claims, monthly progress claims, defects, notices, and a transmittal register that just grows. Spreadsheet-only workflows get fragile the moment two people edit different versions, and the SOP-Act deadlines don’t forgive a missed cell.
Contract administration software handles the mechanics (security, certified amounts, valuation, approval routing) and the audit trail in one place. Gnosis is built specifically for AS 4000 and NZS 3910 — it captures every artefact, calculates security and certified values, tracks statutory response deadlines per jurisdiction, and runs Australian and New Zealand contracts in the same workspace with the right terminology and GST for each. See the features or book a 15-minute walkthrough.
FAQ
Where can I buy AS 4000? Through Standards Australia (and its authorised resellers). AS 4000-1997 and the D&C companion AS 4902 are available as PDF or hard copy.
Is AS 4000 mandatory? No. Parties can adopt any contract form, or write a bespoke one. AS 4000 is the de facto standard for construct-only work in Australia because Principals, contractors, and consultants are all familiar with it.
What’s the difference between AS 4000 and AS 4902? AS 4000 is construct-only — the Principal supplies the design. AS 4902 is the design-and-construct version, where the Contractor carries design responsibility.
Does Security of Payment override AS 4000? Yes, where they conflict. The state/territory SOP Act gives statutory payment and adjudication rights that can’t be contracted out of, and its timeframes apply over the contract’s.
Does the Superintendent have to be independent? The Superintendent acts as the Principal’s agent for some functions, but when certifying — assessing claims, valuing variations, issuing payment certificates — clause 20 requires them to act reasonably and in good faith.
Alexios Kavallaris is the founder of Gnosis, a contract administration platform built for civil engineers working under AS 4000 and NZS 3910. He’s spent 27 years in civil infrastructure across Greece, the UK, New Zealand and Australia — including eight years on New Zealand’s Waikato Expressway programme — and is a 2020 Engineering Science Award recipient (KuDos).