Category
Incident Investigation
124 articles
How to Write Incident Findings That Lead to Better Controls in 21 Days
A practical 21-day method for turning incident evidence into findings that name the failed control, expose decision gaps, and guide verifiable corrective action.

Post-Incident Meetings: 4 Decisions That Determine Whether People Speak Before the Story Hardens
The first post-incident meeting often determines whether the organization learns or simply confirms its first explanation. This diagnostic shows four decisions that protect psychological safety, preserve evidence, and keep the causal story open long enough to become useful.
How Flixborough Exposed the Cost of Treating Design Change as a Local Fix
The Flixborough disaster was not only a story about a failed pipe. It was a case study in how a local design change can outrun engineering control, review, and organizational authority.

New Incident Investigator in 60 Days: What to Do in the First Investigation Cycle
A practical 60-day transition plan for a newly appointed incident investigator who needs to protect evidence, earn trust, and turn findings into stronger controls.

How to Build an Incident Investigation Charter Before Interviews Begin
A short investigation charter gives the team a shared scope, evidence standard, decision owner, and interview sequence before early assumptions harden. This eight-step guide shows supervisors, EHS managers, and incident leads how to build one without turning the investigation into paperwork.

San Bruno and the Leadership Test Hidden in Pipeline Records
The 2010 San Bruno pipeline rupture was not only a technical failure. The NTSB investigation showed how uncertain records, weak validation, and leadership decisions about risk can combine until a serious hazard becomes an irreversible event.

TapRooT vs ICAM vs Bow-Tie Reverse Analysis: Which Investigation Method Fits a Serious-Injury Exposure?
TapRooT, ICAM, and Bow-Tie Reverse Analysis answer different investigation questions. This comparison helps plant leaders choose the method that best matches task failure, organizational complexity, or critical-barrier verification.

Incident Investigation: 4 Assumptions That Weaken Action
Incident reports fail when they explain the last action but leave the operating conditions unchanged. Test four assumptions before approving corrective action.

Kleen Energy: How a Routine Pipe-Cleaning Method Became a Fatality Pathway
The 2010 Kleen Energy explosion killed six workers because a familiar natural-gas pipe-cleaning method created a major hazard that the project controls did not adequately challenge. The case shows why temporary work, shared contractor responsibility, and commissioning decisions require stronger ownership and field verification than routine paperwork can provide.

Incident Investigation: 5 Blind Spots That Keep Serious Causes Out of the Report
A serious incident investigation should explain more than the final action. This diagnostic guide shows five blind spots that hide system conditions, weaken corrective actions, and leave risk available for the next shift.