Effectiveness is where CAPAs fall apart
CAPA procedures under § 820.100(a) were the most-cited device observation in FY2025, with 279 citations (GMP Insiders). King & Spalding notes that “CAPA was consistently the regulatory requirement most commonly cited in FDA 483 observations under the QSR” (King & Spalding). A common pattern: the action is completed, the CAPA closes, and the problem comes back.
For how to audit a CAPA system and prove it works, see CAPA Audit and Effectiveness Checks: How to Prove Your CAPA System Works.
What regulators require
| Source | Requirement |
|---|---|
| FDA QMSR (devices) | Manufacturers “must verify or validate corrective and preventive actions to ensure that such actions are effective and do not adversely affect the finished device” (Federal Register) |
| FDA CP 7382.850 (devices) | Investigators check “Verification and/or validation of effectiveness of corrective action(s)” and “The depth and details of investigation performed” (FDA) |
| ICH Q10 (pharma) | “CAPA should be used, and the effectiveness of the actions should be evaluated”; investigation effort “should be commensurate with the level of risk” (FDA/ICH) |
| FDA draft 483 response guidance (drugs, 2026) | Cites past responses that failed “to address the root cause of observations” (Federal Register) |
Why effectiveness checks fail
- No criteria set in advance. Success is defined after the fact, so almost anything passes.
- Checking completion, not outcome. “SOP revised and training completed” proves the action happened, not that it worked.
- Root cause was never proven. FDA warning letters criticize firms that cannot show “how you determined human error was the sole reason” for failures (FDA Warning Letter, 2025). As one industry leader put it, “human error is always a symptom — a starting point — for an investigation and is never the answer or cause” (Pharmaceutical Online).
- Window too short. Measuring for two weeks when the failure occurs quarterly proves nothing.
- No check for side effects. QMSR requires confirming actions “do not adversely affect the finished device.”
CAPA effectiveness check template
Complete the plan section when the CAPA is approved, before actions start.
| Field | What to write | Example |
|---|---|---|
| CAPA ID and problem statement | Specific, measurable problem | Seal leaks on lot release testing, 6 in Q2 |
| Verified root cause | Cause and the evidence that proves it | Sealing temperature drift; confirmed by DOE and controller logs |
| Actions | Correction, corrective action, preventive action | Controller replaced; temperature alarm added; PM interval shortened |
| Effectiveness criterion | Measurable success definition | Zero seal leaks across 30 consecutive lots |
| Data source | Where evidence will come from | Lot release test results, complaint system |
| Window | How long, and why | 30 lots (about 3 months), covering seasonal variation |
| Side-effect check | What could the action break? | Verify seal strength and bioburden unchanged |
| Owner and due date | Who measures, when | QA engineer, end of Q4 |
| Result | Met / not met, with evidence | 30/30 lots pass; seal strength within spec |
| Decision | Close, extend or reopen | Close |
CAPA effectiveness checklist
- Root cause supported by data, not assumed (“human error” alone is not accepted)
- Systemic scope assessed: other products, lines, sites or batches
- Effectiveness criterion is quantitative and set before implementation
- Measurement window long enough to see recurrence
- Evidence comes from an independent source (process data, complaints, audits), not from the action owner’s report
- Adverse effects on the product or process checked
- Risk file updated where the CAPA changed risk estimates or controls
- Ineffective CAPAs reopened, not closed with a new CAPA number
- CAPA effectiveness trends reviewed in management review
Find weak CAPAs before an investigator does
Weak CAPAs share patterns: vague criteria, “retrained operator” as the only action, missing risk updates. AI document assessment can read closed CAPA records and procedures against QMSR, ICH Q10 and your SOP, flag these patterns and cite the passage behind every finding.
Run a sample regulatory document assessment on a set of closed CAPAs. AskDona shows the evidence; your QA team decides.
FAQ
What is a CAPA effectiveness check? A planned, evidence-based confirmation that a corrective or preventive action achieved its goal and did not cause new problems.
Is CAPA effectiveness verification required under QMSR? Yes. FDA states manufacturers “must verify or validate corrective and preventive actions to ensure that such actions are effective” (Federal Register).
How long should an effectiveness check last? Long enough to see whether the problem recurs, based on how often it occurred before.
Is retraining an acceptable corrective action? Rarely on its own. Regulators expect a verified root cause and actions that address it.
References
All pages opened and checked by October 9, 2026.
| Source | Type | Date | Used for |
|---|---|---|---|
| Federal Register: QMSR final rule | Regulator | Feb 2, 2024 | Verify or validate CAPA |
| FDA: CP 7382.850 | Regulator | Feb 2, 2026 | Effectiveness inspection |
| FDA/ICH: Q10 | Regulator guidance | Apr 2009 | Pharma CAPA effectiveness |
| Federal Register: Draft 483 response guidance | Regulator | Mar 9, 2026 | Root cause expectation |
| FDA Warning Letter 320-25-88 (ProPublica copy) | Regulator | Jul 2, 2025 | Human error criticism |
| Pharmaceutical Online: Beyond human error | Industry roundtable | Nov 16, 2020 | Human error as symptom |
| GMP Insiders: FY2025 observations | Industry analysis | Jan 5, 2026 | CAPA citations |
| King & Spalding: QMSR goes live | Law firm | Feb 3, 2026 | CAPA most cited under QSR |