An interim containment action (ICA) is a temporary firewall in problem-solving, step D3 of the 8D method, that stops a known defect from reaching the customer while the permanent fix is still being found and verified. Typical ICAs are sort, 100% inspect, rework, hold, or return, and they are removed once the permanent corrective action is proven.
When a defect escapes, two clocks start. One is the slow clock of finding and proving the real cause, which can take weeks. The other is the fast clock of the customer, who is receiving bad parts right now. The interim containment action is what you put between the two: a stopgap that protects the customer today so the root-cause work can proceed without more damage. It is not a fix. It is a firewall, and knowing the difference is the heart of disciplined root cause analysis and mature lean manufacturing quality practice.
What Is an Interim Containment Action?
An interim containment action is a temporary measure that isolates a problem from the customer, internal or external, until a verified permanent solution is in place. It treats the symptom, the defective part getting through, not the cause. Its whole job is to buy time safely: keep bad product from shipping, or from moving to the next operation, while the team works the real problem.
Because it is temporary by design, an ICA is expected to be removed later, once the permanent corrective action is proven to work. That temporary nature is the defining feature. An ICA that quietly becomes permanent, sorting a defect forever because nobody closed out the root cause, is a classic sign of a stalled problem-solving effort and a permanent tax on the plant.
Where Does the ICA Fit in the 8D Process?
The 8D method, the Eight Disciplines of Problem Solving formalized by Ford, runs eight steps from D1 to D8 (with a D0 preparation step). The interim containment action is D3 and it sits early on purpose, right after the team is formed (D1) and the problem is described (D2), and before the root cause is identified (D4). You contain first, then investigate, because the customer cannot wait for the investigation to finish.
Later, D4 finds the root cause, D5 chooses the permanent corrective action, D6 implements and validates it, and only then is the D3 containment removed. D7 prevents recurrence and D8 closes out. The sequence matters: the ICA is the bridge that keeps the customer safe across the gap between "we have a problem" (D2) and "we have a proven fix" (D6). It buys the whole rest of the process room to work.
What Are the Common Containment Options?
Containment is a menu, not a single move. You pick the option, or combination, that reliably keeps defects away from the customer at acceptable cost and speed.
| Option | What it does | Best when |
|---|---|---|
| Sort / 100% inspection | Screen all suspect stock and separate good from bad | Defect is detectable by eye or gauge |
| Rework | Correct the defective units to spec | Defect is repairable and rework is validated |
| Hold / quarantine | Lock suspect lots so nothing ships | You are unsure of extent and need to bound it |
| Return / recall from customer | Retrieve suspect parts already shipped | Defect already escaped the plant |
| Add a temporary check | Insert an extra gauge, fixture, or sign-off in the flow | An added inspection reliably catches it |
How Do You Set Up an Interim Containment Action? A 6-Step Routine
- Bound the suspect population. Define exactly what is at risk, which lots, dates, machines, and shifts, and where it lives: on the line, in the warehouse, in transit, at the customer. An is / is-not analysis sharpens this fast so you do not over- or under-contain.
- Choose the containment method. Pick sort, rework, hold, return, or a temporary check based on how the defect is detected and how fast you must act. When in doubt, quarantine first, then decide.
- Contain everywhere the product sits. Apply the action across the whole supply chain at once, in-process stock, finished goods, in transit, and at the customer's dock, not just the line. Missing one location lets a bad part slip through.
- Verify the ICA actually catches the defect. Prove the containment works before trusting it: check that the sort correctly separates good from bad, or that the added gauge flags the failure every time. An unverified firewall is a false sense of safety.
- Communicate, document, and label. Tell the customer and internal stakeholders, log the action on the non-conformance report and 8D, and clearly mark contained stock so nobody releases it by mistake.
- Track it and plan its removal. Record when the ICA started, monitor that it keeps working, and set the condition for pulling it: the permanent corrective action is verified at D6. Review open ICAs regularly so none quietly becomes permanent.
How Do You Verify an ICA Is Working?
An interim containment action is only useful if it reliably does its one job, so you verify it the same way you would any control: prove it catches the defect and prove it stays effective. Before you rely on a sort, seed a few known-bad parts and confirm the sort finds them. After the ICA is live, watch for escapes, any defect that gets past containment, and treat each one as a failure of the firewall to be fixed immediately. Because containment leans on human 100% inspection, which is never perfect, high-stakes cases often add a redundant check or a poka-yoke so a single missed part cannot reach the customer.
What Goes Wrong With Interim Containment?
Three failures show up again and again. The first is the ICA that never comes down: the root-cause work stalls, the sort becomes routine, and a year later a plant is still paying two operators to inspect around a defect nobody fixed. Review open containments on a schedule and treat any that outlive their 8D as an escalation. The second is partial containment, applying the action on the line but forgetting the finished-goods warehouse, the truck already loaded, or the parts sitting at the customer's dock. A defect only has to escape one uncontained location to reach the customer. The third is trusting an unverified firewall: a 100% visual sort feels thorough but misses parts, because sustained human inspection is imperfect. Assume the containment leaks until you have proven it does not, and add redundancy where the cost of an escape is high. Naming these traps up front is how teams keep a temporary firewall both temporary and effective.
How Is an ICA Different From a Permanent Corrective Action?
The two are easy to confuse and dangerous to swap. An interim containment action treats the symptom and is temporary; a permanent corrective action (PCA) treats the root cause and is meant to stay. The ICA stops bad parts from escaping; the PCA stops bad parts from being made. Crucially, containment adds cost, extra sorting, extra rework, extra people, and does nothing to prevent recurrence, so leaving an ICA in place instead of finishing the root-cause work is pure muda: waste you pay for every shift.
The clean handoff is the mark of a healthy problem-solving process: contain (D3), find the cause (D4), implement and verify the permanent fix (D6), then, and only then, remove the containment. That verified permanent action is what feeds your corrective and preventive action system for long-term control. Pull the firewall before the fix is proven and defects come straight back; leave it up forever and you have simply institutionalized the waste.
Interim containment by the numbers
The discipline is standardized in the quality and automotive worlds. The American Society for Quality describes the 8D method's eight disciplines, with D3, interim containment, defined as isolating the effects of the problem from any internal or external customer until a permanent corrective action is implemented (ASQ, Eight Disciplines (8D) Model). In automotive supply agreements, containment is expected fast, commonly with an initial containment in place within 24 hours of notification, reflecting how quickly a customer must be protected. And by definition the ICA is temporary: it is removed after the permanent corrective action is verified, because it adds cost and does not prevent recurrence.
Good containment depends on knowing exactly which product is suspect, and that is a traceability problem. When lot, date, machine, and shift are captured cleanly, you can bound the suspect population tightly and contain only what is at risk. When that data lives on scattered paper, teams over-contain, quarantining weeks of good stock, or under-contain and let a bad lot escape. Plants that capture production and defect data live at the station can define the suspect window in minutes and verify containment the same day, the practical value of live floor data over your existing systems no rip-and-replace. See how tighter floor data speeds problem-solving in our CLS case study.