CAPA (Corrective and Preventive Action) is the quality-system process that finds the root cause of a problem, removes it so it cannot recur, and stops similar problems from appearing elsewhere. This guide walks through the full process, the tools, the records, and the metrics, with worked examples from incoming and outgoing inspection (IQC/OQC).

★ Key Takeaway
All defect numbers in the worked example are illustrative, not real plant data. This is a training guide, not an approved company procedure. Version 1.1, revised 13 October 2026. Owner, reviewer, approver, and status: to be assigned.

1. What CAPA is and why it matters

Removing or repairing the defective part alone is not sufficient to constitute a CAPA. CAPA asks why the defect happened, changes the system that allowed it, and then proves the change worked. Three terms are often mixed up, so keep them apart:

TermQuestion it answersTriggered byIQC/OQC example
CorrectionHow do we fix this nonconforming item now?A detected nonconformitySort, rework, or reject the nonconforming units found in the 5,000-unit lot
Corrective actionWhy did it happen, and how do we stop it recurring?An existing nonconformityChange the supplier's packing method after finding the cause of transit damage
Preventive actionWhat could go wrong, and how do we stop it before it does?A potential nonconformity or trendReview similar materials for the same tool-wear mechanism and add tool-life control or automatic offset adjustment before the drift occurs

ISO 9000:2015 defines the last two by their target: corrective action eliminates the cause of a detected nonconformity, preventive action eliminates the cause of a potential one. ISO 9001:2015 no longer has a separate preventive action clause; it addresses this through risk-based planning (clause 6.1), not simply a renamed preventive action procedure. Medical device and pharmaceutical systems still keep CAPA as a named process. Extra inspection is a detection control; it is not automatically a preventive action.

Containment sits alongside correction but serves a different purpose. Containment is the immediate defensive shield: it stops the problem from spreading to stock, work in progress, and customers. Correction is the localized fix of the nonconforming items already found, such as sorting or reworking a lot. Start containment immediately and perform correction as soon as the disposition is authorized and safe to execute; neither removes the cause.

Standards that require CAPA

StandardClauseWhat it requires, in short
ISO 9001:201510.2 Nonconformity and corrective actionReact to the nonconformity, evaluate the need to remove the cause, implement action, review its effectiveness, update risks, keep documented evidence
ISO 13485:20168.5.2 Corrective action, 8.5.3 Preventive actionDocumented procedures; review nonconformities including complaints; determine causes; verify the action does not harm product safety; verify effectiveness
FDA Quality Management System Regulation (QMSR), 21 CFR Part 820Quality system requirements, including CAPAThe former 820.100 required analysis of quality data, cause investigation, action verification, information sharing and management review; these themes now come through ISO 13485. Effective 2 February 2026, the QMSR incorporates ISO 13485:2016 by reference together with FDA-specific provisions, and applies to manufacturers of finished medical devices for U.S. commercial distribution. Check the current regulation and FDA guidance for what applies to a given product
IATF 16949:201610.2.3 Problem solving, 10.2.4 Error-proofingA documented problem-solving process with a defined root-cause method, systemic corrective action and error-proofing
ICH Q103.2.2 CAPA systemA CAPA system as a core element of the pharmaceutical quality system, feeding management review

Check which of these your customers and certification bodies actually audit you against; the required level of documentation differs between a general ISO 9001 system and a regulated product line. Pharmaceutical and medical device expectations do not automatically apply to other industries.

2. The CAPA lifecycle

Every CAPA moves through the same eight stages. Effectiveness verification is a critical stage that is sometimes overlooked; it provides documented evidence that the actions achieved their intended results.

CAPA lifecycle: eight stages from identify and log to close and share, with a feedback loop from failed verification back to action planning
Figure 1: CAPA lifecycle · 8 stages, 1 feedback loop

A CAPA that fails its effectiveness check goes back to stage 4, not forward to closure. The timelines below are typical starting points; section 4 tightens them for high-risk problems.

StageOwnerKey outputTypical timeline
1. Identify and logQC OfficerCAPA number, problem statement with dataDay 0
2. ContainQC Officer with ProductionQuarantine record, sorted stock, quantitiesWithin 24 hours
3. Classify riskQA ManagerPriority level and due datesWithin 2 working days
4. InvestigateCross-functional teamRoot cause statement with evidence, plus the escape cause10 to 30 working days, by priority
5. Plan actionsCAPA ownerApproved action plan and effectiveness criteriaWithin 5 working days of root cause
6. ImplementAction ownersEvidence for every actionPer plan, usually 30 to 60 days
7. Verify resultsQC OfficerEffectiveness report with dataSet by failure frequency, volume and risk: several months, or a set number of lots
8. Close and shareQA ManagerClosure record and lessons learnedWithin 5 working days of a passed check

3. Triggers: when to open a CAPA

Open a CAPA when the cause of a problem sits in the system and could cause it again; fix locally when it is a contained one-off. A nonconformance report (NCR) records and dispositions the item; a CAPA fixes the reason it happened.

Where CAPAs come from

SourceTypical signalExample
Incoming inspection (IQC)Rejected lot, repeat defect from one supplierThird dimensional rejection from the same vendor in a quarter
In-process inspectionRising scrap or falling first-pass yieldYield on a line drops two points over three weeks
Outgoing inspection (OQC)Failed AQL lot, customer-critical defect found at shippingLabel error found on a packed export lot
Customer complaints and returnsRepeat complaint theme, any safety or regulatory complaintTwo customers report the same seam failure
Internal and external auditsMajor nonconformity, or repeated minor findingsCalibration records missing in two audits running
Process data (SPC)Out-of-control signal, falling CpkA predefined trend rule is triggered, such as seven consecutive rising points, where the charting procedure defines it
Supplier performancePoor quality score, repeated supplier corrective action requests (SCAR)Supplier ppm above target for three months
Equipment and calibrationInstrument found out of toleranceCaliper fails post-use check, so past measurements need review
Risk review and management reviewRisk rated high, or a trend across several areasFMEA score rises after a process change

Open a CAPA or fix locally?

Answer these in order. A single “yes” is enough to open a CAPA. The thresholds are examples; set your own in the CAPA procedure.

QuestionIf yes
Could it affect safety, regulatory compliance, or a customer-critical characteristic?Open a CAPA
Has it happened three or more times in six months, or in more than one lot?Open a CAPA
Could the same cause affect other products, lines, or suppliers?Open a CAPA with a preventive scope
Did a customer, auditor, or regulator ask for a formal response?Open a CAPA, or an 8D if the customer requires one
Is the cost of failure above your set threshold?Open a CAPA
None of the above, and the cause is clear and already removedCorrection plus an NCR record; trend it and review monthly

Watch the monthly NCR trend even for local fixes. Three apparently isolated NCRs with the same underlying cause may indicate that a CAPA should have been opened earlier.

4. Risk-based classification

Score every problem for severity and occurrence, then let the score set how fast the CAPA must move. Severity 5 always escalates as critical, regardless of occurrence.

5 by 5 risk matrix of severity against occurrence with scores from 1 to 25 grouped into Low, Medium, High and Critical bands
Figure 2: Risk matrix · severity 1 to 5 × occurrence 1 to 5, scores 1 to 25

This 5 × 5 matrix is a general risk assessment tool for triaging CAPAs at the inspection bench. It is not an FMEA score. AIAG/VDA FMEA uses 1 to 10 scales for severity, occurrence, and detection, and the 2019 handbook ranks risk by Action Priority instead of a multiplied RPN. Do not mix the two scales in one record; state which method a score came from. Priority comes from the defined bands; some integers, such as 7 or 11, cannot occur as products of two 1 to 5 scores.

PriorityScoreContainmentRoot cause dueActions complete byWho is told
Critical20 to 25, or any severity 5Within 24 hours10 working days45 daysTop management at once
High10 to 16Within 48 hours20 working days60 daysQA Manager and department heads
Medium5 to 9Within 5 working days30 working days90 daysQA Manager
Low1 to 4Correction, recorded through the nonconformity processIf a CAPA trigger from section 3 is met, open a CAPA regardless of the low scoreSet by risk, applicable requirements and company procedureLogged in the monthly NCR trend review

These response times are examples. Set yours in the CAPA procedure and keep them achievable; a target that is missed every month teaches people to ignore it. These dates cover containment, root cause, and implementation. Final closure is separate: close a CAPA only after all actions are done, and the effectiveness criterion in section 8 is met. If a CAPA runs past its target, record the justification, escalate, and keep interim controls in place; never close it just to meet a deadline.

5. Containment and investigation

Contain first, then investigate with data. Containment protects the customer today; it does not remove the cause.

Containment checklist

  • —Stop use or shipment of the suspect material and tag it with a hold label.
  • —Trace every affected lot: stock, work in progress, finished goods, and anything already at the customer.
  • —Where feasible and appropriate to the risk, sort or inspect 100% of suspect units against the failed characteristic, or use an approved alternative containment method, and record accepted, reworked and rejected counts.
  • —Tell production, purchasing, the supplier and, where needed, the customer.
  • —Add interim protection, such as tightened sampling, until the cause is removed.

Evidence to collect

WhatQuestionExamples of evidence
ProductWhich items, and how many?Lot and batch numbers, quantities, photos, failed samples
ProcessWhat was running?Machine, tool, settings, shift, operator, date and time
MeasurementCan the measurement be trusted?Gauge ID, calibration status, repeatability check
Change historyWhat changed recently?Drawing revisions, material or supplier changes, maintenance
HistoryHas it happened before?Past NCRs, earlier CAPAs, audit findings

Worked example: find the vital few

Across lots L-1041 to L-1049, IQC sampled 1,200 units and recorded 100 defects, one per defective unit (so 100 rejected units). A Pareto chart ranks defect types by count so the team investigates what matters most first. The numbers here are illustrative.

Pareto chart of 100 IQC rejects across 6 defect types, with width tolerance the largest at 46
Figure 3: Pareto chart · 100 IQC rejects in 6 defect types, illustrative data

Width tolerance alone is 46 of the 100 defects, so it becomes the CAPA focus. Scratches and labeling are real but smaller; handle them with routine corrections or separate CAPAs if they grow.

6. Root cause analysis

Root cause analysis separates the visible symptom from the system cause. Stop only when you reach a cause you can fix and prove with evidence.

Choose the tool for the problem

ToolBest forStrengthWatch out for
5 WhysOne clear chain of cause, simple problemsFast, no software, easy to teachStops early; needs evidence at every why
Fishbone (Ishikawa)Many possible causes, team brainstormSorts ideas into Method, Machine, Material, People, Measurement, EnvironmentLists candidates, not proof
Is / Is-Not analysisNarrowing down where, when, and how muchCompares what is affected with what is notNeeds data on both sides
Pareto analysisDeciding which defect or cause matters mostRanks by count or costShows size, not cause
FMEAPreventive work on new or changed processesIdentifies failure modes, effects, and causes and prioritizes actions by the applicable FMEA method; feeds the control planScores are subjective; revisit after real failures
Fault tree analysisSafety-critical or multi-path failuresShows how combinations of events lead to failureSlow and needs experience
8DCustomer or supplier problems that need a standard reportFixed format with team, containment and verificationBecomes paperwork if the root cause is weak

Brainstorm with a fishbone

Use a fishbone diagram to organize potential causes when several explanations need to be considered. Put the problem at the head, list candidate causes under the six categories, then test each one with data. Below is the worked example from the previous section; the causes are illustrative candidates.

Fishbone diagram with six cause categories and 18 candidate causes, of which one — the control plan gap — was confirmed
Figure 4: Fishbone diagram · 6 categories, 18 candidate causes, 1 confirmed, illustrative

Only the control plan gap was confirmed by evidence in this example. The rest stayed on the list until data ruled them out.

Confirm with 5 Whys and evidence

Take the confirmed branch and ask why until you reach a cause in the system. Write the evidence next to each answer.

  • —Why 1 — Why was the width above the limit? It drifted upward during each production run. Evidence: IQC measurements rise with piece sequence in every lot.
  • —Why 2 — Why did it drift? The cutting tool wore, and no one adjusted the offset. Evidence: tool wear measurements correlated with part width, plus the supplier's tool-life and offset records, which show changes on a fixed time interval only.
  • —Why 3 — Why was the offset not adjusted? The control plan had a first-article check and no in-process width check. Evidence: the supplier control plan, issued before the drawing change.
  • —Why 4 — Why did the control plan lack a width check? It was written for the old tolerance of ±0.10 mm, where wear stayed inside the limit. Evidence: old and new drawing revisions.
  • —Why 5 — Why was the plan not updated? Our drawing change tightened the tolerance to ±0.05 mm, but no step made the supplier acknowledge it and review its controls. Evidence: change records show no supplier acknowledgment.
★ Key Takeaway
Root cause statement (confirmed only when every step above has supporting evidence; otherwise treat it as a hypothesis): the supplier's control plan was not reviewed after the width tolerance was tightened from ±0.10 mm to ±0.05 mm, because our change process has no drawing-revision acknowledgment step, which allowed tool wear to push width out of tolerance.

Escape cause, to be investigated: whether the sampling plan suited this failure mode, whether trend rules existed, and whether IQC's measurement data could show the drift. In this example, no rule opened a CAPA on a rising trend for one characteristic. AQL sampling is not faulty just because a lot contains defects.

Test your root cause

  • —If you remove this cause, would the problem stop? If not, it is a contributing factor.
  • —Can you show evidence, such as data, records, or a trial, and not only an opinion?
  • —Does the chain read correctly backwards, with “therefore” between each step?
  • —Does it point to a system condition you can change, and not to a person to blame?

7. Action planning and implementation

Prefer actions that eliminate the cause or make the failure difficult or impossible, and validate the chosen control; the weakest actions rely on people remembering. Treat the ladder as a preference order, not a universal ranking, because some problems need several actions together. Rank every proposed action on this ladder and prefer the top rows.

StrengthAction typeIQC/OQC example
StrongestEliminate the failure mechanism or its source where feasibleRedesign the feature or process so the failure mechanism no longer exists, with engineering and customer approval
StrongError-proof (poka-yoke) or use a more robust processFixture that only accepts the part in the correct orientation
MediumEngineering control or automationAutomatic gauge with accept/reject signal on the incoming inspection bench
WeakDetectionExtra inspection step or tighter sampling plan
WeakestAdministrativeReminder, procedure rewrite, or retraining alone

Retraining alone is rarely an acceptable corrective action for a system cause. It is fine as a support for a stronger action. Never relax a specification just to suit a supplier's difficulty; any specification change needs engineering and customer justification and formal change control.

Build a SMART action plan

Every action needs one named owner, a due date counted from CAPA approval, and evidence that it was done. The plan below belongs to the worked example used in this guide: a supplier delivering parts with the width out of tolerance after a drawing revision. All figures are illustrative.

#ActionTypeOwnerDueEvidence of completion
1Sort stock and WIP from affected lots with 100% gauge checkCorrectionQC OfficerDay 1Sort record, rejected quantity
2Move the characteristic to tightened IQC sampling until 5 consecutive lots pass (an example exit rule, valid only if justified by risk and approved; it does not replace the effectiveness check)Interim controlQC SupervisorDay 1Updated inspection plan
3Supplier revises control plan, adds SPC on width and tool-wear offsetCorrectiveSupplier QualityDay 14Revised control plan, first SPC chart
4Train IQC inspectors on the new tolerance and gaugeCorrective (support)QC SupervisorDay 21Signed training record
5Add a drawing-revision notice with supplier acknowledgment to the change procedureCorrective (systemic)Engineering and PurchasingDay 30Procedure revision, acknowledgment log
6Review every supplier drawing revised in the last 12 months for the same gapPreventivePurchasing and QCDay 45Review log, list of gaps found

Implement under change control

  • —Route any change to a procedure, drawing, specification, or inspection plan through your document and change control process, not through the CAPA form alone.
  • —Check that the action does not create a new risk or break a requirement. ISO 13485 asks for this verification explicitly.
  • —Collect the evidence for each action as it closes, not at the end.
  • —Update the FMEA, control plan, and inspection plan so the lesson stays in the system.
  • —Tell every affected team, shift, and supplier. A fix that lives on one line or one shift is a partial fix.

8. Verifying effectiveness

A CAPA is effective only if the problem stays away. Verify it with data, against criteria you set before the actions were implemented.

Pick a method that fits the cause

MethodUse whenExample criterion
Trend monitoringRecurring defects or supplier quality problemsRejection rate at or below 1.0% for 3 consecutive months
Lot-based checkLow or uneven production volume10 consecutive lots accepted at normal inspection
Follow-up audit or re-inspectionProcedure or system changesThe new step found in every sampled record
Process capability studyDimensional or process-control causesCpk of 1.33 or higher on the characteristic; confirm the level your customer requires, and use it only for a stable process with a capable measurement system
Complaint trendComplaint-driven CAPAsNo repeat complaint of the same type in 6 months

Write the criterion down at plan approval: the metric, the target, the monitoring period, who checks and by when. The period must be long enough to see the problem if it still exists, usually meaning several expected occurrences. Count lots, not calendar months: if a supplier ships once every two months, a 3-month window sees only one or two lots, which cannot prove effectiveness. For low-frequency or seasonal problems, set the criterion in lots or cycles (for example, 5 consecutive lots) and cover at least one full season.

Worked example: before and after

The worked CAPA used trend monitoring on the share of IQC lots rejected for width (lots rejected for width ÷ lots inspected that month). The target was 1.0% or lower, held for 3 consecutive months.

Line chart of the monthly IQC width rejection rate over 12 months, falling below the 1.0% target after the corrective actions
Figure 5: Before and after trend · 12 months of IQC width rejection rate, illustrative data

The effectiveness criterion was satisfied in month 6; the CAPA may close once all other closure requirements and QA approval are confirmed. Passing five consecutive lots earlier ended the interim tightened sampling only; it does not prove the root cause is gone. Month 3 sat just above target and did not count toward the three.

Closure criteria

  • —Every action is complete, and its evidence is attached.
  • —The effectiveness criterion is met, with the data in the record.
  • —The actions caused no new risk, and affected documents and training records are updated.
  • —QA approves closure.
  • —If the check fails, reopen the investigation with a new root cause hypothesis. Extending the monitoring period without new action does not fix anything.

9. Documentation, the CAPA form and responsibilities

A CAPA without adequate documented evidence cannot be demonstrated in an audit. One form, one number, and one owner per CAPA keep the record complete.

CAPA form: field by field

SectionFieldsWhat to write
1. HeaderCAPA number, date opened, source reference, product or supplier, initiator, CAPA ownerLink to the NCR, audit finding, complaint, or lot number that started it
2. Problem descriptionWhat, where, when, how many, how detected, evidenceFacts and measurements, with photos and lot numbers; no causes or blame yet
3. Risk classificationMethod, severity (1 to 5), occurrence (1 to 5), risk score, priority levelScores with the reason for each, using the internal severity × occurrence matrix in section 4; record detectability, if you assess it, as a separate note
4. ContainmentActions taken, quantity affected, disposition, dateWhere the suspect product is, and who checked it
5. Root causeMethod used, root cause statement, evidence, escape causeWhy it happened, and why it was not caught earlier
6. Action planActions, type, owner, due dateThe SMART table from section 7
7. Effectiveness checkMetric, criterion, monitoring period, checker, dateDefined before implementation, not after
8. ApprovalNames, roles, datesQA approval of the permanent-action plan before implementation; urgent containment starts immediately under authorized procedures
9. ClosureEvidence reviewed, result, closure date, lessons learnedAttach the data that proves the result

A good problem statement is specific and measurable. Compare “Supplier parts are bad” with “46 of 1,200 inspected units (3.83%) in lots L-1041 to L-1049 exceeded the upper width limit of 12.05 mm at IQC between weeks 31 and 38 (illustrative).” A good root cause statement follows the pattern: cause, because of the condition, which allowed the effect.

Records and traceability

  • —Link the CAPA to every related NCR, lot, supplier file, audit finding, and changed document.
  • —Keep the evidence (photos, measurement data, training records, revised procedures) with the CAPA record.
  • —Retain records for the period set by your quality manual, customer contracts, and any regulator.
  • —Give each CAPA one status at all times: open, in investigation, in implementation, in effectiveness check, or closed.

Who does what

R = responsible for doing, A = accountable for the outcome, C = consulted, I = informed.

ActivityQC OfficerQA ManagerProcess or Engineering ownerPurchasing or Supplier QualityTop management
Identify, log, containRACI—
Classify risk and approve startCA/RCCI
Investigate root causeRARCI
Plan and implement actionsCARRI
Verify effectivenessRACCI
Approve closureIA/RIII
Review CAPA trends in management reviewCRCCA

10. Metrics and KPIs

Measure the CAPA system itself, not only the defects it fixes. Late closures, failed effectiveness checks and repeat issues show where the process is weak.

KPIFormulaExample targetWhat it tells you
On-time closure rateCAPAs closed by due date ÷ CAPAs due in period × 10090% or higherWhether plans are realistic and owners are engaged
Overdue CAPAsCount of open CAPAs past due date, split by priority0 criticalWhere the backlog is hurting risk
Average time to action implementationSum of (date last action completed − open date) ÷ CAPAs with actions complete; effectiveness monitoring excluded60 days or less across all prioritiesSpeed of investigation and implementation
First-time effectiveness rateCAPAs that passed the effectiveness check first time ÷ CAPAs checked × 10085% or higherQuality of root cause analysis
Recurrence rateEligible CAPAs with at least one confirmed recurrence of the same underlying root cause during the 12-month follow-up ÷ CAPAs in the eligible cohort that completed the full 12 months × 1005% or lessWhether CAPAs really remove causes
Retraining-only shareCAPAs whose only action is training or a reminder ÷ all CAPAs × 10010% or lessOver-reliance on weak actions
Aged CAPAsCount of CAPAs open more than 90 daysTrending to zeroStuck investigations
Supplier SCAR on-time responseSCARs answered by the due date ÷ SCARs issued × 10090% or higherSupplier engagement

Define every KPI by period, numerator, denominator, inclusions, and rounding. On-time closure counts CAPAs whose due date fell in the quarter, first-time effectiveness counts only the first check, and recurrence is a trailing 12-month figure. Example quarterly scorecard (illustrative numbers; 24 CAPAs opened and 21 closed during the quarter; 21 CAPAs were due in the quarter; 18 were checked for effectiveness):

KPITargetResultStatus
On-time closure rate90% or higher86% (18 of the 21 CAPAs due were closed on time)Missed
Overdue critical CAPAs00Met
Average time to action implementation60 days or less47 daysMet
First-time effectiveness rate85% or higher83% (15 of 18)Missed
Recurrence rate (trailing 12 months)5% or less2.5% (1 of 40 CAPAs with a full 12-month follow-up)Met

Two misses with healthy cycle times point to rushed investigations: closing fast, then failing the check. Review the root cause quality of the three failed CAPAs.

Recurrence rate: counting rules

The recurrence rate measures how often a problem returns because the same underlying root cause recurs. Apply these rules every period:

  • —Include only CAPAs whose full 12-month follow-up period is complete.
  • —Count each eligible CAPA once in the numerator, even if the issue recurs several times.
  • —Count a recurrence only when evidence confirms the same underlying root cause; a similar-looking defect does not count without that support.
  • —Use the same eligibility rules in every reporting period.

In the illustrative example, 40 CAPAs completed the follow-up and 1 had a confirmed recurrence, so the rate is 1 ÷ 40 × 100 = 2.5%.

Review rhythm

  • —Weekly: a short CAPA board covering every open item, owner and due date.
  • —Monthly: QA reviews the KPIs above and the aged list.
  • —Quarterly or per your schedule: management review of CAPA trends, repeat themes and resource needs. Regulated systems expect CAPA data as an input to management review.
  • —Yearly: review whether the CAPA procedure itself is effective, using the KPIs as evidence.

11. Common pitfalls and best practices

Most weak CAPAs fail in the same few ways, and auditors look for exactly these. Check your own CAPAs against the list.

PitfallWhy it failsBetter practice
Stopping at “operator error”Human error is a symptom; something in the system allowed itAsk why the instructions, tools, layout, or workload made the error possible
Retraining as the only actionTraining fades and does not change the processPair it with error-proofing, a control, or a procedure change
Vague problem statementNothing to measure, so effectiveness cannot be shownState what, where, when, how many, with data
Closing when actions are doneDone is not the same as effectiveClose only after the effectiveness check passes
Setting effectiveness criteria afterwardsCriteria drift to fit the resultAgree metric, target and period at plan approval
Ignoring the escape causeThe same gap lets the next defect throughAsk why inspection did not catch it, and fix that too
Containment onlyThe problem returns when the sorting stopsContainment is step one, never the whole CAPA
Opening a CAPA for every minor defectThe backlog hides the serious onesUse the risk-based triggers in section 3
Accepting supplier responses without evidenceA paper promise is not a changed processAsk for the revised control plan, data, and audit proof
Forgetting related documentsThe FMEA and control plan still describe the old processUpdate every risk and control document the change affects

Supplier corrective action requests (SCAR)

IQC findings often lead to a SCAR. Agree the response times in the supplier quality agreement; the schedule below is a common starting point, not a standard.

StageTypical expectation
Acknowledge the SCARWithin 1 working day
Containment and sorting of stock at supplierWithin 24 hours of notice
Root cause with evidence5 to 10 working days
Corrective action plan with datesWithin 30 days
Effectiveness evidence from the supplierAgreed monitoring period, then QC verifies at IQC

Habits that make CAPA work

  • —Write the problem statement before discussing causes.
  • —Go to the place, look at the part and talk to the people; do not investigate from the office alone.
  • —Ask for data at every why. A cause without evidence is a guess.
  • —Use a small cross-functional team for any CAPA that crosses departments.
  • —Share the lesson across shifts, lines, and sites after closure.
★ Key Takeaway
Rule of thumb for human error: if the action plan only tells someone to be more careful, or retrains them on an existing procedure, without changing the tooling, environment, or documentation, it is not a systemic corrective action.

When the effectiveness check fails

A failed check is information, not a failure of the process. Reopen at investigation, test a new hypothesis against the data, record why the first cause was incomplete, and replace or add actions. Do not just extend the monitoring period.

An NCR records and dispositions a nonconforming item. A SCAR asks a supplier to find and fix its own cause. A CAPA owns the whole investigation and can spawn one or more SCARs. Cross-reference all three records by number, and issue a SCAR when the confirmed cause is within the supplier's process or quality system.

Product impact and measurement reliability

Before root-cause work, assess the impact on shipped product, customer operations, safety, and regulatory compliance, and decide whether a recall or field action is needed. For dimensional problems, check the measurement system first: calibration, gauge resolution, repeatability, and reproducibility.

Escalation authority

Name in the procedure who can place material on hold, approve disposition, notify customers, and approve a risk-based deviation from standard timelines. Without clearly assigned authority, containment may be delayed while responsibilities are clarified.

12. Quick-reference checklist, glossary and references

CAPA checklist

DoneCheck
☐Problem described with facts: what, where, when, how many, evidence attached
☐Containment done and recorded; suspect stock located and dispositioned
☐Risk classified and priority set; due dates agreed
☐Root cause found with a named method and supported by evidence
☐Escape cause (why it was not detected) identified
☐Actions ranked on the strength ladder; owners and due dates set
☐Related documents updated: FMEA, control plan, inspection plan, procedures
☐Effectiveness metric, target and period defined before implementation
☐Effectiveness check run and the data attached
☐QA approval for closure; lesson shared with affected teams

Glossary

TermMeaning
5W2HWho, what, where, when, why, how, how many: a problem-description frame
8DEight-discipline team problem-solving format common in automotive supply chains
AQLAcceptance quality limit, a parameter of acceptance sampling; the sampling plan sets sample size and accept/reject criteria
CAPACorrective and preventive action
CpkA process capability index comparing process mean and variability with specification limits, subject to the method's assumptions
Escape causeThe reason a defect was not caught by inspection or controls (a practical term used in this guide)
FMEAFailure mode and effects analysis, a risk-scoring method
IQC / OQCIncoming/outgoing quality control
NCRNonconformance report
ppmDefective parts per million
RPNRisk priority number: severity × occurrence × detection, using the scales of the FMEA method in use (classic scales run 1 to 10)
SCARSupplier corrective action request
SPCStatistical process control

References

These are standards and regulations named from general knowledge, not fetched for this guide. Confirm clause numbers and current editions before citing them in a procedure or audit response. Authoritative sources: iso.org (ISO standards), fda.gov (QMSR), ich.org (ICH Q10), and iatfglobaloversight.org (IATF 16949). For audits, use the controlled editions and customer-specific requirements.

  • —ISO 9001:2015, Quality management systems: Requirements, clause 10.2
  • —ISO 9000:2015, Quality management systems: Fundamentals and vocabulary
  • —ISO 13485:2016, Medical devices: Quality management systems, clauses 8.5.2 and 8.5.3
  • —FDA Quality Management System Regulation (21 CFR Part 820), effective 2 February 2026
  • —IATF 16949:2016, clauses 10.2.3 and 10.2.4
  • —ICH Q10, Pharmaceutical Quality System, section 3.2.2
  • —AIAG and VDA FMEA Handbook (2019) for FMEA scoring