Root cause analysis is required by BRC Issue 9 for every non-conformance raised during internal audits, customer complaints, and incidents. It is also one of the areas most frequently cited as inadequate during BRC certification visits. The gap is almost always the same: teams document what happened rather than why it happened.
What Clause 3.7 Requires
Corrective actions must address root causes, not symptoms. The standard also states that the effectiveness of corrective actions must be verified. This means your RCA must identify a cause that, when addressed, prevents recurrence. It is not enough to resolve the immediate problem.
The Most Common Failure
Confusing the immediate correction with the root cause investigation. Consider a labelling error NC. The immediate correction is to quarantine and relabel the affected product. That is containment, not root cause analysis. The investigation must ask why the labelling error occurred and address the system failure that allowed it.
BRC auditors describe this as fixing the product instead of fixing the process. It is a repeat finding across hundreds of sites every audit cycle. If you see the same NC appearing in consecutive audits, this is usually why.
5 Whys, Used Correctly
The 5 Whys methodology is the most widely used RCA tool in food manufacturing, and it is frequently misapplied. The discipline of the method is to keep asking why until you reach a systemic cause: a failure in a procedure, a training gap, a management system weakness. Stop at a human error explanation and you have not done the job.
A correct 5 Whys for a labelling error: wrong label applied, because the operator selected the incorrect label, because label storage is not segregated by product, because the labelling procedure does not specify a storage method, because the procedure has not been reviewed since the product range expanded. That last answer is a systemic cause. Fix it and you prevent recurrence.
An incorrect 5 Whys for the same finding stops at: operator selected incorrect label, operator did not follow procedure, human error. Human error is never a root cause. It is always a symptom of a system that made the error possible.
Fishbone Diagrams for Complex NCs
For more complex non-conformances, particularly repeat findings, food safety incidents, or NCs with multiple contributing factors, a fishbone (Ishikawa) diagram is more appropriate than 5 Whys alone. It forces consideration of multiple causal categories: people, process, plant, materials, environment, and management systems.
BRC auditors respond well to fishbone diagrams for serious NCs because they show the investigation considered multiple pathways rather than stopping at the most obvious explanation.
What a Complete RCA Record Looks Like
A complete RCA record for BRC should include: a clear description of the non-conformance, the immediate correction taken, the root cause identified and the method used to find it, the preventive action implemented to address that root cause, the person responsible, the target date, and evidence that the action was effective.
That last element is where otherwise good records fall apart. Stating that training was delivered is not the same as verifying the training was effective. Evidence of effectiveness might be a re-inspection of the area, a supervisor observation record, or a subsequent audit result showing the clause passed cleanly.
Repeat Findings
A repeat NC, the same clause failed in two consecutive audits, is a significant finding at a BRC certification visit. It signals either that the root cause was not correctly identified, or that the corrective action was not effectively implemented or verified. BRC auditors weight repeat findings heavily.
Tracking repeat findings proactively, before the certification auditor spots them, is one of the most valuable things an internal audit programme can do. AuditCore flags repeat findings automatically, giving Technical Managers the chance to address them before they become a risk to certification grade.