How to Build a Risk Register for a Civil Construction Project From Scratch
You’ve just landed a new civil contract, the SiteWise prequalification is due in two weeks, and someone’s asking for your risk register. You open a blank spreadsheet and stare at it. Most site supervisors have been there. A solid risk register for civil construction NZ isn’t just a compliance checkbox — it’s a live document that protects your crew, your contract, and your prequalification score. This guide walks you through building one from scratch that actually holds up under scrutiny.
flowchart TD
A["Project Contract Received"] --> B["Identify Hazards & Risks"]
B --> C["Rate Risk Level"]
C --> D{Risk Acceptable?}
D -->|No| E["Implement Control Measures"]
E --> C
D -->|Yes| F["Document in Register"]
F --> G["SiteWise Prequalification Complete"]
Step-by-Step: How to Build Your Construction Hazard Identification NZ Framework
Before the first machine swings on site, your hazard identification process should already be underway. During the pre-construction planning phase — typically when you’re reviewing the contract documents and scope of works — is the right time to build this foundation.
Start by pulling your scope apart activity by activity. Don’t think in trades. Think in tasks: bulk earthworks, trench excavation, pipe laying, compaction, reinstatement. Every discrete task is a potential hazard source.
Step 1: List every significant activity in your scope — Break the works into minimum 10–15 activity categories. If you’re doing drainage installation on a roading project, that means separate entries for saw cutting, excavation, shoring, pipe installation, backfill, and reinstatement. Don’t group them.
Step 2: Identify the hazard for each activity — Ask: what could go wrong? Use the hierarchy of hazard categories: physical, chemical, biological, ergonomic, psychosocial. For civil works, you’re mostly dealing with physical and chemical.
Step 3: Identify who is at risk — Crew, subcontractors, public, plant operators. Be specific. “Workers” isn’t good enough.
Step 4: Assign an initial (inherent) risk rating — Use a 5×5 likelihood vs consequence matrix before any controls are applied. This is your worst-case number.
Step 5: List your controls using the hierarchy of controls — Eliminate, substitute, isolate, engineer, admin, PPE — in that order. Document all of them.
Step 6: Assign a residual risk rating — Re-rate likelihood and consequence after controls. This is the number SiteWise is looking for evidence of.
Step 7: Assign ownership and review frequency — Every hazard needs a name next to it, not a job title. “Site Supervisor — reviewed monthly or when scope changes.”
how to use the hierarchy of controls on civil sites
Building a Construction Risk Register Template NZ That Satisfies SiteWise Q7
# RiskRegisterBuilder v2.1 — Civil Construction Project Setup # Initializing risk assessment framework for Auckland metro subdivision (Resource Consent Phase) from RiskIdentificationEngine import HazardLibrary, SiteConditionAnalyzer from RegulatoryComplianceMapper import NZBuildingCodeValidator, HealthSafetyReqCheck from StakeholderImpactModeler import CommunityFeedbackProcessor from CostScheduleRiskAnalyzer import ContingencyCalculator, TimelineBuffer from DocumentationAutomator import RiskRegisterTemplate, MitigationPlanner # Scanning project parameters and generating baseline risk matrix... ✓ Hazard identification complete — 47 risks identified across 8 categories ! ALERT: Weather exposure (rainy season) flagged for critical mitigation planning ✓ NZ Building Code compliance check passed — all regulations mapped ! WARNING: Consenting risk marked HIGH — recommend independent consultant review ✓ Cost contingency calculated at 12.5% — contingency buffer generated ✓ Risk Register exported to stakeholder dashboard — ready for review meeting
At your first internal H&S review — usually a week before lodging your SiteWise application — your QA person is going to want to see that the risk register isn’t just a list of hazards. SiteWise Question 7 specifically asks for evidence that you have a documented process for identifying and managing hazards, and that you review it.
Here’s what the register structure needs to look like at minimum:
| Column | Field Name | Notes |
|---|---|---|
| A | Hazard ID | HR-001, HR-002 etc. |
| B | Activity / Task | Be specific — “trench excavation >1.5m” |
| C | Hazard Description | What is the source of harm? |
| D | Who Is at Risk | Crew, public, subcontractors |
| E | Initial Likelihood (1–5) | Before controls |
| F | Initial Consequence (1–5) | Before controls |
| G | Initial Risk Rating | L x C |
| H | Controls (hierarchy) | Eliminate → PPE |
| I | Residual Likelihood (1–5) | After controls |
| J | Residual Consequence (1–5) | After controls |
| K | Residual Risk Rating | L x C — this is your target |
| L | Control Owner | Name, not title |
| M | Review Date | Date last reviewed |
| N | Evidence / Reference | SWMS number, training record, inspection |
The “Evidence / Reference” column is what separates a register that passes SiteWise from one that doesn’t. Linking your hazard to a SWMS number (e.g. SWMS-007 Trench Excavation) or a toolbox talk record makes it auditable.
Use this template: For your register header row, copy and use this exact structure when setting up a new project register in Excel or Google Sheets:
Hazard ID | Project | Activity | Hazard | Who at Risk | Initial L | Initial C | Initial Rating | Controls | Residual L | Residual C | Residual Rating | Owner | Last Reviewed | SWMS / Evidence Ref
Using AI Tools to Speed Up Your Hazard Register for Civil Works
On a Thursday afternoon when you’re trying to get five SWMS written before a Monday start, manually drafting hazard descriptions for 30 line items is the last thing you want to do. This is where AI tools can legitimately save hours of your week — if you use them correctly.
ChatGPT (free tier available; ChatGPT Plus from USD $20/month) is well-suited to drafting initial hazard descriptions and control lists. Give it your activity list and ask it to output a structured register. Best for: sole operators and small subcontractors who don’t have a dedicated safety officer.
Claude by Anthropic (free tier available; Claude Pro from USD $20/month) handles longer documents better and is useful for reviewing an existing register against SiteWise criteria. Best for: supervisors wanting to audit their current register for gaps.
Try this prompt:
You are a New Zealand civil construction health and safety advisor. I am building a risk register for a stormwater drainage project in Auckland. The scope includes: saw cutting asphalt, trench excavation to 2.5m, installation of 600mm HDPE pipe, granular backfill, and asphalt reinstatement. For each activity, provide: hazard description, who is at risk, three controls using the hierarchy of controls, initial risk rating (likelihood 1-5 x consequence 1-5), and residual risk rating after controls. Format as a table. Reference NZ Health and Safety at Work Act 2015 where relevant.
Run this in ChatGPT or Claude and you’ll have a solid first draft in under two minutes. Your job then is to review it against your actual site conditions, modify what doesn’t fit, and add your SWMS reference numbers.
Here’s a structured prompt template you can save and reuse:
RISK REGISTER PROMPT — CIVIL PROJECT NZ
Project: [PROJECT NAME]
Location: [SUBURB / REGION]
Scope items: [LIST EACH ACTIVITY — minimum 5]
Contract type: [LUMP SUM / SCHEDULE OF RATES / D&C]
Special conditions: [E.G. LIVE TRAFFIC, CONFINED SPACE, NIGHT WORKS]
Request: Generate a risk register table with the following columns:
Activity | Hazard | Who at Risk | Initial L (1-5) | Initial C (1-5) |
Initial Rating | Controls (hierarchy) | Residual L | Residual C |
Residual Rating | HSWA 2015 reference
Output format: markdown table
how to write a SWMS using AI tools
How to Keep Your SiteWise Risk Register Evidence Current on Active Projects
When you’re two months into a job and the scope has crept into confined space work that wasn’t in the original contract, your risk register needs to reflect that change before work starts — not at the next quarterly review. This is where most registers fall over.
The SiteWise audit process will ask when your register was last reviewed and whether it reflects current activities. A register dated six months ago that doesn’t mention confined space entry on a project that’s been doing it for eight weeks is a problem.
Build these three habits into your project rhythm:
When scope changes: Any variation that introduces a new activity or changes how an existing one is performed triggers a register update. Add a line item. Raise a new SWMS. Update the evidence column. This takes 15 minutes if your register is structured properly.
Monthly during progress meetings: Every Friday site meeting, the last agenda item should be a 10-minute register review. Ask: is anything on here no longer relevant? Is there anything we’re doing that isn’t on here? A project foreman or leading hand can own this.
After any near-miss or incident: Pull the relevant hazard line item, review the controls that were in place, update as required. If you had a near-miss with an excavator and a pedestrian, that’s a residual risk rating that probably needs to go up until your control is strengthened.
Use a simple version control system in your register filename:
RISK_REGISTER_NAMING CONVENTION
Format: [ProjectCode]-RR-[Version]-[YYYYMMDD]
Example: AKL-DRAIN-22-RR-003-20250610
Version 001 = Initial issue (pre-construction)
Version 002 = First revision (scope change or new activity)
Version 003 = Post-incident review
This gives you an auditable trail showing SiteWise that the register is a living document, not a set-and-forget file.
Frequently Asked Questions
What does a risk register for civil construction NZ need to include to pass SiteWise?
SiteWise Q7 requires evidence that you have a systematic process for hazard identification and management. Your register must show initial and residual risk ratings, controls against the hierarchy of controls, ownership, and review dates. The key differentiator is the evidence column — linking each hazard to a SWMS, inspection record, or toolbox talk proves the controls are actually being applied, not just documented.
What’s the difference between a risk register and a SWMS in civil construction?
The risk register is the master document — it covers all hazards across your entire scope at a project or business level. A SWMS (Safe Work Method Statement) zooms into a specific high-risk activity and details the step-by-step method, hazards, and controls for that task. Your risk register should reference every relevant SWMS. Think of the register as the index, and the SWMS as the chapter.
How often should a construction risk register be reviewed on an active civil project?
At minimum, review it monthly and whenever scope changes. In practice, any variation order, new subcontractor activity, or near-miss should trigger an immediate review of relevant entries. SiteWise wants to see that the document is dated and versioned — a register that hasn’t been touched in six months on an active project raises red flags during an audit.
Can I use a generic construction risk register template NZ for multiple projects?
Yes, but with conditions. A master register at the business level is fine as a starting point. Each project should then have a project-specific version that reflects the actual activities, site conditions, and subcontractors on that job. Copy the master, add a project code to the filename, strip out irrelevant hazards, and add any project-specific ones before works commence.
Conclusion
Building a risk register for civil construction in NZ isn’t complicated — but it does require discipline. Here are the three things that will make the biggest difference:
First, structure your register with both initial and residual risk ratings from day one. The initial rating shows you’ve thought about the real hazard. The residual rating shows SiteWise your controls actually reduce the risk.
Second, use the evidence column religiously. Link every hazard to a SWMS number, a training record, or an inspection log. This is what separates a register that gets you prequalified from one that gets you a phone call asking for more documentation.
Third, treat the register as a live document. Version it, date it, and review it whenever scope or conditions change. A register from pre-construction that doesn’t reflect what’s actually happening on site is a liability, not an asset.
If you want more practical H&S templates and guidance built specifically for civil subcontractors working in the NZ market, subscribe to the ConstructionHQ newsletter — no fluff, just tools you can use on Monday morning.