What is CAPA in Pharma? (Simple Definition)
CAPA (Corrective and Preventive Action) is a structured quality system process used in pharmaceutical manufacturing to identify the root cause of a quality problem, correct it, and implement measures to prevent it from happening again. It is a core requirement of the Pharmaceutical Quality System (PQS) under ICH Q10 and is mandated by regulatory bodies including the FDA, WHO, and EMA.
Think of CAPA as a two-part response to any quality failure:
Fix what already went wrong
Addresses a problem that has already occurred. The goal is to eliminate the root cause of the current non-conformance.
- Reactive — responds to existing failure
- Targets the proven root cause
- Required evidence: the problem has happened
- Example: recalibrate a balance found out-of-tolerance
Stop it from happening at all
Addresses a potential problem that hasn’t happened yet. The goal is to eliminate the risk before it causes a failure.
- Proactive — anticipates future risk
- Targets systemic vulnerabilities
- Required evidence: risk assessment or trend
- Example: implement automated calibration reminders
Corrective Action = Your house is on fire → call the fire brigade and put it out.
Preventive Action = Install smoke detectors so the fire never starts (or is caught early).
A complete CAPA does both — it fixes the current fire AND ensures it cannot happen again.
When is a CAPA Required?
A CAPA is triggered whenever a quality non-conformance, failure, or risk is identified. Common triggers in pharmaceutical manufacturing include:
|
CAPA Trigger
|
Example
|
CAPA Type
|
|---|---|---|
|
OOS / OOT Result
|
Assay result 96.2% vs. spec 98.0–102.0% — investigation finds degraded reference standard
|
Corrective
|
|
GMP Deviation
|
Analyst used wrong SOP revision during HPLC analysis — corrected mid-batch
|
Corrective
|
|
Internal Audit Finding
|
Audit finds 3 instruments with expired calibration certificates in QC lab
|
Corrective
|
|
Customer / Market Complaint
|
Customer reports tablet hardness inconsistency in two successive lots
|
Corrective
|
|
Trend Analysis
|
Trending shows dissolution gradually declining over 6 lots, still within spec but approaching limit
|
Preventive
|
|
Risk Assessment
|
Risk assessment identifies contamination risk in a new filling line procedure
|
Preventive
|
|
Regulatory Observation (483 / Warning Letter)
|
FDA 483 observation on inadequate cleaning validation documentation
|
Both Required
|
|
Product Recall
|
Recall initiated due to microbial contamination in sterile injectable
|
Both Required
|
Step-by-Step: How to Write and Execute a CAPA
1
Problem Identification & CAPA Initiation
Document exactly what happened, when, and how it was detected
The foundation of any CAPA is a clear, specific problem description. A vague problem statement leads to a vague root cause and an ineffective CAPA. Use the 5W1H framework to structure your description:
- What happened? — "Assay result of 96.5% reported for Batch XYZ-001"
- Where was it detected? — "QC Laboratory, HPLC Testing Area"
- When was it detected? — "15 March 2024 at 14:30 hrs during routine release testing"
- Who detected it? — "Analyst name, QC Department"
- Why is it a problem? — "Result falls below specification limit of 98.0% minimum"
- How was it detected? — "Routine HPLC assay per SOP-QC-001, Rev 3"
Also classify the risk level at initiation — this determines your timeline:
|
Risk Level
|
Definition
|
CAPA Timeline
|
|---|---|---|
|
Critical
|
Patient safety risk, regulatory breach, or recall situation
|
Immediate — same day initiation
|
|
Major
|
Significant GMP violation, OOS confirmed, audit finding
|
Within 15 days
|
|
Minor
|
Low-risk deviation, administrative error, procedural gap
|
Within 30–60 days
|
2
Root Cause Analysis (RCA)
Identify the TRUE cause — not just the symptom
Root cause analysis is the most important part of CAPA. A CAPA that addresses only the symptom will fail — the problem will recur. You must dig until you find the fundamental reason the failure occurred.
The Two Most Useful Tools for RCA in Pharma:
Tool 1: The 5-Why Method
Ask "Why?" five times (or until you reach a root cause you can actually fix). Example — OOS assay result:
1
Why OOS? → HPLC system suitability failed (tailing factor >2.0)
2
Why failed suitability? → Column performance deteriorated
3
Why deteriorated? → Column used beyond its validated injection limit
4
Why used beyond limit? → No tracking system for column injection count
5
Why no tracking? → SOP-QC-001 does not specify a column usage log requirement
✓ Root Cause: SOP gap — no column usage tracking requirement defined in the analytical method SOP
Tool 2: 6M Ishikawa (Fishbone) Diagram
Systematically analyse all six potential cause categories. For each category, list potential contributing factors, then test each one:
- Training gap or lapse
- Incorrect technique
- Fatigue or distraction
- New / unqualified analyst
- Calibration expired
- Instrument malfunction
- Poor maintenance
- OQ/PQ not current
- SOP gap or ambiguity
- Wrong revision used
- Method not validated
- Unclear instructions
- Degraded standard
- Wrong lot number
- Supplier quality issue
- Improper storage
- Wrong integration settings
- System suitability failure
- Calculation error
- Data integrity issue
- Temperature excursion
- Humidity too high/low
- Contamination event
- Vibration / power issue
"Human error" is NOT a root cause — it’s a symptom. Ask why the human error occurred: Was training inadequate? Was the SOP unclear? Was there pressure to rush? The root cause is the system or process failure that allowed the human error to happen.
3
Define Corrective Actions
Directly address and eliminate the confirmed root cause
Each corrective action must directly address the confirmed root cause. Use the SMART framework when writing actions:
- Specific — clearly describe what will be done
- Measurable — define how you will know it’s done
- Assignable — one named responsible person per action
- Realistic — achievable within the risk timeline
- Time-bound — exact target completion date
"Revise SOP-QC-001 (Rev 3 → Rev 4) to include a mandatory column usage log recording the injection count per analysis run, with a maximum limit of 500 injections per column. All QC analysts to complete training on Rev 4 within 10 business days of issue. Responsible: QC Section Head. Target: 15 April 2024. "
"Analyst will be more careful in future." — This is not a corrective action. It addresses no root cause, cannot be verified, and provides no systemic improvement.
4
Define Preventive Actions
Eliminate systemic vulnerabilities to stop recurrence
Preventive actions go beyond fixing the current problem — they close the gaps in your quality system that allowed the failure to occur. Ask: "What else in our system could fail in the same way?"
- Could the same issue occur on other analytical instruments or columns?
- Are there other SOPs with similar gaps in consumable tracking?
- Should this be added to the QC supervisor’s periodic review checklist?
- Does the training programme need updating to cover column lifecycle management?
Example preventive action (continuing the column tracking example):
"Conduct a review of all QC analytical SOPs within 30 days to identify any other consumables (GC columns, filters, membranes) lacking usage tracking requirements. Issue a universal ‘Consumable Lifecycle Management’ addendum to all affected SOPs. Responsible: QA Manager. Target: 30 April 2024. "
5
Implement & Track Actions
Execute on time — every overdue CAPA is a compliance risk
Implementation requires active management. Each action must have a single responsible owner, a firm target date, and documented evidence of completion. Common evidence types include:
- Revised SOP with issue date and version number
- Training records signed by all affected personnel
- Calibration certificate for repaired/replaced equipment
- Updated risk assessment or validation document
- New form or logbook with completed first entries
- Change control record if process changes were made
During FDA, WHO, or MHRA inspections, overdue CAPAs are one of the top observations cited. QA must actively monitor CAPA timelines and escalate overdue actions immediately. A CAPA system with many overdue items signals a lack of quality culture — one of the most serious messages you can send to an inspector.
6
Effectiveness Check — The Most Overlooked Step
Verify the CAPA actually worked before you close it
A CAPA is not complete until you verify it was effective. Many organisations implement CAPAs and immediately close them — this is a major compliance gap that FDA inspectors specifically look for.
How to Define a Good Effectiveness Check:
Before implementing the CAPA, define:
- KPI (Key Performance Indicator): What measurable outcome proves success?
- Timeline: When will you check? (Typically 30, 60, or 90 days post-implementation)
- Pass/Fail Criteria: What result means the CAPA was effective?
|
CAPA Type
|
Effectiveness KPI Example
|
Check Period
|
|---|---|---|
|
OOS / Instrument issue
|
Zero recurrence of the same OOS type in next 20 analytical runs
|
60 days
|
|
SOP revision
|
100% of analysts trained and competency re-assessed; zero SOP deviation in 3 months
|
90 days
|
|
Calibration gap
|
Zero overdue calibrations on QC instrument schedule for 3 consecutive months
|
90 days
|
|
Training gap
|
Analyst passes re-qualification assessment with ≥80% score
|
30 days
|
|
Microbial exceedance
|
Environmental monitoring results within alert limits for 4 consecutive monitoring cycles
|
120 days
|
If the CAPA does not achieve its KPI, it must NOT be closed. Re-open the CAPA, conduct additional root cause analysis, revise the actions, and set a new effectiveness check date. This is normal — it means your quality system is working. What is not acceptable is closing a CAPA that hasn’t been verified as effective.
7
CAPA Closure & Documentation
Close with evidence — QA approval required
A CAPA can only be formally closed when all of the following are confirmed:
- All corrective actions implemented with documented evidence
- All preventive actions implemented with documented evidence
- Effectiveness check completed and criteria met
- QA Manager review and written approval obtained
- CAPA closure justification documented with evidence-based conclusion
- Lessons learned shared with relevant departments (if applicable)
3 Real-World CAPA Examples (Complete Walkthroughs)
Problem
Assay result of 96.5% for Batch 24-001 (Paracetamol 500mg Tablets). Specification: 98.0–102.0%. OOS investigation Phase I confirmed: reference standard used was 4 days past its assigned re-standardisation date.
Root Cause
The reference standard inventory log did not include a re-standardisation date field. Analysts had no visible indicator that the standard had expired. SOP-QC-008 Rev 2 required re-standardisation every 30 days but had no tracking mechanism.
Corrective Action
1. Immediately quarantine and discard all reference standards that have exceeded their re-standardisation date. Re-standardise with fresh primary standard. (Responsible: QC Lead. Target: 2 days.)
2. Revise SOP-QC-008 to include a mandatory Reference Standard Log with re-standardisation date clearly flagged. (Target: 10 days.)
3. Retest Batch 24-001 using validated reference standard per approved retest protocol. (Target: 5 days.)
Preventive Action
1. Implement a colour-coded label system: GREEN = valid, AMBER = due within 5 days, RED = expired. All analysts trained on label system.
2. Add reference standard expiry/re-standardisation check to the daily QC lab checklist.
3. QC Supervisor to perform monthly audit of reference standard log compliance.
Effectiveness KPI
Zero reference standard expiry incidents over the next 90 days. Verified by monthly QC supervisor audit review of reference standard log.
Problem
During internal audit, it was discovered that QC Analyst used SOP-QC-012 Rev 4 for a dissolution test, when Rev 5 had been approved and in effect for 3 weeks. The deviation affected 2 batches.
Root Cause
Obsolete SOP Rev 4 was still physically present in the laboratory binder alongside the current Rev 5. The document control procedure did not require physical retrieval confirmation of obsolete documents from bench-level binders.
Corrective Action
1. Immediately retrieve and destroy all physical copies of obsolete SOPs from all laboratory bench binders. Document retrieval with signatures. (Target: 24 hours.)
2. Re-test 2 affected batches under SOP-QC-012 Rev 5 to confirm results are equivalent. (Target: 5 days.)
3. Retrain all QC analysts on document control procedure with specific focus on current version identification. (Target: 7 days.)
Preventive Action
1. Revise document control SOP to require that QA physically collects all obsolete copies before the new version is distributed — with sign-off confirmation list.
2. Implement a "Current Revision" cover sheet on all bench SOPs showing version number and effective date prominently at the top.
3. Add document version check to the pre-analysis checklist in all analytical method SOPs.
Effectiveness KPI
Zero wrong-version SOP usage incidents in the next 6 months. Verified by quarterly document control audit of 10 randomly selected bench binders.
Problem
Settle plate result of 18 CFU/90mm/4hrs recorded in Grade B area of sterile filling suite. Alert limit is 5 CFU, Action limit is 10 CFU. Result exceeds both limits. Isolate identified as Bacillus subtilis.
Root Cause
Investigation found a 15-minute maintenance window on the HVAC system 2 hours before the monitoring event. The maintenance team had opened an access panel adjacent to the Grade B area. The HVAC access procedure did not require the clean area to be vacated and re-qualified before production resumed.
Corrective Action
1. Immediately halt production in the affected Grade B area. Perform full environmental re-qualification (settle plates, active air sampling, contact plates) before resuming. (Target: 48 hours.)
2. Review and quarantine all batches filled during the affected period. Perform additional sterility/bioburden testing. (Target: 5 days.)
3. Sanitise Grade B area with sporicidal agent (2% glutaraldehyde) per validated disinfection SOP. (Target: 24 hours.)
Preventive Action
1. Revise HVAC maintenance procedure to require Grade B area to be vacated, cleaned, and re-qualified (passing 2 consecutive monitoring cycles) before production resumes after any HVAC maintenance.
2. Add a pre-production environmental check to the batch production record — supervisor sign-off required confirming no maintenance events in preceding 4 hours.
3. Install continuous particle monitoring in Grade B area with real-time alert to QA.
Effectiveness KPI
Zero further Grade B action limit exceedances for the next 12 environmental monitoring cycles. All HVAC maintenance events followed by confirmed clean-room re-qualification before production restart.
CAPA vs Deviation — What's the Difference?
These two terms are often confused. Here’s a clear comparison:
|
Aspect
|
Deviation
|
CAPA
|
|---|---|---|
|
What it is
|
A record that something departed from approved procedure
|
A system to fix the root cause and prevent recurrence
|
|
When it's opened
|
At the time the deviation occurs
|
After investigation identifies root cause
|
|
Timeframe
|
Short-term — documents the event
|
Medium to long-term — implements and verifies change
|
|
Reactive or Proactive?
|
Always reactive
|
Can be both (reactive to failure; proactive to risk)
|
|
Requires root cause?
|
Not always — simple deviations may not
|
Always — CAPA without root cause is meaningless
|
|
Needs effectiveness check?
|
No
|
Always — this is a core regulatory requirement
|
|
Regulatory basis
|
21 CFR 211.192 / GMP deviation procedures
|
ICH Q10 §3.2.3 / ISO 9001:2015 §10.2 / FDA 820.100
|
Complete CAPA Lifecycle — From Opening to Closure
1
Day 0 — CAPA Initiated
Quality event detected (OOS, deviation, audit finding, complaint). CAPA opened in QMS with unique reference number, risk classification, and 5W1H problem description. QA notified.
2
Days 1–5 — Root Cause Investigation
Cross-functional team conducts root cause analysis using 5-Why and 6M Ishikawa. All findings documented with supporting data (chromatograms, batch records, training records, etc.).
3
Days 5–10 — CAPA Action Plan Defined
SMART corrective and preventive actions defined, assigned to named owners with firm target dates. Effectiveness KPIs and check timeline defined. QA approval of plan obtained.
4
Days 10–30 — Implementation
Actions executed — SOPs revised and issued, training conducted, equipment fixed or replaced, processes updated. Each action completed with documented evidence (not just "completed" checkbox).
5
Days 30–120 — Effectiveness Check Period
Monitoring period to verify CAPA worked. KPIs tracked. If any recurrence or failure of KPI — CAPA is extended, not closed. QA monitors status throughout this period.
6
Day 120+ — CAPA Closure
All actions confirmed complete with evidence. Effectiveness check criteria met. QA Manager signs closure with evidence-based justification statement. CAPA record archived in QMS. Lessons learned shared if applicable.
8 Most Common CAPA Mistakes (and How to Fix Them)
|
#
|
Mistake
|
Why It's a Problem
|
The Fix
|
|---|---|---|---|
|
1
|
"Human error" listed as root cause
|
Not a root cause — it's a symptom. Leads to ineffective CAPA.
|
Ask why the error occurred. Find the system or process failure that enabled it.
|
|
2
|
CAPA closed without effectiveness check
|
Top FDA 483 observation. No proof the action worked.
|
Always define KPI + timeline before implementing. Verify before closing.
|
|
3
|
Vague action items ("review the procedure")
|
Cannot be verified. May never actually be done.
|
Use SMART format. State exactly what will be done, by whom, and when.
|
|
4
|
CAPA opened but never completed (overdue)
|
Serious compliance risk. Destroys QMS credibility.
|
QA must actively manage overdue CAPAs and escalate weekly.
|
|
5
|
Same CAPA root cause recurring
|
Shows corrective action was superficial or wrong root cause identified.
|
Re-investigate root cause. Consider systemic process review.
|
|
6
|
No preventive action — only corrective
|
Fixes current problem but leaves system vulnerable to recurrence.
|
Always ask: what else in our system has a similar gap?
|
|
7
|
CAPA assigned to many people, no single owner
|
"Everyone's responsibility = nobody's responsibility." Actions slip.
|
One named, accountable owner per action. Others can support.
|
|
8
|
Evidence of implementation is missing
|
During inspection, verbal claims are not accepted. No evidence = not done.
|
Attach physical evidence: signed training records, revised SOP, certificate, etc.
|
Frequently Asked Questions
Regulatory References for CAPA
|
Reference
|
What It Requires for CAPA
|
|---|---|
|
ICH Q10 §3.2.3
|
Pharmaceutical Quality System must include a CAPA system. Root cause investigation required. Effectiveness monitoring required before CAPA closure.
|
|
FDA 21 CFR 820.100
|
Establishes CAPA as a mandatory quality system element. Requires documented procedures, root cause analysis, verification of effectiveness, and dissemination to affected departments.
|
|
FDA 21 CFR 211.192
|
All OOS results must be fully investigated. Connects directly to CAPA requirements for pharmaceutical manufacturers.
|
|
ISO 9001:2015 §10.2
|
Requires organisations to react to non-conformities, evaluate need for action, implement actions, and review effectiveness.
|
|
WHO GMP TRS 986 Annex 4
|
WHO GMP requirements for CAPA systems in pharmaceutical manufacturing for developing markets and global generics.
|
|
EU GMP Annex 11
|
For computerised systems — any CAPA resulting from a computer system failure must include audit trail review and data integrity assessment.
|
|
ICH Q9 — Quality Risk Management
|
Risk-based approach to prioritising CAPA actions and determining the depth of preventive measures required.
|
Ask PharmaTutor
Pharma QC & QA Education · 14+ Years Industry Experience
AskPharmaTutor provides practical, industry-based guides on pharmaceutical quality control, GMP compliance, and regulatory affairs. All content is based on current official guidelines and real industry experience — simplified for students and professionals alike.