Quality & Continuous Improvement

Corrective and Preventive Actions: CAPA and Examples

By Claudia · · 6 min read

Quality technician logging corrective and preventive actions in a report

Corrective and preventive actions: CAPA and examples

Corrective and preventive actions are the heart of any quality management system in the food industry. Yet many quality teams handle them reactively, incompletely, or without proper follow-up — which means the same problems keep coming back. In this article we explain how to design a corrective and preventive action system that actually works, from opening to closing, including how it connects to non-conformities and audits.

The difference between corrective and preventive action

Before getting into the mechanics of the process, it's essential to be clear on the conceptual distinction between these two types of actions. Confusing them is one of the most common mistakes quality teams make.

A corrective action responds to a problem that has already happened. Its goal is to eliminate the root cause of a detected non-conformity so it doesn't happen again. It's not about patching the symptom, but about attacking the source: why did the process fail? What condition allowed it? A corrective action acts on the past to protect the future.

A preventive action, on the other hand, kicks in before the problem occurs. It starts from identifying a potential risk or a worrying trend, and aims to eliminate the cause of a potential non-conformity. This is where data analysis, system reviews, and proactive monitoring of quality indicators come into play.

In regulatory terms, as set out by the International Organization for Standardization in its ISO 22000 and ISO 9001 standards (ISO, n.d.), management systems must include structured mechanisms for both types of action, ensuring continuous improvement of the system and preventing failures before they affect product safety or quality.

In practice, many food companies only document corrective actions because they're visible and urgent. Preventive actions get pushed to the back burner — and that's precisely what holds back the maturity of the quality system.

Well-documented corrective and preventive actions: how to open and close them

A poorly documented action is almost as useless as never opening one. For a corrective or preventive action to be effective, it needs to follow a complete, traceable cycle.

Opening the action: The starting point is always identifying the problem or risk. It must be clearly recorded who detected the situation, when, and in what context. Next, a rigorous root cause analysis is essential. Tools like the 5 whys, the Ishikawa diagram, or fault tree analysis help you avoid stopping at the surface.

Planning the action: Once the root cause has been identified, you define the measures to implement, who's responsible for carrying them out, and a realistic closing deadline. Without an owner and a date, the action stays just an intention.

Verifying effectiveness: This is the step most often skipped, and the most critical one. Once the action has been carried out, you need to check whether it actually eliminated the cause of the problem. This verification must be documented and signed off by someone with the authority to validate it.

Formal closure: The action can only be closed once effectiveness has been demonstrated. Closure must be recorded with a date, evidence, and the quality manager's sign-off.

A well-documented system also lets you show any auditor that the organization has a genuine continuous improvement cycle, not just a formal one on paper.

Linking to non-conformities and audits

Corrective and preventive actions don't exist in isolation within the quality system. Their value multiplies when they're properly linked to detected non-conformities and to findings from internal and external audits.

When a non-conformity is detected — whether during production, in final product checks, or in an audit — it should automatically trigger the option to open an associated corrective action. This traceability between the non-conformity and the action is what closes the loop and proves the problem hasn't gone unanswered. You can dig deeper into how to manage this flow in the issue management section.

In the context of audits, auditors for standards such as BRCGS Global Standards (BRCGS, n.d.) expect to find a corrective action system that shows not just that actions were opened, but that they were closed with verified effectiveness and generated organizational learning. Actions left open, or closed without evidence of effectiveness, are red flags that can turn into major non-conformities during an audit.

This linkage should also extend to internal audits. Every internal audit finding should translate into an action — corrective if the deviation has already occurred, preventive if a potential risk is detected — and both must be traceable in the system. If you want to learn more about structuring this process, check out our guide to ISO 9001 auditing.

A good management system lets you cross-reference recurring non-conformity data with open and closed actions, spotting patterns and prioritizing the most critical areas for improvement. Without that overall view, quality managers are working blind.

How to automate follow-up in Solved

Managing corrective and preventive actions with spreadsheets or emails creates documentation chaos that makes follow-up, traceability, and audit preparation much harder. Solved is built specifically to solve this problem for food industry companies.

With Solved, you can open a corrective or preventive action in seconds, linked directly to the non-conformity or issue that triggered it. The system assigns owners, sets deadlines, and sends automatic reminders so no action gets forgotten in a drawer.

The tracking module lets you see the status of every open action in real time: how many are on schedule, how many are overdue, who's responsible, and what evidence has been attached. This control panel is especially useful for quality managers who need a full view of the system without wasting time manually consolidating information.

Effectiveness verification is also built into the workflow. Solved guides you to document whether the action was effective before allowing formal closure, ensuring the cycle is always completed correctly and in an auditable way.

When an audit comes around, all the information is centralized, traced, and available in one click: open and closed actions, their links to non-conformities, effectiveness evidence, and deadlines met. That's the difference between a stressful audit and one you face with confidence.

If your goal is to build a quality system that genuinely improves with every deviation and every risk identified, corrective and preventive actions managed in Solved are the engine that makes it possible.

References