HazNode® Safety · Incident management

From first report to closed investigation, on one record.

Capture what happened in minutes, get a prompt on whether it is notifiable, run a structured investigation, and track every corrective action to completion — without the story living across a text message, a Word file and someone’s memory.

Explore the platform

What it does

The parts of an investigation that usually go missing

Reporting an incident is the easy bit. What separates a defensible record from a filing exercise is what happens in the days and weeks afterwards.

Incidents register showing five incidents with severity, status, assignee and open action counts

Reporting anyone will actually use

Minutes, from any device

A worker, supervisor or contractor can report an event from a phone in a few minutes, with photos and a plain-language description. Low friction is the whole point — an incident that never gets reported cannot be investigated.

What you get

Report from phone, tablet or desktop
Photos and witness details captured at the scene
Injury, near miss, property damage and environmental events
Works for employees and contractors alike

Notifiable event check on an incident, with a banner saying it looks like it could be notifiable and the HSWA criteria listed

Notifiability, prompted

Before the clock runs out on you

The hardest call in the first hour is whether an event has to be notified to the regulator. HazNode® prompts against the notifiable event criteria so the question is asked and the answer recorded, with the reasoning attached to the incident.

What you get

Prompts aligned to notifiable event criteria
The decision and its reasoning recorded on the incident
Escalation to the right people immediately
Preservation-of-site reminders where relevant

Incident investigation tab with the investigation approach, PEEPO evidence gathered, findings and causes, and a 5 Whys panel

Structured investigation

Causes, not just a narrative

Run the investigation in the system rather than in a Word template that lives on a laptop. Contributing factors, root causes and the evidence behind each conclusion stay attached to the incident they belong to.

What you get

Structured cause analysis, not a free-text box
Evidence, statements and photos on the record
Findings that convert straight into actions
Review and sign-off before closure

Corrective actions on an incident: three open actions, each with an owner, due date, category and a Close with evidence button

Actions that close with evidence

Owner, due date, proof

Findings become corrective actions on the same record, each with an owner, a due date and a category. An action is closed with evidence of what was done, so “we fixed it” is a photo or a document rather than a tick, and the register shows how many are still open.

What you get

Every action has an owner and a due date
Categorised: engineering, administrative, PPE
Closed with evidence, not a checkbox
Open actions counted on the incidents register

Trends that mean something

Across sites, time and cause

Once incidents, near misses and observations sit in one place, the same mechanism showing up repeatedly becomes visible — by site, by activity, by contributing factor — instead of being three separate write-ups nobody compared.

What you get

Trends by site, activity and cause
Lead and lag indicators together
Overdue corrective actions surfaced
Board and client reporting without a manual roll-up

Sound Familiar?

Sound familiar?

The first report arrives as a text message and gets typed up two days later.

Nobody is quite sure whether the last event should have been notified.

Investigations live in Word files on individual laptops.

Corrective actions are agreed in a meeting and never tracked again.

You cannot show a pattern across sites because every site records it differently.

When a client or regulator asks for the file, assembling it takes days.

What changes

A record that holds up when it matters

The value of an incident system is only tested on the worst day. That is the day it needs to be complete, timestamped and coherent.

Defensible, not reconstructed

One continuous record from first report to closure, timestamped as it happened rather than assembled afterwards.

The notifiability question gets asked

Prompted at the point of reporting, with the decision and its reasoning captured, rather than remembered differently by different people later.

Actions actually close

Every corrective action has an owner, a due date and evidence of completion — so the investigation changes something.

Repeat mechanisms surface early

The same cause appearing across sites becomes visible while it is still near misses, not after it becomes an injury.

Common questions

Questions about incident management.

Who can report an incident?

A worker, supervisor or contractor, from a phone, tablet or desktop, in a few minutes, with photos and a plain-language description. Injury, near miss, property damage and environmental events are all covered.

Does HazNode® Safety tell me whether an incident is notifiable?

It prompts against the notifiable event criteria so the question is asked in the first hour, and records the decision and its reasoning on the incident. The call remains yours.

How are investigations run?

In the system rather than in a Word file: structured cause analysis, with evidence, statements and photos kept on the record, findings that convert into corrective actions, and review and sign-off before closure.

What happens to corrective actions?

Each has an owner, a due date and a category, and is closed with evidence of what was done rather than a tick. The incidents register counts the actions still open.

Can an incident be reported from a phone?

Yes. From any phone’s browser, or from HazNode Field, the companion app for iPhone and iPad, which reports a near miss, injury, property damage or environmental event on one screen with photos, offline included. Triage, investigation and actions stay on the desktop.

Walk through a real incident, end to end

We will take a scenario from your operation and follow it through reporting, notifiability, investigation and close-out so you can see exactly what the record looks like.