Platform

Incident & Near Miss Reporting

Incident and near-miss reporting, connected back to risk assessments and actions.

Available
Connected

Incidents linked to the real record

An incident connects back to the equipment, risk assessment, COSHH substance or permit it relates to, instead of sitting as a standalone note.

Never a standalone note
Investigated

A full investigation, not just a report

Chronology, immediate actions, investigator notes and lessons learned are tracked through to close-out, with RIDDOR classification recorded where it applies.

Investigated, not just logged
Confidential

Reporting that protects the reporter

Anyone can raise a report confidentially or anonymously, with no name recorded and a reference code to follow it up — enforced in the database, not just hidden in the interface.

Anonymous, by design

Overview

Incident & Near Miss Reporting is a real, governed module — report what happened, assign an investigator, and track the investigation through chronology, immediate actions, root cause and lessons learned.

Incidents connect back to the real records they relate to (equipment, risk assessment, COSHH substance, permit, fire risk assessment) and can carry RIDDOR classification and reference details.

Anyone on the team can raise a report — including confidentially (visible only to owners and administrators) or anonymously, with no name recorded against it. Anonymous reporters get a reference code so they can still follow the report up.

If a report is started with no signal — a basement, a plant room, a rural site — it saves on the device and synchronises automatically the moment a connection returns, using the same phone or tablet browser your team already has. This covers incident reporting specifically; it isn't yet available for every SafetyOps workflow.

Why it matters

Near misses are early warnings — capturing them structurally, not just informally, is how patterns get caught before a real incident happens. A confidential, name-off route means people raise concerns they would otherwise keep quiet.

Benefits

Full investigation record

Chronology, immediate actions, investigator notes and lessons learned, kept against the incident.

Connected to the real source

An incident links back to the equipment, risk assessment or permit it relates to — never a standalone note.

RIDDOR classification

Record RIDDOR category, reference and submission details where an incident is reportable.

Confidential & anonymous reporting

Raise a report with no name attached, or restrict it to owners and administrators — enforced in the database, not just hidden in the UI.

Reports offline, syncs automatically

Started with no signal, saved on the device, and synchronised the moment a connection returns — a real, live-verified capability, not a roadmap promise.

Workflow

  1. Report an incident or near miss, linking it to the equipment/site/risk assessment it relates to — optionally confidential or anonymous, and still possible with no signal.
  2. Assign an investigator; record chronology, immediate actions and investigator notes as the investigation proceeds.
  3. Record RIDDOR classification and reference details where the incident meets that threshold.
  4. Close the incident with recommendations and lessons learned, visible in the Incident Learning view.

Connected across SafetyOps

Incidents ↔ Risk Assessments

An investigation can link back to the risk assessment that covered the work, connecting what happened to what was already assessed — not a standalone note.

Incidents ↔ Action Centre

Immediate actions and corrective actions raised during an investigation are tracked through the same Action Centre as every other module, to real close-out.

Incidents ↔ On The Move

Reporting keeps working with no signal — the report saves on the device and synchronises automatically once a connection returns.

Interface

See incident reporting that never stops

From a report captured with no signal to a closed corrective action — book a walkthrough, or see how offline reporting works on your own phone.

Frequently asked questions

Does SafetyOps automate RIDDOR reporting?

No — SafetyOps records RIDDOR classification, category and reference where an incident is reportable, but does not decide reportability or submit reports to HSE automatically. See the Legal & Compliance Library's RIDDOR page for what that legislation requires.

How does anonymous reporting work?

Tick 'submit anonymously' when raising a report. No reporter identity is stored against it — not the name, not the account. You're given a reference code (INC-XXXXXX) so you can follow the report up without identifying yourself. A confidential report keeps the reporter's name but restricts who can see the report to owners and administrators.

Can an incident be reported without an internet connection?

Yes — if a report is started with no signal, it's saved on the device and synchronised automatically the moment a connection returns, in your phone or tablet's own browser. This covers incident reporting today; it isn't yet available for every SafetyOps workflow.

Report it. Investigate it. Close it out.

Confidential, anonymous, or offline — every incident becomes a real, connected record, not a standalone form.