Inspection Case File · CF06 · Quality Systems

The CAPA closure most files can't defend.

The 60-second version

The problem: The CAPA is closed and signed. The investigator asks who authorized the effectiveness conclusion, on what evidence, and against what alternative explanations.
The gap: Most files contain the closure. They don't contain the reasoning. That gap is what 21 CFR 211.192 evaluates and what 483 observations cite.
What you'll see: The exact 483 language, the five fields a defensible record requires, a complete reference example, and the blank template for your facility.

See What Defensible Looks Like → Free to read. No payment to continue.

Citation · 21 CFR 211.192 ICH · Q10 Used by Quality leaders preparing for FDA inspections

The Scene

Day three of the inspection. The investigator pulls CAPA-2023-0894 — a label mix-up. Three months later, no recurrence. The CAPA Coordinator signed the closure. The investigator turns to the conclusion.

Read the full scene

The investigator pulls CAPA-2023-0894. A label mix-up incident on the packaging line in 2023. Corrective actions: revised line clearance procedure, additional verification step, operator retraining.

The effectiveness check was completed in February 2024 — three months post-implementation. The conclusion: actions are effective. CAPA closed.

The investigator turns to the conclusion.

Investigator

"Who authorized the effectiveness conclusion? What metrics were tracked, and over what period? What constituted sufficient evidence of effectiveness? And how did the team rule out that the absence of recurrence was due to factors other than the corrective action?"

She listens to the verbal answer. Then she asks for the documented reasoning.

Why this matters

The conclusion belongs in the file. The decision belongs in the record.

By every internal measure, this CAPA was sound. Three months without recurrence. Documented verification. Signed closure. But the file contained a conclusion — not a decision.

Most QA teams answer the investigator's question verbally. The file does not contain the documented reasoning. That is the gap.

Read the full evaluation context

21 CFR 211.192 requires that corrective actions be effective. The standard is not whether recurrence happened. The standard is whether the effectiveness conclusion was reached on a documented basis.

Under ICH Q10 expectations, effectiveness verification requires defined metrics, defined observation periods, and documented analysis distinguishing the corrective action effect from confounding variables.

The effectiveness check must demonstrate — in writing, contemporaneous with the conclusion — that the metrics were appropriate, that the observation period was sufficient, and that the named authorizing individual reviewed both before concluding effectiveness.

Three months without recurrence is data. Three months without recurrence is not, on its own, a documented effectiveness conclusion.

The Gap

The corrective actions may have been effective. The file does not show the work behind the conclusion.

Which effectiveness metrics were tracked, and why those metrics
Why three months was deemed a sufficient observation period
What confounding factors were considered
How the line audit results were weighed
The named individual who authorized the effectiveness conclusion

The CAPA file documents the closure. It does not document who decided the actions were effective, on what evidence, against what alternatives, and under what authority.

The 483 Observation

This is the citation language an investigator drafts when the gap appears in a CAPA file.

"Failure to document the scientific and risk-based rationale used to justify the conclusion that the corrective action and preventive action were effective, including the specific evidence supporting the determination that recurrence had been prevented and the basis on which the observation period was deemed sufficient. The CAPA closure record establishes that the action was completed but does not reconstruct the reasoning that justified the effectiveness conclusion."

Cited under · 21 CFR 211.192 · applied regulatory framework

Continued · Part 02 of 03

That 483 was avoidable.

See the record that prevents it.

The five fields the investigator expects to find. The alternative-causes evaluation that distinguishes a decision from a signature. A complete reference example from the label mix-up scenario.

Show Me the Record →

✓ Free to read · No payment required to continue

Used by Quality and Validation leaders preparing for FDA and EMA inspections. Built around 21 CFR 211.192 and ICH Q10.