Root Cause Analysis: Corrective Actions That Stop Problems Coming Back
Why do problems keep coming back after corrective actions are closed, and how can root cause analysis deliver real results?
Many organisations close their nonconformity reports on time, only to find a few weeks later that the same problem has returned in a different form. The reason is rarely a missing procedure. More often it is confusion between correction, which deals with the visible effect, and corrective action, which removes the cause and prevents recurrence.
Management system standards, including ISO 9001, ISO 14001, ISO 45001 and ISO 22000, require the organisation to evaluate the need for action to eliminate the cause of a nonconformity and to review the effectiveness of what was done. That only happens with a structured root cause analysis based on evidence, not impressions or a search for someone to blame.
This article explains the key concepts, the main analysis tools, practical steps for effective corrective action and the mistakes auditors find again and again.
1. Correction, corrective action and prevention
| Concept | What it addresses | Example from a food plant |
|---|---|---|
| Correction | The immediate effect of the nonconformity | Holding and reprocessing a batch pasteurised at a low temperature |
| Corrective action | The root cause, to prevent recurrence | Changing the cleaning schedule of the heat exchanger whose scaling caused the low temperature |
| Risk-based thinking | Preventing the problem in the first place | Assessing critical equipment risks and planning preventive maintenance before deviations occur |
Recent editions of management system standards removed the separate “preventive action” clause because prevention is now part of planning and of managing risks and opportunities. Even so, the question “could this happen somewhere else?” remains an essential part of any good corrective action.
2. Root cause analysis tools
2.1 The 5 Whys
Start with the problem as it occurred and keep asking “why?” about each answer until you reach a cause that can be controlled through management or technical measures. Five is a guide: three questions may be enough, or you may need seven.
A short example:
- Why did a delivery reach the customer at 8 °C? Because the truck’s refrigeration unit failed.
- Why was the failure not detected before loading? Because the truck was loaded before it had cooled to 4 °C.
- Why was it loaded early? Because the morning loading schedule is tight and leaves no time for pre-cooling.
- Why did nobody stop the loading? Because the truck inspection form does not require a temperature reading before loading.
The root cause is not “driver negligence”. It is a gap in loading planning and in the inspection controls.
2.2 Fishbone (Ishikawa) diagram
Useful when there are many possible causes. It groups them into categories such as people, methods, equipment, materials, measurement and environment, and stops the team settling on the first explanation that comes to mind.
2.3 Data and trend analysis
A single case may be random, but repeated nonconformities of one type reveal a system weakness. Link the analysis to complaint records and monitoring results, and classify cases by process, line, shift and supplier.
2.4 Advanced tools
For critical or repeated problems, consider fault tree analysis, failure mode and effects analysis (FMEA), or the eight-disciplines (8D) problem-solving method common in automotive and manufacturing.
3. Steps to an effective corrective action
Step 1: Describe the problem precisely
The description should state what happened, where, when, which requirement was not met and what the evidence is. A vague statement such as “quality problem” leads to a vague analysis.
Step 2: Respond immediately
Control and correct the nonconformity and deal with the consequences, for example by holding product or informing the customer. In the food sector, assess whether the product is potentially unsafe and apply the withdrawal or recall procedure when needed.
Step 3: Form the right team
Do not leave the analysis to one person from quality. Involve the process owners and the people who actually do the work, because they are closest to the real causes.
Step 4: Analyse and confirm the root cause
Once a likely cause is found, confirm it with evidence: would removing it really prevent the problem? Does it explain all similar cases?
Step 5: Look for similar cases
Are other lines, sites or suppliers exposed to the same cause? This step turns a local fix into a system improvement.
Step 6: Implement the action and update the system
The action may require a revised procedure or form, training, an equipment change or an update to the risks and opportunities register. Any significant change should go through change management.
Step 7: Verify effectiveness
Do not close the action just because it was implemented. Define an effectiveness criterion and a follow-up period in advance, for example “no recurrence for 60 days and the KPI within target”.
4. Common mistakes found by auditors
- “Human error” as the root cause: human error is the result of conditions that can be controlled, such as job design, training, supervision or time pressure.
- “Retraining” as the only action: training helps, but it does not fix missing controls or a poorly designed process.
- Closure without evidence of effectiveness: closing an action because its due date has arrived, not because its results were proven.
- Analysing each case in isolation: handling every complaint separately hides trends.
- No link to risk: failing to update the risk assessment after a new cause is found.
5. KPIs for the corrective action system
| KPI | Calculation | Suggested target |
|---|---|---|
| On-time closure | Actions closed on time ÷ actions due | 90% or more |
| Effective actions | Actions proven effective ÷ actions closed | 85% or more |
| Recurrence rate | Cases recurring within 12 months ÷ total cases | Below 10% |
| Average closure time | Total days to closure ÷ number of actions | According to severity class |
These KPIs belong in management review and help decide whether more training or resources are needed.
Conclusion
A good corrective action system is not measured by the number of closed forms but by the number of problems that no longer return. Organisations that build root cause analysis skills in their teams, and link the results to risk, measurement and management review, turn every nonconformity into a real improvement opportunity.
Start by reviewing your last ten corrective actions: how many really removed the cause?