Incident Register for Construction: How to Keep Records That Protect You When WorkSafe Calls

WorkSafe doesn’t announce their visits. One phone call — or worse, one serious harm event — and an inspector is on your site within hours. Your incident register is the first document they’ll ask for. Most contractors hand over a half-filled spreadsheet and hope for the best. That’s not a strategy.

⬢ Workflow Diagram
flowchart TD
    A["Incident or Near Miss Occurs"] --> B{Document Immediately?}
    B -->|No| C["Records Incomplete
WorkSafe Risk"] B -->|Yes| D["Enter Into Register
Date, Time, Details"] D --> E["Site Manager Reviews
& Investigates"] E --> F["Assess Severity
& Root Cause"] F --> G{WorkSafe
Notifiable?} G -->|Yes| H["Report to WorkSafe
Within Required Time"] G -->|No| I["Maintain Complete
Register Records"] H --> I I --> J["Protected When
Inspector Visits"]

A solid construction incident register NZ WorkSafe investigators can actually work with isn’t just about compliance — it’s your evidence trail. Done right, it shows a pattern of proactive safety management. Done poorly, it becomes evidence against you.

This article breaks down exactly what belongs in your register, how to investigate incidents so the records hold up, and why near misses are the most under-reported — and most legally dangerous — gap in most site safety systems.


What WorkSafe NZ Incident Reporting Actually Requires You to Record

Before 7am toolbox talk on any given Monday, your foreman should already know which incidents from last week are sitting in your register — and which ones still need a corrective action closed out. That’s the standard WorkSafe NZ incident reporting expects to see demonstrated in practice, not just in policy documents.

Under the Health and Safety at Work Act 2015 (HSWA), you must notify WorkSafe of notifiable events — these are work-related deaths, notifiable injuries or illnesses, and notifiable incidents (unplanned or uncontrolled events that expose a worker to serious risk). But your internal register needs to capture far more than just notifiable events.

Here’s what a compliant register entry needs to include at minimum:

Field What to Record Common Gap
Date / Time Exact time, not just date “Afternoon” isn’t enough
Location Grid ref, zone, or chainages “Near the shed” won’t cut it
People involved Names, trades, employer Missing subcontractor names
Incident type Near miss / first aid / LTI / notifiable Left blank or guessed
Immediate cause What physically happened Stops at “slipped”
Root cause Why the condition existed Almost always blank
Corrective actions Who does what by when Open forever
Evidence attached Photos, SWMS ref, witness statements Zero attachments

The corrective action column is where most registers collapse. WorkSafe wants to see that you identified the problem and did something about it. An open corrective action from three months ago is a red flag — it tells an inspector your system has no teeth.

how to write corrective actions that actually close out


Near Miss Register Construction: Why Under-Reporting Is Your Biggest Legal Risk

incident_register_tracker.py

# IncidentRegisterSystem v2.1 – WorkSafe Compliance & Record Management
# NZ Construction Safety Documentation Assistant

from modules.IncidentClassifier import classify_hazard_type
from modules.DateCompliance import check_notification_deadline
from modules.AutoReportGenerator import format_incident_record
from modules.WorkSafeValidator import validate_record_completeness
from modules.PhotoEvidenceLinker import attach_site_images
from modules.NotificationScheduler import alert_site_manager



# Initializing incident register for site: Mount Eden Commercial Project

✓ Incident record ID-2847 created – 14 March 2024, 10:45 AM
! Missing: Witness names (recommended for WorkSafe inquiry)
✓ Hazard classified as: Fall from height – High risk
! WorkSafe notification deadline: 15 March 2024 (within 24 hours)
✓ Site photos attached and timestamped
✓ Record validation complete – Ready for WorkSafe submission

At the 4pm end-of-shift debrief, your excavator operator mentions the spotter wasn’t in position when he reversed near the edge. Nobody got hurt. The operator logged it verbally and moved on. You never wrote it down. That’s a near miss that just disappeared — and it’s one of the most dangerous things that can happen to your safety programme.

Here’s the reality: under HSWA, failure to maintain adequate records isn’t just a technical breach. If a serious harm incident occurs later in similar circumstances, an empty near miss register construction history tells WorkSafe you either didn’t know about the hazard or chose to ignore it. Neither story helps you.

Near misses are leading indicators. They tell you where your controls are failing before someone gets hurt. A site running three or four recorded near misses a month is almost always safer than a site recording zero — because zero near misses doesn’t mean zero incidents, it means no one is reporting.

How to actually get near misses reported on site:

Step 1: Remove the friction — Make reporting a two-minute job. A QR code on site that opens a simple form on any smartphone. Workers won’t fill in a four-page PDF from memory at 5:30pm.

Step 2: Kill the blame culture — Your first words after a near miss report cannot be “whose fault was this.” Ask what condition existed and what would have prevented it.

Step 3: Acknowledge every report publicly — At the next toolbox talk, name the near miss (not the person) and explain what’s being done. If nothing happens after they report, they stop reporting.

Step 4: Cross-reference your SWMS — Every near miss should trigger a review of the relevant SWMS. Was the hazard identified? Were the controls adequate? Update the document and reissue if needed.

Step 5: Track your near miss rate monthly — If it drops suddenly, that’s not good news. That’s a reporting culture breakdown.


Incident Investigation Construction NZ: Building Records That Actually Hold Up

incident_register_response.jsonJSON
```json
{
  "incident_register_config": {
    "project_id": "PROJ-2024-0847",
    "site_name": "Westfield Shopping Centre Extension - Auckland",
    "client": "Westfield Management Ltd",
    "worksafe_compliance": {
      "registration_number": "NZ-WS-2024-156432",
      "last_audit_date": "2024-01-15",
      "next_audit_due": "2024-07-15",
      "audit_status": "compliant"
    },
    "incident_records": [
      {
        "incident_id": "INC-2024-0021",
        "date_reported": "2024-03-12",
        "time_occurred": "14: 35",
        "trade": "Scaffolding",
        "subcontractor": "SafeHeight Solutions Ltd",
        "description": "Minor slip on wet scaffolding platform",
        "severity": "low",
        "injury_type": "none",
        "site_supervisor": "Mark Johnson",
        "swms_reference": "SWMS-SCAF-001",
        "corrective_action": "Increased cleaning schedule implemented",
        "status": "closed"
      },
      {
        "incident_id": "INC-2024-0022",
        "date_reported": "2024-03-14",
        "time_occurred": "09: 20",
        "trade": "Electrical",
        "subcontractor": "PowerGrid Contractors",
        "description": "Near-miss: Exposed live wire in ceiling cavity",
        "severity": "high",
        "injury_type": "none",
        "site_supervisor": "Sarah Mitchell",
        "swms_reference": "SWMS-ELEC-002",
        "corrective_action": "All electrical work halted pending review and re-training",
        "status": "under_review"
      }
    ],
    "reporting_metrics": {
      "total_incidents_ytd": 22,
      "high_severity_count": 3,
      "ltifr": 0.8,
      "trifr": 2.1
    },
    "next_sync": "2024-03-19T08: 00: 00Z"
  }
}
```

When a scaffolder on your Wellington commercial project takes a fall from height — even a minor one — your investigation needs to start within the hour, not at the end of the week when everyone’s moved on and the scene has changed. Incident investigation in construction NZ has to be methodical and documented in real time.

WorkSafe investigators are trained to look for inconsistencies between what your register says happened and what the physical evidence shows. If your register says “adequate edge protection was in place” but your own site photos from that day show otherwise, you have a problem that no amount of paperwork fixes after the fact.

Use this template for your immediate post-incident documentation:

POST-INCIDENT RECORD — IMMEDIATE CAPTURE
Date: DD/MM/YYYY | Time: HH:MM | Weather: [condition]
Project: [project name and number] | Location on site: [zone / grid / chainage]
Trade involved: [e.g. Scaffolding — subcontractor: Apex Scaffolding Ltd]
Workers present: [full names]
Incident type: Near miss / First aid / Medical treatment / LTI / Notifiable
Describe what happened (what, where, how — facts only, no blame):
Immediate actions taken: [e.g. area isolated, first aid provided, WorkSafe notified]
Evidence secured: Photos Y/N | Witness statements Y/N | SWMS ref: [document number]
Reported by: [name and role] | Signature: ______

The key phrase in that template is “facts only, no blame.” The investigation record should read like a journalist’s account — who, what, where, when. Save the why for the root cause analysis section, completed within 48 hours once you’ve had time to interview witnesses properly.

SWMS review after a near miss: what needs to change


SiteWise Incident Evidence: What Prequalification Auditors Actually Check

During a SiteWise audit, the assessor isn’t just ticking boxes — they’re reading the story your records tell about your safety culture. SiteWise incident evidence is assessed as part of your overall health and safety management score, and a thin or inconsistent incident register will cost you points that directly affect your ability to win work with tier-one contractors and government clients.

What SiteWise auditors specifically look for in your incident records:

SITEWISE INCIDENT REGISTER REVIEW — ASSESSMENT LOGIC

Does register include incidents from all workers on site?
  → YES: Continue
  → NO: Flag — subcontractor incidents often missing

Are near misses recorded separately from first aid events?
  → YES: Continue
  → NO: Flag — classification system absent

Do corrective actions have owners and due dates?
  → YES: Check closure rate
    → >80% closed within 30 days: Positive indicator
    → <50% closed: Flag — system not functioning
  → NO: Flag — corrective action tracking absent

Is there evidence of trend analysis (monthly review)?
  → YES: Strong indicator of proactive system
  → NO: Flag — reactive only

The practical implication: if you’re preparing for a SiteWise renewal audit, pull your incident register and run that logic yourself before the assessor does. Look at the last 12 months. If you have fewer than 10 recorded entries and you’re running a crew of 15 or more, you’re either the safest site in New Zealand or you have a reporting gap. The auditor will assume the latter.

ConstructionHQ’s safety module helps you track incident trends and flag open corrective actions — best suited for subcontractors managing their own safety system without a dedicated HSE advisor.


Frequently Asked Questions

Frequently Asked Questions

What incidents do I legally have to report to WorkSafe NZ?

Under HSWA 2015, you must notify WorkSafe as soon as practicable after a notifiable event. This includes any work-related death, a notifiable injury or illness (e.g. fractures, amputations, serious burns, hospitalisation), or a notifiable incident where a worker was exposed to serious risk. Near misses and first aid events don’t need to be reported to WorkSafe but must be recorded in your internal register.

How long do I need to keep incident records in construction NZ?

WorkSafe guidance recommends retaining incident records for a minimum of five years. For incidents involving minors, or where WorkSafe has opened an investigation, keep records indefinitely until you receive written confirmation the matter is closed. Store originals securely — a cloud backup plus a physical copy is standard practice on well-run sites.

What’s the difference between a near miss and a notifiable incident?

A near miss is an unplanned event that could have caused harm but didn’t — a load that swung close but missed a worker, a trench edge that crumbled but no one fell in. A notifiable incident is an unplanned event that did expose a worker to serious risk of harm, regardless of whether they were actually injured. The line is exposure to risk, not whether someone got hurt.

Can my incident register be digital, or does WorkSafe NZ require paper records?

Digital registers are fully acceptable. WorkSafe requires that records are accessible, legible, and capable of being produced on request. The format doesn’t matter — a well-maintained spreadsheet, a purpose-built safety app, or a platform like ConstructionHQ are all acceptable. What matters is completeness, accuracy, and that entries are made in real time, not retrospectively.


Conclusion: Three Things to Do Before You Close Your Laptop Today

If you take nothing else from this article, take these three:

1. Audit your last 12 months of records right now. Check for gaps — missing corrective action owners, blank root cause fields, and incidents with no attached evidence. Anything open for more than 30 days needs a status update today.

2. Fix your near miss reporting process. If your team isn’t reporting near misses, the hazards aren’t disappearing — they’re just invisible to your register. A QR code, a no-blame response, and a public acknowledgement at toolbox are the minimum to turn that around.

3. Treat your incident register as evidence, not admin. Every entry is a record that either supports your position or undermines it the day an inspector walks on site. Write entries like you’re writing for a judge.

For practical templates, SWMS review workflows, and safety documentation tools built for NZ construction, explore the ConstructionHQ resource library — or subscribe to the ConstructionHQ newsletter for site-ready guides delivered fortnightly.

How to structure your safety management system for a SiteWise audit