Glossary Term

CAPA (Corrective and Preventive Action)

The regulated process for investigating quality issues, removing their causes, and preventing recurrence across a QMS.

CAPA is the backbone of quality governance. A well-run CAPA program shows inspectors that your organization does not just fix issues — it understands why they happened and prevents them from returning.

Remove the cause. Prove it is gone.
On this page
  1. Definition
  2. Why It Matters
  3. Regulatory Context
  4. In Practice
  5. Key Controls
  6. Complere Approach
  7. Related Terms

What CAPA means

CAPA stands for Corrective Action and Preventive Action. It is the regulated quality process for responding to deviations, nonconformances, audit findings, customer complaints, and other quality issues in a structured, documented, and verifiable way.

A CAPA record captures the problem, the investigation, the root cause, the actions taken to correct it (corrective action) and to prevent recurrence (preventive action), and an effectiveness check that confirms the fix worked.

Why CAPA matters in regulated industries

CAPA is one of the most-inspected areas of any regulated quality system. FDA, EMA, MHRA, and notified bodies all look at CAPA records as primary evidence of a functioning quality culture.

A weak CAPA program — missing root causes, repeat deviations, late actions, missing effectiveness checks — is one of the top reasons regulatory bodies issue 483s, warning letters, and notified body findings.

The 3 questions inspectors ask

Did you find the true root cause? Did your actions remove that cause? Did you verify the cause is actually gone?

Where CAPA appears in regulations

CAPA requirements appear across most GxP regulations and standards:

  • FDA 21 CFR Part 820 §820.100 — Medical device QSR CAPA procedures
  • FDA 21 CFR Part 211 §211.192 — Drug manufacturing investigations
  • EU GMP Chapter 1 & Chapter 8 — Quality system + deviation and CAPA
  • ICH Q10 §3.2.2 — CAPA as one of four enablers of pharmaceutical quality systems
  • ISO 13485 §8.5.2 and §8.5.3 — Corrective and preventive action for medical devices
  • ICH Q9(R1) — Quality risk management feeds into CAPA prioritization

The CAPA lifecycle

A typical CAPA record moves through these stages:

  • Initiation — source event documented (deviation, audit, complaint)
  • Investigation — root cause analysis using tools like 5 Whys, Fishbone, FMEA
  • Action planning — corrective + preventive actions defined with owners, due dates
  • Implementation — actions executed, evidence captured
  • Effectiveness check — verification after a defined period that the issue has not recurred
  • Closure — formal close-out with QA approval

What good CAPA controls look like

Inspection-ready CAPA programs share common control patterns:

  • Defined escalation criteria — when an event becomes a CAPA
  • Controlled root cause templates — reduce shallow analysis
  • Mandatory effectiveness checks — no closure without verification
  • Links to source events, changes, training, and risk assessments
  • KPI dashboards — open count, average age, overdue actions
  • Trending and recurrence analysis — feeds into Management Review

How Complere manages CAPA

The Complere CAPA & Deviations module provides a controlled CAPA lifecycle with structured root cause capture, action plan tracking, and mandatory effectiveness checks.

  • One record from deviation through effectiveness check — no handoffs between systems
  • Configurable root cause taxonomy aligned to your QMS
  • Automated overdue action escalation
  • Dashboards surface repeat root causes and late effectiveness checks
  • Full audit trail and e-signatures meeting 21 CFR Part 11
  • Linked to change control, risk assessment, training, and documents

Frequently asked questions

Common questions about CAPA (Corrective and Preventive Action) sourced from regulatory references and inspection patterns.

What makes an effective CAPA system for pharma?

An effective CAPA program captures meaningful signals, investigates root causes, documents proportional actions, and verifies effectiveness to prevent recurrence.

How is CAPA different from logging deviations?

CAPA connects deviations to root cause analysis, documented action plans, verification activities, and cross-functional oversight rather than just recording events.

Which regulations require CAPA programs?

FDA 21 CFR 211, 21 CFR 820, EU GMP Chapter 1, and ICH Q10 expect documented CAPA governance with verification.

What do inspectors assess during CAPA reviews?

Inspectors review signal validity, root cause rationale, proportional actions, verification data, and whether the CAPA links to deviations, complaints, and management review.

How does Complere keep CAPA evidence connected to the rest of the quality system?

Complere links CAPA findings to deviations, change control, document proofs, and audit trails, so inspectors see the full investigation-to-action story without manual compilations.

About the author

Complere Reference Team

Compliance and quality-systems specialists maintaining the Complere glossary for regulated quality, validation, and inspection-readiness teams. Entries are reviewed against current FDA, MHRA, EMA, ICH, and PIC/S guidance.

Continue Exploring

Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.

CAPA module screenshot
Related

CAPA & Deviations

Deviations, nonconformances, and complaints in one risk-based process with evidence-backed closure.

Explore
Deviation checklist template
Related

Deviation Investigation Checklist

Structured fields for event intake, root cause, CAPA planning, and effectiveness review.

Explore
QMSR 12-clause map to your eQMS
Related

QMSR: The 12-Clause Map to Your eQMS

The buttons in your eQMS did not change on 2 February 2026 — the evidence behind them did.

Explore
OOS investigation FDA expectations 2026
Related

OOS Investigation — What FDA Still Expects in 2026

Barr limits on retesting, Phase I/II under the May 2022 Level 2 revision, and the records investigators pull.

Explore
Deviation, CAPA and change control companion post
Related

Deviation, CAPA, and Change Control: Why They Must Stay Linked

The five seams where the deviation→CAPA→change chain breaks, what an investigator traces backwards, and a seven-question linkage test.

Explore
QMS vs eQMS companion post
Related

QMS vs eQMS in Pharma: What Actually Changes

CAPA is a Q10 element, not a module you buy. If follow-up still lives in a tracker, the QMS never moved.

Explore
Training effectiveness companion post
Related

Training Effectiveness in Pharma: Why Completion Is Not Enough

How many open CAPAs name retraining as the action, and how many of those checks are only a second signature?

Explore
Connected quality records companion post
Related

Connected Quality Records in Pharma: Why Silos Still Fail Under Inspection

A CAPA closure is stronger when the trigger, action, change, training, and effectiveness evidence remain one path.

Explore
FDA Form 483 examples companion post
Related

FDA Form 483 Examples: What Quality Teams Should Learn from Common Observations

§820.100(a) CAPA procedures was the most-cited device row of FY 2025 (279); §211.192 investigations the second for drugs. The record that answers each.

Explore
Warning letter trends companion post
Related

Warning Letter Trends 2025: What Recurring Quality-System Breakdowns Reveal

§211.192 investigations added 63 citations between FY 2024 and FY 2025, more than any other drug section; what the letter then asks for.

Explore
Slow CAPAs companion post
Related

If Your CAPAs Are Slow, Your QMS Architecture Is Wrong

The cycle-time data says the wasted days sit at the seams between modules, not with QA — and the seam is where the trail goes silent.

Explore
Purolea warning letter companion post
Related

The Purolea Warning Letter, Read as an Audit-Trail Spec

FDA's first cGMP letter to cite AI names two clauses and one accountability boundary — read backward, the clauses are a record schema.

Explore
Per-tenant validation companion post
Related

Per-Tenant Validation: How CDMOs Prove Sponsor Segregation

Sponsor tagging is a metadata field, not segregation — the SQL probe, the eight auditor requests and the records a sponsor audit asks for.

Explore
First IND quality gaps companion post
Related

The 6 Quality-System Gaps That Kill Your First IND

Six predictable CMC and quality gaps that turn a strong first IND into a clinical hold — and where each closes cheaply before the pre-IND meeting.

Explore
Tenant of one companion post
Related

Why CDMO Quality Systems Break: Tenant of One

Five seams where CDMO quality systems break between shared infrastructure and the sponsor-facing record — and the architecture that closes them.

Explore
483 response after QMSR companion post
Related

483 Response After QMSR: Are Your CAPAs Ready?

Fifteen working days, a citation written against Part 820 as amended, and the CAPA records the response now has to attach.

Explore
Risk register where every assessment scores medium
Related

ICH Q9(R1): What Changed for Quality Risk Management

Subjectivity named, formality made a spectrum, supply risk in scope — what the 2023 revision asks of a risk register.

Explore
One supplier file whose approval ended before the lot was received
Related

Supplier Quality Management: What Your eQMS Should Carry

Supplier quality management is one decision made repeatedly. What it has to produce, what spreadsheets and email cost, and what to demand from an eQMS.

Explore

See CAPA workflows in action during a Complere demo

Walk through real CAPA investigations — root cause capture, action plans, effectiveness checks — connected to deviations, audits, and change control.