CAPA software that links every action to the record behind it
Corrective and Preventive Action is the most cited area in FDA Form 483 observations, year after year, because companies cannot show what they did about the problems they found.
Watch it explained
Ten minutes on why CAPAs fail at audit
The short version
Regulators expect problems. They want to see that you found them, fixed them, and proved you did
Every regulated company has nonconformities, and regulators know it. But CAPA still draws findings year after year. The failure is almost always the inability to show the investigation, the reasoning, the action, and the evidence that the action worked. So what makes a CAPA defensible is whether the record still connects to everything around it months later, when somebody asks.
Where CAPA comes apart
The complaint is in one system, the investigation in a document, and the procedure change in a third
A CAPA starts with a signal: a complaint, an audit finding, a supplier nonconformity, a deviation, an out-of-spec result, or a trend somebody noticed in the data.
In most companies that signal lives in one place, and the investigation gets written in a document somewhere else. The action lands in a project tracker, and the procedure that finally changed sits in a different system again. Each step is done properly. The links between them exist only in somebody’s memory. Months later an investigator asks how you knew the action worked, and the answer has to be reassembled from four places by whoever is still there.
When the CAPA and the records around it are the same system, that reassembly never has to happen. The finding, the investigation, the action, the effectiveness check, and the procedure it changed are one connected object.
What it looked like at one company
Years of audit findings, then zero findings every year
Irrimax Corporation came to Melita’s team tangled in audit findings, with years of CAPAs from those audits and its MDSAP certificate at risk. Six weeks after go-live it had a full quality system and a new auditing organization, and it has had zero findings at every audit since.
“We also had multiple CAPAs which needed to be addressed coming out of an internal audit gone astray. Melita and her team helped me institute and customize a new validated QMS software along with new procedures, work instructions and forms which simultaneously addressed all the CAPAs and achieved the paperless QMS goal.”
What runs here
CAPA software covering identification, investigation, action, and effectiveness checks
The eight stages from her CAPA guide, running against live records instead of in a separate document.
Identification
Triggering signal captured with its source record, so a CAPA always points back at the complaint, audit finding, or deviation that raised it.
Evaluation
The documented decision about whether this warrants a CAPA at all, with risk and systemic impact recorded. Opening a CAPA for every minor issue is one of the fastest ways to drown a quality team.
Investigation and root cause
The reasoning is written on the record itself, where an investigator can read it in context.
Action, implementation, and effectiveness
Actions link to the procedures and documents they change, and effectiveness checks link back to the original signal.
Closure and trending
Closed CAPAs stay connected to the data they came from, so trending is a view of live records rather than an export.
Common questions
Common questions about CAPA
What is the difference between corrective and preventive action?
Corrective action eliminates the cause of a nonconformity that has already been detected, so it does not happen again. Preventive action eliminates the cause of a potential nonconformity that has not occurred yet. Both live under the same process, and regulators expect to see evidence of both.
Does every complaint or deviation need a CAPA?
No, and treating it that way causes its own problems. Complaints, deviations, and out-of-spec results have their own processes. CAPA is reserved for issues significant enough by severity, frequency, or trend to warrant root cause analysis and a systemic change. The documented decision about which route an issue takes is itself part of a defensible process.
Which regulations govern CAPA?
ISO 13485 clauses 8.5.2 and 8.5.3, which the FDA’s Quality Management System Regulation has incorporated by reference since February 2026. The former 21 CFR 820.100 no longer stands on its own, so a CAPA process built to ISO 13485 satisfies both.
Why is CAPA the most cited area in Form 483s?
Because it is where the absence of connected evidence shows up most clearly. Investigators can follow a CAPA from the signal to the action to the proof it worked, and any break in that chain is visible. Most citations are about the record rather than about the underlying problem.
Can a small team run CAPA properly?
Yes, and the deciding factor is usually whether the process is proportionate. A CAPA process designed for a 400-person manufacturer will not survive contact with a team of nine. What matters is that the evaluation step is honest, so small issues go to the right process and CAPA is reserved for what genuinely needs it.
A CAPA process is only defensible if it fits the company running it
The mapping session establishes which processes your company needs and how they should be sized, CAPA included.
The map is yours to keep either way.