Incidents, Injuries and Observations

Three separate registers record when something goes wrong, or nearly does. Keeping them apart matters because they are reported and investigated differently.

Incidents

An incident is an event — including a near miss. The register records the "Incident" type, a "Description", the "Organization" involved, the "Incident Date" and a "Status".

The incidents register with the Incidents tile marked 1 and the Injuries tile marked 2

1 The "Incidents" tile · 2 The "Injuries" tile

Injuries

An injury record covers harm to a person. It carries the "Injury", a "Description", the "Organization", the "Injury Date" and a "Status".

An event that injured someone usually needs both records: the incident describes what happened, the injury records the harm. They are linked but reported separately.

Observations

An observation is something noticed before it caused harm — an unsafe condition or behaviour. Unlike incidents, observations are assigned and chased to closure, so the register carries more workflow:

  • Location and Assigned To
  • Status and Priority
  • Due Date and Days Left
The Observations tile highlighted in Safety Management above the observations register

"Days Left" turns an observation into something actionable. Sort by it to see what is about to fall overdue.

Notes & Recommendations

  • Record near misses as incidents. A near miss with no injury is still the cheapest lesson a project gets
  • Observations need an owner and a due date or they are just notes
  • Each register has its own search. Search incidents by description rather than by ID — the ID is rarely what people remember

Need More Support?

For Individual requests related to using Plexa Tools, Contact PLEXA SUPPORT

Email: support@plexapro.com

Phone: 1300 117 140

We're here to help you get the most out of Plexa.