Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

A CAPA can be marked complete after a procedure, training, or design change is implemented—even if nobody has shown that the original failure stopped. The key distinction is implementation versus effectiveness: completing an action is not the same as proving it corrected the cause or prevented recurrence.

What CAPA closure does—and does not—show

Corrective and preventive action (CAPA) is a quality process for containing a problem, investigating its cause, assigning and implementing actions, verifying implementation, and checking later whether those actions worked. A record may document each planned task as complete, but that alone does not establish that the action addressed the failure mechanism.

A useful review separates two questions: Was the action carried out? and Did it change the outcome that made the action necessary? For example, a revised procedure can be issued and training can be recorded while the underlying product or system issue remains. The effectiveness check is meant to test the result, not merely confirm that the planned activity occurred. FDA inspection guidance directs inspectors to assess whether actions were effective and whether similar problems occurred after implementation: FDA CAPA inspection guidance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What a meaningful effectiveness check needs to test

The check should be connected to the original failure and the conditions in which it occurred. FDA’s examples illustrate why a favorable metric can still be inadequate when it measures the wrong people or fails to distinguish between plausible causes.

  • Failure mechanism: Does the measure test whether the original problem stopped, or only whether the planned task was completed?
  • Representative conditions: Does the sample reflect the users, products, processes, and circumstances where the failure can happen?
  • Cause and action alignment: Did the investigation distinguish plausible causes, and does the action address them rather than a convenient proxy?
  • Observable evidence: Could the pass criterion still be met if the channel that should detect failures stopped producing observations?
  • Decision rules: Are the observation window, threshold, responsible owner, and conditions for escalation or reopening defined?

These are practical review questions drawn from the cases below, not a claim that FDA mandates one universal statistical method, duration, or closure formula.

FDA example: a 100% pass rate did not establish effectiveness

In a warning letter dated January 28, 2026, FDA criticized Beta Bionics’ CAPA 0050 for its iLet Bionic Pancreas System. The company’s verification-of-effectiveness assessment used employees taking revised training material, rather than the actual iLet user population. Beta Bionics reported a 100% assessment pass rate, but FDA found the check inadequate: the root-cause determination and criteria did not distinguish potential system-design issues from user-training deficiencies. The resulting preventive actions focused on training without addressing potential device-design issues.

FDA stated: “The root cause determination and verification of effectiveness criteria for CAPA-0050 is deficient in that it fails to distinguish between system design issues versus user training deficiencies and subsequently the preventive actions were solely focused on training improvements without addressing potential device design issues.” Read the FDA Beta Bionics warning letter.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The point is not that a pass rate is inherently meaningless. It is that a result can look strong while failing to answer whether the action addressed the actual cause in the population exposed to the problem.

FDA example: a procedure change and same-day closure

FDA’s May 22, 2026 warning letter to ZIIP describes CAPA 33 being closed on the same date as the document change notice for revised complaint procedures, without documented verification of effectiveness. The letter also identifies other CAPAs whose effectiveness-check fields lacked documentation. A recorded process change shows that a change was made; without a documented follow-up, it does not show that the change worked. See the FDA ZIIP warning letter.

How to review a closed CAPA when the problem still occurs

  1. Trace the record back to the original failure. Identify the complaint, defect, or other event and the conditions under which it happened.
  2. Read the root-cause analysis, not just the action list. Check whether it considered plausible alternatives and whether the chosen cause explains the failure.
  3. Match each action to the cause it is supposed to address. A training change may be appropriate for a training gap, but it does not by itself resolve a possible design problem.
  4. Inspect the effectiveness evidence. Look for the measure, sample, observation period, threshold, and results—not only a completion date or an assertion that the action was implemented.
  5. Check for recurrence in the relevant population and conditions. If similar failures continue, determine whether the sample or detection process could have missed them and whether escalation or reopening is warranted under the applicable quality process.

A continuing problem does not, by itself, prove that every part of a CAPA was ineffective. It is a reason to examine whether the closure evidence tested the original failure adequately and whether the investigation or action needs to be revisited.

Keep performance claims in their proper context

The Project Shadow post that shares this article’s central thesis describes a beta/prelive system and says it is neither production authorization nor proof of real-world efficacy. Its creator reports that a synthetic “BLACK floor” was respected in 6 of 10 cases in a smoke test, and reports a 3–10% improvement in personal testing when an optional narrative “Myth” sidecar was used on most tasks. The post does not establish independent validation or a validated outcome measure for that improvement; it calls for a preregistered myth-on/myth-off study. These are author-reported observations, not generalizable performance findings. See the Project Shadow post and discussion.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

What the examples establish

The FDA letters document specific deficiencies at Beta Bionics and ZIIP; they do not establish how common these failures are across industry, or that every closed CAPA is ineffective. They do show why closure status and evidence of effectiveness are different things: a completed action can leave the original problem unresolved if the follow-up does not test the relevant cause, users, or conditions.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.