qms-capa

CAPA Management

Correct. Prevent. Prove.

Training completed. CAPA closed. Three more failures in the same suite. The CAPA that never actually worked. Mandatory effectiveness verification that proves your fixes work.

CAPA Management

The CAPA that never actually worked.

The FDA investigator asks to see CAPA-2023-047. Opened fourteen months ago after a sterility failure. Corrective action: additional training for aseptic technique. CAPA closed after training records were collected.

Then the investigator pulls up your deviation log. Three sterility failures in the past six months—all in the same suite, all with operators who completed that training. The CAPA is closed. The problem isn't fixed.

483 observation: "inadequate CAPA."

CAPA Lifecycle

The checkbox that lies

"Effectiveness verification complete." Click it and the CAPA closes. No evidence required. No criteria defined. No waiting period to see if the fix actually worked.

Effectiveness Verification

In Seal, effectiveness verification is a gate. When you open a CAPA, you define specific criteria: "Zero recurrence in the next 100 batches." You define the verification method: batch record review. You define the timeline: after 100 batches.

The CAPA cannot close until verification is complete and evidence is attached.

When the fix doesn't work

When verification fails, the CAPA reopens automatically. Your root cause analysis was wrong. Go deeper. The cycle continues until the fix actually works.

Finding the real root cause

"Operator error" isn't a root cause. Why did the operator err? Were they trained? Was the procedure clear? Was the equipment functioning?

5-Why analysis: Why did the operator skip the step? The step was unclear. Why unclear? The SOP was poorly written. Why poorly written? Never peer-reviewed. Why not reviewed? No review process exists.

Now you have something you can fix.

40 symptoms, one disease

CAPA Trending

40% of your CAPAs involve training gaps. You've been treating them as 40 individual problems. But it's one problem: your training program doesn't work. Fix the system, prevent 40% of future CAPAs.

Capabilities

01Linked to Source
CAPAs connect to their source—deviation, audit finding, complaint. Full context travels with the CAPA. No orphaned actions.
02Root Cause Tools
Built-in 5-Why, Fishbone, and Is/Is-Not analysis. Structured investigation ensures you find the real cause, not just the obvious one.
03Action Tracking
Every action has an owner, due date, and evidence requirement. Overdue actions escalate automatically.
04Mandatory Effectiveness
CAPAs can't close until effectiveness is verified. Define criteria upfront, schedule verification, provide evidence.
05Automatic Reopen
If verification fails—problem recurred—the CAPA reopens automatically. Back to root cause until the fix actually works.
06Trend Analysis
See patterns across CAPAs. Which areas, categories, root causes appear most? Find systemic issues, not just symptoms.
07Escalation Workflows
Overdue CAPAs escalate through defined paths. Owner → Manager → QA Leadership. No CAPAs lost in the queue.
08Audit-Ready Records
Complete CAPA history in one place. Show any CAPA from initiation to verified closure in seconds.
01 / 08
Linked to Source
Linked to Source

Entities

Entity
Description
Kind
CAPA
Corrective and Preventive Action. Cannot close until effectiveness is verified with evidence.
type
Corrective Action
Fix a problem that has occurred. Verify it doesn't recur.
template
CAPA-2023-047
Sterility failure. Training completed, CAPA closed. Three more failures. Reopened—training wasn't the root cause.
instance
Preventive Action
Fix a potential problem before it occurs. Proactive, from risk or trend analysis.
template
Systemic CAPA
40 symptoms, one disease. Fix the training program, prevent 40% of future CAPAs.
template
Effectiveness Verification
The gate that blocks closure. Criteria defined upfront, evidence required. If it fails, CAPA reopens.
type
VER-2024-001
Zero recurrence in 100 batches. Batch records reviewed. Evidence attached. Now it can close.
instance
Root Cause Analysis
'Operator error' isn't a root cause. Keep asking why until you hit something systemic you can fix.
type
5-Why Analysis
Why unclear? SOP poorly written. Why? Never peer-reviewed. Why? No review process. Now you can fix it.
template
Fishbone Diagram
Equipment, Process, People, Materials, Environment, Measurement. Consider all categories before settling.
template
Is/Is-Not Analysis
Only happens on second shift? Only with lot X? Patterns reveal causes.
template
Source Event
Deviation, audit finding, or complaint. Full context travels with the CAPA.
type
Action Item
Owner, due date, evidence requirement. Overdue actions escalate automatically.
type
Escalation
Owner → Manager → QA Leadership. No CAPAs lost in the queue.
type

FAQ

Effectiveness verification is mandatory—the CAPA literally cannot close without it. When you open a CAPA, you define verification criteria, method, and timeline. The system schedules the verification and blocks closure until evidence is attached.