A non-conformity you fix at the surface comes back. That is the difference between a correction and a corrective action, and the tool that separates them is root cause analysis. In an SQF audit, an auditor does not just want the problem fixed; they want proof you found and eliminated the reason it happened.
Root cause analysis (RCA) is a systematic method for finding the underlying cause of a non-conformity, so a corrective action fixes the real problem instead of the symptom. Applied well, it stops findings from recurring and turns each audit into continuous improvement. This guide covers what RCA is, whether SQF requires it, the main methods, a five-step process, and real SQF examples.
Key Takeaways
- RCA finds the "why behind the why." It looks past the surface problem to the systemic cause, so the fix actually prevents recurrence.
- SQF requires it. The corrective and preventive action clause requires investigating root cause, and SQF Edition 10 makes that clause a Core Clause worth more points.
- Four methods do most of the work: the 5 Whys, fishbone (Ishikawa) diagrams, Pareto analysis, and fault tree analysis.
- "Human error" is not a root cause. If an operator made a mistake, ask why the mistake was possible: training, procedure clarity, or workload.
- Verify the fix. A corrective action is not closed until you have evidence the root cause is gone and the problem has not returned.
What Is Root Cause Analysis in an SQF Audit?
Root cause analysis is the structured investigation that determines the fundamental reason a deviation or non-conformance occurred within a food safety management system. In an SQF audit it separates three things auditors treat very differently:
- Correction: the immediate fix (throw out the affected product, re-clean the line).
- Corrective action: the action that removes the root cause so it does not happen again.
- Preventive action: a change that stops similar problems elsewhere before they occur.
A correction without a corrective action is why the same finding shows up year after year. RCA is how you get from one to the other.
Does SQF Require Root Cause Analysis?
Yes. The SQF Food Safety Code's clause on corrections, corrective and preventive actions requires the site to investigate and record the root cause of a non-conformity, not just correct it.[1] Under SQF Edition 10, that clause is designated a Core Clause, so a major non-conformity there carries a heavier scoring penalty, raising the stakes on doing RCA properly. The FDA's preventive controls rule sets the same expectation: corrective action procedures must identify and correct the problem and reduce the likelihood it recurs.[2] In short, root cause analysis is not optional, and auditors are trained to test whether yours is real.
What Are the Main Root Cause Analysis Methods?
Four problem-solving tools cover almost every food safety investigation. Most sites use them in combination, for example a fishbone diagram to map possible causes and the 5 Whys to drill into the likeliest branch.
| Method | How it works | Best for |
|---|---|---|
| 5 Whys | Ask "why" repeatedly (about five times) until you reach a systemic cause you can act on | Simple, single-cause problems and quick investigations |
| Fishbone (Ishikawa) diagram | Map possible causes across categories such as people, process, equipment, materials, and environment | Complex problems with several possible causes |
| Pareto analysis | Rank causes by frequency to find the vital few that drive most of the problem (the 80/20 rule) | Recurring defects where you need to prioritize |
| Fault tree analysis | Work backward from the failure through the logical combinations of events that could cause it | High-risk failures and supply-chain or systems problems |
How to Do Root Cause Analysis: A 5-Step Process
- Define the problem precisely. State exactly what the non-conformity is, where and when it happened, and how it was detected. A vague problem statement produces a vague root cause.
- Collect the evidence. Gather records, monitoring data, observations, and photos before the trail goes cold.
- Investigate with a method and a team. Apply the 5 Whys, a fishbone diagram, Pareto, or fault tree analysis, with a cross-functional group so the problem is seen from every angle.
- Identify and verify the true root cause. Test your conclusion: if you removed this cause, would the problem stop? If not, keep digging. Stop at a cause you can actually control, never at "human error."
- Correct, act, and verify effectiveness. Make the correction, implement the corrective action that removes the root cause, and then confirm with evidence that it worked and the problem has not returned.
Root Cause Analysis Examples in SQF Audits
These four examples show how a method leads from a surface finding to a corrective action that sticks:
| Audit finding | Method used | Root cause found | Corrective action |
|---|---|---|---|
| Elevated microbial counts in finished product | 5 Whys + fishbone | Inadequate sanitation, traced to undertrained cleaning staff and poor equipment | Retrained cleaning staff, upgraded protocols, invested in better sanitation equipment |
| Variable quality in a key ingredient | Fault tree analysis | Supplier's weak quality control and poor transport conditions | Tightened supplier controls, added transport checks, diversified sourcing |
| Recurring packaging defects | Pareto analysis | Most defects traced to one machine on an irregular maintenance schedule | Preventive maintenance schedule, operator training, added pre-release quality checks |
| Temperature swings in cold storage | Data and record analysis | Malfunctioning temperature controls and inadequate insulation | Overhauled controls, upgraded insulation, added real-time alarms and monitoring training |
Why Corrective Actions Fail Without Root Cause Analysis
The most common reasons a corrective action does not hold, and the ones auditors see repeatedly:
- Fixing the symptom. Discarding contaminated product without asking why it was contaminated guarantees a repeat.
- Blaming "human error." That is where the analysis should start, not stop. Ask why the error was possible.
- Stopping at the first plausible cause. The first answer is often a contributing cause, not the root.
- No effectiveness check. A closed corrective action with no verification is a guess. SQF expects proof it worked.
Looking for an SQF certification body? Request a quote or explore SQF certification with Kiwa ASI.
Frequently Asked Questions
Q: What is the 5 Whys method?
A: A root cause technique where you ask "why" the problem happened, then "why" about that answer, roughly five times, until you reach a systemic cause you can control. It is the fastest RCA tool and works best for straightforward, single-cause problems.
Q: What is the difference between a correction and a corrective action?
A: A correction is the immediate fix, such as discarding affected product. A corrective action removes the root cause so the problem does not recur. SQF audits require both, and the corrective action is where root cause analysis lives.
Q: Does SQF require root cause analysis?
A: Yes. The SQF corrective and preventive action clause requires investigating and recording the root cause of non-conformities, and SQF Edition 10 elevates that clause to a Core Clause with a heavier scoring weight.
Q: What are common root causes in food safety audits?
A: The recurring ones are inadequate or unclear procedures, insufficient training, missed or poorly designed preventive maintenance, weak supplier controls, and gaps in monitoring or verification. "Human error" is almost always a symptom of one of these.
Related reading
Sources
[1] Safe Quality Food Institute. The SQF Code (corrections, corrective and preventive action requirements).
[2] Electronic Code of Federal Regulations. 21 CFR 117.150: Corrective Actions and Corrections.