Report and investigate an incident

May not be enabled

Incident managementmay not be turned on for your workspace or plan. If you don't see it, contact your workspace admin.

The incident register records what went wrong — injuries, security events, environmental releases, operational failures — and the near-misses that warn you before any of them happen. Each incident gets a reference like INC-0001 and carries its investigation and corrective actions with it.

Find it under Governance → Incidents.

Report an incident

1. Go to Incidents and select Report incident.
2. Enter the Title and a factual Description of what happened.
3. Choose the Type — Safety, Security, Environmental or Operational.
4. Choose the Severity — Near-miss, Minor, Major, Critical or Fatality.
5. Set Occurred — when it happened — and Discovered if that was later.
6. Choose the location, and add the assets involved.
7. Add the people involved, any attachments, and labels.
8. If it must be reported to a regulator, mark it notifiable.
9. Name the regulator body and set the notification deadline.
10. Save the incident.

Caution

Record what you observed, not who you think is at fault. The investigation establishes cause; the initial report should hold facts a reader can verify.

Note

A Fatality is marked notifiable to a regulator by default. You can change this, but do so deliberately.

Use Report near-miss for something that nearly happened. Only a title is required, so there is no excuse not to log it.

Investigate

1. Open the incident and start the investigation.
2. Choose the methodology — 5-Why (RCA), Fishbone, Bow-tie or Narrative.
3. Record your findings as you go.
4. Set the root cause category — human error, equipment failure, process deficiency, environmental, management system, or unknown.
5. Complete the investigation.

You cannot complete an investigation without a methodology, findings and a root cause.

Track corrective actions

Add a corrective action with a description, the person assigned to it and a due date. Adding the first one moves the incident to Corrective action.

Actions run Open → In progress → Completed → Verified, and flip to Overdue when the due date passes. Reminders go out daily, three days before an action is due.

Note

An incident can hold up to 100 corrective actions, 200 witness statements and 200 immediate actions.

Link the work it caused

Link the work orders, risks and permits connected to the incident so the repair and the incident stay joined up.

Close it out

Move the incident to Closed and give a reason — closing always requires one. Open corrective actions block the close; an owner or admin can force it if that is genuinely the right call.

An incident can be reopened from Closed back to Corrective action if new information arrives.

Statuses to expect

Reported → Under investigation → Corrective action → Closed. A minor incident that needs no formal investigation can go straight from Reported to Corrective action.

Report on the register

Reports covers incident rate, near-miss ratio, open corrective actions and root-cause distribution. Export the register itself with Export CSV or Export PDF.