Effectiveness Check

What an effectiveness check is

An effectiveness check (sometimes called effectiveness verification or effectiveness review) is the verification step that confirms a corrective or preventive action actually addressed the root cause and prevented recurrence. It happens after the action's been implemented and after enough time has elapsed for the effect to be observable. The check produces a documented conclusion — effective, partially effective, or not effective — with the corresponding decision on CAPA status.

It's the discipline that separates closed CAPAs from credibly closed ones. Programs that close CAPAs on the basis of action-implemented rather than action-verified-effective produce repeat findings in the next inspection cycle. The action got done; whether it actually worked was never proven.

Effectiveness check is explicitly required by 21 CFR §820.100(a)(4) for medical devices, expected by ICH Q10 §3.2.2 for pharmaceutical quality systems, and required by ISO 13485 §8.5.2 for medical device QMS. The expectation is universal: implementing the action is necessary but insufficient; verification of effectiveness is the closure gate.

Why effectiveness check is the most-watched CAPA closure control

The recurring pattern in enforcement findings is consistent. The firm closed a CAPA that subsequently failed. The action was implemented (training delivered, procedure revised, equipment replaced), the CAPA was closed on the basis of completion, and within six to twelve months the same root cause produced another deviation, another batch failure, another complaint. The inspector pulls the CAPA, sees it was closed without effectiveness verification, and the finding stacks: the original deviation, the missed effectiveness check, the recurrence that should have been prevented.

Modern regulator practice now expects this discipline explicitly. ICH Q10 §3.2.2 names effectiveness assessment as part of the CAPA system. ISO 13485 §8.5.2 requires verification that actions taken are effective. The FDA December 2018 DI Q&A treats CAPA effectiveness as a quality-program indicator. Inspections increasingly ask not just \"do you have CAPAs?\" but \"do you have evidence the CAPAs worked?\".

There's a behavioural side as well. Programs that close CAPAs without effectiveness verification develop a pattern of repeat root causes — same issues, same actions, repeated cycle after cycle. The action-implemented-equals-closed habit prevents the learning that effective CAPA is supposed to produce. Programs with strong effectiveness discipline learn faster and find fewer recurrences.

Inspector perspective: the CAPA closure record is the trace. Pick a closed CAPA, look at how the action was verified effective. What were the criteria? When was the check performed? What evidence supports the conclusion? Then look for recurrences (same root cause, similar issue) in the period after closure. When criteria were vague, the check was premature, or recurrences happened, the finding writes itself.

Where effectiveness check obligations come from

Effectiveness verification is explicit in several frameworks and implicit in many more:

• 21 CFR §820.100(a)(4) — Corrective and preventive action: each manufacturer shall establish procedures to verify or validate the corrective and preventive action to ensure that such action is effective and doesn't adversely affect the finished device. The most explicit U.S. requirement.
• 21 CFR §820.100(b): all activities required under §820.100 and their results shall be documented — the evidence requirement.
• 21 CFR §211.192: investigation of unexplained discrepancies; effectiveness verification of resulting actions implicit in the closure expectation.
• 21 CFR §211.180(e): quality unit responsibility for evaluation of complaints, recalls, returned products, investigations — implicitly includes effectiveness of resulting actions.
• ICH Q10 §3.2.2 — CAPA: the CAPA process should include assessment of the effectiveness of the corrective and/or preventive actions taken. The explicit pharmaceutical-side requirement.
• ICH Q10 §4 — Continuous Improvement: CAPA is an enabler of continuous improvement; effectiveness verification is what makes it actually improve.
• ICH Q9(R1) (effective 2023): quality risk management evaluation of CAPA outputs.
• ISO 13485 §8.5.2 — Corrective action: organisation shall verify that actions taken are effective. The explicit device QMS requirement.
• ISO 13485 §8.5.3 — Preventive action: same verification expectation for preventive action.
• ISO 9001:2015 §10.2: nonconformity and corrective action; review of effectiveness of any corrective action taken.
• EU GMP Chapter 1 §1.4(xiv): deviations investigated and documented; effectiveness implicit in the management of corrective actions.
• EU GMP Chapter 8: complaints and product defects; effectiveness of resulting corrective actions implicit.
• FDA Data Integrity and Compliance With Drug CGMP Q&A (December 2018): CAPA effectiveness referenced in DI context.
• MHRA "GxP" Data Integrity Definitions and Guidance for Industry (March 2018, updated September 2021): CAPA closure and effectiveness as DI controls.

How effectiveness check actually runs

A defensible effectiveness check moves through these stages:

• Criteria definition at CAPA approval. When the action plan is approved, the effectiveness criteria are defined: what will be measured, against what threshold, over what period, with what evidence. Defining criteria at check time invites bias and tends to produce "it worked" conclusions.
• Action implementation. The corrective or preventive action is executed. Implementation evidence captured (training records for training-based actions, signed SOP revisions for procedure-based actions, qualification records for equipment-based actions).
• Waiting period. Time for the action to demonstrate impact — typically defined per action type. 60-90 days for training. A process cycle or quarter for process changes. Multiple supply cycles for supplier-related actions. The waiting period is defined when the action is approved, not improvised.
• Evidence collection. During or after the waiting period, evidence is gathered against the defined criteria: trend data, audit verification, performance metrics, follow-up sampling, complaint trends in the affected category.
• Verification. An independent reviewer (typically QA, not the CAPA owner) evaluates the evidence against the criteria and documents the conclusion. Conclusion options: effective, partially effective with residual risk noted, not effective.
• Closure or reopening. Effective conclusion routes to CAPA closure with signed effectiveness review record. Partially effective triggers extended monitoring with documented residual-risk acceptance. Not effective reopens the CAPA, often with revisited root cause analysis.
• Learning feedback. Failed effectiveness checks feed back into the investigation discipline — what did the original RCA miss? Why was the action insufficient? Patterns of failed checks across CAPAs reveal systemic gaps in investigation depth.
• Management Review input. Effectiveness check closure rates, failed-effectiveness rates, recurring root causes after closure are standing inputs to Management Review under ICH Q10 §3.2.4 and ISO 13485 §5.6.2.

What strong effectiveness check programs do

The patterns that hold up at inspection:

• Criteria defined at action approval. Not at check time. Objective, measurable, time-bound, tied to root cause.
• Risk-based depth. Critical CAPAs get deeper effectiveness verification with longer monitoring; minor CAPAs proportionate.
• Independent verifier. Not the CAPA owner. QA or an independent quality function performs the check.
• Appropriate waiting period. Defined per action type at approval. Not improvised. Not premature.
• Evidence-based conclusion. "Effective" backed by documented data, not opinion. Trend data, audit verification, metrics.
• Three-outcome capability. Effective / partially effective / not effective — not binary. Partial effectiveness with documented residual risk is a valid outcome.
• Closure gated on effectiveness. CAPA can't close until effectiveness is verified. System enforces, not just policy.
• Failed effectiveness reopens CAPA. With revisited root cause analysis if needed. Failed checks are escalated, not ignored.
• Recurrence tracking. Closed CAPAs are monitored for recurrence; recurrence within defined period reopens or triggers a new CAPA with reference to the prior.
• Learning feedback. Patterns of failed effectiveness checks feed investigation training, RCA template improvements, and Management Review.
• Management Review input. Effectiveness metrics standing input per ICH Q10 §3.2.4.

How Complere supports effectiveness check

Inside the CAPA workflow, your effectiveness check is a required step before the CAPA can close. When your team approves the action plan, the criteria, the evidence basis, and the verification timing are defined right there — not bolted on weeks later when the check is due. That removes the most common bias: writing criteria around the outcome you want.

The effectiveness review itself is a distinct record attached to the CAPA. You see who performed the review, what evidence they relied on, the conclusion they reached — effective, partially effective, or not effective — and the signed sign-off with the meaning attached. The review carries its own history of edits. Each conclusion drives the next move automatically: effective takes the CAPA to closure, partially effective opens extended monitoring with residual risk noted, not effective reopens the CAPA with a clear link back to the failed check so the investigation can be revisited.

Where a CAPA is closed out through a change, the change-control effectiveness review carries the same discipline. The two records cross-link, so the CAPA closing on the back of a change can show the change actually delivered the result.

What stays with your team: defining the right criteria for each specific CAPA (the threshold, the observation window, the evidence that will actually demonstrate the action worked), choosing an independent reviewer who isn't the CAPA owner, and the discipline of treating failed effectiveness as learning that feeds back into your investigation practice. Complere provides the closure gate and the record structure; the substance of whether a CAPA actually worked is your quality decision.

Related CAPA and quality system terms

Effectiveness check sits at the closure end of CAPA and intersects with several disciplines:

• CAPA — effectiveness check is the closure gate for CAPA
• Root Cause Analysis — failed effectiveness often signals weak RCA
• Change Control — change effectiveness review uses same discipline
• Deviation — significant deviations trigger CAPAs requiring effectiveness check
• Investigation Management — the investigation feeds the action that effectiveness verifies
• Management Review — effectiveness metrics are standing MR inputs
• Internal Audit — audit findings drive CAPAs requiring effectiveness check
• CAPA & Deviations Module