Containment & Response Clocks
The 24-Hour Containment Window: Running the Clock on a Customer Complaint
Many teams work to a 24-hour containment window, but the real number is whatever your customer's manual says. This guide covers confirming it, starting the clock and recording the interim response.
Rovaryn Digital · · 6 min read

The rejection email that lands late on a Thursday
The 24-hour containment window is a habit, not a rule. Take a rejection notice for a lot of brackets that a tier-1 customer sends at 4:40 p.m. on a Thursday, asking for containment. The engineer who normally handles that customer is out until the following week, and the record of the last similar request sits somewhere in an email thread from last spring.
Many teams in this spot reach for the phrase they have heard before. It is a reasonable working habit, and it is also one of the most repeated half-truths in supplier quality. The number that governs your response is the one your customer wrote in its supplier manual or customer-specific requirements (CSRs). That number can differ from the customer next door, and from the same customer's earlier revision.
This guide covers how to confirm the window, when to start the clock, how to count it, and what to record in the interim response.
What a 24 hour containment customer complaint window really means
"24 hours" is a search phrase and a common starting value. It is not an industry rule. When people ask how long an 8D report takes to complete or when an 8D report is due, the honest answer is that there are usually several deadlines. One covers the interim response with containment. One covers root cause and the corrective action plan. One covers final closure. Each customer sets its own, and some set only one.
Containment comes first because it protects the customer's line and your next shipment. It is separate from root cause and permanent corrective action. If you want the distinction spelled out, read what containment means in quality.
The standard behind all this does not hand you a number either. IATF 16949 clause 10.2.3 requires a documented problem-solving process that covers containment and interim actions, root cause analysis and systemic corrective actions. It also says that where a customer has prescribed problem-solving processes or tools, you use them unless the customer approves otherwise (IATF 16949:2016 with Sanctioned Interpretations, Nov 2025). In other words, the standard sends you to the customer's requirements.
Auditors pay attention here. simpleQuE's analysis of IATF nonconformance data found clause 10.2.3 (problem solving) was the most frequent major nonconformance, at 10.06% of major nonconformances as of November 25, 2024. How you record containment is worth getting right.
Confirm your customer's window before the clock matters
Do this once per customer, not once per complaint. Keep the answers somewhere your whole team can find them.
- Find the current revision of the customer's supplier manual and CSRs. Check the revision date, because older copies circulate. The guide to customer-specific requirements covers where they usually live.
- Locate the response section and note which event starts the clock: the date the notice was issued, the date you received it, or the date it was posted to the portal.
- Note the unit: hours, calendar days or working days.
- Note what the first deadline requires. It might be an acknowledgment, a containment confirmation or an initial 8D.
- Note the later deadlines for root cause, the corrective action plan and closure.
- Note any administrative charge or escalation attached to a late response.
- When the manual is silent, or the request itself states a different date, ask the SQE and keep the reply with the record.
Windows and units genuinely differ. Adient's Global Supplier Standards Manual – Quality, published in 2021, expected written 8D results within five working days. Horton's supplier quality manual, revised in October 2025, set root cause within 14 calendar days and completion through D8 within 30 calendar days. These are dated examples of variation, not current requirements. Read your own customer's current revision for the exact windows.
The window is whatever your customer's current manual says. Learn it before the notice arrives, and record the received time the moment it does.
Start the clock at receipt and count it the way the manual does
Record the time the request reached you, taken from the email header or the portal posting. Do not use the time someone got around to reading it. If the manual starts the clock at issue rather than receipt, record both timestamps so the difference is visible.
Then count in the manual's unit.
| Unit | What it counts | What to watch |
|---|---|---|
| Hours | Elapsed time, including nights and weekends | Which time zone the customer's timestamp uses |
| Calendar days | Every day, including weekends | Whether the day of receipt counts as day zero or day one |
| Working days | Weekdays only | Whose holiday calendar applies, yours or the customer's |
Here is a worked example with hypothetical windows, not any customer's rule. Say the Thursday 4:40 p.m. notice arrives. Using 24 hours as an editable starting value, the containment response is due Friday at 4:40 p.m. If a window were five working days counted from the day after receipt, it would run Friday, Monday, Tuesday, Wednesday, Thursday, and fall due the following Thursday. Five calendar days from the same notice would fall due Tuesday. Same notice, three different due dates. That is why the unit matters as much as the number.
The guide to customer response times goes further on how customers phrase these deadlines.
What goes into the interim response
The interim response says what you have done to protect the customer now, before you know the root cause. Treat the 24 hour containment customer complaint as a record you can hand to someone else on Monday. Capture these fields when the request arrives:
- Request number, customer, part number and severity as stated in the notice
- Received date and time, and where it came from (email, portal, phone)
- Suspect locations: incoming material, work in process, finished goods, in transit, at the customer
- Quantities checked and quantities rejected at each location
- Sort or inspection method, and who performed it
- How contained material is marked, such as tags, labels or segregated racks
- Date, time and owner for each containment action
- Evidence: photos, sort sheets, inspection records
- The next deadline and who owns it
The interim is not the final answer. It should say plainly that root cause is still open and name the date for the next update. For the discipline itself, see D3 containment action. For how to watch several of these at once, see tracking containment deadlines.
If you need a wider view of the topic, the automotive containment hub collects the related guides.
A spreadsheet or Word file can hold every field above. What it will not do on its own is start a clock, flag an overdue response, or connect today's complaint to the one from another customer last year, unless someone builds and maintains that by hand.
Where a supplier-side record can hold this
Supplier CAR Response Desk is designed to keep each request as its own record across all of your customers, alongside whatever portal each customer requires. The Response Desk is built so you can set response rules per customer and have a containment clock and a plan clock start from the received date. Any default values are editable starting values, not a statement of any customer's rule. It is also designed to provide reminders and an overdue state, evidence uploads attached to a discipline, and interim and final versions with revision history and reviewer sign-off before export.
The Response Desk records and calculates. It is not advice or certification, it does not write your root cause analysis, and it does not submit to customer portals. You would still read each customer's manual and enter its rules.
To hear when the Response Desk opens, you can join the waitlist.
Put it to work
Compare plans on the pricing page.
Get the next guide
Practical guides for supplier quality teams, delivered straight to your inbox.
Related guides

What Is Containment in Quality? A Supplier's Guide to the First Hours
Containment is the work that protects the customer while the cause is still unknown. This guide covers where suspect stock sits, how to bound it, and what to record.
Rovaryn Digital · · 10 min read

8D Response Time: Reading Your Customer's Requirements and Running the Clocks
There is no single 8D deadline. Each customer sets its own windows, and this guide shows how to find them, record them once and keep every clock running.
Rovaryn Digital · · 13 min read

8D D3 Containment Action: What to Do in the First Hours
D3 is the first thing a customer sees from you. This guide covers locating suspect stock, sorting and marking it, and drafting an interim response your team can sign off.
Rovaryn Digital · · 8 min read