Method guide · Quality management
CAPA: corrective and preventive action, meaning, process and a worked example
Short answer
CAPA, short for corrective and preventive action, is the quality process that finds the cause of a problem and removes it. Corrective action stops a problem that has already happened from coming back. Preventive action removes the cause of a problem that has not happened yet.
A CAPA opens from a trigger such as a customer complaint, a repeat NCR, an audit finding or a supplier failure. The team contains the problem, finds the root cause, puts in an action that removes that cause, and checks after a set period that the problem has stayed away. Only then does the CAPA close. Sorting or reworking the bad parts is a correction, not a corrective action: it deals with the parts in front of you and leaves the cause in place.
Last reviewed:
What is CAPA?
CAPA stands for corrective and preventive action. It is how a plant makes sure a quality problem is fixed at its cause rather than patched each time it shows up. The word covers two things: the process a team follows, and the record that proves it was followed, from the problem statement to the check that the fix held.
A CAPA is bigger than a fix on the line. When a supervisor swaps a worn tool and the scrap stops, that is good practice but it is not a CAPA. A CAPA asks why the tool wore out without anyone noticing, changes something in the system so it cannot happen that way again, and then proves it. That is why quality standards treat CAPA as the core of a quality system: it is the part that learns.
Most CAPAs start from a non-conformance report, which records the problem and what was done with the parts. The NCR contains; the CAPA removes the cause. When the cause is not obvious, the CAPA uses root cause analysis tools such as the 5 Whys and the fishbone to find it.
Correction vs corrective action vs preventive action
Three terms get mixed up on almost every audit. Take one problem, loose bolts on an assembly, and the difference is plain.
Correction, corrective action and preventive action for one problem
Correction
- What it deals with
- The problem in front of you: the bad parts
- When
- Now, before the cause is known
- Example: loose bolts on a bracket assembly
- Hold the lot, check every assembly with a torque wrench, retighten the loose ones
Corrective action
- What it deals with
- The cause of a problem that has happened
- When
- After the root cause is found
- Example: loose bolts on a bracket assembly
- Repair the monitored nutrunner and stop the station if it is down, so an unmonitored gun is never used
Preventive action
- What it deals with
- The cause of a problem that has not happened yet
- When
- Before a failure, from a risk or a trend
- Example: loose bolts on a bracket assembly
- Apply the same rule to the other stations that use monitored tools, before any of them ships a loose bolt
What is a corrective action?
A corrective action is a change that removes the cause of a nonconformity so it does not recur. The test is simple: if the same conditions came back tomorrow, would the problem happen again? If yes, the action was a correction. Good corrective actions change the process, the equipment, the method or the check, not only the people. An error-proofing device, a changed fixture or a gauge that stops the line are corrective actions. A reminder at the shift huddle is not.
What is a preventive action?
A preventive action removes the cause of a potential problem. It comes from looking forward: a trend on a control chart heading for a limit, a high risk line in the FMEA, a near miss, or a fix on one line that should be copied to the lines that have the same weakness. The most useful source in a plant is the last one. Every corrective action should end with the question: where else could this happen?
Corrective and preventive actions often sit in the same CAPA record. The corrective part fixes the line that failed; the preventive part spreads the fix to the lines that have not failed yet.
What should open a CAPA
A CAPA takes people and time, so it is kept for problems that justify the effort. Common sources:
- Customer complaints and returns, especially any that reach the field.
- NCRs that repeat, cost a lot, or point at a system weakness rather than a one-off.
- Internal, customer and certification audit findings.
- Supplier problems, which go to the supplier as a supplier corrective action request.
- Process data: a control chart out of control, a falling first pass yield, rising scrap on one part.
- Safety incidents and near misses that have a quality or process cause.
- Management review, when a measure has stayed off target for several months.
Not every NCR needs a CAPA. A single cosmetic mark with an obvious cause can be corrected and logged. Most plants write a short rule so the decision is the same on every shift, for example:
| Condition | Open a CAPA? |
|---|---|
| Safety, legal or regulatory impact | Always |
| Reached the customer | Always |
| Same defect three or more times in 90 days | Yes |
| Major nonconformity on an audit | Yes |
| One-off, minor, cause known and already removed | No: correct, record on the NCR, watch for repeats |
Illustrative. Set the thresholds for your plant and write them in the quality procedure, so the rule is the same for every shift and every auditor.
The CAPA process in eight steps
Companies number the steps differently, five, seven or eight, but the content is the same. These are the eight a plant can audit against.
The CAPA process in eight steps
- 1
Describe the problem
- 2Correction
Contain it
- 3
Set the scope and the team
- 4Occurrence and escape
Find the root cause, twice
- 5
Plan the corrective action
- 6
Implement and update the documents
- 7Decision
Did the problem stay away?
- Yes:
- Close and spread.
- No:
- Back to step 4, the root cause.
- 8Preventive action
Close and spread
- 1
Describe the problem
Write what is wrong, on which part and line, since when, how many, and how it was found. Say what it is and what it is not: which shift, which tool, which lot is affected and which is not. A vague problem statement produces a vague cause.
- 2
Contain it
Protect the customer first. Hold suspect stock, sort or check it, add a temporary inspection, post a quality alert at the station. Record what was checked and what was found, because those counts are evidence later.
- 3
Set the scope and the team
Judge the risk: how bad, how often, how far it may have spread. Name an owner and the people who know the process, usually the supervisor, an operator from the station, quality and maintenance or engineering.
- 4
Find the root cause, twice
Find why it happened (the occurrence cause) and why it was not caught before it left the station (the escape cause). Use the 5 Whys, a fishbone or an is/is not comparison, and test the cause: can you switch the problem on and off with it?
- 5
Plan the corrective action
For each cause, choose an action that removes it. Prefer changes to the process or the equipment over instructions. Write the plan with an owner, a date and the measure that will show it worked.
- 6
Implement and update the documents
Make the change, then update what describes the process: the work instruction or SOP, the control plan, the PFMEA, the check sheet, and the training records of the people affected.
- 7
Verify that it worked
After a set period, check the measure chosen at step 5. Done is not the same as effective. If the problem has come back, the cause was wrong or the action was too weak: go back to step 4.
- 8
Close and spread
Close the CAPA with the evidence attached. Then take the fix to every line, product and site with the same weakness. That spread is the preventive action, and it is where most of the value is.
Step 7 is the step auditors look at hardest and plants skip most often. A CAPA closed the day the action is done has not been verified. Decide at step 5 what effective will look like and when it will be checked, and put the date in the CAPA log.
How to write a corrective action plan
A corrective action plan is the part of the CAPA that says who will do what, by when, to remove each cause, and how everyone will know it worked. One line per action is enough, as long as each line answers six questions.
| Field | What to write | Weak entry | Strong entry |
|---|---|---|---|
| Cause | The verified cause this action removes | Operator error | Pneumatic gun used while the monitored nutrunner was down |
| Action | The change to the process, equipment or check | Retrain operators | Hold a spare nutrunner in the tool crib; station stops if no monitored tool is available |
| Type | Correction, corrective or preventive | Not stated | Corrective (occurrence) |
| Owner | One named person | Maintenance | The maintenance supervisor on days |
| Due date | A date, not a week | ASAP | A calendar date two weeks out |
| Effectiveness measure | What will be checked, how, and when | Monitor | Zero torque rejects in a 600-unit audit over 60 production days |
The free [corrective action form](/templates/corrective-action-form) has these fields, with separate lines for the occurrence and the escape cause and a closure check.
What is a corrective action request?
A corrective action request, or CAR, is a formal request to the person or group responsible for a problem to investigate it and respond with a corrective action plan by a set date. Inside a plant, quality might raise a CAR to the paint shop after an audit finding. When the request goes outside the company to a supplier, it is called a supplier corrective action request, or SCAR, and the supplier often answers in an 8D format. The request opens the CAPA; the response is the plan.
A CAPA example from a plant, step by step
This example is illustrative, not from a real plant. A plant builds a steel bracket assembly held by two M8 bolts, tightened at station 3 with a nutrunner that monitors torque and stops on a reject. Output is 1,150 assemblies a day.
| Step | What the team did and found |
|---|---|
| 1. Problem | The customer checked a delivery of 1,200 assemblies after one failed at their line and found 6 with a loose bolt: 6 / 1,200 = 0.5%. All 6 came from three production days in one week. |
| 2. Containment | The 2,250 assemblies from those three days still in the warehouse were held and every bolt checked with a torque wrench: 9 loose, 0.4%. The 9 were retightened and rechecked. Stock from other days was sampled; none were loose. |
| 3. Scope and team | Risk rated high because it reached the customer. Owner: the quality engineer. Team: the station 3 supervisor, two operators, the maintenance supervisor. |
| 4. Root cause | Occurrence: the nutrunner failed on the first of the three days and the line used a pneumatic gun with no torque monitoring until the spare part arrived. Escape: nothing after station 3 checks torque, and the gun gave no reject signal. |
| 5. Plan | Corrective (occurrence): spare nutrunner held in the tool crib; station stops if no monitored tool is available, written into the SOP. Corrective (escape): torque audit of 5 assemblies per shift with a calibrated wrench. Preventive: the same rule and a spare tool for the four other stations that use monitored tools. |
| 6. Implement | Spare tools bought and logged, SOP and control plan updated, the PFMEA line for tool substitution rescored, operators on both shifts briefed and signed off. |
| 7. Verify | Measure set at step 5: zero torque rejects in the shift audit for 60 production days, and no unmonitored tool use in the maintenance log. Result: 5 x 2 shifts x 60 days = 600 assemblies checked, 0 rejects; one nutrunner fault in the period, covered by the spare in 20 minutes. |
| 8. Close and spread | Closed with the audit records attached. The tool rule was added to the standard for new stations so the next line starts with it. |
Check the counts the other way: three days at 1,150 a day = 3,450 assemblies, of which 1,200 shipped and 2,250 stayed, and 1,200 + 2,250 = 3,450. Loose bolts found: 6 + 9 = 15, so 15 / 3,450 = 0.43% of the three days' output. Audit: 600 / 60 days = 10 a day = 5 on each of 2 shifts.
Two things in this example are worth copying. The team found an escape cause as well as an occurrence cause, so a future tool failure would be caught at the station even if the first rule were broken. And the preventive action went to the four stations that had not failed, which is where the next complaint would have come from.
CAPA and 8D, A3 and PDCA
CAPA is the requirement: find the cause, remove it, prove it. 8D, A3 and PDCA are ways to do the work. 8D, the eight disciplines, is common in automotive and with customers who ask for a written report. Its steps line up with the CAPA steps above.
| 8D discipline | CAPA step |
|---|---|
| D0 Plan, D1 Form the team | 3. Set the scope and the team |
| D2 Describe the problem | 1. Describe the problem |
| D3 Interim containment | 2. Contain it |
| D4 Root cause and escape point | 4. Find the root cause, twice |
| D5 Choose permanent corrective actions | 5. Plan the corrective action |
| D6 Implement and validate | 6. Implement, and 7. Verify |
| D7 Prevent recurrence | 8. Spread the fix (the preventive action) |
| D8 Recognize the team | Close |
The free [8D report template](/templates/8d-report-template) and the [8D problem solving poster](/posters/8d-problem-solving-poster) follow these disciplines.
An A3 puts the same thinking on one sheet and suits problems inside the plant that a team owns end to end. Underneath both is the PDSA or PDCA cycle: plan the fix, do it, check that it worked, act to standardize it. The CAPA record is the evidence that each turn of the cycle was finished. For a side by side of all the methods, see problem solving methods.
CAPA in ISO 9001, IATF 16949, ISO 13485 and FDA 21 CFR 820
This section names the requirements without quoting them. Wording and numbering depend on the edition, so check the current text of the standard that applies to you.
| Standard | Where CAPA is | What to know |
|---|---|---|
| ISO 9001:2015 | Clause 10.2, nonconformity and corrective action | Preventive action is no longer a separate clause. It is covered by risk-based thinking, clause 6.1, actions to address risks and opportunities. |
| IATF 16949:2016 | Clause 10.2 with 10.2.3 problem solving and 10.2.4 error-proofing | Automotive adds a documented problem solving process and error-proofing on top of ISO 9001; customers often specify 8D. |
| ISO 13485:2016 | Clause 8.5.2 corrective action and 8.5.3 preventive action | The medical device standard keeps preventive action as its own requirement. |
| FDA 21 CFR Part 820 | The Quality Management System Regulation, in force since 2 February 2026 | It incorporates ISO 13485:2016 by reference. The earlier Quality System Regulation had its own CAPA section, 820.100. |
Why did ISO 9001 drop preventive action as a clause? The 2015 edition built thinking about risk into the whole system, from planning onward, so preventing problems became the job of every process rather than a separate form filled in afterwards. Many plants still keep a preventive action field on the CAPA, and it is still good practice; it just is not a clause on its own in ISO 9001.
How to tell if your CAPA system works
A long list of open CAPAs is not a sign of a strong quality system. These measures, reviewed monthly, say more:
- Repeat rate: how many closed CAPAs had the same problem come back within a year. This is the measure that matters most.
- Effectiveness passed first time: the share of CAPAs whose check at step 7 passed without going back to the root cause.
- Overdue: open CAPAs past their due date, and how far past.
- Age: days open, as an average and as a list of the oldest.
- Source mix: complaints, audits, NCRs, suppliers. A plant where nearly every CAPA comes from customer complaints is finding problems late.
The free CAPA log template works out days open, flags late items and counts CAPAs by source. To put a cost on the problems behind them, the cost of poor quality calculator adds up scrap, rework and failure costs.
Common CAPA mistakes
- Closing on implementation. The action is done, so the CAPA is closed. Without step 7 nobody knows if it worked.
- Root cause: operator error. People make mistakes in every process. Ask what made the mistake possible and why it was not caught.
- Retraining as the corrective action. Training fixes a gap in knowledge. If the operator already knew the method, retraining changes nothing; change the process or add an error-proofing check.
- Only the occurrence cause. If the escape cause is left alone, the next different failure will also reach the customer.
- A CAPA for everything. When every minor NCR opens a CAPA, the list grows past what the team can work and the important ones wait. Use a written rule.
- Preventive action that never leaves the line. The same weakness is usually on the next line, the sister product or the other site.
- Documents left behind. The fix lives in the team's heads, and the SOP, control plan and PFMEA still describe the old process.
Running CAPA on paper, in a spreadsheet or in software
A small plant can run CAPA well with a form and a log. Start with the corrective action form for each CAPA and the CAPA log template for the list. The log breaks down when CAPAs come from several places, the NCR in one file, the audit finding in another, the supplier response in an email, and nobody can see what is late.
In LeanSuite, operators raise an NCR as a tag with photos at the line, and a systemic issue becomes a CAPA: a project type with its own approval steps, root cause sections and action plan. A failed audit or checklist item can start a CAPA, and a supplier defect can raise a SCAR with photos and a response deadline. See non-conformance management, the corrective action log for the shop floor, or the best CAPA software comparison if you are choosing a system.
CAPA management
Run CAPA in LeanSuite
CAPA management in LeanSuite runs each corrective action as a project with its own approval steps, root cause sections and action plan, and shows what fewer defects saved.
Go deeper
This page is the short version. These guides cover each part in full.
- Non-Conformance Reports: Managing Quality Deviations in ManufacturingThe NCR that most CAPAs start from, and how to manage it.
- 8D Problem Solving: The Eight Disciplines Method for ManufacturingEach of the eight disciplines in depth, the format many customers ask for.
- What is the 5 Whys Root Cause Analysis Method?The quickest way to get from a problem to a cause at step 4.
- Is/Is Not Analysis: Problem Definition for Root Cause AnalysisHow to write the problem statement at step 1 so the cause can be found.
All our articles on this subject are in the quality management topic.
Free templates and tools
- 3C problem boardConcern, cause and countermeasure with an owner for each, as a Lean Studio board for the line's open problems.
- Corrective action request (CAPA) formOne problem from containment to proof the fix worked, with occurrence and escape causes and a closure check that tells you when it can close.
- CAPA log templateAn Excel CAPA tracker with status, days open, late flags and counts by source, plus a printable log and monthly review.
- 8D report templateD0 to D8 with targets, containment counts, occurrence, escape and systemic causes, verified actions and a worked example.
- Supplier corrective action request (SCAR) formA SCAR from the problem and containment asked for to the supplier's 8D-style response, verification and closure, with a filled-in example.
- 5 Whys templateA problem statement, a why chain that can branch, evidence for every answer, root causes and countermeasures that are checked.
- Is / is not analysis templateWhat, where, when and extent with is, is not, distinctions and changes, then each possible cause tested against every pair and ranked.
- Quality alert formA quality alert to post at the line, a sign-off sheet for every shift, and a log of open, expired and closed alerts.
- Cost of poor quality (COPQ) calculatorTotal COPQ and cost of quality, and each as a share of revenue, from the four quality cost categories.
- First pass yield (FPY) calculatorFirst pass yield at each step and rolled throughput yield (RTY) across the whole process.
Doing this in LeanSuite
Non-Conformance (NCR)
Moves non-conformance reports into an automated workflow and links each defect report to root-cause problem solving.
See Non-Conformance (NCR)Quality Improvement
Log quality issues from the floor, trace each one to its root cause and follow the corrective action through to closure.
See Quality ImprovementKaizen & Projects
Manage every improvement project in one visual hub, from a small kaizen event to a full DMAIC project, and track each one through to results.
See Kaizen & Projects
Open this board in LeanSuite
The 3C problem board is one of the 30 ready-made boards in Lean Studio, LeanSuite's whiteboard. Try the interactive demo in your browser with sample data, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.
What Lean Studio isFAQ
Questions about cAPA (corrective and preventive action)
CAPA stands for corrective and preventive action. It is the quality process that finds the root cause of a problem and removes it, then checks that the problem has not come back. Corrective action deals with a problem that has happened; preventive action removes the cause of one that has not happened yet.
Corrective action removes the cause of a problem that has already happened, so it does not recur. Preventive action removes the cause of a problem that has not happened yet, found from a risk, a trend or a fix on another line. Both can sit in the same CAPA: the corrective part fixes the line that failed and the preventive part spreads the fix to lines with the same weakness.
A correction deals with the problem in front of you, such as sorting, reworking or scrapping the bad parts. A corrective action removes the cause so the problem does not happen again. Retightening loose bolts is a correction; changing the process so an unmonitored tool can never be used is a corrective action.
Describe the problem, contain it, set the scope and team, find the root cause (why it happened and why it was not caught), plan the corrective action, implement it and update the documents, verify after a set period that it worked, then close the CAPA and spread the fix to other lines. Some companies use five or seven steps; the content is the same.
A corrective action request, or CAR, is a formal request to the person or group responsible for a problem to investigate it and reply with a corrective action plan by a set date. When it goes to a supplier it is called a supplier corrective action request, or SCAR, and the reply is often an 8D report.
Loose bolts reached a customer because a torque-monitoring nutrunner broke and the line used a plain pneumatic gun. The corrective action was a spare nutrunner in the tool crib and a rule that the station stops if no monitored tool is available, plus a torque audit of five assemblies per shift to catch any escape.
A corrective action plan lists, for each verified cause, the action that removes it, the type of action, one named owner, a due date and the measure that will show it worked, with the date it will be checked. It is the part of a CAPA that turns the root cause into work someone is accountable for.
Not as a separate clause. ISO 9001:2015 covers corrective action in clause 10.2 and replaced the old preventive action clause with risk-based thinking, mainly clause 6.1 on actions to address risks and opportunities. ISO 13485:2016 for medical devices still has preventive action as its own requirement, in clause 8.5.3.
Only when the cause was a real gap in knowledge, such as a new operator who was never shown the method. If the person already knew the method, retraining does not remove the cause. Look at what made the mistake possible and why it was not caught, and change the process, the fixture or the check.
CAPA is the requirement to find a cause, remove it and prove the fix worked. 8D is one structured method for doing that work in eight disciplines, from forming the team to preventing recurrence, and it is common in automotive. An 8D report is often the record of a CAPA.
Related guides and tools
- Nonconformance and the NCR: the record that starts most CAPAs
- Root cause analysis: the tools for step 4 of a CAPA, with a worked example
- Material review board: deciding what happens to the nonconforming parts
- Corrective action form: one CAPA from containment to the closure check, in Excel and PDF
- CAPA effectiveness check: proving the fix held
More method guides
- The 6 Ms of production
- Poka-yoke
- Model area 90-day plans
- Moving from Excel to one system
- Reducing machine downtime: a worked month
- Andon
- Cycle time vs lead time, worked through
- Root cause analysis
- How many operators a line needs
- Reducing scrap and rework: a worked month
- Unsafe acts and unsafe conditions
- Just culture
- Stop-work authority
- Material review board (MRB)
- Nonconformance and NCRs
- Problem solving methods
- Quad chart
- OEE calculation
- Quality assurance vs quality control
- SOP meaning and format
- Job hazard analysis
- Near miss reporting
- Fishbone diagram
- Pareto chart
- Histogram
- Control chart
- What is a gemba walk
- What is lead time
- What is operational excellence
- How to improve product quality
- Preventive vs predictive maintenance
- Kanban
- FMEA
- PDSA cycle
- Safety moments
- Just-in-time manufacturing
- Kaizen
- 5S
- Total quality management (TQM)
- Layered process audit (LPA)
- Lean tools
- Lockout tagout (LOTO)
- A3 problem solving
- Preventive maintenance
- APQP
- High reliability organization (HRO)
- Manufacturing KPIs
- Quality metrics
- Practical problem solving
- CMMS
- Risk assessment
- Production efficiency
- Total productive maintenance (TPM)
- Reliability-centered maintenance (RCM)
Or browse the topics, the full library and the lean glossary.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

