The Report Is Not the Investigation
The first document after an accident captures the event: who, when, where, what. It is necessary and insufficient — because an accident fully described is still an accident completely unexplained. The investigation document exists to answer the harder question, the one the initial form deliberately avoided: why did this become possible?
This template is that second document. Completed by the safety lead or investigating manager in the days after the event, it turns a description into a diagnosis — and a diagnosis into a fix with a name and a deadline attached.
Phase One: Gather the Facts
The investigation starts where the first report ended: reviewing the original entry, walking the scene, photographing conditions as they now stand, and reading the equipment and training records that bear on the event. A structured long text field consolidates the factual timeline — established from evidence, not recollection, and kept free of interpretation until the facts are complete.
Phase Two: Map the Contributing Factors
Almost no accident has one cause. The disciplined approach names the full chain:
| Factor type | The question it answers | Example |
|---|---|---|
| Direct | What actually caused the harm? | Wet floor at the loading door |
| Contributing | What conditions allowed it? | Drain blocked for a week; no floor signage stocked |
| Organizational | What decisions shaped those conditions? | Signage never on the reorder list; no weekly walk-through assigned |
Each row of the chain gets its own evidence line, because the organizational layer is where prevention actually lives — and it is invisible to anyone who stops at ‘someone slipped.’
Phase Three: Name the Root Cause, Assign the Fixes
The root cause statement is one honest sentence about the deepest factor the evidence supports. Then the document earns its keep:
- Corrective actions — each fix as a short text line with a named owner and a due date.
- The immediate vs. systemic split — mopping the floor today is not a corrective action; restocking signage and assigning the walk-through are.
- The verification step — who confirms, weeks later, that each fix actually happened.
Actions without owners are wishes; this section refuses to produce them.
The Register Is the Payoff
Investigations accumulate into the hazard register: every root cause, every action, every verification — held in the response archive, filterable by site and category with hidden-field tagging. The register is what turns individual accidents into a prevention program — and what a regulator or insurer asks for first. Investigations handling sensitive injury detail stay sealed to the safety team through role-based access.
Frequently Asked Questions
How soon after the accident should the investigation start?
Within days, while the scene is intact and recollections are fresh — but after the immediate response is complete. The investigation must never compete with first aid.
Who leads it?
Someone with enough distance to be objective — the safety lead, or a manager from outside the immediate team. The supervisor of the area involved contributes facts; leading their own investigation invites findings shaped by self-defense.
What if the root cause is genuinely 'human error'?
Then keep digging one layer: what made the error easy, likely, or unpunished-by-consequences? Organizations that stop at human error repeat the same accident with different names attached.
How do we know the corrective actions worked?
The verification step, taken seriously: each action gets checked on its due date, and the register notes completion. An action verified closed is the only kind that counts.