Draft — pending founder review. This page is excluded from the blog index and disallows indexing until approved.
NZ electrical compliance software: why general trade tools fail EWRB-registered work
You're accountable to two frameworks at once — the EWRB on the practitioner side and the Electricity Safety Regulations 2010 (administered by WorkSafe) on the install side. This post is the 5-minute version of why general trade software falls short on EWRB-registered work, where the audit risk sits now, and how KoruAI keeps the quote and the records straight without a Monday admin pile-up.
The pain
The four things NZ compliance eats in a generic trade tool
Every EWRB-registered sparky 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.
Electrical Safety Certificates trapped in the van
An ESC starts life as a printed form in the glove box, gets a wet signature, and ends up in a folder nobody owns. By the time EWRB or WorkSafe asks for the certificate behind a job, three printed versions exist — and nobody trusts the figures themselves, only that the paper trail exists.
COCs and ESCs get conflated
The client asks for a "CoC". The inspector wants an "ESC". They're not the same document, and a handwritten "CoC" that's actually on the ESC template is the audit posture that gets flagged in an investigation — even when the install is fine.
Test records scattered across jobs
A single install produces insulation resistance, earth continuity, polarity, and RCD trip-time records. They live in three folders, two inboxes, and one photo roll of meter screens. ESR 2010 expects each row filed against the source job, not rebuilt from memory on the Monday before an inspection.
Generalist trade software doesn't speak ESR 2010
Adapting an Australian or US trade management tool to NZ compliance is a documented failure mode — it doesn't know EWRB from PGDB, doesn't map to the Electricity Act 1992 or the Electricity Safety Regulations 2010, and doesn't know the difference between an ESC and a CoC. You end up maintaining a parallel spreadsheet to keep the regulator side straight.
The regulator split
Two regulators, two hats — EWRB licenses the person, ESR 2010 governs the install
An EWRB-registered electrician 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.
EWRB — the person
The Electrical Workers Registration Board licenses the individual practitioner under the Electricity Act 1992 administered by EWRB.
- Who EWRB licenses — registered electricians (including registered electrician, electrical installer, electrical service technician, and end-of-line tester classes), plus the supervision chain that lets trainees and limited-certificate holders work on EWRB-registered tasks.
- What EWRB regulates — licensing and registration, supervision obligations, operative competency requirements, complaints and disciplinary processes for individual practitioners.
- What EWRB does NOT do — the technical safety rules. EWRB licenses the person; ESR 2010 governs the install you're signing off and the test records behind it.
ESR 2010 — the install
The Electricity Safety Regulations 2010 govern the install itself, administered by WorkSafe NZ.
- The Electricity Act 1992 and the Electricity Safety Regulations 2010 (ESR) — the technical rules for electrical work, administered by WorkSafe NZ under Electricity Act oversight.
- Electrical Safety Certificates (ESCs) and Certificates of Compliance (CoCs) — the documents that prove an install is electrically safe and Code-compliant. Issued per install, requested by inspectors, held as the auditor-facing record.
- Prescribed test records — insulation resistance, earth continuity, polarity, RCD trip-time — each row filed against the source job, not retrieved from memory.
- Inspections and audit posture — WorkSafe investigations, EWRB disciplinary processes, 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 EWRB renewal pack and the current ESR amendment directly. We reference ESR 2010 and the parallel PGDB frame only to position EWRB on its own — they're separate boards covering separate practitioner scopes.
EWRB complaints and disciplinary exposure
EWRB 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 tested, signed, and supervised consistent with the Electricity Act 1992 and the class you're registered under.
ESR-driven inspection failures and rework cycles
WorkSafe and EWRB increasingly check test records, supervision notes, and the chain back to the source job — not just the dated ESC sitting in a folder. A missing test record at inspection means a re-inspection fee and a delayed sign-off on the whole job.
Audit-bundle rebuilds the night before
When an inspector asks for everything behind install #4127, you spend a full day pulling the ESC, the CoC, the test results, the supervision notes, and the site photos into a single PDF. The same work, every quarter, manually rebuilt from scratch because each piece lives in a different place.
Retention and audit posture
Retention periods on electrical records have crept upward in practice, even where the formal wording has not changed. Treat records as if WorkSafe or EWRB may ask in seven years, not three. Storage that rotates off after two years is the failure mode.
From EWRB to PGDB
Same record-keeping pattern, different trade board
The record-keeping pattern KoruAI is built around adapts across NZ trade boards — the workflow works the same whether you're registered under EWRB (sparkies) or under PGDB (plumbers, gasfitters, drainlayers). We've published the EWRB-registered review of the 2025 ESR changes and the PGDB-licensed perspective on the same workflow; pick either to see how the pattern fits your board and your prescribed certificates.
The workflow
Capture once, generate the quote + ESC + CoC + test record in one pass
The same workflow that drafts a job summary becomes the workflow that drafts the quote AND the compliance record. The sparky writes one note — KoruAI drafts against the right ESR 2010 record and EWRB registered class, you approve, the quote goes to the client and the record is filed with provenance. No re-keying, no reconstructing the bundle the night before a WorkSafe investigation.
Capture the job note in one place
A sparky writes the brief note after the install — same place, every job. Photos of the work, the meter screens, the board layout, and a paragraph on what was done. Captured once, on the device already in the van.
AI drafts the quote, the ESC, the CoC, and the test log
KoruAI reads the note and drafts the matching paperwork in one pass: the quote you send the client, the Electrical Safety Certificate, the Certificate of Compliance, the test results sheet (insulation resistance, earth continuity, polarity, RCD trip), and the supervision attestation. Drafted against your templates, mapped to the EWRB classes you're registered under and the ESR 2010 clauses that apply. The quote and the compliance record share the same source note, so the line items and the record behind them can't drift.
You approve the draft
The draft lands in your dashboard with the source note and the meter photos attached. You read, edit if anything is off, and approve. One approval per record, not one approval per keystroke — and the quote gets the same single approval before it goes out the door.
Filed with the install record attached
Every approved ESC, CoC, test log, and supervision attestation is stored with its draft history, the source job note, and the revision timestamps. When WorkSafe or EWRB asks for the bundle behind install #4127, you produce it in seconds — the same record the inspector will read.
Why KoruAI
Built for the EWRB + ESR 2010 workflow, not adapted from a generic form
NZ-based
A team that has worked with NZ trade businesses understands the EWRB framework, the Electricity Safety Regulations, and the audit posture both regulators bring. Built in Christchurch, supported in business hours NZST.
Built for the EWRB + ESR 2010 framework
Maps directly to the working obligations — ESC, CoC, prescribed test records, supervision attestation, retention, ESR test-record rows. Drafted against your templates, not adapted from a generic trade form, and the same workflow drafts the quote alongside the compliance record.
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 EWRB-registered electricians
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 EWRB classes, your ESR 2010 templates, your ESC / CoC / test record shape, and the quote your team sends on each job. Browse the pricing page when you're ready to compare, or grab the AI-readiness checklist first.