This is a ready-to-use SOP for CAPA effectiveness verification, the step that proves a corrective or preventive action actually worked, not just that it was completed. It complements a general CAPA management procedure by governing the effectiveness phase specifically. Replace every <<FILL: ...>> placeholder, set your document numbers and dates, and route through your normal document control. A filled specimen follows. Confirm each cited regulation against the current source before you rely on it. This is general educational reference, not regulatory or professional advice; adapt it to your quality system.
Document control header
| Field | Entry |
|---|---|
| Document title | CAPA Effectiveness Verification |
| Document number | <<FILL: SOP-ID, e.g. SOP-QA-021>> |
| Version | <<FILL: version, e.g. 1.0>> |
| Effective date | <<FILL: date>> |
| Supersedes | <<FILL: prior version or "New">> |
| Document owner | <<FILL: role, e.g. Head of Quality Assurance>> |
| Parent SOP | <<FILL: SOP-ID for CAPA management>> |
1. Purpose
This procedure defines how <<FILL: COMPANY NAME>> designs, schedules, executes, and closes effectiveness verification for corrective and preventive actions, so that a CAPA is confirmed to have achieved its intended result and the original problem and its cause have not recurred. It distinguishes effectiveness verification from implementation verification and prevents the most common CAPA weakness: closing on “action completed” without proving the problem stopped.
2. Scope
This procedure applies to CAPAs raised under <<FILL: parent CAPA SOP>> at the sites in scope. It governs the effectiveness phase only; event triage, investigation, root-cause analysis, and action implementation are covered by the parent SOP.
3. Definitions
- Implementation verification: documented confirmation that the action was completed as planned (SOP issued, training records complete, equipment installed).
- Effectiveness verification: documented, objective confirmation that the completed action achieved its intended result and the problem did not recur, judged against criteria set before data collection.
- Verification window: the defined period or number of occurrences over which recurrence is monitored, starting when the action became effective in the live environment.
4. Responsibilities
| Role | Responsibility |
|---|---|
| CAPA / action owner | Proposes the effectiveness-check design; implements the action; provides implementation evidence; often executes the data collection. |
| Subject matter expert (SME) | Confirms the metric reflects the root cause; helps set a realistic window; interprets borderline results. |
| Quality Assurance | Approves the effectiveness-check design before data collection; reviews evidence; makes or approves the effective / not-effective decision; owns closure integrity. |
| Area / line management | Sustains the action in daily operation beyond the window. |
5. Procedure
5.1 Design the effectiveness check at action approval
Before any action is implemented, define and have QA approve the five elements. Designing criteria after seeing data is a finding.
- Metric: objective, measurable, tied directly to the root cause and action. Default to recurrence of the specific event type.
- Acceptance criterion: quantitative or clearly observable, set against a documented baseline, and able to fail. Zero recurrence is the usual bar for safety-critical or major events.
- Sample size / window: justified by occurrence frequency, not calendar convenience. For a zero-recurrence claim, size the window so the absence is meaningful (a useful check: to bound the rate below a target p from zero events, aim for roughly 3 divided by p opportunities).
- Timing: the window starts only when the action is effective in the live environment; set a target verification date and owner.
- Objective evidence: state in advance what dated, attributable record will prove the result.
5.2 Implement and verify implementation
Implement the action through its own controls (change control, training, document revision). Confirm and document that it was completed as planned, and attach the implementation evidence. This is not effectiveness.
5.3 Run the verification window
- Record the start date as the date implementation became effective in the live environment.
- Collect the metric over the window (deviation query, observations, audit-trail review, trend chart). Do not adjust the criterion based on what you see.
- Record actual numbers, not just “pass”.
5.4 Evaluate and decide
- Effective: result meets the pre-set criterion. Document the conclusion with evidence; QA approves; close the CAPA or the effectiveness phase.
- Not effective: result misses the criterion. Do not close. Reopen or escalate, re-examine root cause (the action likely treated a symptom), define a new action, and design a new effectiveness check. Document the original failure honestly.
5.5 Closure model
Use one defined model and state it in the record:
- Model A: the CAPA stays open until effectiveness is verified, then closes.
- Model B: the implementation phase closes and the effectiveness check is tracked as a scheduled forward activity with its own due date, owner, and independent closure.
Under either model the effectiveness check must actually be performed and documented. Closing the whole record with the effectiveness check marked “to be completed” and no follow-through is not permitted.
5.6 Feed trending
Record the outcome where it feeds trending and management review, so recurrence patterns across multiple CAPAs are visible. See quality-metrics-and-kpis and management-review-q10.
6. Acceptance criteria
A closure is acceptable when all of the following are true:
- The five design elements were defined and QA-approved before data collection.
- The metric is objective and tied to the root cause; the criterion could fail.
- The window has a documented rationale based on occurrence frequency.
- The evidence is objective, dated, attributable, and matches the pre-defined plan.
- The conclusion states actual results; a failed check shows reopening, not a quiet pass.
- The effectiveness check was completed before the record (or the effectiveness phase) closed.
7. References
21 CFR 820.100(a)(4) (verify/validate CAPA effectiveness); 21 CFR Part 4 (combination products); QMSR incorporating ISO 13485:2016, effective 2 February 2026. 21 CFR 211.192 (investigation, conclusions, follow-up) and 211.22 (quality unit responsibility). ICH Q10, Pharmaceutical Quality System (CAPA as a core element). ICH Q9(R1), Quality Risk Management (risk-based formality).
Confirm the current version and clause numbers of each reference before issue.
8. Records generated
- The completed effectiveness-check plan and result (see CAPA Effectiveness Check template).
- The effectiveness-check tracking entry (see CAPA Effectiveness Check Tracking Log).
9. Revision history
| Version | Date | Author | Summary of change |
|---|---|---|---|
<<FILL: 1.0>> | <<FILL: date>> | <<FILL: author>> | Initial issue. |
10. Approvals
| Role | Name | Signature | Date |
|---|---|---|---|
| Author | <<FILL>> | ||
| Reviewer (QA) | <<FILL>> | ||
| Approver (Quality Head) | <<FILL>> |
Filled specimen
The following shows the section 5.1 design completed for an illustrative CAPA. Details are illustrative.
Parent CAPA: CAPA-2026-041, recurring mis-weigh deviations at dispensing. Root cause: ambiguous SOP step and no independent weight verification.
| Element | Definition |
|---|---|
| Metric | Recurrence of dispensing deviations attributable to incorrect weight |
| Baseline | 4 such deviations in the prior quarter (about 1 per 8 operations) |
| Acceptance criterion | Zero mis-weigh deviations across the window; 100 percent of observed operations show the second-operator verification performed |
| Sample size / window | First 30 dispensing operations after implementation, or 90 days, whichever comes later, plus 12 direct observations across 3 shifts (30 chosen because baseline of ~1 in 8 gives multiple recurrence opportunities) |
| Timing | Window starts on the SOP effective date confirmed in the live area; target verification date 90 days out |
| Evidence | Deviation-system query for mis-weigh events with search criteria recorded; signed observation checklists |
| Owner / approver | Dispensing lead executes observations; QA owns the effectiveness conclusion |
QA approved this design before the SOP revision was implemented, so the criterion could not later be shaped to fit the result.
Common inspection findings this SOP prevents
- Implementation evidence presented as effectiveness (“we retrained” with no recurrence data).
- Criteria written at closure to match whatever happened.
- Windows too short or too small to make “zero recurrence” meaningful.
- A CAPA closed with the effectiveness check “to be performed” and no record it ever was.
- A failed check quietly passed by arguing the miss was acceptable.
- Effectiveness outcomes never fed into trending, so recurring patterns stay invisible.
How to adapt this SOP
- Set your document number, owner, and parent CAPA SOP in the header.
- Choose and state one closure model (A or B) in section 5.5.
- Make the effectiveness-check due date a tracked, alerting item in your CAPA system so it cannot lapse.
- Point the records in section 8 to your real forms and tracking tool.
- Confirm every regulation in section 7 against the current published version before issue.