How to Write a CAPA
Turn a problem into a corrective and preventive action that actually holds.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
A CAPA (Corrective and Preventive Action) is how a quality system stops a problem from recurring — not just fixes the instance in front of you. The hard part is not the form; it is finding the real root cause and proving the action worked. This is the sequence that survives an inspection.
- 1
Confirm it actually needs a CAPA
Not every event is a CAPA. A one-off correction with no recurrence risk may just need a documented fix. Reserve CAPA for issues where the system, not the instance, is at fault — recurring deviations, trends, audit findings, complaints.
- 2
Investigate to root cause
Use a structured method (5 Whys, fishbone, fault tree). Stop at a systemic cause you can act on — "the two containers were easy to confuse", not "operator error". A symptom-level cause produces a symptom-level action.
- 3
Define the corrective action
The corrective action addresses the specific occurrence and its immediate consequences — contain, correct, remediate affected product. This is the "make it right now" step.
- 4
Define the preventive action
The preventive action changes the system so the cause cannot recur — distinct labelling, an added verification step, a design change. This is the part inspectors probe hardest, because it is the part teams skip.
- 5
Assign owners, due dates, and verification
Every action needs a named owner, a due date, and a defined way to verify effectiveness. Without an effectiveness check, you have a task list, not a CAPA.
- 6
Implement and verify effectiveness
Execute the actions, then confirm — with evidence, after enough time or occurrences — that the cause is actually gone. Effectiveness verification is what closes the loop.
- 7
Close with the evidence trail intact
Close the CAPA only when the effectiveness check passes, with the investigation, actions, and evidence all traceable. A CAPA closed before effectiveness is verified is a finding waiting to happen.
- !A "retrain the operator" CAPA — the classic weak action that treats the occurrence, not the recurrence, and leaves the system unchanged.
- !Closing the CAPA before effectiveness is verified.
- !Confusing the correction (fix the instance) with the preventive action (stop recurrence) — you need both.
- !Root cause stated as "human error" with no systemic cause behind it.
How to Write a CAPA: frequently asked questions
Common questions on write a capa.
What is the difference between corrective and preventive action?
Corrective action addresses the specific problem that occurred (fix it and remediate its consequences). Preventive action changes the system so the cause cannot recur. A complete CAPA has both — an inspector who sees only correction will ask where the prevention is.
Does every deviation need a CAPA?
No. A one-off event with a clear, contained cause and no recurrence risk may only need a documented correction. CAPA is for issues where the system is at fault — recurring events, adverse trends, audit findings, or complaints — so that effort goes where recurrence is actually likely.
What is effectiveness verification?
It is the evidence, gathered after the action is implemented, that the root cause is actually gone — the deviation has not recurred over a defined period or number of occurrences. It is the step that lets you close the CAPA, and the step teams most often skip.
Is "retraining" an acceptable CAPA?
Rarely on its own. Retraining treats this occurrence, not the recurrence, and leaves the conditions that made the error easy fully in place. Use it only alongside a systemic change that makes the mistake hard to make.