CAPA for customer complaints

What CAPA means

CAPA stands for Corrective and Preventive Action — the quality-system process for reacting to a problem in a way that both eliminates its cause and stops it happening elsewhere. In complaint handling, CAPA is what turns "we replaced the part and apologised" into "we found why it failed, removed that cause, checked everywhere else the same weakness could exist, and confirmed the fix worked." It is the mechanism that converts individual complaints into permanent organisational improvement.

CAPA is a formal requirement in every serious quality standard — ISO 9001, ISO 13485 for medical devices, IATF 16949 for automotive, and the FDA's regulations for regulated industries. But you do not need to be regulated to benefit: any organisation that handles customer complaints and wants them to stop recurring is doing CAPA, whether it uses the word or not.

Correction vs corrective vs preventive action

The most common — and most expensive — confusion in the whole field is treating these three as synonyms. They are three different actions with three different purposes, and a CAPA that stops at the first one has fixed nothing.

Read it once and the distinction sticks: correction deals with the thing in front of you, corrective action deals with the cause of a problem that did happen, and preventive action deals with the cause of a problem that could happen. In modern practice — and in the current ISO 9001, which folded much of "preventive action" into risk-based thinking — the honest way to see it is that horizontally deploying a proven corrective action to similar products is the preventive action for those products. The clarifying question to ask on every complaint is simply: "We fixed this one — where else could the same cause be waiting?"

The CAPA process, step by step

Effectiveness verification — the step that gets skipped

The difference between a CAPA system that improves quality and one that generates paperwork is effectiveness verification. Implementing an action is not evidence it worked; a CAPA is only genuinely closed when you can show, with data, that the nonconformity has not recurred over a meaningful window. That means defining upfront what success looks like — zero recurrences over the next N lots, a defect rate back below target, no repeat complaints from the customer for a set period — and then checking against it before closure. ISO 9001 makes this explicit: clause 10.2 requires you to review the effectiveness of any corrective action taken. Skipping verification is how organisations accumulate a fat CAPA log and a defect rate that never moves: the actions are "done", but nobody confirmed they did anything.

CAPA and ISO 9001 clause 10.2

For a certified organisation, complaint-driven CAPA is the core of the standard's improvement requirement. Clause 8.7 requires control of nonconforming outputs — identify, contain and disposition bad product, and keep records. Clause 10.2 requires that when a nonconformity occurs, including a customer complaint, you react to it, evaluate the need to eliminate the cause so it does not recur, implement action, review its effectiveness, and retain documented information as evidence of both the action and the result. An auditor's standard move is "show me a complaint and walk me through the corrective action and how you verified it worked." A structured CAPA answers in minutes; an email thread and a replaced part do not. The same discipline underpins ISO 13485 and IATF 16949, where CAPA and the 8D report are frequently the customer-facing deliverable.

Common CAPA mistakes

Four failures recur across almost every weak CAPA system. Correction mistaken for corrective action — the replaced part is logged as the fix and the cause is never touched. Symptom mistaken for root cause — "operator error" recorded as a cause when the real cause is a process that permitted the error; a proper root-cause analysis prevents this. No effectiveness check — actions closed on completion rather than on proven result. And CAPA overload — raising a full CAPA on every trivial issue until the backlog is so large that the serious ones drown; risk-grading at step 3 is the antidote. Avoid these four and a CAPA system starts to visibly bend the defect trend downward.

How Fast Complaint Software runs CAPA

Fast Complaint Software, built by Improsys on the Fast Suite platform, makes the correction / corrective / preventive distinction operational. A complaint captured as a numbered ticket records the immediate correction as an action, then escalates into the structured 8D and CAPA workflow for the real work: fishbone and cause categorisation for the root cause, a Problem Solving Report for the narrative, a Past Trouble Database of proven countermeasures, Horizontal Deployment as the preventive spread, and a Change Request to formalise a permanent process or design change. Closure is gated by a supervisor's Release Complaint verification — the handler cannot self-close — which is where effectiveness is confirmed, and every step is retained as the audit trail an ISO 9001 clause 10.2 assessor expects. Overdue actions surface through SLA follow-up and escalation, and the post-resolution rating feeds the Customer Satisfaction Index so you can see whether the corrective action rebuilt the relationship, not just the product.

Frequently asked questions