CAPA report: the document a customer audit reads line by line

A CAPA report — CAPA is corrective and preventive action — is the document recording what went wrong, why it happened, what was done to fix it, what was done to stop it recurring, and the evidence that the fix worked. It is issued to customers after a complaint, produced to auditors during an inspection, and kept as the permanent record of how the problem was closed.

Because it is read by people who were not there, the report is judged on its internal logic rather than on the effort behind it. A cause that does not explain the failure, or an action that does not address the cause, is visible immediately — and in a regulated environment it turns one problem into two.

What a CAPA report contains

• The problem statement: what happened, when, how it was detected, and the scope — how many units, batches, orders or customers are affected.
• Immediate containment: what was done to stop the harm continuing, distinct from the corrective action.
• Investigation: the evidence examined and the method used, not just the conclusion.
• Root cause, stated as a cause and not as a category. "Human error" is a category.
• Corrective action: what changes so this cause cannot produce this failure again.
• Preventive action, where the same cause could produce failures elsewhere.
• Implementation record: who did what, on what date.
• Effectiveness check: how you will know it worked, when it will be assessed, and the result.
• Closure, with approval by someone other than the author.

The three sections that fail

Root cause is the first. A root cause analysis that ends at "operator did not follow procedure" has stopped one step early: why was the procedure not followed, and was it followable? The corrective action that follows from the shallow version is retraining, which is why retraining appears in so many reports and prevents so few recurrences.

Scope is the second. A complaint about one shipment prompts a report about that shipment, while nobody asks whether the same cause affected everything else made that week. Auditors ask, and an unanswered scope question reopens the whole investigation.

Effectiveness is the third, and it is the one that distinguishes a real system from a paperwork one. Closing a CAPA on the day the action is implemented tests nothing. Effectiveness needs a defined measure and a defined period afterwards — the same defect rate reviewed a quarter later, the same audit finding not repeating.

Not every problem deserves a CAPA. Systems that route every minor deviation into the full process produce backlogs of open records, and an overdue CAPA list is itself an audit finding. Define a threshold — severity, recurrence, regulatory exposure — and handle the rest as corrections.

Writing one that closes cleanly

1. Write the problem statement in terms a reader outside the department can follow, with quantities and dates.
2. Separate correction from corrective action explicitly; both belong in the report, in different sections.
3. Show the investigation method, and where evidence sits, so a reviewer can follow the reasoning rather than trust it.
4. Make each action specific enough to have a completion date and an owner.
5. Define the effectiveness measure at the time of writing, not at closure — deciding it afterwards invites a measure that was always going to pass.
6. Have closure approved by someone independent of the action.

A CAPA report is a record with a long afterlife: it will be sampled in audits for years, and its attachments — investigation notes, revised procedures, effectiveness data — must still be attached when it is. Ettex Records keeps the report with its evidence and its approval trail, so the version presented to a customer is the version that was approved, and the effectiveness check that was promised is visible as an open item until it is done. The wider quality management system still has to define when a CAPA is raised.