Clause 10 is where a QMS proves whether it can learn. It covers the reactive side of improvement through nonconformity and corrective action, and the proactive side of improvement through continual improvement. Organizations that only react to failures may satisfy the surface of Clause 10.2 while still failing Clause 10.3.
This guide treats Clause 10 as a system discipline, not just a CAPA form. The critical distinction is between fixing the symptom and changing the system condition that caused it. That distinction determines whether the same problem will come back under a new tracking number.
Visual Summary
Use the Clause 10 visual to anchor the reactive-versus-proactive distinction, corrective-action expectations, verification discipline, and methodology integration.
Jump to Guide Sections
1. Why Clause 10 Is the Master Loop of Improvement
Clause 10 closes the QMS loop. When something fails, it requires containment, cause analysis, corrective action, and verification that the failure will not recur. When nothing has failed yet, it still requires the organization to pursue improvement opportunities proactively so the system keeps evolving.
Reactive Dimension
Clause 10.2 responds to actual failures: complaints, NCRs, audit findings, supplier escapes, or process alerts.
Proactive Dimension
Clause 10.3 seeks opportunity before failure: better controls, stronger capability, higher objectives, and a visible improvement pipeline.
2. Clause 10.2: Nonconformity and Corrective Action
Clause 10.2.1 contains six required actions. Precision here matters because many CAPA systems do some of these steps and call the work complete before the root cause has been addressed.
| Required Action | What It Means | What It Does Not Mean |
|---|---|---|
| React, control, and correct | Contain the nonconforming output, stop further loss, isolate affected product, and correct the specific instance. | Calling the immediate fix a complete corrective action. |
| Deal with consequences | Look downstream and upstream for what else has been affected by the nonconformity. | Ignoring product in transit, at customer sites, or already processed downstream. |
| Evaluate need for corrective action and determine cause | Decide whether formal CAPA is warranted and, when it is, determine the cause through structured analysis. | Assuming a cause without evidence or opening a CAR without deciding what problem scale justifies it. |
| Implement needed actions | Change the system condition that allowed the problem to occur. | Only retraining people when the underlying procedure, verification, or process design is still weak. |
| Review effectiveness | Verify after an observation period that the corrective action prevented recurrence and changed the relevant conditions. | Closing the record the day the action was implemented. |
| Update risks and the QMS if necessary | Carry the learning into the risk register, procedures, controls, and documented information. | Leaving the lesson trapped inside a single closed CAPA record. |
3. Correction vs. Corrective Action
This is the most important distinction in Clause 10. A correction fixes the specific nonconforming instance. A corrective action changes the system so the same failure does not recur.
| Correction | Corrective Action |
|---|---|
| Addresses the immediate nonconforming instance. | Addresses the systemic cause that produced the nonconforming instance. |
| Happens immediately after detection. | Happens after analysis and may take days, weeks, or months. |
| Examples: rework the part, scrap the batch, replace the broken gage, retrain the employee involved in the event. | Examples: revise the setup verification process, add poka-yoke, update procedure controls, change supplier controls, redesign release checks. |
| Evidence: NCR record showing what happened to the affected output. | Evidence: CAR record showing root cause, system-level action, implementation, and effectiveness verification. |
4. Root Cause Analysis Methods and Method Selection
Root cause analysis quality determines corrective action quality. The point is not to use the most elaborate tool every time. The point is to select a method that matches the problem structure.
| Method | Best Used When | Why It Fits |
|---|---|---|
| 5-Why | The problem likely has a mostly linear cause chain and speed matters. | It is quick, practical, and effective when one dominant cause is expected. |
| Fishbone | The problem may have multiple interacting causes across methods, materials, machines, people, or environment. | It helps teams generate structured hypotheses before narrowing them through evidence. |
| Is / Is Not | The problem has distinctive patterns by machine, shift, operator, material, location, or time. | It helps isolate what is unique about failing conditions versus normal conditions. |
| DMAIC project | The problem is chronic, costly, multi-factor, and statistically complex. | It provides deeper data collection, analysis, solution validation, and control planning. |
5. Effectiveness Verification
Effectiveness verification is the step that proves the system changed, not just the paperwork. It must include a defined observation period, a specific verification method, and a positive record of what evidence confirmed the result.
Required Elements
- A verification period long enough for recurrence to show itself if the cause still exists.
- An active verification method: observation, audit, data review, or targeted follow-up.
- A record of the specific evidence examined and why it proves the action worked.
Weak Verification Signals
- “Action complete” with no observation period.
- “No recurrence observed” with no confirmation of changed system conditions.
- Closure based only on paperwork implementation rather than operational evidence.
6. When Every Nonconformance Does Not Need a Full CAPA
Clause 10.2 requires the organization to evaluate the need for action to eliminate the cause. That evaluation is mandatory. A legitimate conclusion may be that a formal CAPA is not required, but the rationale has to be documented.
| CAPA Usually Required | CAPA May Not Be Required |
|---|---|
| Repeat events or clear recurrence risk. | Truly isolated low-impact events with no systemic pattern. |
| Customer escapes, safety risk, regulatory risk, or high business impact. | Events already addressed through a broader improvement effort in progress. |
| Systemic conditions that could produce the same outcome elsewhere. | A documented rationale showing why formal CAPA is unnecessary. |
7. Clause 10.3: Continual Improvement
Clause 10.3 is shorter than Clause 10.2 but broader in implication. It requires the organization to continually improve the suitability, adequacy, and effectiveness of the QMS by considering the results of analysis and evaluation and the outputs of management review.
| Improvement Dimension | What It Means | Typical Trigger |
|---|---|---|
| Suitability | Keeping the QMS appropriate for the organization’s current context, customer base, and operating reality. | New markets, regulatory change, growth, product mix shift, new customers. |
| Adequacy | Ensuring the QMS has enough resources, controls, and capability to achieve intended results consistently. | Capacity constraints, weak supplier controls, training gaps, measurement bottlenecks. |
| Effectiveness | Improving how well the QMS achieves conforming outputs, satisfied customers, and better process results. | Weak objective performance, shallow audits, poor CAPA rigor, stagnant metrics. |
8. Sources of Improvement Opportunity
Proactive improvement opportunities should not depend on a single source. The strongest systems pull them from across the QMS so opportunity identification is continuous instead of accidental.
Operational Sources
- Internal audit findings and observations.
- Quality objective trend analysis.
- CAPA cycle time and effectiveness data.
- Customer feedback and perception shifts.
Strategic Sources
- Management review outputs.
- Risk and opportunity register items.
- Benchmarking and industry references.
- Employee improvement suggestions.
9. Integration with Lean Kaizen and Six Sigma DMAIC
Clause 10 aligns naturally with both Lean Kaizen and Six Sigma DMAIC. The methodologies differ in depth and pace, but they solve the same problem: how to improve system performance deliberately rather than hoping it improves on its own.
| Clause 10 Element | Lean Kaizen Equivalent | Six Sigma DMAIC Equivalent |
|---|---|---|
| Identify nonconformity | Genchi Genbutsu and direct observation at the gemba. | Define phase and problem framing. |
| Contain and correct | Immediate Kaizen or emergency response. | Define / Measure transition to protect the customer while analysis begins. |
| Determine root cause | 5-Why, Fishbone, A3, process observation. | Measure and Analyze phases with data-driven cause isolation. |
| Implement action | Kaizen event, standard work revision, error-proofing. | Improve phase with validated solution deployment. |
| Verify effectiveness and sustain | Sustain discipline in standard work and daily management. | Control phase with monitoring and response planning. |
10. Building the Improvement Pipeline
A mature Clause 10.3 system maintains a visible improvement pipeline so improvement is not episodic. The pipeline should be managed in three horizons: active projects, backlog, and idea collection. When employee ideas disappear into a void, the improvement culture collapses.
Pipeline Structure
- Active: resourced projects in execution with owners and milestones.
- Backlog: approved opportunities waiting for capacity.
- Idea Collection: frontline suggestions reviewed, dispositioned, and fed back to submitters.
High-Value Practice
Use an A3 format for CAPA and improvement work when practical. It naturally captures the problem statement, current condition, root cause logic, countermeasures, implementation plan, results, and lessons learned in one disciplined structure.
11. Quick Reference
Clause 10 Audit Readiness
- CAPA is triggered from all appropriate sources, including complaints, audits, NCRs, supplier failures, and monitoring alerts.
- Correction and corrective action are documented separately.
- Root causes are systemic and supported by evidence.
- Effectiveness verification is active, delayed long enough to matter, and evidence-based.
- Risk registers and QMS documents are updated when corrective actions change the system.
- Proactive improvement opportunities are visible and managed, not just reactive CAPA records.
Common Clause 10 Findings
- Shallow root cause analysis that stops at “operator error.”
- Corrective actions that address symptoms instead of causes.
- Missing or passive effectiveness verification.
- Customer complaints handled by rework without CAPA.
- No evidence of proactive improvement beyond reaction to failures.
- Management review improvement actions assigned but not tracked to completion.
Series Completion and Next Direction
Previous Guide
Guide 2.6: Performance Evaluation covers the intelligence and review disciplines that should trigger both corrective action and proactive improvement.
Volume 2 Complete
Guide 2.7 closes the clause-by-clause ISO 9001 series for Clauses 4 through 10. The next layer in the hub is the ready-to-use template track, which will turn the implementation and clause guides into deployable working records.