On March 25, 2026, the FDA’s device center sent a warning letter to a manufacturer whose own trending data had flagged a corrective action as failing for three straight quarters. The CAPA was marked “done.” The problem was not. That gap — between an action closed on paper and a fix proven to work — is where recalls, warning letters, and repeat incidents live.
Summary: A corrective action fixes a known problem; verified closure proves the fix actually worked and holds over time. Marking a CAPA “done” closes the task, but only an effectiveness check — backed by evidence — confirms the underlying issue is gone. Most CAPA tools track status, not proof, which is why inadequate CAPA shows up in more than 60% of FDA warning letters. This guide explains the difference and how to build a workflow that closes the loop.
CAPA failures by the numbers
- The FDA issued 303 drug warning letters in FY2025, a 59% jump over the 190 sent in FY2024 (FDA, via The FDA Group).
- Inadequate CAPA appears in more than 60% of FDA warning letters — one of the most-cited quality-system failures (FDA Group analysis).
- In a March 2026 case, complaint data breached the threshold in Q1, Q2 and Q3 2025, yet no CAPA reopened until a warning letter arrived (CDRH).
Corrective action vs verified closure: the difference
A corrective action is the step you take to fix a problem and stop it recurring. Verified closure is the final gate: documented evidence that the action worked and the issue has not returned. One records intent. The other records proof.
The distinction matters because “closed” is the status auditors trust least. ISO 9001 and FDA expect an effectiveness check, not just a completed task. Without that check, you have a closed ticket and an open risk.
Why “marked done” is the most expensive status in your QMS
A closed CAPA feels like progress. It clears the queue and looks good on a dashboard. But if the fix did not hold, you have simply hidden the risk behind a green status.
The cost shows up later, and larger. A recurring defect becomes a recall. A repeat finding becomes a warning letter. The 2026 enforcement data makes the pattern clear: regulators increasingly cite firms whose own data flagged a failure they had already “closed.” For the wider pattern, see our analysis of 2026 FDA warning letters.
What verification actually requires
Verification is not a second signature. It is evidence that the corrective action changed the outcome. That means three things: objective evidence the action was implemented, a defined effectiveness check with a measurable criterion, and a re-trigger rule if the check fails.
Done properly, the CAPA cannot reach “verified closed” until the data confirms the fix. If the effectiveness check fails, the action reopens automatically. That single rule turns a status field into a control. Learn more about the concept in our guide to verified closure.
Closing CAPAs that actually stay closed? Download our free Verified-Closure CAPA Checklist — the evidence and effectiveness-check steps every corrective action should clear before it closes.
Where standard CAPA tools fall short
Most CAPA modules are workflow trackers. They move a record from open to closed and timestamp who did it. That is useful, but it measures activity, not effectiveness. Recurring checks like layered process audits help confirm a fix holds over time.
The missing pieces are evidence capture and the effectiveness gate. If the tool lets a user close a CAPA without attaching proof or passing a check, “closed” means only that someone clicked a button. A platform built around audit management should make verified closure the default, not an optional field.
Building a verified-closure workflow
Start by separating two states in your system: “action complete” and “verified closed.” Completing the action moves the record forward; it does not close it. Closure waits for the effectiveness check.
Then make evidence mandatory. Attach the photo, the measurement, the retest result, or the trend that proves the fix. Finally, set the re-trigger: if the check fails or the metric drifts back, the CAPA reopens and notifies the owner. The loop, not the checkbox, is what keeps problems from coming back.
Key Takeaways:
- A corrective action fixes a problem; verified closure proves the fix worked and holds.
- “Marked done” closes a task, not a risk — auditors trust evidence, not status.
- Verification needs implementation evidence, an effectiveness check, and a re-trigger rule.
- Most CAPA tools track workflow, not effectiveness — the gap drives recalls and warning letters.
- Separate “action complete” from “verified closed,” and reopen automatically when a check fails.
You might also be interested in
What Is Verified Closure in Audit & Inspection?
The definition behind the brand wedge — what verified closure means and why CAPA tools miss it.
FDA Warning Letters in 2026: Quality System Failures
What 2026 enforcement reveals about CAPA gaps — and how to avoid the same citations.
QMS Audit Checklist for 2026
A practical, clause-by-clause checklist for quality leaders preparing for 2026 audits.
Frequently Asked Questions (FAQs)
What is the difference between corrective action and verified closure?
A corrective action is the fix you apply to a problem. Verified closure is documented proof that the fix worked and the problem has not returned. The first records what you did; the second records the result.
Is closing a CAPA the same as fixing the problem?
No. Closing a CAPA marks the task complete. Without an effectiveness check, you have no evidence the root cause is gone — which is how “closed” issues resurface as recalls or repeat findings.
What is an effectiveness check?
An effectiveness check is a defined test, after the corrective action, that confirms the problem no longer occurs. It has a measurable criterion and a timeframe, and it must pass before the CAPA can reach verified closure.
Why do most CAPA tools miss verified closure?
Many tools are workflow trackers that let a user close a record once the action is marked done. If evidence and an effectiveness gate are optional, the system measures activity rather than whether the fix actually held.
How does verified closure satisfy ISO 9001 and the FDA?
Both expect evidence that corrective actions are effective, not just completed. A workflow that requires implementation evidence, an effectiveness check, and re-trigger on failure produces exactly the auditable record regulators look for.
Prove every CAPA actually worked
Certainty closes the loop with evidence and effectiveness checks — not just a status field.
