Incident Management & Investigation

Report, classify and investigate through to root cause — and to the corrective actions that come out of it.

The register

Every incident, one register.

Severity, type, investigation lead and the number of actions each incident has spawned — visible without opening anything.

Scroll the image sideways to read it →

The BSLR incident register: KPI tiles for open investigations, reportable cases year to date, days since last lost-time injury, average days to close, and actions arising from incidents; below, a table of incidents with reference, title and location, date reported, type, severity, status, investigation lead and action count.

The incident register — severity and type classified, investigation lead named, actions counted.

BSLR product interface · illustrative data, fictional tenant “Meridian Contracting Group”

Root cause, not a blame column.

A structured Five Whys chain leads to a written root-cause statement and the contributing factors around it. The corrective actions that follow are the same governed records as every other action on the platform.

Scroll the image sideways to read it →

An incident investigation: potential severity and matrix score, persons affected, evidence count and linked actions; the incident record and a five-why root cause chain on the left; an evidence timeline and the corrective actions arising, with reviewer approval steps, on the right.

One investigation: the Five Whys chain, the evidence timeline, and the corrective actions it produced.

BSLR product interface · illustrative data, fictional tenant “Meridian Contracting Group”

Built so the closure means something.

Report from the field

A supervisor can report from a phone or WhatsApp at the moment it happens, with photos attached at the point of capture.

Severity and potential, separately

A near miss that could have killed someone is rated on potential, not outcome — so high-potential events get investigated properly.

Structured root cause

A Five Whys chain and a written root-cause statement, with contributing factors recorded alongside.

The evidence pack assembles itself

Statements, photos, CCTV references and documents attach to the record as they are gathered — nothing reconstructed before an audit.

Actions linked, not listed

Corrective actions become tracked records with owners and verifiers, in the same register as audit and training actions.

Closure rules enforced

An incident cannot close while a linked action is open, and the reviewer who approves is not the person who investigated.

See it against a real investigation.

Bring a recent incident to the walkthrough and we will run it through the workflow end to end.

Request a demo All modules