How to Read a CAPA

A CAPA record is supposed to end an investigation, not just close a ticket. Reading one for real means checking that the correction actually addresses the cause that was found, and that someone went back afterward to confirm it worked.

In brief

A CAPA under 21 CFR § 820.100 carries two separate obligations most files blur together: the corrective action fixes what already happened, and the preventive action stops the same failure mode from recurring elsewhere. A record that only does one has only done half the job.
Root cause has to be an actual cause, not a restatement of the symptom. “Operator error” or “the procedure was updated” are conclusions dressed up as causes if the record doesn’t show why the error was possible in the first place.
Effectiveness verification is the step that gets skipped most often — and the one an inspector asks about first. A CAPA that closes without evidence the fix actually worked is a plan, not a completed corrective action.
A CAPA rarely starts from nothing. It’s triggered by a complaint, a nonconformance, an audit finding, or a trend crossing a threshold, and a usable file states that trigger explicitly instead of presenting the investigation as if it began in a vacuum.

What separates a root cause from a symptom

A usable root-cause analysis traces backward from the nonconformance until it reaches something the organization can actually change — a process step, a specification, a training gap, a design element — and stops there, not one level short. “The seal failed because the seal did not hold” restates the failure in different words; it isn’t an explanation. “The operator did not follow the procedure” is closer, but still incomplete on its own: it doesn’t say why the procedure wasn’t followed. Was the step unclear as written? Was training inadequate? Did the procedure conflict with a production-line reality nobody had reconciled? Whichever answer is true is the actual root cause, and it’s usually one layer past where the first draft of the investigation stops.

Why effectiveness verification is not optional

Implementing a fix and verifying it worked are two different milestones, and a file that closes them on the same date usually means the effectiveness check didn’t happen, or happened too early to mean anything. A real effectiveness check uses the same metric that caught the problem in the first place — the same inspection point, the same complaint category, the same audit criterion — observed over a defined period after the fix is in place, not just a confirmation that the fix was installed. This is also where a CAPA connects to the rest of the quality system: closing an investigation without checking it against ongoing complaint trending or the relevant entry in the risk management file is how the same failure mode gets rediscovered from scratch the next time it surfaces, instead of being recognized as a repeat.

Where this goes wrong

Writing the root cause as a restatement of the nonconformance

Describing the failure again in different words isn’t the same as explaining why it happened, and a reviewer reading both statements side by side will notice.

Closing the CAPA the day the fix is implemented

Implementation and effectiveness are different milestones. Closing them together usually means the effectiveness check didn’t happen, or happened too soon to be meaningful.

Scoping the CAPA to the single unit that failed

If a design or process cause is confirmed, the same defect exists in every unit built under that design or process — not only the one a customer happened to notice.

None of this is unique to CAPA — it’s the same documented-reasoning discipline that runs through a complaint file or a risk management file. What makes a CAPA distinct is that it’s the record meant to prove the organization actually learned something, not just that it responded.

Sources & further reading

21 CFR § 820.100 — Corrective and Preventive Action ecfr.gov
Regulatory Academy — How to Read a Complaint File regulatoryacademy.com
Regulatory Academy — How to Read a Risk Management File regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.