Compliance Software for Construction in New Zealand (2026): The Practical Guide

Construction is one of the most heavily regulated and most dangerous industries in New Zealand, and the compliance load that sits on a builder or trade business reflects that. Under the Health and Safety at Work Act 2015, the expectations are real and continuous, and the practical consequences of a gap are immediate: a lapsed competency, a missing certificate or an SSSP that does not match the site can stop work, fail a prequalification, or turn a WorkSafe visit into a very bad day. This guide explains what compliance software does for a New Zealand construction business, how it maps to HSWA and WorkSafe New Zealand, and how to choose a system that survives contact with a real site.

Why construction compliance is so demanding

A construction business is not managing one obligation; it is managing dozens at once, across every worker, every subcontractor, every item of plant and every job. Under HSWA, a PCBU must so far as is reasonably practicable ensure the health and safety of workers and others, and on a construction site that translates into a stack of concrete requirements: a site-specific safety plan, task analyses or safe work method statements for high-risk work, competent and inducted workers, certificates for restricted work such as scaffolding, plant that is inspected and maintained, current insurances, and notification to WorkSafe of particular hazardous work and of notifiable events.

Every one of those items has a date, an owner and a document, and every one of them can lapse. Multiply that across a growing team and a handful of concurrent jobs and you have exactly the kind of load that outruns a spreadsheet and a good memory. That is the problem compliance software is built to solve.

The SSSP and task-level safety documents

The Site-Specific Safety Plan is the document at the centre of construction compliance in New Zealand, and the one most often done badly. Head contractors routinely require an SSSP before a subcontractor can start, and it is meant to describe how health and safety will actually be managed on that particular site — the hazards, the controls, the roles, the emergency arrangements — not a generic template with the address changed. Beneath the SSSP sit task-level documents: task analyses, job safety analyses or safe work method statements for the higher-risk work, describing how each task will be done safely, understood by the workers doing it.

The failure inspectors and head contractors see most often is a safety plan that exists but bears no relationship to the actual job. Compliance software helps in two ways: it makes building a site-specific plan and task analyses quick, so there is no incentive to reach for a stale template, and it keeps every document against the job it belongs to, with worker sign-ons recorded, so a plan can actually be produced and shown to be live. A plan you can find, that matches the work, with evidence the crew was inducted into it, is the difference between a document that protects people and one that simply exists.

Competencies, certificates and inductions

If a construction business only fixed one thing with software, competency tracking would be the one that paid for it. Workers carry a range of competencies and certificates — site safety training, first aid, working at height, confined space, and for scaffolding above a certain height a Certificate of Competence — and all of it has to be current, all the time, across a workforce that turns over and moves between sites. Tracking that in a spreadsheet means one person scanning rows for approaching dates and hoping nothing was mistyped or missed.

Software watches every date at once, flags what is approaching expiry weeks in advance, and lets workers upload their own certificates so the site manager is not the single point through which every renewal must pass. The failure it prevents is concrete: a worker turned away at induction because their certificate cannot be found, restricted work done by someone whose CoC lapsed last month, a prequalification stalled because the evidence is not current. None of these reflect a business that does not care — they reflect a tracking method that depends on memory.

Onboarding subcontractors without inheriting their risk

Most builders run on subcontractors, and every subcontractor is a compliance risk you cannot see directly. Their insurances, their workers' competencies, their safety documents — if any of it is out of date, the exposure can flow up to the head contractor who let them on site, because under HSWA duties overlap and cannot be contracted away. Chasing that information by email and spreadsheet is slow and leaky, and it tends to be done once at the start and never checked again.

Compliance software turns subcontractor onboarding into a defined, repeatable process: you send a secure link, the subcontractor uploads their insurances, competencies and safety documents, and the system verifies and tracks them, flagging anything that lapses. Instead of a folder of documents collected once and trusted forever, you get a live view of whether each subcontractor is currently compliant — and a record that you checked. For a head contractor carrying overlapping duties, that is not administrative tidiness; it is the evidence that you exercised the care the law expects.

Prequalification: SiteWise, Site Safe and getting on the list

For a growing construction business, a large share of compliance effort goes not into a regulator visit but into prequalification — proving to a head contractor or principal that you are safe to engage before you are even shortlisted. In New Zealand this is often run through schemes such as SiteWise and Site Safe, and increasingly a shared prequalification approach, and they all want the same underlying things: current insurances, a health and safety management system, safety documents, competencies and evidence of a safety record. When that information lives in a spreadsheet and a filing cabinet, every prequalification becomes a scramble that ties up your best people for days and still risks being incomplete. When it lives in compliance software, assembling a prequalification pack is a matter of exporting what is already current and organised. Businesses that can prequalify quickly and completely win more of the work they chase, and lose fewer opportunities to a deadline they could not meet in time.

Plant, inspections and notifiable events

Plant and equipment carry their own obligations: pre-start checks, scheduled inspections, and maintenance. Recording those checks on paper that lives in a cab or a site container makes them almost impossible to produce later. Software lets you schedule and log plant inspections and keep the records against the item, so a question about a particular machine has an answer. And when a notifiable event occurs — a death, a serious injury or illness, or a notifiable incident as defined in HSWA — the duty to notify WorkSafe and preserve the site is immediate; a system that already holds your SSSP, inductions and records makes meeting that duty far less frantic.

Inductions and toolbox talks: proving the everyday

Beyond the big-ticket competencies and the SSSP, construction compliance is made up of dozens of small, everyday records that are easy to do and easy to lose: site inductions, toolbox talks, pre-start meetings, plant pre-starts, hazard reports. Individually none is hard; collectively they are exactly the evidence a regulator or a head contractor asks for after an incident, and exactly the evidence a paper-based site cannot reliably produce. Software lets you capture inductions and toolbox talks against the job and the person, on a phone, at the moment they happen, so the record exists the instant the conversation does. When someone asks whether a crew was inducted and briefed on the fall-from-height controls, the answer is a search, not an archaeology project.

Getting your crew to actually use it

The best system fails if the people on the tools will not touch it. In construction, the compliance information is generated at the coalface — the worker whose certificate just renewed, the foreman running the toolbox talk, the subbie arriving on site — so the software has to work on a phone, in the weather, in seconds. If adding a certificate or signing onto an SSSP is quick and obvious, it gets done where the work happens and the data stays current. If it is awkward or tied to the site office computer, everything funnels back through one overloaded person and the system falls behind reality within a fortnight. This is the single most important thing to test before you buy: put the actual screens in front of an actual foreman and an actual subbie, on a phone, and watch whether they can do the everyday tasks without help.

The real cost of getting it wrong

The numbers are serious. HSWA penalties are significant, and beyond the penalties a serious incident brings a WorkSafe investigation, prosecution risk, delay and lasting reputational harm. A lapsed competency or insurance can get a crew removed from a site and cost a head-contractor relationship built over years. A failed prequalification loses a tender before you have priced it. Against all of that, the cost of software that would have flagged the renewal is trivial — which is the honest frame for the decision.

Why generic software struggles on site

A blank, configure-it-yourself compliance platform sounds appealing until the reality of setting it up for construction lands. Construction has a specific vocabulary and a specific set of documents — SSSP, task analyses, competencies, Certificates of Competence, plant records — and a generic or overseas tool asks you to build all of that structure yourself, or to translate from another country's system, which is weeks of work a busy builder does not have. The result is predictable: the flexible tool that could do anything ends up half-configured and abandoned, and the crew goes back to the spreadsheet. The alternative is software that already understands New Zealand construction and HSWA from day one — that knows what an SSSP is and when a head contractor will want it, that treats competencies and Certificates of Competence as first-class records, that onboards subcontractors the way a head contractor actually needs. Fluency out of the box is the difference between a system adopted in a week and one written off in a month.

Overlapping duties and the reality of shared sites

One feature of HSWA that catches businesses out is that duties overlap and cannot be transferred away by contract. On a shared site, more than one PCBU can hold a duty to the same workers at the same time, and each is expected to consult, cooperate and coordinate with the others so far as is reasonably practicable. In practice that means a head contractor cannot simply assume a subcontractor has their own house in order, and a subcontractor cannot assume the head contractor's plan covers them. Compliance software supports this shared-duty reality by giving everyone on the job a common, current picture: the head contractor can see which subcontractors are compliant and which are not, subcontractors can see what the site requires of them, and the evidence of consultation and coordination — inductions, briefings, shared documents — is captured rather than assumed. When something goes wrong, being able to show that you consulted, cooperated and coordinated is exactly what HSWA expects, and exactly what paper struggles to prove.

What good looks like on site

Once it is in place, the change shows up in the everyday. A worker's certificate is on file before they start, not chased at the gate. An SSSP for the job is built in minutes and signed on a phone, not copied from the last site. A subcontractor's insurance is verified before they arrive, and flagged automatically when it is about to lapse. When a head contractor or WorkSafe asks for evidence, it is a few clicks, not a scramble through folders and containers. The site runs the same, but the paperwork stops being the thing that trips you up — and the head contractor relationships that depend on you being reliably compliant get easier to keep.

How to choose it

A handful of plain tests separate software that earns its place from software you will resent. Is it built for New Zealand construction — SSSP, competencies, CoC, prequalification — or a generic or overseas tool you must bend into shape? Does it build and store an SSSP and task analyses against each job, or just hold files? Does it actively track competency and insurance expiries and remind you? Will the people on site actually use it on a phone, or does everything route through the office? Can subcontractors upload their own documents through a link? And does the pricing make sense for a business your size, ideally with a free trial so you can prove it on your own jobs first?

Getting started without disruption

The mistake that makes any software change painful is trying to move everything at once. The better path is to load your live obligations first — the insurances, competencies, certificates and current SSSP in force, with their dates — so the reminders start working immediately and you feel the value in the first week. Historical records can follow or be archived. Add your workers and let them upload their own certificates, connect your regular subcontractors, and within days the business has a live compliance picture where it had a spreadsheet and a filing cabinet. It is an afternoon to start, not a project to dread.

Compliance as a way to win work

It is worth remembering that construction compliance in New Zealand is not only about avoiding a WorkSafe problem; increasingly it is about winning work. Head contractors and principals choose subcontractors they can trust to be safe and to keep their paperwork current, and prequalification schemes exist precisely so clients can filter for that. A business whose competencies, insurances and safety documents are always in order, and who can produce a prequalification pack the same day it is asked for, is simply an easier and more attractive business to engage. So the software that keeps you out of trouble is the same software that helps you onto more tender lists — compliance and commercial advantage pull in the same direction.

Where Complys fits

Complys is compliance software built for New Zealand construction: it builds and stores your SSSP and task analyses against each job with worker sign-ons, tracks competencies, certificates and insurances with expiry reminders, onboards subcontractors through a secure link with their documents verified, and produces a site-ready or prequalification-ready pack on demand — shaped around HSWA and WorkSafe rather than a generic tool you configure yourself. It is free for 90 days, so you can load your own workers and jobs and judge it on your own sites.

The bottom line

Construction compliance in New Zealand is heavy, constant and high-stakes, and a passive spreadsheet leaves the whole burden of remembering on one person. Compliance software carries that load for you: an SSSP built and kept against the job, competencies watched, subcontractors verified, and a complete pack ready whenever a head contractor or WorkSafe asks. Whether you choose Complys or something else, hold it to the same tests — built for New Zealand construction, active rather than passive, genuinely used on site, and priced so it pays for itself the first time it stops a competency from lapsing or a crew from being turned away.