On this page
CAPA stands for Corrective and Preventive Action — the structured process a quality system uses to fix a problem, stop it from happening again, and prevent likely problems before they occur. If you’ve ever wondered what CAPA is or what the acronym means, that’s the short version; the rest of this guide explains the difference between corrective and preventive action, the CAPA process step by step, real examples, and why auditors sample CAPA records first.
What is CAPA?
CAPA is a core quality management process for investigating problems, eliminating their root causes, and preventing recurrence. It turns a one-off fix into a documented, verifiable improvement. The term bundles two related but distinct activities: corrective action (responding to something that already went wrong) and preventive action (acting on a risk before it becomes a problem). A CAPA record captures the whole story — what happened, why, what you did about it, and proof that it worked.
Corrective action vs. preventive action
This is the distinction most people blur, and auditors test:
- Corrective action addresses a problem that has already occurred. A nonconformance, a customer complaint, a failed inspection — you investigate the root cause and act so it doesn’t recur.
- Preventive action addresses a problem that hasn’t happened yet but could. A trend heading the wrong way, a risk identified in a review, a near-miss — you act to stop it before it becomes a nonconformance.
Correction is a third thing people confuse with both: a correction is the immediate fix (scrap the bad part), while corrective action is eliminating the cause so you stop making bad parts. All three have a place; only root-cause work closes a CAPA.
The CAPA process, step by step
A sound CAPA follows a repeatable flow:
- 1. Identify and document the problem or risk, with enough detail to investigate.
- 2. Contain / correct — take immediate action to limit the impact (quarantine product, notify affected parties).
- 3. Investigate root cause — use a real method (5 Whys, fishbone, 8D) rather than guessing. Symptoms aren’t causes.
- 4. Plan the action — define corrective (and where relevant preventive) actions, owners, and due dates.
- 5. Implement the actions and record what was done.
- 6. Verify effectiveness — the step teams skip most. Confirm, with evidence, that the action actually prevented recurrence.
- 7. Close the CAPA with the effectiveness evidence attached.
Miss step 6 and you don’t have a CAPA — you have a to-do list. Effectiveness verification is what turns action into assurance.
CAPA examples
- Corrective: Repeated label mix-ups trace to two similar part numbers stored together. Action: physically separate them and add a scan-verify step; verify by auditing the next 50 builds for zero mix-ups.
- Preventive: Calibration due-dates are trending toward lateness. Action: add automated reminders and a buffer; verify the next quarter has zero overdue instruments.
- From a complaint: A customer reports a packaging defect; root cause is a worn tool. Action: replace the tool and add it to preventive maintenance; verify with post-change inspection data.
Why CAPA matters — ISO 9001, ISO 13485, and FDA
CAPA isn’t optional for most regulated organizations. ISO 9001 requires corrective action and a risk-based approach to prevention; ISO 13485 and the FDA’s regulations make CAPA an explicit, heavily scrutinized requirement for medical device makers. In an audit, CAPA records are among the first things an auditor pulls, because they reveal whether your quality system actually learns from problems or just logs them. A weak CAPA program is one of the most common sources of findings. It also connects to the rest of the system — a CAPA often starts from a deviation or nonconformance and surfaces during an audit.
Common CAPA mistakes
- Treating a correction as a corrective action — fixing the symptom and closing the record without addressing the cause.
- Skipping effectiveness verification — closing on “action completed” instead of “problem prevented.”
- Opening a CAPA for everything — overloading the system so real issues get buried; use risk to decide what warrants a full CAPA.
- Weak root-cause analysis — stopping at the first plausible explanation.
- No traceability — the CAPA, the triggering event, and the resulting document or training changes living in separate places.
How QMS software manages CAPA
A spreadsheet can list CAPAs, but it can’t enforce the process or prove effectiveness. QMS software runs each CAPA through a consistent workflow — identification, root cause, action plan, verification, closure — with due dates, reminders, and a complete audit trail. More importantly, it connects CAPA to the rest of the quality system: a CAPA can link to the deviation that triggered it, drive a document revision through change control, and assign the resulting training automatically — all traceable in one place. That connected flow is the whole point of an eQMS, and it’s exactly how TLM handles CAPA. If you want to see a CAPA run end to end — from problem to verified closure — book a demo and we’ll walk it through on your kind of process.
Frequently asked questions
What does CAPA stand for?
CAPA stands for Corrective and Preventive Action. It’s the quality-management process for investigating a problem, eliminating its root cause so it doesn’t recur (corrective action), and acting on likely problems before they occur (preventive action).
What is the difference between corrective and preventive action?
Corrective action responds to a problem that has already happened — you find and eliminate the root cause so it doesn’t recur. Preventive action addresses a potential problem that hasn’t happened yet but is likely — you act on the risk or trend before it becomes a nonconformance. Both are part of CAPA.
What is the difference between a correction and a corrective action?
A correction is the immediate fix — scrapping or reworking the bad product. A corrective action goes further: it eliminates the underlying cause so you stop producing the problem at all. A correction treats the symptom; corrective action treats the disease.
What are the steps in the CAPA process?
Identify and document the problem; contain or correct the immediate impact; investigate root cause with a real method (5 Whys, fishbone, 8D); plan corrective and preventive actions with owners and dates; implement them; verify effectiveness with evidence; and close the CAPA with that evidence attached. Effectiveness verification is the step teams most often skip.
Is CAPA required by ISO 9001 and the FDA?
Yes. ISO 9001 requires corrective action and a risk-based approach to prevention; ISO 13485 and FDA regulations make CAPA an explicit, closely audited requirement for medical device manufacturers. CAPA records are among the first things an auditor reviews, because they show whether a quality system actually learns from problems.
What is the difference between 8D and CAPA?
8D (Eight Disciplines) is a specific structured problem-solving methodology often used to execute a corrective action, especially in automotive and manufacturing. CAPA is the broader quality-system process that includes corrective and preventive action; an 8D can be the method you use inside a CAPA’s root-cause and action steps.