Safety and compliance tutorials · 3 of 6 · 2:59

    Need an incident investigation that holds up, from the first report to a signed close-out?

    In Inspecable, an incident runs through stages the database enforces, with a classified severity, an investigation team, a root-cause analysis in one of six methods, and a close-out signed by someone other than the investigation lead.

    01In this video

    How to Run an Incident Investigation With Root Cause Analysis | Inspecable

    This web dashboard tutorial reports an incident, classifies its actual and potential severity (a high potential is flagged), appoints the investigation lead and team, records a root-cause analysis (5-Whys, fishbone, fault tree, bow-tie, ICAM-style or loss causation), records mitigation measures and converts them to corrective actions, and closes it out. The app suggests which South African regulator reports may be needed (OHS Act section 24, COIDA, MHSA, Railway Safety Regulator) but does not file them. Recorded in a live demonstration organisation.

    03Transcript

    The narration, word for word

    Read the transcript

    Introduction

    In this video you'll take an incident from the first report to close-out: classifying it, investigating it with a root-cause analysis, recording what's being done about it, and closing it with a signature.

    The incident register

    Incidents live in the Safety Hub, under the Incidents tab. The register shows each incident's number, title, type, severity, stage and date, and who reported it. Filter by stage, and export the whole register to Excel or PDF.

    Reporting an incident

    Report opens the form: a title, the type and severity, the date and time, the site and location, what happened and who was affected. The type adds its own questions, and injury details where they apply. Field teams report from the phone. We'll cancel this one.

    Stages

    Open an incident to run it. This one, a rigger struck by a swinging load, is under investigation. An incident moves through eight states, from reported to closed, plus reopened and void, and the database refuses any move that breaks a rule. The header carries the incident's number, severity and stage, with buttons to edit the report details, escalate it, and export the record as a PDF. Below the stages, the activity timeline exports to PDF or CSV.

    Classification

    Classification records two levels on your organisation's five-point scale: what actually happened, and the worst credible outcome had it gone further. A high potential with a lower actual is flagged as a high-potential incident. The investigation can't start until it's classified.

    Investigation

    The investigation needs a lead. Choose one, then add responders, members and worker representatives from your organisation's people. Nobody is on this team yet, so the stage still asks for a lead and a root cause. The lead is locked once the incident awaits close-out.

    Root-cause analysis

    Add analysis opens the root-cause analysis. There are six methods: five whys, fishbone, fault tree, bow-tie, ICAM-style and loss causation. Each records the immediate cause, the root cause and contributing factors. A recorded root cause is what close-out needs.

    Actions and regulators

    Under actions, record mitigation measures, immediate or preventive, each with an owner and a due date. Convert to CAPA turns a measure into a corrective action in the register, and every linked action must be closed before the incident can close. Below that, the app suggests reports you may owe a regulator, from the type, the injury details and your industry: OHS Act section 24, COIDA, MHSA and the Railway Safety Regulator. It only suggests. It files nothing. You confirm each one and record your submission.

    Close-out

    Close-out has a checklist in the same order the database checks it: a lead, a root cause, every linked corrective action closed, and the closer's own signature. The investigation lead can't close their own incident. Someone else signs it off.

    Recap

    So: report the incident and classify it. Investigate it with a lead, a team and a root-cause analysis. Record what's being done, check the regulator reports, and close it out with a signature from someone other than the lead. Next, see how permits to work and isolations are run. Every tutorial is on our website, linked on screen now.

    Safety and compliance tutorials

    See it on your own checklists

    Fourteen days on the Safety & Compliance edition, no card

    Or book a 30-minute walkthrough and we show this on your industry's checklists.