CAPA Officer Toolkit

A specialized skill for Corrective and Preventive Action (CAPA) management within quality management systems — covering root cause analysis, corrective action planning, effectiveness verification, and regulatory compliance documentation.

When to Use This Skill

Choose CAPA Officer Toolkit when you need to:

• Investigate quality deviations and non-conformances systematically
• Perform structured root cause analysis (5-Why, Fishbone, Fault Tree)
• Write CAPA plans that satisfy FDA 21 CFR 820 or ISO 13485 requirements
• Track corrective actions through implementation and effectiveness checks
• Prepare CAPA documentation for regulatory audits

Consider alternatives when:

• You need general project management (use a PM skill)
• You're handling customer complaints without quality system ties
• You need statistical process control analysis (use a data analysis skill)

Quick Start

Copy
# Initiate a CAPA investigation
claude "Create a CAPA investigation plan for a recurring label misprint defect on medical device packaging, including root cause analysis template"

Copy
# CAPA-2024-037: Recurring Label Misprint

## 1. Problem Statement
Three lots of Device-X packaging had incorrect UDI barcodes
printed on secondary labels during Q4 2024 production.
Lots affected: L2024-089, L2024-091, L2024-094

## 2. Immediate Containment
- [ ] Quarantine remaining inventory from affected lots
- [ ] Notify distribution to hold shipments
- [ ] Assess field risk (any units shipped?)

## 3. Root Cause Analysis (5-Why)
1. Why were labels misprinted?
   → Wrong template file loaded by operator
2. Why was the wrong template loaded?
   → Multiple template versions in shared folder
3. Why were multiple versions accessible?
   → No version control on label templates
4. Why no version control?
   → Label management not included in document control SOP
5. Why excluded from SOP?
   → Labels were treated as "non-critical" documents

**Root Cause**: Label templates lacked document control
governance, allowing outdated versions to remain accessible.

Core Concepts

CAPA Process Phases

Phase	Activities	Output
Identification	Detect issue, log in CAPA system	CAPA initiation form
Containment	Stop impact, quarantine affected items	Containment action log
Investigation	Root cause analysis, data collection	Investigation report
Planning	Define corrective & preventive actions	CAPA action plan
Implementation	Execute approved actions	Implementation evidence
Verification	Confirm actions are effective	Effectiveness check report
Closure	Document outcomes, close CAPA record	Closed CAPA file

Root Cause Analysis Methods

Copy
## Fishbone Diagram (Ishikawa) Categories

### Manufacturing Context
- **Man**: Training gaps, procedure non-compliance
- **Machine**: Equipment calibration, maintenance
- **Method**: SOP inadequacy, process design
- **Material**: Incoming quality, specification drift
- **Measurement**: Inspection accuracy, sampling plans
- **Environment**: Temperature, humidity, contamination

### Selection Guide
| Method         | Best For                    | Complexity |
|---------------|----------------------------|------------|
| 5-Why         | Single linear cause chains  | Low        |
| Fishbone      | Multi-factor exploration    | Medium     |
| Fault Tree    | Complex system failures     | High       |
| FMEA          | Preventive risk analysis    | High       |
| Is/Is-Not     | Narrowing problem scope     | Low        |

Effectiveness Verification

Copy
## Effectiveness Check Plan

### Short-Term Verification (30 days)
- [ ] Corrective action implemented per plan
- [ ] Responsible parties trained on changes
- [ ] No recurrence of original defect

### Long-Term Verification (90 days)
- [ ] Trend data shows sustained improvement
- [ ] No new failure modes introduced
- [ ] Process capability metrics maintained

### Evidence Required
- Updated SOP revision history
- Training records with signatures
- Quality data trending charts (before/after)
- Internal audit findings (if applicable)

Configuration

Parameter	Description	Example
regulation	Applicable regulatory framework	"FDA 21 CFR 820"
severity_level	Risk classification of the issue	"critical" / "major"
rca_method	Root cause analysis methodology	"5-why" / "fishbone"
tracking_id	CAPA numbering format	"CAPA-YYYY-NNN"
verification_days	Effectiveness check period	90
output_format	Document output format	"markdown" / "docx"

Best Practices

1. Write problem statements with measurable specifics — "Labels were wrong" is vague. "3 of 47 lots produced in Q4 had UDI barcodes referencing superseded GUDID entries" gives investigators clarity on scope, frequency, and impact.

2. Stop 5-Why analysis at systemic causes, not human error — "Operator loaded wrong file" is not a root cause. Keep asking why until you reach a system gap (missing controls, inadequate training design, or process design flaw) that can be fixed permanently.

3. Separate corrective from preventive actions explicitly — Corrective actions fix the current problem. Preventive actions stop similar problems elsewhere. Document both distinctly — auditors specifically look for preventive thinking.

4. Define effectiveness criteria before implementing actions — Decide what "success" looks like quantitatively before you make changes. Otherwise you end up with subjective effectiveness checks that don't prove anything to auditors.

5. Close CAPAs with trend data, not single checks — A single "no recurrence" observation proves nothing statistically. Require at minimum 90 days of data showing the defect rate remains at or below the target threshold.

Common Issues

CAPAs address symptoms instead of root causes — Teams under pressure implement quick fixes and close the CAPA before reaching the true root cause. This creates repeat CAPAs for the same issue. Require investigation sign-off from quality leadership, and track repeat CAPA rates as a quality metric.

Effectiveness verification is perfunctory — Many organizations check "no recurrence" once and close. Regulators expect evidence that the corrective action actually prevented the problem, not just that nobody noticed it again. Define measurable acceptance criteria and collect trending data over 60-90 days minimum.

CAPA backlog grows uncontrollably — Organizations open CAPAs for every minor issue, creating backlogs that delay critical investigations. Implement a severity-based triage system where minor issues go through simpler non-conformance processes, reserving full CAPA investigations for significant and critical quality events.