Finding the root cause is only half the battle. Without a strong corrective action plan, the same problem will keep coming back. This guide shows you how to go from root cause to lasting fix using the CAPA framework — the standard approach in manufacturing, healthcare, and quality management worldwide.
What is a corrective action plan?
A corrective action plan (CAP) is a documented set of steps designed to eliminate the root cause of a problem and prevent it from recurring. It is the natural next step after a root cause analysis or a 5 Whys session.
A good corrective action plan answers four questions:
- What caused the problem? (root cause — already identified)
- What will we do to fix it? (corrective action)
- How will we prevent it from happening elsewhere? (preventive action)
- How will we know it worked? (verification)
Corrective vs. preventive action
Corrective action eliminates the root cause of a problem that has already occurred. For example: recalibrating a machine that produced defective parts.
Preventive action addresses potential causes in similar processes before a problem occurs. For example: adding automated calibration alerts to all machines on the floor, not just the one that failed.
Together, they form the CAPA (Corrective And Preventive Action) framework — a requirement in ISO 9001, FDA regulations, and most quality management systems.
The CAPA framework: 6 steps
Whether you work in manufacturing, IT, healthcare, or any other field, the CAPA process follows the same structure:
Define the problem
Restate the problem from your root cause analysis. Be specific and measurable: "15% defect rate in batch #4420 on Line 3" is far better than "quality issues."
Confirm the root cause
If you ran a 5 Whys analysis, the root cause is already identified. Verify it one more time: "If we eliminate this cause, would the problem definitely not recur?" If the answer is uncertain, dig deeper. See common 5 Whys mistakes for pitfalls to avoid.
Develop corrective actions
Define specific actions that eliminate the root cause. Each action must be concrete, not vague. "Improve training" is not an action. "Create a 30-minute calibration module and certify all Line 3 operators by April 15" is.
Develop preventive actions
Look at similar processes and systems. Could the same root cause exist elsewhere? Preventive actions extend the fix beyond the immediate problem. If calibration was missed on Line 3, check Lines 1, 2, and 4 too.
Assign owners and deadlines
Every action needs a single owner (not a team — a person) and a specific deadline. Without ownership, actions drift into "someone should do this eventually" territory, which means they never happen.
Verify effectiveness
After implementation, measure the results. Did the defect rate drop? Did the incident recur? Schedule a verification check 2-4 weeks after the fix goes live. If the problem returns, your root cause was incomplete — go back to step 2.
How to prioritize corrective actions
Not all actions are equal. When your root cause analysis reveals multiple actions to take, use the Impact vs. Effort matrix to prioritize:
| Category | Impact | Effort | Priority |
|---|---|---|---|
| Quick wins | High | Low | Do first (this week) |
| Major projects | High | High | Plan and schedule (this month) |
| Fill-ins | Low | Low | Do if time allows |
| Money pits | Low | High | Deprioritize or drop |
Always ask: "Will this prevent recurrence, or just reduce frequency?" Actions that prevent recurrence entirely are worth more effort than those that only make the problem less likely.
Corrective action plan template
Use this structure to document your plan. You can also download a ready-to-use version from our free templates page.
Corrective Action Plan
Problem statement: [Specific, measurable description of the problem]
Date identified: [Date]
Root cause: [From your 5 Whys or RCA]
Root cause method used: [5 Whys / Fishbone / FTA / Other]
Corrective actions:
1. [Action] — Owner: [Name] — Deadline: [Date]
2. [Action] — Owner: [Name] — Deadline: [Date]
Preventive actions:
1. [Action to prevent recurrence in similar processes] — Owner: [Name] — Deadline: [Date]
Verification method: [How you will confirm the fix worked]
Verification date: [2-4 weeks after implementation]
Status: [Open / In Progress / Completed / Verified]
Example 1: Manufacturing quality issue
1. Recalibrate CNC machine on Line 3 immediately. Owner: Maintenance Lead. Deadline: Today.
2. Assign calibration tasks to roles (not individuals) in the maintenance schedule. Owner: Plant Manager. Deadline: March 22.
Preventive actions:
1. Install automated calibration reminder alerts for all CNC machines (Lines 1-4). Owner: IT. Deadline: April 1.
2. Add a "calibration status" gate to the batch start checklist — production cannot begin if calibration is overdue. Owner: QA Manager. Deadline: April 1.
Verification: Track defect rates on Line 3 for the next 5 batches. Target: below 2%. Review date: April 15.
Example 2: IT service disruption
1. Renew the expired SSL certificate and restore payment processing. Owner: DevOps Lead. Deadline: Completed (March 8).
2. Migrate all certificate notification emails to ops-infra@company.com team alias. Owner: DevOps Lead. Deadline: March 15.
Preventive actions:
1. Deploy automated certificate monitoring (cert-manager or similar) that alerts 60, 30, and 7 days before expiration. Owner: SRE Team. Deadline: March 30.
2. Create an infrastructure ownership registry documenting every critical service, its owner (role, not person), and renewal dates. Owner: Engineering Manager. Deadline: April 15.
Verification: Confirm zero certificate-related incidents for 60 days. Audit the ownership registry monthly. Review date: May 15.
Start with the root cause
A corrective action plan is only as good as the root cause it addresses. Use our free guided tool to find the real cause first.
Start Free 5 Whys Analysis →Common mistakes in corrective action planning
- Vague actions. "Improve training" or "be more careful" are not corrective actions. Every action must answer: what exactly will change, who will do it, and by when?
- No owner assigned. If nobody owns it, nobody does it. Assign a single person, not a team or department.
- No deadline. "As soon as possible" is not a deadline. Set a specific date.
- Skipping the verification step. Without verification, you have no idea whether the fix actually worked. Schedule a check 2-4 weeks after implementation.
- Fixing symptoms instead of root causes. If your corrective action addresses a symptom rather than the underlying cause, the problem will recur. Use the 5 Whys method to dig deeper before writing your plan.
- Only corrective, no preventive. Fixing the immediate problem is good. Preventing it from occurring in similar systems is better. Always ask: "Where else could this happen?"
- No documentation. An unwritten plan does not exist. Use a template to keep everything in one place.
When to use CAPA
The CAPA framework is mandatory in regulated industries (FDA, ISO 9001, aerospace), but it is just as valuable in any business context:
- After any root cause analysis — to turn findings into action
- After incident postmortems — especially in DevOps and SRE teams
- After customer complaints — when the same issue comes up repeatedly
- After audit findings — to demonstrate corrective response
- In Agile retrospectives — when a sprint action item requires more structure than a Jira ticket. See 5 Whys in Agile for more.
Sources & further reading
- ASQ — Corrective Action — American Society for Quality resource on CAPA fundamentals
- FDA — Guide to Inspections of Quality Systems — FDA's guidance on CAPA in regulated environments
- ISO 9001:2015 — International standard for quality management systems, includes CAPA requirements
- ASQ — Five Whys — Overview of the 5 Whys method for root cause identification
Frequently asked questions
What is a corrective action plan?
A corrective action plan (CAP) is a documented set of steps designed to eliminate the root cause of a problem and prevent it from recurring. It typically includes the problem statement, root cause, specific corrective and preventive actions, owners, deadlines, and verification criteria.
What is the difference between corrective and preventive action?
Corrective action eliminates the root cause of an existing problem so it stops happening. Preventive action addresses potential causes in similar processes or systems before a problem occurs. Together they form the CAPA framework used in quality management.
How do you write an effective corrective action?
An effective corrective action is specific, measurable, and owned. Instead of "improve training," write "Create a 30-minute onboarding module covering calibration procedures by April 15. Owner: QA Manager. Verify by auditing the next 3 batches for zero calibration-related defects."
What is CAPA in quality management?
CAPA stands for Corrective And Preventive Action. It is a systematic framework used in regulated industries like manufacturing, healthcare, and aerospace to address existing problems (corrective) and prevent potential future problems (preventive). ISO 9001 and FDA regulations require documented CAPA processes.
How long should a corrective action plan take to implement?
Quick fixes (low effort, high impact) should be implemented within days. Medium-term actions typically take 2-4 weeks. Long-term systemic changes may take 1-3 months. Every action should have a specific deadline. The verification step should happen 2-4 weeks after implementation to confirm the fix worked.
📚 Recommended Reading
- The Checklist Manifesto — Atul Gawande — Build reliable corrective action checklists
- The Lean Six Sigma Pocket Toolbook — George et al. — 100+ tools for quality improvement and CAPA