BRCGS Issue 9 made documented root cause analysis a mandatory part of corrective action, not an optional best practice. If your team’s investigation process still stops at “what happened” rather than “why it happened,” it’s time to build root cause analysis into your training program directly.

Why symptom-fixing no longer passes

Auditors reviewing corrective actions under Issue 9 are specifically looking for evidence that the underlying cause was identified and addressed, not just the immediate symptom. A recurring non-conformance with a different corrective action each time is a red flag that root cause analysis isn’t happening in practice.

Teach a simple, repeatable method

You don’t need a complex Six Sigma toolkit to satisfy this requirement. A structured “5 Whys” approach or a simple fishbone diagram, taught consistently and applied every time, is often more effective than an elaborate method used inconsistently. The goal is a repeatable habit, not a one-off exercise.

Make it a team skill, not just a QA task

Root cause analysis works best when it isn’t treated as something only the quality department does after the fact. Training frontline supervisors to ask “why” questions in real time — right when an issue is spotted — produces better data and faster, more accurate corrective actions.

Document as you go

Whatever method you use, make sure the investigation and its conclusion are documented in a way an auditor can follow without you in the room. Clear, consistent documentation is what turns a good investigation into audit-ready evidence.