A fix is not always a lasting solution
Suppose an assembly team finds that a batch of reusable bottles leaks around the cap. Replacing the faulty caps may make those bottles usable, but it does not explain why the leak appeared. If the cause remains in the design, materials, equipment or assembly process, the next batch could have the same problem.
Corrective and preventive action, often shortened to CAPA, is a structured way to move beyond that immediate fix. A correction deals with the defect already found, such as reworking a bottle or removing it from sale. Corrective action addresses the cause of an existing problem so it is less likely to recur. Preventive action addresses a plausible problem before it occurs, often by applying what a team has learned to similar products or processes.
Not every minor defect needs an elaborate investigation. The effort should fit the potential impact, frequency and scope of the problem. What matters is keeping the distinctions clear: containing affected products protects the present batch, while changing the underlying process protects future batches.
Contain the problem and define its scope
When a defect is found, the first task is to identify what might be affected. A team might pause the relevant production step, separate suspect stock, review inspection records and check whether products made with the same materials or settings have already moved onward. The aim is to prevent further escapes while the cause is still unknown.
A useful problem statement describes what failed, where and when it was observed, and how the result differed from the requirement. “Caps are bad” gives an investigator little to work with. “Three bottles from the afternoon assembly run leaked during the specified seal check” identifies a measurable symptom and a group of products worth examining. The team should also record how the defect was detected and what remains uncertain.
Containment is temporary by design. Extra inspection, for example, may help sort acceptable bottles from leaking ones, but it can add work and may miss defects that are difficult to detect. It should not quietly become a substitute for understanding why the seals fail.
Investigate causes, not just symptoms
A root-cause investigation works backward from the defect through the conditions that could produce it. For the leaking bottles, the team might examine cap dimensions, gasket placement, tightening settings, bottle-neck shape and the inspection method. Comparing affected and unaffected units can help narrow the possibilities. So can looking for a change: a new material lot, a worn fixture, an adjusted machine or an updated work instruction.
The first plausible explanation is not necessarily the cause. If an operator installed a gasket incorrectly, the investigation should ask why that placement was possible and why the error was not detected. Perhaps the gasket can sit in two positions, the fixture gives no clear feedback, or the inspection check does not reveal a misaligned seal. Those findings point toward different actions than a reminder to “be more careful.”
Evidence matters because actions built on guesses can leave the real problem untouched. A team may test a suspected cause by measuring parts, observing assembly or comparing results under controlled settings. If the evidence is incomplete, it is better to record the uncertainty and investigate further than to present a convenient explanation as fact.
Choose an action that changes the process
Once a likely cause is supported, the team can choose an action aimed at it. A fixture that locates the gasket in only one orientation may be more reliable than a reminder in a work instruction. If parts vary beyond what the seal can tolerate, the answer may involve tighter incoming checks, a process adjustment or a design change. The chosen action should be practical for normal production, not just for a carefully supervised trial.
Changes can create new problems, so they need to be assessed before release. A revised cap, for instance, might improve sealing but become harder to open or incompatible with existing bottles. Teams should decide which checks will show that the change meets the original requirement without compromising other important features.
Preventive action extends the lesson where it reasonably applies. If the same gasket-fitting method is used on another product line, reviewing that line before leaks appear may be worthwhile. This does not mean changing every process after every defect; it means asking whether similar conditions exist elsewhere and acting in proportion to the risk.
Verify the result and keep a usable record
Putting an action in place does not prove that it worked. Effectiveness checks should look at production under ordinary conditions, using measures tied to the original failure. For the bottles, that could mean repeating the seal check on subsequent runs and confirming that the new gasket placement method is used consistently. The team should decide in advance what result would count as success and when to review it.
A concise record makes the work easier to follow: the defect and its scope, containment steps, evidence considered, identified cause, action taken, responsible person and effectiveness result. If the defect returns, that record helps the team see whether the action was incomplete, was not sustained or addressed the wrong cause.
The purpose of CAPA is not to produce a perfect-looking form. It is to make the next product more reliable by turning a detected failure into a tested improvement.
