NZ plumbing compliance software: why general trade tools are a liability
You’re accountable to two frameworks at once — the PGDB on the practitioner side and the NZ Building Code (including E2/AS1) on the install side. This post is the 5-minute version of why general trade software falls short, where the audit risk sits now, and how KoruAI keeps the records straight without a Monday admin pile-up.
The pain
The four things NZ compliance eats in a generic trade tool
Every PGDB-licensed plumber recognises at least two of these from the last inspection cycle. They aren’t dramatic failures — they’re the slow stand-up of admin overhead that nobody scheduled time to fix.
Certificates of Compliance trapped in paper
A CoC starts on a printed form in the van, gets a wet signature, and lands in a folder nobody owns. By audit time nobody trusts the figures themselves — only that the paper trail exists.
Test records scattered across jobs
A single install may produce pressure test, gas tightness, drainage test, and asbestos/existing-pipe records. They live in three folders, two inboxes, and one memory. PGDB asks for the gas tightness record from job #3471 and you scroll for an hour.
Inspection-ready bundles take a full day
When PGDB or a Building Inspector asks for the records behind a job, you spend a day pulling the CoC, the test results, the photos, and the site notes into a single PDF. The same work, every quarter, manually rebuilt from scratch.
Generalist trade software doesn’t speak NZ
Adapting an Australian or US trade management tool to NZ compliance is a documented failure mode — it doesn’t know PGDB from EWRB, doesn’t map to the Plumbers, Gasfitters and Drainlayers Act 2006, and doesn’t reference E2/AS1. You end up maintaining a parallel spreadsheet to keep the regulator side straight.
The regulator split
Two regulators, two hats — PGDB licenses the person, the Building Code governs the install
A PGDB-licensed plumber, gasfitter, or drainlayer is accountable to two frameworks simultaneously. The line between them shapes which paperwork survives a complaint and which disappears — get it wrong and you “comply” with one and breach the other.
PGDB — the person
The Plumbers, Gasfitters and Drainlayers Board licenses the individual practitioner under the Plumbers, Gasfitters and Drainlayers Act 2006 administered by PGDB.
- Who PGDB licenses — registered plumbers, registered gasfitters, and registered drainlayers, across the PGDB classes and scopes of work.
- What PGDB regulates — licensing and registration, supervision obligations, operative competency requirements, complaints and disciplinary processes for individual practitioners.
- What PGDB does NOT do — the technical building rules. PGDB licenses the person; the NZ Building Code (including E2/AS1) governs the install you’re signing off.
NZ Building Code — the install
The NZ Building Code governs the install itself, administered by MBIE via Building.govt.nz.
- The NZ Building Code — the technical rules for plumbing and drainage work in NZ, administered by MBIE under the Building Act 2004. Compliance is verified at consent and inspection by Building Consents Authorities (BCAs).
- Acceptable Solutions (e.g. E2/AS1 for external moisture, G13 for plumbing and drainage) — the prescribed paths that, if followed, satisfy the Building Code. Deviating from an Acceptable Solution requires an Alternative Solution.
- Certificates of Compliance and Code Compliance Certificates — the documents that prove the install satisfies the Building Code. Issued to the client, requested by BCAs, and held as the auditor-facing record.
- Inspections and audit posture — BCA inspections, PGDB investigations, and the records inspectors ask for. Retention expectations run for the life of the installation plus several years for installer records.
What’s at stake now
The paperwork risks that move the needle in 2026
Treated at a high level so the framing is durable across legislative rewording — for clause-level specifics, read your PGDB renewal pack and the current Building Code amendment directly. We reference E2/AS1 external moisture and the parallel EWRB frame only to position PGDB on its own — they’re separate boards covering separate practitioner scopes.
PGDB complaints and disciplinary exposure
PGDB complaints follow paperwork failures that look sloppy only after the fact. The risk isn’t the install — it’s the records proving the install was checked, signed, and supervised consistent with the Plumbers, Gasfitters and Drainlayers Act 2006.
BCA inspection failures and rework cycles
Building Consents Authorities increasingly check test records, supervision notes, and the chain back to the source job note — not just the dated CoC sitting in a folder. A missed test record at inspection means a re-inspection fee and a delayed sign-off on the whole job.
E2/AS1 external moisture and weathertightness
E2/AS1 governs weathertightness for the plumbing-side penetrations (showers, decks, balconies, pipework through cladding). A non-conforming detail here is a weathertightness risk that surfaces months later — and the audit trail will say whether the install matched E2/AS1 or not.
Retention and audit posture
Retention periods on plumbing and drainage records have crept upward in practice, even where the formal wording has not changed. Treat records as if PGDB or a BCA may ask in seven years, not three. Storage that rotates off after two years is the failure mode.
From PGDB to EWRB
Same record-keeping pattern, different trade board
The record-keeping pattern KoruAI is built around adapts across NZ trade boards — the works the same whether you’re licensed under PGDB (plumbers, gasfitters, drainlayers) or under EWRB (electricians). We've published the EWRB-licensed perspective on the workflow; the same workflow fits a PGDB-licensed practitioner once you swap in your CoC, test record, and supervision templates.
The workflow
Capture once, generate the CoC + test record + supervision note in one pass
The same workflow that drafts a job summary becomes the workflow that drafts a compliance record. The plumber, gasfitter, or drainlayer writes one note — KoruAI drafts against the right Building Code and PGDB template, you approve, the record is filed with provenance. No re-keying, no reconstructing the bundle the night before a PGDB investigation.
Capture the job note in one place
A plumber writes the brief note after the install — same place, every job. Photos of the work, the test results, and a paragraph on what was done. Captured once, on the device already in the van.
AI drafts the CoC, the test log, and the BC-facing record
KoruAI reads the note and drafts the matching compliance record: the Certificate of Compliance, the test results sheet (pressure / gas tightness / drainage), and the supervision attestation. Drafted against your templates, mapped to the PGDB classes you’re registered under and the Building Code clauses that apply.
You approve the draft
The draft lands in your dashboard with the source note and the test results attached. You read, edit if anything’s off, and approve. One approval per record, not one approval per keystroke.
Filed with the install record attached
Every approved CoC, test log, and supervision attestation is stored with its draft history, the source job note, and the revision timestamps. When PGDB or a BCA asks for the bundle behind install #3471, you produce it in seconds — the same record the inspector will read.
Why KoruAI
Built for the PGDB + Building Code workflow, not adapted from a generic form
NZ-based
A team that has worked with NZ trade businesses understands the PGDB framework, the NZ Building Code, and the audit posture both regulators bring. Built in Christchurch, supported in business hours NZST.
Built for the PGDB + Building Code framework
Maps directly to the working obligations — CoC, test records, supervision attestation, E2/AS1 detail, retention, BCA inspection paperwork. Drafted against your templates, not adapted from a generic trade form.
Reach a real person
You can email the team behind the build at hello@koruaitrades.com. Replies come from a real person, usually the same day. No support-ticket queue, no chatbot intermediary.
Common questions
FAQ for NZ plumbers, gasfitters, and drainlayers
Next step
See what the rollout looks like for your business
The diagnostic, the 30-day sprint, and the ongoing managed plan all ship the same record-keeping workflow — applied to your PGDB classes, your Building Code templates, your CoC / supervision / test record shape. Browse the pricing page when you're ready to compare, or grab the AI-readiness checklist first.