NZ Pre-Tender Risk Register — 30 Minutes Saves $20-40k Per Build

sp8002
2 hours ago
7 min read

Most NZ residential builders run a pre-start meeting per trade and a variation register once the build is underway. Very few run a pre-tender risk register — the document that sits between the consent issue and the trade quotes, identifying the variation risks on paper before any subcontractor is asked to price. 30 minutes per build. $20-40k saved on a typical $1.5M residential.

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

What you'll learn in this post

The variation cost curve through a build
What goes in the register — six headings
A worked example

Quick answer: A pre-tender risk register is a single 2-4 page document that sits between consent issue and trade tender — naming drawing inconsistencies, code-clause gaps, manufacturer-warranty conditions, long-lead supply items, site-specific conditions, and spec ambiguities. On a typical $1.5M NZ residential, the register takes 30-60 minutes to build and saves $20,000-40,000 of variations across the build. The leverage is highest on residential precisely because most residential builds don't run one.

There are three risk-management documents most NZ residential builders run as standard. The variation register — opened on day one of the build, updated each week with the variations raised and resolved. The trade pre-start sheet — built per trade, signed before the trade lands on site. The defect-and-snag list — opened at practical completion and closed at end-of-defects.

The document that's mostly missing from this set, and that delivers the highest leverage per minute spent, is the pre-tender risk register. It sits in the gap between consent issue and trade quotes — the 2-4 week window before the head contractor solicits subcontract prices — and identifies the variation risks that exist in the documents before any subcontractor is asked to look at them.

It takes 30 minutes per build. On a typical $1.5M residential, it saves $20,000-40,000 of variations across the build. The ratio of effort to return is the highest in the construction risk-management toolkit.

The variation cost curve through a build

Variations on a NZ residential build follow a predictable cost curve depending on when they're identified:

| Stage | Cost to resolve | Why | |---|---|---| | Pre-tender (before quotes solicited) | $0-$2k | Architectural redraw, engineer's clarification memo | | Tender stage (during pricing) | $500-$5k | Trade-specific clarifications, RFI to designer, re-quote | | Pre-trade-start (after award) | $1k-$10k | Drawing markup, scope adjustment letter, programme re-sequence | | On site (during construction) | $5k-$50k+ | Programme delay, re-work, engineer's variation, council re-inspection | | Post-construction (defect, weathertightness, warranty) | $20k-$400k+ | Re-clad, re-roof, decant, legal |

Each step costs roughly 5-10× the previous step. The pre-tender risk register catches variations at the cheapest step in the curve.

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?

What goes in the register — six headings

The pre-tender risk register is a single document, typically 2-4 pages on a residential build, that captures six categories:

1. Drawing inconsistencies. Where two drawings disagree, or where the architectural and structural sets call up different products, materials, or specifications. The register names the inconsistency, identifies which drawing should govern under the documents-hierarchy clause of the contract (NZS 3910 §6.2 or equivalent), and flags the items that need designer clarification.

2. Code clauses that aren't fully addressed in the documents. E2/AS1 §9 cladding junctions are the most common gap — the drawings show the cladding system but don't fully detail the inter-storey junction, the cladding-to-cladding interface, or the deck-to-wall upstand. The register names the clause, identifies the missing detail, and flags the design clarification needed.

3. Manufacturer-warranty conditions. Every product-warranted element on the build (roof sheet, joinery, membrane, tanking, cladding system) carries warranty conditions. The register lists each warranted product, the manufacturer's stated installation requirements, and any condition that's at risk if the install isn't precisely controlled (e.g. H1.2 only for purlins under metal roofing per MRM CoP §4.5).

4. Long-lead supply items. Engineered I-joists (5-7 weeks). Premium aluminium joinery (8-12 weeks). Imported stone or stainless components (variable, often 10-16 weeks). The register names the item, the lead time, the latest order date that protects the programme, and the trigger document (engineer's plan, architect's selection schedule) that has to be issued to start the order clock.

5. Site-specific conditions. Marine atmosphere (Waiheke, Northland coast, exposed Wellington), heritage overlays, Resource Consent conditions on working hours, neighbour interfaces, access constraints. The register names the condition and the trade scopes that need to reflect it.

6. Spec ambiguities likely to produce a quote variation. The "all 20-series block UNO" foundation note while the detail sheets call up 25-series. The "internal red oxide primer" steel spec while the engineer's coating spec calls duplex. These are the items the register surfaces before the blocklayer and the steel fabricator look at the drawings.

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?

A worked example

A recent Auckland residential, $1.4M head contract value. The pre-tender risk register identified 23 items across the six categories.

Eight items were resolved by a single RFI to the architect (a 90-minute meeting), with redrawn details issued in 2 weeks:

Inter-storey flashing detail clarified
Steel coating spec confirmed against engineer's Appendix B
25-series block confirmed on all retaining walls
Engineered I-joist order date set against engineer's plan issue date

Membrane installer's deck-to-wall detail requested and reviewed

| Item | Cost | |---|---| | Additional architect's design-fee | $1,500 | | Estimated variation savings across the build (based on similar projects) | $25,000-35,000 | | Net leverage | 15-25×

Who builds the register

The register can be built by:

The head contractor's principal (if they have the 4-8 hours of focused time and the technical reading skills)
An external QS or construction consultant on a fee-for-service basis ($2,000-5,000, typically returning 4-8× in saved variations)
The architect or engineer as part of the design team (sometimes built into the fee, more often not)

The discipline matters more than the source. A risk register built by the contractor, reviewed by the architect, and signed off before tender close is the document that survives the build.

What to do with the register once it's built

Three uses:

As a quality check on the design documents — drawing inconsistencies and code-clause gaps feed back to the architect or engineer for resolution before the tender goes out
As a tender-package addendum — manufacturer warranties, long-lead items, site conditions, spec ambiguities flagged in the tender documents so subcontractors price with the information visible
As the seed for the trade-by-trade Pre-Trade-Start Compliance Sheets that follow at award

The process is a 30-60 minute discipline per build: read the consent set end-to-end before issuing the tender package; note items in the six categories above as you read; send the document to the architect or engineer as an RFI; update with the answers and circulate to the design team as the agreed risk position; carry the document forward into trade engagement.

A note on residential vs commercial

The pre-tender risk register is more common practice on commercial work, where the QS or contract administrator typically builds it as part of the tender preparation. On residential it's rarer — most residential builds don't have a separately-engaged QS. The leverage is higher on residential precisely because no-one else is doing it. The cost-to-benefit ratio on the work we've reviewed is consistently 10:1 or higher.

What to put on the register every time

Six headings, every build:

Drawing inconsistencies
Code clauses not fully addressed
Manufacturer-warranty conditions
Long-lead supply items with order trigger dates

Site-specific conditions
Spec ambiguities likely to produce a quote variation

Even a one-page register with three bullets under each heading does more than no register at all. The discipline is in the reading, not the formatting.

FAQ — NZ pre-tender risk register

Q1: When in the build cycle should the pre-tender risk register be built? After consent issue, before the head contractor solicits subcontract prices. Typically a 2-4 week window. Built earlier than consent issue and the design isn't stable; built later and the subcontractor quotes are already in.

Q2: What's the difference between a pre-tender risk register and a project risk register? The pre-tender risk register is design-focused — drawing inconsistencies, code-clause gaps, spec ambiguities. The project risk register that runs through the build covers operational risks (weather, supply chain delays, sub-contractor performance). Different documents, different purposes.

Q3: Who signs off the pre-tender risk register? Best practice is a three-way sign-off: the head contractor's principal (built or commissioned it), the architect or engineer (reviewed and answered the design RFIs), the principal/client (acknowledges the residual risks carried forward into tender). All three signatures on one cover page.

Q4: Does the pre-tender risk register need to be disclosed to tendering subcontractors? Items affecting trade scope (manufacturer-warranty conditions, code gaps relevant to the trade, long-lead items the trade depends on) should be included in the tender package. Items affecting only the head contractor's risk position (programme contingency, dispute exposure) typically stay internal to the principal-side team.

Q5: How does the pre-tender risk register interact with the NZS 3910 §14 variation procedure? A risk identified pre-tender and resolved in the tender documents typically eliminates the §14 variation downstream. A risk identified pre-tender and accepted into the tender documents as a known item is no longer a §14.2.1.1.d (changed conditions) trigger when it surfaces — the contractor priced with full disclosure.

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