A containment action is a fast, temporary measure that protects the customer from a known defect while you find and fix its root cause. It does not solve the problem; it stops the bleeding by keeping bad product away from the next process and the customer.
When a defect gets loose, the clock is the enemy. Every hour it goes uncontained is more suspect product shipping, more parts moving downstream, more risk landing on a customer's line. Containment is the first thing a good quality response does, before anyone argues about cause. It buys the time to investigate properly without letting the problem keep escaping while you think.
What is a containment action?
A containment action is anything that keeps a known defect from reaching the next step or the customer, put in place quickly and meant to be temporary. It is a wall across the escape path, not a repair of the process. Typical containment on a plant floor is sorting: pulling suspect work-in-process and finished stock, quarantining it, and adding a 100% inspection at the point where the defect can escape. It also means checking where product already is, the warehouse, trucks in transit, the customer's dock, because containment that ignores product already downstream is a wall with a hole in it.
The word "temporary" is doing real work in that definition. Containment is expensive and manual by design: extra people sorting, extra inspection, slower flow. You accept that cost precisely because it is short-term insurance while the permanent fix is developed. The failure mode to avoid is letting containment quietly become permanent, a 100% sort that is still running six months later is a sign the root cause was never actually fixed.
Why contain before you fix?
Because root cause takes time and the customer cannot wait. A real investigation, running down the cause, confirming it, designing a change that removes it, proving the change works, takes days to weeks. If you wait until you understand the problem to protect the customer, you ship defects for the entire investigation. Containment decouples the two clocks: protection happens in hours, understanding happens over the following weeks, and the customer is safe the whole time.
There is a discipline point here that separates strong quality systems from weak ones. Containment is not the corrective action, and it must be recorded as a separate step so nobody mistakes one for the other. A team that sorts the bad stock, ships clean product, and then closes the issue has contained the problem and fixed nothing, the process is still making the defect, and the moment the sort stops, escapes resume. Containment protects; corrective action cures. You need both, and you need to keep them straight.
Where does containment sit in 8D and CAPA?
In 8D problem solving containment is discipline D3, the Interim Containment Action, and it is deliberately placed before root cause (D4) and permanent corrective action (D5). The Interim Containment Action is defined as any action that keeps the customer from experiencing the symptom of the problem; it is temporary and is removed once the permanent corrective action is verified and in place. 8D puts it early on purpose: protect first, investigate second, cure third.
The same logic runs through CAPA. Containment is the step right after you identify and document the nonconformity and before you launch the root cause analysis. It maps to the requirement in ISO 9001 clause 10.2 to take action to control and correct a nonconformity and deal with its consequences, the "control and correct" language is containment, distinct from the corrective action that removes the cause. Whether your framework is 8D, CAPA, or your own house process, containment occupies the same slot: the fast protective move that makes room for a proper fix. Our comparison of 8D and CAPA walks through how the two methods line up step for step.
How do you contain a problem fast?
Speed matters more than elegance here. Work the steps in order and do not wait for perfect information to start.
- Define the defect and the suspect population. What is the defect, how do you tell good from bad, and what is the boundary, which lots, dates, lines, or serial ranges are suspect? A containment with fuzzy boundaries either misses bad product or quarantines the whole plant.
- Stop the flow and quarantine. Hold suspect work-in-process and finished stock immediately, tag it clearly, and physically separate it so it cannot be shipped or used by mistake. Log it as a nonconformance.
- Add inspection at the escape points. Put a 100% check where the defect can leave, in line, at final, and at shipping, using a clear, trained method so sorters actually catch it.
- Chase product already gone. Check the warehouse, in-transit shipments, and the customer's stock. If suspect product reached the customer, notify them and contain on their side too. This is the step teams forget and regret.
- Protect the customer's supply. Make sure known-good product keeps flowing so containment does not starve the customer's line, set up controlled shipping if they require it.
- Verify the containment is working. Confirm the sort is actually catching defects and no more escapes are reaching the customer. Containment you never check is a hope, not a control.
- Hand off to root cause and set the exit. Record containment as its own action, start the root cause analysis and state plainly that containment comes down only when the permanent fix is verified effective.
What is controlled shipping?
Controlled shipping is a formal containment a customer imposes when they have lost confidence that normal controls will keep defects out, and it comes in two escalating levels. CS1 requires the supplier to add a dedicated redundant inspection, a check over and above the normal process controls, run by the supplier, with results tracked and reported to the customer. It is the standard first response when escapes reach a customer.
CS2 stacks a second, independent inspection on top of CS1, frequently performed by a paid third party the customer trusts, and is triggered when CS1 has not stopped the escapes or the customer's confidence is low enough to demand outside verification. Both levels are containment, not cure: they exist to guarantee the customer sees only good product while the supplier drives the permanent fix. Controlled shipping is expensive and reputationally painful, which is exactly why it motivates a fast, real corrective action, the way off controlled shipping is a verified effective fix, not a promise.
Where containment lives in the standards
- ASQ places containment as discipline D3 of the 8D method, the Interim Containment Action that isolates the effect of the problem from the customer until permanent corrective action is implemented (ASQ, Eight Disciplines (8D)).
- FDA's CAPA subsystem guidance treats correcting and containing the immediate nonconformity as distinct from the corrective action that addresses the cause, and expects both to be documented (FDA, Corrective and Preventive Actions (CAPA) subsystem).
- ISO 9001 clause 10.2 requires organizations to react to a nonconformity by taking action to control and correct it and to deal with its consequences, the standard's language for containment, separate from eliminating the cause (ISO 9001:2015).
How do you know when to remove containment?
When the permanent corrective action has been verified effective, not the day you install it, and never just because the containment is expensive and everyone is tired of it. This is the single most common containment mistake: pulling the sort when the fix goes in, before there is any evidence the fix actually holds. If the corrective action turns out to be weak, escapes resume with no wall to catch them, and now the customer has caught a second dose of the same defect.
The clean sequence is: install the permanent fix, keep containment running, confirm through data over a defined window that the defect is gone and the fix created no new problem, and only then remove containment. That confirmation is exactly the effectiveness check that CAPA and 8D both require, which is why containment and effectiveness verification are two ends of the same rope.
What are the common containment mistakes?
The patterns repeat across plants and industries:
- Treating containment as the fix. The sort works, escapes stop, the issue gets closed, and the process keeps making the defect. Containment protects; it never cures.
- Fuzzy boundaries. Suspect population defined too narrowly misses bad product; defined too broadly grinds the plant to a halt. Nail the lots, dates, and ranges.
- Forgetting product already gone. Containment that stops at the shipping dock ignores what is in transit and at the customer. Chase it.
- Removing containment too early. Pulling the wall before the fix is verified invites a repeat escape and destroys customer confidence.
- Containment that never ends. A permanent 100% sort is a confession that root cause was never fixed, and a standing cost that quietly eats margin.
Every one of these gets easier when the data is visible: what is on hold, where suspect stock sits, whether the sort is still catching anything, whether the fix is holding. When holds and defect records live on clipboards, containment gets managed by memory and the mistakes above are almost guaranteed. Capturing it digitally at the station, what Harmony's quality and downtime intelligence is built for, turns containment from a scramble into a controlled, visible response; see our CLS case study for how that works in a real plant.