CAPA in Manufacturing: A Practical Guide
Introduction
Your customer rejects a batch of parts. Dimensions are out of spec. You tell the operator to adjust the machine, rerun the parts, and ship replacements.
Two months later, the same customer rejects another batch. Same dimensions. Same machine. Different operator. You adjust and rerun again.
This is fixing the symptom without fixing the cause. Manufacturers typically spend around 20% of total sales revenue on the cost of poor quality, including scrap, rework, warranty claims, and the labor burned chasing the same problems repeatedly.
CAPA (corrective and preventive action) is the formal process for breaking that cycle. Instead of patching the immediate problem and moving on, CAPA forces you to find the root cause, fix it, and verify the fix actually worked. Instead of waiting for the next failure, it asks what else might go wrong and addresses it before it does.
What is CAPA?
CAPA stands for corrective and preventive action. It's a structured approach to quality problems that goes beyond the immediate fix to address the underlying cause.
Corrective action starts after something has already gone wrong. A part fails inspection, a customer returns a defective product, a process drifts out of control. You investigate why, fix the root cause, and put controls in place so it doesn't happen again.
Preventive action starts before something goes wrong. You notice a trend in your inspection data, a risk assessment flags a weak point, or an operator reports uneven fixture wear. You address the risk before it produces a nonconformance.
Together, they form a feedback loop. Corrective actions generate data about what goes wrong. That data feeds preventive actions, which reduce future failures. A good CAPA system gets quieter over time, not louder.
CAPA is one part of a broader quality management system. It connects to your inspection processes, your nonconformance handling, and your manufacturing traceability. If you track first-pass yield, CAPA is how you improve it. If you track scrap rates, CAPA is how you reduce them. If you track customer complaints, CAPA is how you prevent the same complaint from showing up twice.
Why CAPA matters for manufacturers
The cost of fixing symptoms
When you fix a symptom, you pay for it every time the problem recurs. Scrapped material, rework labor, expedited shipping, customer communication. None of that is a one-time expense if the root cause is still there.
A machine shop that reworks the same tolerance issue four times a year at $3,000 per incident isn't dealing with four problems. It's dealing with one problem it never solved, at $12,000 a year. CAPA converts that recurring cost into a one-time investigation and a permanent fix.
Regulatory and customer requirements
If you work in aerospace, medical devices, automotive, or food manufacturing, CAPA isn't optional. ISO 9001 requires organizations to take action on nonconformities. AS9100 quality management adds aerospace-specific requirements. ISO 13485 makes CAPA a formal, documented procedure for medical devices. The FDA 21 CFR Part 11 considers "insufficient corrective and preventive action procedures" one of its most common compliance findings.
Even outside regulated industries, OEMs and prime contractors increasingly expect suppliers to have a functioning CAPA process. If your customer's quality questionnaire asks about corrective action procedures and you don't have a clear answer, that's a risk to the relationship.
Production data you can act on
CAPA generates useful data as a byproduct. When you track corrective actions over time, patterns emerge. Maybe 40% of your CAPAs trace back to the same work center. Maybe most nonconformances happen during changeovers. Maybe one supplier's material shows up disproportionately in your quality records.
This connects directly to production scheduling decisions, OEE improvements, and job costing accuracy.
The CAPA process, step by step
1. Identify the problem
A CAPA starts with a trigger: customer complaints, failed inspections, audit findings, nonconforming material, equipment failures, or trend data showing a process drifting.
Not every problem needs a full CAPA. A one-time mistake caught and corrected by an operator doesn't require a formal investigation. CAPA is for systemic issues, recurring problems, or significant events.
Document what happened in specific, measurable terms. "Parts were out of spec" isn't enough. "Lot 20260310-A, Job 4580, bore diameter measured 0.503" on 12 of 50 parts, tolerance is 0.500" +/- 0.001"" gives you something to investigate.
2. Contain the problem
Before investigating the root cause, contain the immediate impact. Quarantine suspect material. Segregate affected inventory. Notify customers if defective product may have shipped. This is the correction, not the corrective action.
Good traceability makes containment faster. If you can trace the affected lot to specific jobs and customers, you quarantine only what's affected instead of pulling everything off the shelf.
3. Investigate the root cause
This is where most CAPA processes fail. A survey of over 300 quality professionals found that poor root cause analysis was the single most cited problem with their CAPA systems.
The failure mode is stopping too early. "The operator didn't follow the procedure" is not a root cause. Why didn't they follow it? Was the procedure unclear? Was it physically impossible given the setup? Were they never trained on it?
Two common methods:
5 Whys. Start with the problem and ask "why" repeatedly until you reach a cause you can control. The rejected bore diameter: Why were parts oversize? The tool was worn. Why? It wasn't replaced at the scheduled interval. Why not? The schedule wasn't posted at the machine. Why not? No standard process for posting tool change schedules. Now you have something actionable.
Fishbone diagram. Organize potential causes into categories: machine, method, material, manpower, measurement, and environment. Work through each category to identify contributing factors. This works well when the cause isn't obvious or when multiple factors combined.
If your root cause could apply to almost any quality problem ("lack of training," "human error"), you haven't dug deep enough.
4. Plan and implement corrective action
Design a fix that addresses the root cause, not the symptom. If the root cause is that tool change schedules aren't posted at machines, the corrective action isn't "retrain the operator." It's "create a standard process for posting tool change schedules at each work center and verify it's being followed."
Good corrective actions name who is responsible, what they need to do, and when it needs to be done. "Improve the process" isn't a corrective action. "Engineering to update SOP-4520 to include tool change schedule posting requirements by April 15, and shift leads to verify compliance daily for 30 days" is one.
5. Implement preventive action
This is the step most manufacturers skip. You've fixed the problem that happened. Now ask: where else could this same type of failure occur?
If the root cause was missing tool change schedules at one work center, check whether other work centers have the same gap. If a supplier's material caused a nonconformance, review whether your incoming inspection process catches that defect type for other materials.
Preventive action takes the lesson from one failure and applies it across the operation before the same failure shows up somewhere else.
6. Verify effectiveness
A corrective action isn't complete when it's implemented. It's complete when you can prove it worked.
Set a verification period and define what success looks like in measurable terms. If the problem was oversize bore diameters, check inspection data for that operation over the next 30, 60, or 90 days. If the defect rate dropped to zero, the corrective action was effective. If the problem recurs, your root cause analysis missed something, and you need to reopen the investigation.
This is the second most common failure point. Teams implement the fix, close the CAPA, and never check whether it actually worked.
Common CAPA mistakes
Treating every issue as a CAPA
Not every defect needs a formal investigation. If you open a CAPA for every minor deviation, your quality team drowns in paperwork and the serious issues don't get attention.
Use risk-based criteria. A CAPA makes sense when a problem is recurring, affects product safety, results in a customer complaint, or when an audit identifies a systemic gap. A one-time cosmetic defect on a non-critical part probably doesn't need one.
Never triggering a CAPA at all
The opposite problem. Some shops treat CAPA as something that only happens during audits. Problems get fixed informally, the same issues keep coming back, and there's no record of what was investigated. If you're seeing the same problem more than twice, it needs a formal investigation with documented root cause analysis and verified corrective action.
Shallow root cause analysis
"Operator error" is the most common root cause finding, and it's almost never the actual root cause. Blaming the operator closes the CAPA on paper but doesn't prevent the next operator from making the same mistake. Push past the human error. Ask what about the process, the training, the tooling, or the environment allowed the error to happen.
Skipping verification
Implementing a corrective action and closing the CAPA on the same day means you assumed the fix would work without testing it. Build a verification check into every CAPA, and don't close it until the data confirms the problem is resolved.
Measuring your CAPA process
Track these numbers to know whether your process is working.
Recurrence rate. How often do closed CAPAs reopen because the problem came back? If your recurrence rate is above 10-15%, your investigations aren't going deep enough.
Time to closure. How long from opening a CAPA to verified closure? Track the median, not the average, since a few complex CAPAs will skew the mean.
CAPAs by source. Customer complaints, internal inspections, audit findings, operator reports? The distribution tells you where detection is strong and where problems are slipping through to customers.
Corrective vs. preventive ratio. If nearly all your CAPAs are corrective, you're always playing catch-up. A healthy system includes preventive actions from trend analysis and risk assessments, not just from failures.
Moving CAPA off spreadsheets
Most small shops start with a CAPA log in Excel. A row for each CAPA, columns for the problem description, root cause, corrective action, responsible person, due date, and status. For a shop that processes five CAPAs a year, this is fine.
It stops working when volume increases, when multiple people need to update the same records, or when an auditor asks for change history on a specific CAPA. The problems are the same ones that push manufacturers from spreadsheets to dedicated software in other areas: no audit trail, no workflow routing, and no connection between your CAPA log and the production data that triggered it.
A manufacturing ERP with quality management built in keeps CAPA records connected to the production data they reference. The nonconformance, the lot number, the inspection results, and the corrective action all live in the same system. When an auditor asks about a specific quality event, you pull it up in seconds instead of assembling it from three files.
How to get started
If you don't have a formal CAPA process today, here's a practical path.
Pick your top three recurring quality problems. Look at your scrap reports, rework logs, and customer complaints from the last six months. Which problems keep showing up? Start there. Solving three real, recurring problems is worth more than writing a procedure that covers everything but solves nothing.
Investigate one properly. Take the most expensive recurring problem and run a real root cause analysis. Get the operator, the engineer, and the quality person in a room. Use the 5 Whys or a fishbone diagram. Write down the root cause, design a corrective action, assign an owner, and set a due date.
Verify and document. After implementing the corrective action, track results for 60-90 days. Did the problem stop? Document what you found, what you did, and the results. That's your first completed CAPA record.
Create a simple procedure. Based on what you learned, write a one-page procedure that defines when to open a CAPA, who's involved, what the steps are, and how verification works. A ten-page procedure that nobody reads is worse than a one-page procedure that everyone follows.
Build the habit. Run your CAPA process consistently for three months. Review open CAPAs in weekly production meetings. The goal is a process your team uses because it helps them, not one they endure because the auditor requires it.
Conclusion
CAPA is the difference between a shop that fixes the same problems over and over and a shop that fixes them once. Corrective action finds the root cause and eliminates it. Preventive action applies that lesson before the next failure occurs. Verification confirms the fix worked.
You don't need a dedicated quality department or an enterprise QMS to start. You need the willingness to investigate problems beyond the surface, the discipline to follow through, and a way to check whether your fixes made a difference.
Ready to connect quality data to your production floor?
WorkCell gives manufacturers built-in quality tracking that links nonconformances, corrective actions, and inspection results to your actual jobs and materials. No separate QMS software required.
Book a demo and we'll show you how it works with your production data.