Contractor Health and Safety Management Plan NZ: What Principals Actually Want

Your mobilisation date is two weeks out and the principal's H&S rep emails asking for your "contractor health and safety management plan NZ." You send your company H&S manual. It comes back rejected. Sound familiar? Understanding what a principal is actually asking for — and why generic documents fail — is the difference between starting on time and sitting on the bench while your crew waits.

Here's the first thing to get straight: there is no document called a "contractor health and safety management plan" mandated by name anywhere in the Health and Safety at Work Act 2015 (HSWA). That phrase is procurement language, not legislation. What the principal is almost always asking for is a bundle of documents — and the backbone of that bundle is your SSSP.

What "H&S Management Plan" Actually Means in NZ — and the SSSP NZ Document Behind It

When you're standing at the site office counter on day one of a commercial fitout or civil earthworks package, the H&S advisor isn't going to accept a 40-page company policy document and call it done. What they want to see is a coherent package that proves you've thought about this site, this scope, and these hazards.

In NZ practice, that package typically contains four things:

Your SSSP (Site-Specific Safety Plan) — how H&S will be managed across the project
Your Task Analyses (TAs) for high-risk activities, attached to the SSSP
Your company H&S policy or system overview, as background
Current prequalification evidence — a valid SiteWise assessment or equivalent

Australia handles this differently. Under the model WHS Regulations (r309), the principal contractor must prepare a WHS Management Plan for construction projects over a set cost threshold. It's a regulated document with a regulated name. NZ has no equivalent threshold or mandated document name — the SSSP is driven by principal requirements and procurement practice, not by a specific regulation naming it.

That distinction matters. If you're working across the Tasman, check the requirements in the relevant state. In NZ, the weight falls on your PCBU duties under HSWA — primarily the primary duty of care under s36 and the obligation to consult, cooperate and coordinate with other PCBUs under s34.

SiteWise prequalification explained

What Goes Inside a Site Specific Safety Plan — and the Order It Needs to Follow

At the 8am pre-start on day one of any new package, the site manager will flip through your SSSP. If they can't find the hazard register inside two minutes, or the emergency contacts page is missing, you've already lost credibility. Structure matters.

Here's the order a well-built SSSP follows:

Step 1: Project and PCBU details — names, addresses, roles, licence numbers. This establishes who's on the hook under s36.

Step 2: Roles and responsibilities — who is the H&S rep, who signs off on TAs, who calls WorkSafe if something goes wrong.

Step 3: Scope of work and project phases — written for this job, not lifted from a template. If you're doing structural steel in Stage 1 and services fitout in Stage 2, say so.

Step 4: Site hazard register with controls — each hazard listed with controls applied through the hierarchy. PPE sitting at the bottom is fine; PPE as your only control is a rejection reason.

Step 5: Critical risk identification — height work, excavations, lifting operations, traffic management. These need to be called out explicitly with reference to attached TAs.

Step 6: Overlapping duties and coordination arrangements (s34) — this is the section most subcontractors forget entirely. Who are the other PCBUs on site? How are you coordinating with them? How does the main contractor's induction and site rules integrate with your plan?

Step 7: Notifiable works and asbestos check — confirm whether any notifiable work exists and whether an asbestos survey has been completed before commencement.

Step 8: Induction, training, competency records — what training is required, who holds it, where the records are kept.

Step 9: Emergency response plan, incident reporting, consultation and review arrangements — including how the SSSP gets updated as phases change.

SSSP vs SWMS — Which Document Do You Actually Need?

This question comes up every time a subcontractor gets a document request from a main contractor. The short answer: you probably need both, and they serve different purposes.

Document	Scope	Covers	Updated when?
SSSP	Whole project or site	H&S management system for the job	Phases change, new hazards emerge
SWMS (AU) / TA (NZ)	Single high-risk task	Step-by-step hazard controls for that task	Task changes, incident occurs, 12 months
Company H&S Manual	Business-wide	Policy, systems, general procedures	Annually or after significant change

In NZ, what Australians call a SWMS (Safe Work Method Statement) is most commonly called a Task Analysis or TA. Some principals do use "SWMS" — particularly those with Australian parent companies or working on joint-venture projects — but the document function is the same: identify the task steps, identify the hazards at each step, and record the controls you'll apply.

The SSSP sits above the TA. It references which tasks require a TA and holds the completed TAs as attachments. If your SSSP references a TA for elevated work platforms but the TA isn't actually attached and signed, expect a rejection.

How to write a task analysis for high-risk construction work

Why Generic Contractor Safety Plans Get Rejected Every Time

Before the Thursday afternoon progress meeting where the principal's H&S rep reviews submissions, your SSSP goes through a checklist — whether formal or informal. Here are the real reasons documents come back:

The "S" is missing. The most common rejection reason, by a significant margin. The plan reads as a generic template with the company logo dropped in. Street addresses are wrong, the scope describes a different type of work, and the hazard register includes risks that don't apply to this site. The "site-specific" in SSSP is not optional.

s34 coordination is absent. The plan is written as if the contractor is the only PCBU on site. There's no reference to the principal's site rules, no mention of how conflicting work will be managed, and no coordination with other trades.

Hazard controls stop at PPE. A hierarchy of controls exists for a reason. Eliminating or isolating a hazard is expected to be considered first. When every line in the hazard register ends with "wear PPE," it tells the reviewer you haven't applied the hierarchy — you've just ticked a box.

Cut-and-paste errors. The plan references the wrong site address, a previous project name, or a client that has nothing to do with this job. This happens more than it should, and it tells the principal your document process is not in control.

Static document, never updated. An SSSP is a living document. If you submit it at mobilisation and never touch it again, it stops being useful and starts becoming a liability.

Use this template — SSSP version control entry when you revise for a new phase:

SSSP Revision Record Project: [SITE ADDRESS / JOB NUMBER] Trade: [SUBCONTRACTOR TRADE] Rev: [VERSION NUMBER e.g. Rev 3] Date: [DD/MM/YYYY] Revised by: [ROLE — e.g. Site Supervisor] Sections updated: [e.g. Hazard Register, Emergency Contacts, Scope — Stage 2 Added] Reason for revision: [e.g. Transition from demolition phase to structural phase; new TA attached for concrete cutting] Distributed to: [Principal's H&S Rep, Main Contractor Site Manager]

SSSP Document Reference Structure

When you're managing multiple documents across a project, a consistent naming convention stops you submitting Rev 1 when Rev 3 exists:

SSSP DOCUMENT REGISTER — [PROJECT NAME / NUMBER]

File naming: [TRADE]-SSSP-[SITE CODE]-Rev[##]-[YYYYMMDD]
Example:     ELEC-SSSP-AKLD04-Rev03-20260601

Attachments naming: [TRADE]-TA-[TASK CODE]-Rev[##]-[YYYYMMDD]
Example:           ELEC-TA-EWP-Rev01-20260601

Version status:
  Rev 00 = Draft for review
  Rev 01 = Issued for mobilisation (principal accepted)
  Rev 02+ = Updated for phase/scope change

Hold point: Principal H&S rep sign-off required before Rev 01 is active on site.

Frequently Asked Questions

What is the difference between an SSSP and a health and safety plan?

In NZ, these terms are often used interchangeably, but "health and safety plan" is not a regulated document name. When a principal asks for a contractor health and safety management plan, they typically mean your SSSP plus TAs for high-risk tasks, your company H&S policy as background, and current prequalification evidence. The SSSP is the site-level document; the company plan is the system behind it.

Do I legally need an SSSP in NZ?

HSWA 2015 does not mandate an SSSP by name. However, your PCBU duties under s36 (primary duty of care) and s34 (overlapping duties — consult, cooperate, coordinate) effectively require you to have a documented approach to managing H&S on site. Principals and main contractors make an SSSP a contractual requirement before mobilisation, which means practically speaking, you do need one.

What's the difference between an SSSP and a SWMS?

An SSSP covers how H&S is managed across the whole site or project. A SWMS (called a Task Analysis in most NZ contexts) covers a single high-risk task — step by step. You typically need both: the SSSP references which tasks require a TA and holds the completed TAs as attachments.

Why does my SSSP keep getting rejected?

The most common reasons are: the plan is generic and not specific to the site; the s34 coordination section is missing or vague; the hazard register controls stop at PPE; TAs are referenced but not attached; or the document hasn't been updated to reflect the current phase of work. Fix the "S" in SSSP first — make it genuinely site-specific.

Conclusion

Three things to take away and act on before your next mobilisation:

Know what's actually being asked for. A "contractor health and safety management plan NZ" is not a single regulated document. It's a bundle — SSSP, TAs, company policy, prequal evidence. Get the structure right before you submit anything.
Make it genuinely site-specific. Address, scope, hazards, phase, other PCBUs on site, coordination with the main contractor under s34 — all of it must reflect this job, not a previous one.
Treat it as a living document. Submit at mobilisation, update at each phase change, and make sure the TAs are attached and signed. A static SSSP is a compliance gap waiting to be found.

SSSP template for NZ subcontractors — what to include in each section

Contractor Health and Safety Management Plan NZ: What Principals Want