Incidents — Overview

Report, investigate, and close safety incidents — with root cause, corrective actions, stand-downs, and policy-gated close-out.

Incidents capture what went wrong — near misses, injuries, damage, and environmental events — and drive them through a report → investigate → close workflow, so nothing is left unresolved.

Safety is in beta

Incidents are part of the Safety module, which is in beta — in production and usable, but not yet part of a versioned release of its own.

Incident register with types, investigation status, and stand-down flags — The incident register — types, investigation status, and stand-down flags

Reporting an Incident

Anyone with safety create access can report. From Safety → Incidents, click Report incident. The capture panel steps through:

What happened — the type (near miss, first aid, lost time injury, property damage, environmental, fatality, or other) and a clear description
When & where — the time it occurred, the location, and the weather if relevant
Evidence & actions — photos, whether to stand down the affected area, and whether a regulatory report is needed

Report incident panel with type, when/where, description, and stand-down toggles — Reporting an incident — type, when and where, description, and stand-down

Press Report incident — the incident is created as reported.

Investigating

Open the incident to work the investigation panel:

Root cause — record why it happened
Corrective actions — add actions and mark each one open or done
Stand-down — signal that work in the affected area is paused, and lift it when it's safe

Incident under investigation with report snapshot, root cause, and corrective actions — Investigating — root cause and corrective actions drive the close-out

The Guarded Close-out

Closing an incident isn't a single button — it's gated by policy. Depending on your project settings, you can't close an incident until:

The root cause is filled, and
Every corrective action is marked done

If a gate isn't met, the close is blocked and the outstanding items are shown.

Status	Meaning
Reported	Logged, awaiting investigation
Investigating	Under investigation — root cause and corrective actions in progress
Closed	Investigated and signed off, with gates satisfied

Incidents can come from walks

A serious safety walk observation can be escalated straight into an incident — the detail carries across, so the investigation starts with context.

A stand-down signals that work in the affected area is paused. From the incident list you can select several incidents and apply a stand-down (Stand down) or lift it (Resume work) in bulk — useful when a site-wide pause is called.

Tips

Report near misses — they're the cheapest lessons; the trend chart on the Hub rewards it
Write actions someone can tick off — a vague action rarely gets done
Flag regulatory events early so reporting deadlines aren't missed

Next Steps

Safety Policies — set the close-out gates
Safety Walks — where escalated incidents originate
Safety Hub — open incidents and the 8-week trend

Questions

I got a detail wrong in the report. Can I change it?

No. The type, time, location and description are fixed once it's reported. The root cause, corrective actions, regulatory flag and stand-down can be changed until the incident is closed, so note the correction there.

Can I reopen or delete an incident?

No. A closed incident can't be reopened or edited, and incidents can't be deleted in the app. Closing an incident also lifts its stand-down and tells everyone on the project.

Who can close an incident?

Anyone whose role can update Safety records. On the web, a reported incident is first moved on with Investigate, then closed once your close-out rules are met: by default a root cause and every corrective action done.