All guides How-to · 3 min read

Building a CAPA process that works

Corrective and preventive action is where quality systems prove they learn. Auditors read CAPA records to see whether problems get fixed for good, or just fixed. Here's a process that holds up, and the records it needs.

Updated October 7, 2026 · Not legal or regulatory advice: check the current regulation and your own procedures.

Correction, corrective action, preventive action

  • Correction fixes the problem in front of you (rework the batch, recalibrate the balance).
  • Corrective action removes the cause so it doesn't happen again.
  • Preventive action removes the cause of a potential problem before it happens.

Not every deviation needs a CAPA. Decide by risk: a one-off with a known cause may need only a correction; a recurring or serious problem needs an investigation and a CAPA.

The steps

  1. Identify the problem and its source (deviation, complaint, audit finding, trend, nonconformance).
  2. Evaluate its risk and decide whether a CAPA is needed.
  3. Contain it: protect product and customers now.
  4. Investigate the root cause with a method suited to the problem (5 whys, fishbone, fault tree), with evidence, not opinion.
  5. Plan actions that address the root cause, each with an owner and a due date.
  6. Implement them, through change control where they change processes or documents.
  7. Verify effectiveness after enough time has passed to show it worked, against criteria set in advance.
  8. Close it with approval, and feed it into management review.

The record auditors look for

  • A clear problem statement and where it came from, linked to the source record
  • The risk assessment and the decision that a CAPA was (or wasn't) needed
  • Containment actions and what happened to affected product
  • The investigation and the root cause, with evidence
  • Actions with owners, due dates and completion
  • The effectiveness check: the criteria, the result, and who decided
  • Approval signatures, and the full history of changes

Mistakes that lead to observations

  • "Retrain the operator" as the root cause and the action, every time.
  • Effectiveness checks that are just "action completed".
  • CAPAs open for months with no extensions approved.
  • No trending: the same problem opened as new CAPAs again and again.

Requirements for this sit in 21 CFR 211.192 and 211.100 for drugs, ISO 13485 §8.5.2 and §8.5.3 (and so the FDA's QMSR) for devices, and ISO 9001 §10.2 everywhere else.

Sources

Templates for this

Start from a working process.

Quality

Deviations and CAPA

Record deviations, assess their impact, and open a corrective and preventive action when one is needed. CAPAs are reviewed and approved, with reminders before they fall due.

  • Deviations 15 columns · IDs like DEV-0001 · signed: QA approval
  • CAPA 13 columns · IDs like CAPA-0001 · signed: Reviewed by, Approved by
  • Reminder: Deviation due in 3 days
  • Reminder: Deviation overdue
  • Reminder: CAPA due in 3 days
  • Reminder: CAPA overdue

21 CFR 211.192 · FDA QMSR (21 CFR 820) · ISO 13485 §8.5.2 · ISO 9001 §10.2 · EU GMP Ch. 1

Quality

8D problem solving

Customer and internal problems worked through the eight disciplines, from the team and containment to root cause, permanent corrective action and preventing recurrence, approved by Quality, with reminders before the due date.

  • 8D reports 16 columns · IDs like PS-0001 · signed: Approved by
  • Reminder: 8D report due in 3 days
  • Reminder: 8D report overdue

IATF 16949 §10.2.3 · ISO 9001 §10.2 · AS9100 §10.2

Quality

Nonconformances

Product or material that doesn't meet requirements: identify it, decide its disposition, and get it approved.

  • Nonconformances 14 columns · IDs like NC-0001 · signed: Disposition approved by
  • Reminder: Nonconformance due in 3 days
  • Reminder: Nonconformance overdue

ISO 9001 §8.7 · ISO 13485 §8.3 · FDA QMSR (21 CFR 820) · AS9100 §8.7 · IATF 16949 §8.7

See it with your own process

Bring your own process to a demo.