Process Improvement

Corrective Action / CAPA

A quality management process that corrects existing nonconformities (corrective action) and prevents potential ones (preventive action) by addressing their root causes.

Read summarized version with

What is Corrective Action / CAPA?

Corrective action is what you do after a problem has already happened: you identify it, fix it, and make sure it doesn’t come back. CAPA stands for Corrective and Preventive Action. It’s a paired discipline that sits at the heart of nearly every formal quality management system. The corrective half deals with problems that already exist. The preventive half goes after problems that haven’t happened yet but probably will if nothing changes.

In quality and manufacturing operations, CAPA is the structured way you respond to a nonconformity, a customer complaint, an audit finding, or a process failure. Instead of patching the symptom and walking away, a proper CAPA digs into why the issue happened and builds a fix that lasts. That’s why it shows up as a core requirement in standards like ISO 9001 and in FDA-regulated industries, where regulators want documented evidence that you caught the defect and actually got rid of its cause. The FDA issued 105 drug quality warning letters in FY2024 - the highest count in five years - and inadequate CAPA systems appear as a recurring driver across a large share of those enforcement actions.

CAPA leans heavily on root cause analysis. You can’t write a corrective action worth anything until you genuinely understand what went wrong, which is why techniques like the 5 Whys and Fishbone diagrams feed straight into the CAPA workflow.

Key Characteristics of CAPA

  • Root-cause driven: Every CAPA depends on finding the true underlying cause, not just the symptom you can see.
  • Documented and traceable: Each step, owner, and decision gets recorded, so an audit can verify the loop was actually closed.
  • Effectiveness verified: A CAPA isn’t done until you’ve confirmed the fix worked and the problem stopped recurring.
  • Risk-prioritized: Not every issue needs a full CAPA. Teams triage based on severity, frequency, and risk.

Corrective Action vs Preventive Action

People mix up the two halves of CAPA constantly, but they do different jobs.

AspectCorrective ActionPreventive Action
TriggerA problem that already happenedA potential problem identified through analysis
GoalEliminate the cause of an existing nonconformityStop a likely future nonconformity before it occurs
ExampleReworking a defective batch and fixing the process gapAdjusting a procedure after trend data signals drift
TimingReactiveProactive

Both depend on the same investigative discipline that underpins good quality assurance and quality control programs.

The CAPA Process Steps

  1. Identification: Document the nonconformity, deviation, or complaint clearly.
  2. Evaluation: Assess severity and risk to decide whether a CAPA is warranted.
  3. Root cause analysis: Investigate why the issue occurred using a structured method.
  4. Action plan: Define corrective steps (and preventive steps where applicable) with owners and deadlines.
  5. Implementation: Execute the plan and update affected procedures or work instructions.
  6. Verification of effectiveness: Confirm the action resolved the issue and prevented recurrence.
  7. Closure: Record results and close the CAPA with full traceability.

CAPA Examples

Example 1: Corrective Action on a Defective Batch

Picture a quality engineer named Priya who gets a complaint that a batch of medical components is failing a dimensional check in the field. The corrective action isn’t just scrapping the bad parts. She pulls the team into a root cause analysis, runs a quick 5 Whys, and finds the real culprit: a tooling fixture that drifts out of tolerance after a certain number of cycles, and nobody had a check for that. So the fix isn’t only reworking the bad batch. It’s adding a fixture inspection step to the procedure, assigning an owner, and then watching the next several runs to confirm the defect actually stopped before she closes the CAPA. That last part matters. If you skip the verification, you’ve just guessed.

Example 2: Preventive Action from a Trend

Now picture the same plant a few months later. Nothing has failed yet, but Marcus, who owns the line metrics, notices the seal-failure rate creeping up week over week. Still inside spec, but clearly trending the wrong way. That’s the preventive half of CAPA doing its job. Instead of waiting for an actual nonconformity and a customer escalation, the team tightens the sealing parameter and updates the work instruction now, before anything ships bad. It’s the same investigative muscle that good quality assurance and quality control programs lean on, just pointed at a problem that hasn’t happened yet.

How Glitter AI Helps with CAPA

Here’s the thing about CAPA: a corrective action only sticks if the procedure actually changes, and people on the floor actually do the new thing. That’s where most CAPAs quietly fail. The fix lives in a closed record somewhere while the line keeps running the old way.

Glitter AI closes that gap for you. When your corrective action changes how work gets done, you just record the corrected process once, and Glitter turns it into a clear step-by-step guide your team can actually follow, screenshots and all. No one has to sit down and write a manual nobody reads. As preventive actions roll out, the same approach keeps your manufacturing SOPs current instead of drifting back to “how we’ve always done it.” And when an auditor asks to see that the loop was really closed, the documentation is right there, holding up under exactly that kind of scrutiny.

Turn any process into a step-by-step guide

Teach your co-workers or customers how to get stuff done – in seconds.

Frequently Asked Questions

What is corrective action / CAPA?

CAPA stands for Corrective and Preventive Action. It's a quality management process that fixes existing nonconformities by eliminating their root cause (corrective action) and prevents potential issues before they occur (preventive action).

What is the difference between corrective action and preventive action?

Corrective action responds to a problem that has already happened and eliminates its cause. Preventive action is proactive: it addresses a potential problem identified through analysis or trend data before it actually occurs.

What are the steps in the CAPA process?

The typical CAPA process steps are: identification of the issue, evaluation of risk, root cause analysis, action planning, implementation, verification of effectiveness, and closure with documentation.

Why is CAPA important in quality management?

CAPA prevents problems from recurring, reduces costs from repeated failures, improves product and process quality, and provides documented evidence required by standards like ISO 9001 and FDA regulations.

How is root cause analysis related to CAPA?

Root cause analysis is the investigative core of the CAPA process. You can't write an effective corrective action until you understand why the problem happened, so methods like the 5 Whys and Fishbone diagrams feed directly into CAPA.

What triggers a CAPA?

Common CAPA triggers include nonconformities, customer complaints, audit findings, internal deviations, failed inspections, and adverse trends spotted in quality data.

What does it mean to verify CAPA effectiveness?

Verifying effectiveness means confirming, with evidence, that the implemented action actually resolved the issue and that the problem has not recurred. A CAPA cannot be closed until effectiveness is demonstrated.

Is CAPA required by ISO 9001?

Yes. ISO 9001 requires organizations to take corrective action to eliminate the causes of nonconformities, and modern versions emphasize risk-based thinking that supports preventive action as well.

Who is responsible for CAPA?

CAPA is typically owned by the quality team or a quality manager, but execution involves cross-functional contributors from operations, engineering, and the departments where the issue originated.

How do you document a CAPA?

A CAPA record documents the problem description, risk evaluation, root cause findings, the action plan with owners and dates, implementation evidence, effectiveness verification, and formal closure for full audit traceability.