Incident Investigation and Root-Cause Analysis

What separates a real safety program from a poster on the wall is what happens after something goes wrong (or almost does). A rigorous, blame-free investigation turns one near-miss into a permanent fix. FIRST Safety Advisors explicitly value teams that document how they respond to issues over teams claiming a perfect record.

Step 1 - Capture every near-miss, not just injuries. A near-miss (a battery that slipped but didn't drop, a cylinder that fired into empty air) is a free lesson. Make reporting easy and never punitive - punishing reporters just hides the next incident.

Step 2 - Run a 5 Whys. Ask 'why' until you reach a fixable system cause, not a person to blame:

Event: Student's sleeve caught on the drill press.
Why? Loose long sleeve near the rotating chuck.
Why? No rule enforced about sleeves at the drill press.
Why? New members weren't trained on machine dress code.
Why? Onboarding had no machine-safety module.
Why? Training was informal and undocumented.
Root cause: No structured machine-safety onboarding.

Note the root cause is a system gap, not 'the student was careless.' That's the point.

Step 3 - Write a structured report. Capture: what happened, when/where, who was involved, the immediate correction, the 5-Whys root cause, the preventive action, an owner, and a due date - the same fields as a Corrective and Preventative Action (CAPA) entry.

Step 4 - Close the loop (CAPA). A finding isn't done until the preventive action is implemented and verified. For the example above: add a machine-safety onboarding module, require sign-off, and post a JSA at the drill press. Re-check at the next meeting and mark it closed.

Step 5 - Track trends. Keep a running safety event log; if 'pinch point' shows up three times, that's a design problem for your next FMEA cycle, not three unlucky people. Feed recurring root causes back into your design FMEA and JSAs so the whole system improves.

Why this wins: advisors talk to random members and look for evidence of a living process. A near-miss log with closed CAPA entries, traced to system root causes and fed back into design, is the clearest possible proof that safety is part of your engineering culture - and since safe practices gate eligibility for every judged award, that evidence pays off broadly.