
CAPA stands for Corrective and Preventive Action. CAPA management is the process of finding the root cause of a quality problem, fixing it so it does not recur (corrective action), and removing the causes of potential problems before they happen (preventive action). A standard CAPA process has eight steps: identify and log the issue, assess risk and contain it, investigate, find the root cause, plan actions, implement them, verify effectiveness, and close with lessons standardized. Automating CAPA management routes each step to the right owner with deadlines, escalations and an audit trail, so CAPAs close faster and auditors see complete evidence.
Every manufacturer has quality problems. The difference between plants that improve and plants that keep firefighting is what happens after the problem is found. If a failed inspection is fixed on the line and forgotten, the same defect comes back next month. If it becomes a CAPA with a real root cause, an owner and an effectiveness check, it stops coming back.
This guide explains what CAPA is, the eight steps of the CAPA process, the root cause methods quality teams use, what ISO 9001 auditors expect, and how to automate CAPA management without buying a heavyweight quality suite.
CAPA (Corrective and Preventive Action) is a structured quality process for eliminating the causes of problems. It is a core part of any quality management system (QMS) and is used in manufacturing, pharmaceuticals, food processing, engineering and any operation that must deliver consistent quality.
CAPA management is how an organization runs that process consistently: logging issues, assigning owners, investigating, tracking actions to closure, checking that the fix worked and keeping records.
These three terms are often mixed up, and auditors notice. The difference is in what each one targets:
| Correction | Corrective action | Preventive action | |
|---|---|---|---|
| Targets | The immediate problem (the symptom) | The root cause of a problem that occurred | The cause of a problem that could occur |
| Timing | Right away | After investigation | Before any failure |
| Example | Rework or scrap the defective batch | Replace the worn fixture that caused the defect and add it to the maintenance schedule | Add the same fixture check to similar lines that have not failed yet |
| Question it answers | How do we contain this now? | Why did this happen, and how do we stop it recurring? | Where else could this happen? |
A correction without a corrective action is the most common CAPA failure: the batch is fixed, but nothing changes, so the defect returns.
A CAPA can be triggered by any signal that something is not meeting requirements. The most common sources are:
Not every issue needs a full CAPA. Most quality teams use a simple risk screen: low-risk, one-off issues get a correction and a log entry, while repeat, high-severity or customer-facing issues get a full CAPA.
Many plants still run CAPAs in a spreadsheet, a shared folder and a lot of email. It works until volume, audits or recurring defects expose the gaps:
These gaps slow non-conformance response, which is one of the hidden drags on manufacturing efficiency.
Most CAPA procedures, including those built around ISO 9001 and the 8D method, follow these eight steps:
Record what happened, where, when, which product or process, the requirement that was not met, and any photos or measurements. Give every CAPA a unique number.
Rate severity and likelihood, decide whether a full CAPA is needed, and take immediate correction: quarantine stock, stop the line, notify the customer if required.
Assign an owner and a cross-functional team. Gather data: batch records, inspection results, maintenance logs, operator interviews.
Use a structured method (see the next section) to find the underlying cause rather than the symptom. Document the analysis.
Define specific actions, owners and due dates. Include actions for similar products, lines or sites where the same cause could exist.
Carry out the actions: change the process, update the SOP, retrain operators, adjust maintenance, or change the supplier. Record evidence for each action.
After an agreed period, check with data that the problem has not recurred. If it has, reopen the investigation.
Get approval to close, update documents and training, and share the lesson across lines and sites.

| Method | How it works | Best for |
|---|---|---|
| 5 Whys | Ask “why” repeatedly until you reach a cause you can act on | Simple, single-cause problems |
| Fishbone (Ishikawa) diagram | Group possible causes under categories such as man, machine, method, material, measurement and environment | Problems with several possible causes |
| Pareto analysis | Rank causes by frequency or cost to find the vital few | Recurring defects with lots of data |
| FMEA | Score failure modes by severity, occurrence and detection to prioritize risk | Preventive action and new processes |
| 8D | An eight-discipline team method from problem description to recognition | Customer complaints and supplier issues |
| Fault tree analysis | Map logical combinations of events that lead to a failure | Complex or safety-critical failures |
Whatever the method, the CAPA record should show the analysis, not just the conclusion. That evidence is what makes CAPA part of real continuous improvement rather than paperwork.
A good CAPA form captures enough to investigate, act and prove effectiveness. Use this as a template for your own corrective action form or report:
| Section | Fields |
|---|---|
| Identification | CAPA number, date, source (inspection, complaint, audit, incident), product or process, line or site, raised by |
| Problem description | What happened, requirement not met, quantity affected, photos and attachments |
| Risk and containment | Severity, likelihood, risk rating, immediate correction taken, containment owner |
| Investigation | Owner, team members, data reviewed, investigation due date |
| Root cause | Method used, root cause statement, contributing causes |
| Action plan | Each corrective and preventive action with owner, due date and status |
| Implementation evidence | Documents updated, training records, change records, photos |
| Effectiveness check | Verification method, check date, result, reviewer |
| Closure | Approver, closure date, lessons learned, linked CAPAs |
ISO 9001 requires organizations to react to nonconformities, evaluate and determine their causes, implement corrective action, review whether that action was effective and keep documented evidence. Since the 2015 edition, preventive action is no longer a separate clause; prevention is handled through risk-based thinking across the quality management system. Many manufacturers still use the CAPA label because it keeps both halves in one process.
ISO 9001:2026 is now published. ISO announced the new edition on 16 September 2026 (ISO). It keeps the harmonized management system structure and adds emphasis on areas such as quality culture and risk and opportunity management (ISO 9001 standard page). Certified organizations have a transition period to move to the new edition, so check the deadline with your certification body and review your CAPA procedure as part of the gap analysis.
In audits, CAPA is one of the most examined processes. Auditors typically look for:
A system with a complete audit trail turns these questions into a report rather than a scramble; see workflow compliance management.
| Metric | What it tells you |
|---|---|
| Average CAPA cycle time | How long it takes from opening to closure, ideally by severity |
| Overdue CAPAs | How many actions have passed their due date, and where |
| On-time closure rate | Share of CAPAs closed by their target date |
| Effectiveness rate | Share of closed CAPAs where the problem did not recur |
| Recurrence rate | How often the same issue reopens |
| CAPAs by source and area | Which processes, lines or suppliers generate the most issues |
| Type | Best for | Strengths | Watch-outs |
|---|---|---|---|
| Spreadsheets and shared forms | Very low CAPA volume | No cost, familiar | No reminders, escalation, audit trail or trend view |
| CAPA module in an enterprise eQMS | Regulated life sciences and large multi-site quality teams | Deep validation, document control and regulatory features | Cost, long implementation, rigid to change |
| CAPA inside MES or ERP | Plants where production systems already run quality | Close link to production data | Limited workflow flexibility; changes need IT or vendor |
| Configurable (no-code) CAPA workflow | Mid-size manufacturers on ISO 9001 that need structure without a full eQMS | Forms, routing and approvals match your procedure; connects inspections, maintenance and suppliers; quality teams can change it | Needs initial configuration; confirm regulatory requirements if you are in a validated environment |
Automating CAPA does not change the process; it makes sure the process actually runs. A practical rollout looks like this:
Quixy is a no-code platform that manufacturers use to build quality and operations workflows, including CAPA, as part of its manufacturing solution. Quality teams design the CAPA process themselves and change it as their procedure evolves.
Proof points:
If you operate in a regulated, validated environment with electronic signature requirements, confirm those requirements with any vendor you evaluate, including Quixy.
CAPA works best when it is connected to the processes that create and resolve quality issues. That is why manufacturers that start with CAPA usually extend to the rest of quality and operations:
| Process | How it connects to CAPA |
|---|---|
| Inspections and audits | Failed items and findings raise CAPAs with evidence attached |
| Maintenance | Equipment-related root causes create maintenance work orders and schedule changes |
| Supplier quality | Supplier-caused issues trigger supplier corrective action requests and scorecard updates |
| Document control and training | Updated SOPs trigger retraining tasks and acknowledgements |
| EHS incidents | Safety incidents and near misses follow the same root cause and action process |
| Task management | Every CAPA action becomes a tracked task with an owner and deadline; see task management system |
Run CAPA, inspections, maintenance and supplier quality on one platform.
Quixy’s manufacturing solution lets your quality and operations teams build connected workflows that match how your plant works. Explore Quixy for manufacturing or book a demo.
CAPA management is where quality problems either get solved or come back. A strong CAPA process separates correction from corrective action, finds real root causes, assigns owners with deadlines, proves effectiveness before closure and keeps the evidence auditors expect. With ISO 9001:2026 now published, it is a good moment to review your CAPA procedure and the system that runs it. If spreadsheets and email are letting CAPAs go overdue, a configurable CAPA workflow inside a connected manufacturing solution gives you structure without the weight of a full quality suite.
CAPA stands for Corrective and Preventive Action. It is a quality management process for finding and eliminating the causes of actual and potential problems.
In quality management, CAPA is the structured process of investigating a nonconformity, identifying its root cause, implementing actions to stop it recurring or occurring, and verifying that those actions worked.
Corrective action eliminates the root cause of a problem that has already happened. Preventive action eliminates the cause of a potential problem before it happens.
A correction fixes the immediate problem, such as reworking a defective batch. A corrective action removes the root cause so the problem does not recur.
Identify and log the issue, assess risk and contain it, investigate, find the root cause, plan corrective and preventive actions, implement them, verify effectiveness, and close and standardize.
Since the 2015 edition, ISO 9001 no longer has a separate preventive action clause. Prevention is addressed through risk-based thinking, while corrective action remains a requirement when nonconformities occur.
Agree a verification method and time period when the CAPA is planned, then check data such as defect rates, inspection results or complaints after implementation. Close the CAPA only if the problem has not recurred.
CAPA management software digitizes the CAPA process: logging issues, assigning owners, guiding root cause analysis, tracking actions with deadlines and escalations, scheduling effectiveness checks and keeping an audit trail.