The gap usually isn't effort. It's structure. A CAP that doesn't separate containment from root cause, or implementation from effectiveness, can't tell you whether the fix worked.
This guide gives you a reusable corrective action plan template, defines every field, walks through how to complete it, and includes a worked manufacturing example. The central principle: a strong CAP addresses the observed problem, its verified root cause, the corrective action taken, objective evidence it was implemented, and proof the issue won't recur.
Key Takeaways
- Separate immediate containment from the long-term corrective action: they solve different problems
- Every action needs one named owner, a due date, completion evidence, and an effectiveness check
- Root cause analysis must address system or process failure, not stop at "retrain the operator"
- Closure requires documented proof the action worked, not just proof it was done
What Is a Corrective Action Plan and When Should You Use One?
A corrective action plan is a documented method for resolving an existing nonconformity or recurring issue by addressing its underlying cause and preventing it from happening again. It's not the same as fixing the immediate problem in front of you.
ISO 9000:2015 draws a precise line here: correction eliminates a detected nonconformity, while corrective action eliminates its cause and prevents recurrence, according to ISO 9000:2015. Preventive action, by contrast, addresses a potential problem that hasn't occurred yet.
CAP vs. Other Documentation Types
A CAP is the wrong tool for several common situations:
- Quick correction: reworking a single bad part with no systemic cause
- Troubleshooting note: informal diagnosis with no formal closure requirement
- Project task: planned improvement work, not a response to a nonconformity
- Employee performance plan: individual coaching, not a process failure
- Preventive action: addressing a risk that hasn't yet produced a defect
When a Formal CAP Is Warranted
In US quality and compliance environments, common triggers include:
- Internal audit findings
- Customer complaints
- Product or process nonconformities
- Supplier issues, safety incidents, and recurring defects
- Regulatory findings
Not every nonconformity needs one, though. The FDA's own CAPA guidance states that the degree of corrective action should be commensurate with the significance and risk of the problem, according to FDA's CAPA training. Before opening a formal CAP, weigh:
- Severity: could this harm a customer, worker, or product safety?
- Recurrence: has this happened before, even in a different form?
- Customer or regulatory impact: does a contract, standard, or agency require escalation?
- Systemic risk: could the same failure occur on another line, shift, or site?
If a simple correction resolves the issue with no systemic exposure, a CAP may be overkill. If any of the above apply, it isn't.
Corrective Action Plan Template: The Fields to Include
Think of this as a flexible structure, not a rigid form. Map these fields to whatever system you run (ISO 9001, AS9100D, medical device QMS, EHS program, or internal manufacturing procedure) and adjust for your own applicable requirements.
Reference, Source, and Risk
- Finding or issue ID and date opened
- Source (audit, complaint, inspection, supplier issue)
- Affected process or product
- Applicable requirement or clause
- Severity or risk rating
- Links to supporting records
Problem Statement
Describe observable facts: what happened, where, when, and how it was detected. Avoid assumptions about cause or blame. Skip vague phrases like "communication issue". They hide the actual failure instead of describing it.
Immediate Correction and Containment
Separate what controls the current problem from what eliminates it long-term. Containment actions include:
- Segregating affected product
- Stopping a process temporarily
- Correcting a record
- Issuing a temporary work instruction
Root Cause Analysis
Record the method used, who participated, evidence reviewed, contributing causes, and the verified root cause. "Operator error" alone is not an adequate analysis unless you've investigated the system factors that let the error happen.
Corrective Action(s), Owner, Resources, and Due Date
Each action should:
- Begin with a specific verb (redesign, revise, install, not "address")
- Target a verified cause, not a symptom
- Name one accountable owner
- State dependencies or resources needed
- Include a realistic completion date
Verification of Implementation
Objective evidence that proves the action happened: an approved procedure revision, equipment record, updated inspection form, training record, supplier response, or configuration change.
Verification of Effectiveness and Closure
Include the effectiveness measure, review date, reviewer, results, residual risk, follow-up actions if needed, closure approval, and where the final record lives. Completing an action is not the same as proving it worked. That's a separate field, with separate evidence.
How to Fill Out a Corrective Action Plan
Start with the source record. Before proposing any solution, scope the issue: which lots, products, processes, shifts, suppliers, sites, or customers are affected?
Write a Factual Problem Statement
Use this formula: requirement or expected condition + observed condition + evidence + impact. Replace general language with verifiable facts tied to traceable records. "Inspection records didn't match actual practice" is weak. "Records on 14 work orders show verification signed off within 2 minutes of a 20-minute process step" is usable.
Decide on Containment and Correction
Document immediate risk control separately from permanent corrective action:
- Identify affected material and apply temporary controls
- Notify customers if shipped product is implicated
- Reinspect suspect lots or work
- Record disposition decisions (use-as-is, rework, scrap)
Select an Appropriate Root Cause Method
Match the method to the complexity and risk of the issue. Don't apply one tool mechanically to every problem.
| Method | Best fit |
|---|---|
| 5 Whys | Simple, single-cause issues |
| Fishbone | Multiple possible cause categories |
| Fault tree analysis | Complex combinations of failures |
| 8D | Cross-functional, customer-facing issues |
| FMEA | Prospective risk, not an actual failure's cause |
Test proposed causes against evidence. Don't assume correlation proves cause. Ask whether the same failure could occur elsewhere in the organization, not just on the line where it was found.
Write Actions That Eliminate the Cause
Convert vague actions into real changes:
- "Retrain staff" → revise the work instruction and add a verification checkpoint
- "Improve communication" → add a documented handoff step with sign-off
- "Monitor more closely" → set a defined check frequency with recorded results
Make each action SMART without inventing targets you can't support: define the expected condition, owner, deadline, required evidence, and a measurable effectiveness criterion tied to the actual process.
Plan Implementation and Evidence
Identify who approves, communicates, executes, and verifies the change. Account for document control, affected training, record updates, and system changes.
A connected workflow, where the finding, root cause analysis, corrective action, revised documents, training records, and verification results all link together, keeps the audit trail intact instead of scattered across emails and shared drives.
QMS Learning's AI Workbench and Manager Dashboard are one example of this kind of system: the Workbench helps route a problem to the right method, and the dashboard tracks evidence through closure.
Corrective Action Plan Example: From Finding to Closure
Here's a realistic manufacturing scenario, worked field by field.
Source and problem statement: Incoming inspection found an out-of-tolerance bore on three lots from one supplier. Records show the required dimensional verification was signed off, but measurement-system checks reveal the inspection couldn't physically have been completed within the time logged for that process step.
Containment and correction: Suspect stock across all three lots was segregated immediately, pending full remeasurement. A temporary 100% reinspection instruction was issued for incoming material from this supplier until the investigation closed.
Root cause analysis: The investigation didn't stop at "inspector skipped the check." It traced the failure further:
- The checklist required 14 verification points in a time slot designed for 8
- Backlog from a prior shift created pressure to sign off quickly
- No secondary review existed to catch incomplete verifications
- Similar checklists on two other lines shared the same time-to-task mismatch
Corrective actions:
- Redesign the checklist around actual cycle time (Owner: Process Engineering, due in 3 weeks)
- Approve the revision through document control (Owner: Quality Manager, due in 1 week after redesign)
- Update training records for all affected inspectors (Owner: Training Lead, due 1 week after approval)
- Review two other lines for the same failure mode (Owner: Quality Manager, due in 4 weeks)
Implementation evidence: Approved checklist revision, updated training records with inspector sign-offs, and a completed review memo for the other two lines.
Effectiveness evidence: A 90-day follow-up review of inspection records and dimensional data from the supplier's subsequent shipments. It confirmed no recurrence of the out-of-tolerance condition and verification timestamps consistent with actual process duration.
Common Corrective Action Plan Mistakes—and How to Make a CAP Audit-Ready
Plans fail for predictable reasons: vague causes, ownership assigned to a department instead of a person, missing due dates, containment mistaken for final correction, and closure signed off immediately after implementation—before anyone checked whether it worked.
Bad versus better:
| Weak action | Better version |
|---|---|
| "Provide awareness training" | Revise the SOP, add a competency check, and record pass/fail results |
| "Improve quality culture" | Add a mandatory second-sign verification step with evidence retention |
Before closing any CAP, run an audit-readiness check:
- Source traceability confirmed
- Requirement or clause linked
- Root cause analysis documented, not assumed
- Actions approved and implemented
- Objective evidence attached
- Effectiveness reviewed against a defined measure
- Residual risk assessed
- Closure authorized by name
The ISO/IAF closure guidance is explicit on this point: closure needs evidence of full implementation and evidence the action prevented recurrence—not just one or the other.
When an action runs overdue or proves ineffective, don't quietly let it slide. Document the reason, revise the plan through controlled approval, reopen the issue if needed, and record what the team learned for other processes or sites.
Frequently Asked Questions
What is a corrective action plan?
A corrective action plan is a documented plan to correct an existing issue, address its root cause, assign responsibility, and verify that recurrence has been prevented. It goes beyond a quick fix to target the underlying cause.
What fields should be included in a corrective action plan?
At minimum: source and reference details, a factual problem statement, containment, root cause analysis, corrective action with owner and due date, implementation evidence, effectiveness verification, and closure approval.
How do you write a corrective action plan?
Define the factual issue, investigate the root cause with an appropriate method, select targeted actions, assign one owner per action, set realistic dates, and document both implementation and effectiveness evidence before closing.
What is the difference between correction and corrective action?
Correction addresses the immediate detected problem, like reworking a bad part. Corrective action eliminates the underlying cause so the problem doesn't happen again.
How do you verify the effectiveness of a corrective action?
Effectiveness verification relies on objective follow-up evidence (records, observations, audits, defect data, or process results) collected after implementation to confirm the change achieved its intended outcome.
When should a corrective action plan be closed?
Close a CAP only after actions are implemented, evidence is reviewed, effectiveness is confirmed, residual risk is acceptable, and an authorized person documents the closure decision.