NZIA Architect Variation Review under NZS 3910 §14 — the defensible CA workflow

sp8002
2 hours ago
7 min read

High-end residential alteration work in Auckland's character suburbs produces 15-40 contractor-issued variations across a build. For an NZIA architect in the CA role, each variation is a §14 determination that has to survive a PI claim three years later. A 20-minute structured review per variation is the difference.

By Steve Parker · Trueworks · NZ construction estimation · 5 min

What you'll learn in this post

What the CA role asks of an NZIA architect under NZS 3910:2023
The four typical variation patterns on Auckland character-suburb work
The 20-minute structured variation review

Quick answer: An NZIA architect in the contract-administration role under NZS 3910:2023 has to determine each §14 variation impartially, with the determination written so it would hold up if examined by an adjudicator, an outside CA, or a professional-indemnity claim handler. A 20-minute structured review — naming the §14.2 sub-clause, the documents reviewed, the §14.4 valuation method, and the §10.3 time effect — is the discipline that protects the architect's CA position over the life of the build and three years past practical completion.

Auckland's character suburbs (Parnell, Remuera, Herne Bay, Mt Eden, Epsom, Mission Bay) carry a particular mix of construction work — heritage residences, large modern alterations, embassies and consulates, the occasional commercial-into-residential conversion. Most of it carries a build value in the $2-4M range, runs under NZS 3910:2023 with the architect as the named Engineer to the Contract, and produces between 15 and 40 contractor-issued variations across the build.

For an NZIA-registered architect sitting in the CA role, each of those variations is a §14 determination — a decision that has to be defensible if it ever lands in front of an adjudicator, a court, or a professional-indemnity insurer three years from practical completion. A poorly-structured variation review isn't an immediate problem. It's the file that gets opened by the next CA, or by the PI claim handler, and used to assess whether your determination was reasonable.

What the CA role asks of an NZIA architect under NZS 3910:2023

NZS 3910:2023 names the Engineer to the Contract as the party who, among other duties:

Determines variations under §14
Acts impartially between principal and contractor (§6.1.1)
Reviews payment claims under §12
Determines extensions of time under §10.3

The NZIA's own Practice Notes and the Architect's Code of Ethics overlay this with the architect's separate duties to the client. The two roles are not automatically in conflict — but they are not the same. The CA role exists to determine, not to advocate. A variation determined in the client's favour because the client is paying the fee is the kind of finding that gets used against the architect at a later dispute. Conversely, a variation rolled to the contractor because "it's easier" is the determination that surfaces in the principal's later claim against the architect for failure to administer the contract impartially.

Send us your stamped drawings + the supplier's quote. We'll return a code-cited Quote-Check packet inside 5 business days. Free for first-time customers. NDA available, NZ-hosted processing.
→ Email steve@trueworks.co.nz or submit at trueworks.co.nz

💡 Caught something similar on your job?

The four typical variation patterns on Auckland character-suburb work

In our experience reviewing CA files on this tier of residential alteration, four variation patterns produce most of the §14 contention:

1. Heritage discovery variations. Most character residences hide non-compliant or unanticipated structure behind the linings. Asbestos, rotten subfloor, undersized footings, retrofitted electrical without a permit — these surface during demolition. The contractor's variation is properly under §14 (changed conditions, §14.2.1.1.d). The architect's CA determination has to test whether the principal's documents could reasonably have anticipated the condition. The honest answer is often "no" — and that's a principal-side cost, not a contractor-side problem.

2. Spec ambiguity variations. A drawing shows a detail one way, a specification reads another, and the contractor priced what they read. §6.2 of NZS 3910 sets the documents hierarchy — but the hierarchy only resolves the conflict, it doesn't make the variation go away. If the contractor priced reasonably off the available documents, the variation is valued at the price difference between what was priced and what's now required.

3. Programme-driven variations. Long-lead items (premium aluminium joinery, custom steel, imported stone) ordered to a programme that the contractor priced. If the programme slips on the principal's side — late instructions, late selections, late council sign-off — the §14 + §10.3 variation lands. Most of these can be avoided with a written selections schedule and dates, signed at award.

4. Coordination interface variations. Where one trade hands off to another and the interface ownership wasn't agreed. Roof-to-wall flashing junctions, steel-to-timber framing connections, tanking-to-cladding interfaces. The contractor priced one side, didn't price the other, and the variation appears when the trades meet on site.

The Trueworks Per-Project pack is NZ$8,000–12,000 for the full estimation, risk register, contingencies table and pre-trade-start sheets across all major trades on a build. Builders typically save NZ$10,000–20,000 of their own time per job.
See pricing on trueworks.co.nz →

📋 Want this kind of risk review on every trade?

The 20-minute structured variation review

The discipline that protects the architect's CA position is the same review pattern on every variation, written down, filed. The 6-step protocol:

| Step | Action | Cite | |---|---|---| | 1 | Restate the variation in your own words; cite drawing reference + spec clause; identify §14.2 sub-clause | §14.2.1.1.a-d | | 2 | Read the principal's documentation — drawing revision, spec page, code clause (E2/AS1, NZS 3604, etc.) | §6.2 documents hierarchy | | 3 | Test what the contractor reasonably priced against the issued-for-tender documents | §14.2.1.1.a-d | | 4 | Test the valuation method — schedule rates → analogous rates → first principles → daywork | §14.4 | | 5 | Determine the time effect separately from the cost | §10.3 | | 6 | Write the determination — 3-5 sentences, signed, dated | Engineer to the Contract |

The whole thing fits on one A4 page. After 20 variations across a build, you have a 20-page file that an outside reviewer can follow.

Heritage-suburb-specific PI exposures

Two patterns we see often: heritage-fabric reinstatement, where character overlays require "match existing" — a defensible spec at concept, an undefined spec at construction. The variation lands when the contractor asks for the colour, profile or timber species and the answer wasn't pre-agreed. And neighbour-driven scope creep

— close-set inner-suburb sites mean boundary disputes, party-wall conditions, neighbour-imposed access restrictions all turn into mid-build variations. The CA can only determine on what was in the principal's documents at tender; late neighbour conditions are typically a §14.2.1.1.b (instructed change), not a contractor problem.

What to check before issuing the next variation determination

Six elements, every variation: the §14.2 sub-clause named; the documents reviewed with revision numbers and dates; the §14.4 valuation method named; the §10.3 time effect determined separately; a note on impartiality (what facts considered, what rejected and why); and the architect's signature and date as Engineer to the Contract, not as the client's agent. None of this is exotic — all of it is the standard a PI claim handler will test against if the file is ever opened.

FAQ — NZIA architect variation review under NZS 3910 §14

Q1: Can the architect refuse to act as the Engineer to the Contract under NZS 3910? Yes. The CA role is a separate appointment from the architect's design agreement. Some NZIA practices decline the CA role on jobs over a certain value or risk profile because the impartiality requirement under §6.1.1 sits in tension with the architect's client relationship. If declined, a separate independent CA must be named.

Q2: Does the architect's PI insurance cover CA-role determinations? Most NZIA-practice PI policies cover CA work — but the policy wording matters. CA determinations are decisions, and a determination found to have been made without impartiality or without reference to the contract documents is the most common PI exposure on residential work. Confirm with your insurer that CA work is named.

Q3: How long does the architect have to determine a §14 variation under NZS 3910:2023? The 2023 edition tightened the determination timeframes. The Engineer is expected to determine variations within reasonable time, and most §14 determinations on residential work close within 10-15 working days from the contractor's notification. A determination held open for 60+ days becomes a §13 dispute.

Q4: Is a verbal instruction from the architect on site a valid §14 variation? A verbal instruction is a valid contractual basis for a variation but the Engineer must confirm it in writing within a reasonable period. Best CA practice is to issue all variation instructions in writing first, with verbal-then-written confirmation used only when site urgency requires.

Q5: What records must the architect keep to defend a §14 determination at a later dispute? Six items: the contractor's variation request; the documents reviewed (drawings + revisions + dates); the §14.2 sub-clause cited; the §14.4 valuation method and the calculation; the §10.3 time-effect determination; and the signed-dated determination itself. These six items on one page survive the PI claim handler's review.

Get a free Quote-Check on your next job

Drawings + one supplier quote + 5 business days = a code-cited risk packet ready for your pre-start meeting.

Free for first-time customers. No commitment. NDA available. Files NZ-hosted, deleted after 30 days unless you ask us to retain them.

→ Email steve@trueworks.co.nz or start the intake at trueworks.co.nz

About Trueworks

Trueworks is built by Steve Parker — 20 years on the analytical side of NZ construction. Variation reviews, contract advisory, programme review, and AI-augmented document workflows. Trueworks is the productisation of that practice for builders: same defensible analysis, at a price and pace a NZ builder can actually use.

I answer every email personally during pilot phase. If you've got a quote you want a second opinion on, the easiest way to find out if Trueworks is useful is to send it.

📧 steve@trueworks.co.nz · 🌐 trueworks.co.nz