PleoStack

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.

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

Reporting an Incident

Anyone on the project can report. From Safety → Incidents, click Report incident. The capture panel steps through:

  1. Type — near miss, first aid, lost time injury, property damage, environmental, fatality, or other
  2. When & where — the time it occurred and the location
  3. Description — a clear account of what happened, plus weather if relevant
  4. Evidence — photos and documents
  5. Stand-down & regulatory — flag if work must stop, and whether it's reportable to a regulator
Report incident panel with type, when/where, description, and stand-down toggles
Reporting an incident — type, when and where, description, and stand-down

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 with an owner, a due date, and an open/done status
  • Involved persons — list those involved and any witnesses
  • Stand-down — keep the affected area 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.

StatusMeaning
ReportedLogged, awaiting investigation
InvestigatingUnder investigation — root cause and corrective actions in progress
ClosedInvestigated 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.

Stand-downs & Bulk Actions

A stand-down signals that work in the affected area is paused. From the incident list you can select several incidents and apply (or lift) a stand-down 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
  • Own every corrective action — an unassigned action rarely gets done
  • Flag regulatory events early so reporting deadlines aren't missed

Next Steps