Manufacturing & custom software · Bengaluru · Whitefish, USA
Manufacturing

What Is CAPA in Quality? Corrective and Preventive Action Explained With Examples

A clear explanation of CAPA (corrective and preventive action) in manufacturing quality: correction vs corrective vs preventive action, the CAPA process step by step, root cause tools, effectiveness checks, ISO 9001 and IATF expectations, examples and common mistakes.

By Corposol Team··5 min read
Vernier caliper used for dimensional inspection
Photo: Caliper full view by Simon A. Eugster, CC BY-SA 3.0 (cropped)

CAPA stands for Corrective and Preventive Action. It is the process a manufacturer uses to find the cause of a quality problem, remove it so the problem does not recur, and prevent similar problems elsewhere. Every quality standard — ISO 9001, IATF 16949, GMP and others — expects some form of it, and every customer audit looks at how well it works.

This guide explains CAPA in practical terms, with a step-by-step process, examples and the mistakes that make CAPAs fail.

Correction, corrective action, preventive action

TermPurposeExample
Correction (containment)Deal with the immediate problemSort all stock and WIP for oversized bores; rework or scrap
Corrective actionEliminate the cause of a problem that occurredReplace worn boring bar holder; add tool-life limit; add in-process gauge check
Preventive actionEliminate the cause of a potential problem before it occursApply tool-life limits and checks to all similar boring operations on other machines

Many organisations confuse correction with corrective action and close CAPAs after sorting the parts. The problem then returns.

The CAPA process, step by step

1. Identify and describe the problem

What happened, where, when, how many, and how it was detected. A precise description — "bore diameter 25.06 mm against 25.00 +0.03 on part X, 40 pieces found at customer incoming inspection, lot 2311-07" — makes everything that follows easier. Link the CAPA to its source: a customer complaint, an NCR, an audit finding.

2. Contain

Protect the customer immediately: block suspect stock, sort WIP and finished goods, inform the customer, and arrange replacement. Use traceability to find every affected lot.

3. Find the root cause

Use structured tools: 5 Why, fishbone (Ishikawa) diagrams, data analysis and process observation. Look for two causes: why it happened (occurrence) and why it was not detected (escape). Verify the root cause — if possible, show that switching it on and off makes the problem appear and disappear.

4. Plan and implement corrective actions

Actions that remove the root causes, each with an owner and due date. Prefer actions that make the error impossible or immediately detectable, such as poka-yoke, over "retrain the operator" and "be more careful".

5. Extend to similar processes (preventive)

Ask where else the same cause could occur — other machines, parts, products or plants — and apply the actions there too.

6. Update documents

Control plans, PFMEAs, work instructions, inspection plans and training records updated to reflect the change. See control plans.

7. Verify effectiveness

After a defined period, check the data: has the problem recurred? Is the new control working? Only then close the CAPA. If not effective, return to root cause.

8. Close and share

Close with evidence, and share lessons across teams. Many customers require the steps in an 8D format — see 8D problem solving.

A worked example

Problem: a customer finds burrs on a stamped bracket in two consecutive deliveries.

Containment: stock at customer and in-house sorted; 100% visual check added temporarily at packing.

Root cause (occurrence): die cutting edge worn; the die had run 30% beyond its usual regrind interval because stroke counts were tracked on paper and missed.

Root cause (escape): burr height was checked only at first piece, not during the run.

Corrective actions: stroke counts captured automatically from the press, with a regrind alert at the defined limit (see press tool regrind records); burr check added to patrol inspection every two hours.

Preventive action: regrind limits and alerts applied to all progressive dies.

Effectiveness: no burr complaints over the next three months; regrinds performed on time.

Common CAPA mistakes

  • "Operator error" as the root cause — ask why the process allowed the error.
  • Closing after containment, without corrective action.
  • Actions without owners or dates.
  • No effectiveness check.
  • Too many CAPAs for minor issues, so important ones get little attention.
  • CAPAs stored in separate files, so repeat problems are not noticed.

Managing CAPA with software

A CAPA system links each CAPA to its source (complaint, NCR, audit), tracks actions and due dates, sends reminders, stores evidence, schedules effectiveness checks, and shows open CAPAs by age and owner. Most importantly, it makes repeat problems visible: the same defect, part or supplier appearing again. See quality management software development.

CAPA record checklist

A complete CAPA record should contain:

  • Source (complaint, NCR, audit, supplier issue) and reference number.
  • Problem description with facts and quantities.
  • Containment actions and results.
  • Team members.
  • Root cause analysis for occurrence and escape, with evidence.
  • Corrective actions with owners, due dates and completion evidence.
  • Preventive extension to similar processes.
  • Documents updated (PFMEA, control plan, instructions).
  • Effectiveness check method, date and result.
  • Closure approval.

Prioritising CAPAs

Not every problem needs the same effort. A simple matrix by severity (safety, customer impact, cost) and frequency helps decide which issues get a full CAPA with a team and 8D, which get a simple corrective action, and which are handled through daily problem solving. This keeps the CAPA list short enough to manage properly.

CAPA measures

  • Number of open CAPAs and their age.
  • On-time completion of actions.
  • Effectiveness rate — CAPAs closed without recurrence.
  • Repeat problems by part, process or supplier.

Frequently asked questions

What is the difference between correction and corrective action?

Correction fixes the immediate problem — sorting, reworking or replacing the defective parts. Corrective action removes the cause so the problem does not happen again. Both are needed, but only corrective action prevents recurrence.

Does ISO 9001 still require preventive action?

ISO 9001:2015 replaced the separate preventive action clause with risk-based thinking throughout the standard. Preventing problems is still expected; it is addressed through risk and opportunity planning rather than a separate procedure. Many companies still use the CAPA term.

How long should a CAPA take?

Containment should be immediate, often within 24 hours. Root cause and corrective action commonly take days to a few weeks. Effectiveness verification needs enough time — often several weeks or production runs — to show the problem has not returned.

When should a CAPA be raised?

For customer complaints, repeated or significant internal non-conformances, audit findings, supplier problems and safety issues. Not every minor defect needs a full CAPA; define criteria so effort goes where it matters.

  • CAPA
  • Corrective action
  • Preventive action
  • Root cause analysis
  • ISO 9001

Let's discuss your factory's software

Tell us about your process or idea. You'll get a free consultation and a clear, fixed quote — no obligation.

  • Free consultation
  • Prototype before you commit
  • Fixed, itemised quote
  • You own the software

Get a free quote

We reply within one working day. Your details are never shared.