Capa Officer

What This Skill Does

This skill facilitates Corrective and Preventive Action (CAPA) management within Quality Management Systems. It focuses on systematic root cause analysis, action implementation, and effectiveness verification.

• It is designed for quality managers and CAPA officers.

When to Use

• Document trigger events.
• Assess CAPA necessity.
• Form investigation teams.
• Collect data and evidence.
• Identify root causes.
• Develop corrective actions.

Key Features

• Systematic CAPA investigation workflow.
• Root cause analysis methodologies.
• Corrective and preventive action planning.
• Effectiveness verification processes. CAPA metrics and reporting.
• Reference documentation and tools.

Manual Installation

Corrective and Preventive Action (CAPA) management within Quality Management Systems, focusing on systematic root cause analysis, action implementation, and effectiveness verification.

Table of Contents

CAPA Investigation Workflow

• Root Cause Analysis
• Corrective Action Planning
• Effectiveness Verification
• CAPA Metrics and Reporting
• Reference Documentation
• Tools

CAPA Investigation Workflow

Conduct systematic CAPA investigation from initiation through closure:

• Document trigger event with objective evidence
• Assess significance and determine CAPA necessity
• Form investigation team with relevant expertise
• Collect data and evidence systematically
• Select and apply appropriate RCA methodology
• Identify root cause(s) with supporting evidence
• Develop corrective and preventive actions Validation: Root cause explains all symptoms; if eliminated, problem would not recur

CAPA Necessity Determination

Investigation Team Composition

Evidence Collection Checklist

[ ] Problem description with specific details (what, where, when, who, how much) [ ] Timeline of events leading to issue [ ] Relevant records and documentation [ ] Interview notes from involved personnel [ ] Photos or physical evidence (if applicable) [ ] Related complaints, NCs, or previous CAPAs [ ] Process parameters and specifications

Root Cause Analysis

Select and apply appropriate RCA methodology based on problem characteristics.

RCA Method Selection Decision Tree

Is the issue safety-critical or involves system reliability? ├── Yes → Use FAULT TREE ANALYSIS └── No → Is human error the suspected primary cause? ├── Yes → Use HUMAN FACTORS ANALYSIS └── No → How many potential contributing factors? ├── 1-2 factors (linear causation) → Use 5 WHY ANALYSIS ├── 3-6 factors (complex, systemic) → Use FISHBONE DIAGRAM └── Unknown/proactive assessment → Use FMEA

5 Why Analysis

Use when: Single-cause issues with linear causation, process deviations with clear failure point. Template:

PROBLEM: [Clear, specific statement]

WHY 1: Why did [problem] occur? BECAUSE: [First-level cause] EVIDENCE: [Supporting data]

WHY 2: Why did [first-level cause] occur? BECAUSE: [Second-level cause] EVIDENCE: [Supporting data]

WHY 3: Why did [second-level cause] occur? BECAUSE: [Third-level cause] EVIDENCE: [Supporting data]

WHY 4: Why did [third-level cause] occur? BECAUSE: [Fourth-level cause] EVIDENCE: [Supporting data]

WHY 5: Why did [fourth-level cause] occur? BECAUSE: [Root cause] EVIDENCE: [Supporting data]

Example - Calibration Overdue:

PROBLEM: pH meter (EQ-042) found 2 months overdue for calibration

WHY 1: Why was calibration overdue? BECAUSE: Equipment was not on calibration schedule EVIDENCE: Calibration schedule reviewed, EQ-042 not listed

WHY 2: Why was it not on the schedule? BECAUSE: Schedule not updated when equipment was purchased EVIDENCE: Purchase date 2023-06-15, schedule dated 2023-01-01

WHY 3: Why was the schedule not updated? BECAUSE: No process requires schedule update at equipment purchase EVIDENCE: SOP-EQ-001 reviewed, no such requirement

WHY 4: Why is there no such requirement? BECAUSE: Procedure written before equipment tracking was centralized EVIDENCE: SOP last revised 2019, equipment system implemented 2021

WHY 5: Why has procedure not been updated? BECAUSE: Periodic review did not assess compatibility with new systems EVIDENCE: No review against new equipment system documented

ROOT CAUSE: Procedure review process does not assess compatibility with organizational systems implemented after original procedure creation.

Fishbone Diagram Categories (6M)

See references/rca-methodologies.md for complete method details and templates.

Root Cause Validation

Before proceeding to action planning, validate root cause:

[ ] Root cause can be verified with objective evidence [ ] If root cause is eliminated, problem would not recur [ ] Root cause is within organizational control [ ] Root cause explains all observed symptoms [ ] No other significant causes remain unaddressed

Corrective Action Planning

Develop effective actions addressing identified root causes:

• Define immediate containment actions
• Develop corrective actions targeting root cause
• Identify preventive actions for similar processes
• Assign responsibilities and resources
• Establish timeline with milestones
• Define success criteria and verification method
• Document in CAPA action plan Validation: Actions directly address root cause; success criteria are measurable

Action Types

Action Plan Components

ACTION PLAN TEMPLATE

CAPA Number: [CAPA-XXXX] Root Cause: [Identified root cause]

ACTION 1: [Specific action description] Type: [ ] Containment [ ] Correction [ ] Corrective [ ] Preventive Responsible: [Name, Title] Due Date: [YYYY-MM-DD] Resources: [Required resources] Success Criteria: [Measurable outcome] Verification Method: [How success will be verified]

ACTION 2: [Specific action description] ...

IMPLEMENTATION TIMELINE: Week 1: [Milestone] Week 2: [Milestone] Week 4: [Milestone] Week 8: [Milestone]

APPROVAL: CAPA Owner:_____________Date:_______Process Owner: