Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

Containment & Response Clocks

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

A rejection and the clock nobody has read

How long do you have to answer a customer's 8D request? It depends on the customer, and the answer is written in a specific place: that customer's supplier manual or customer-specific requirements (CSRs). If nobody has opened the manual since the last audit, and the engineer who remembered the response window has moved on, the clock is running on a rule that no one in the building has read.

Many response clocks start this way, with a message and not a plan. The window may be stated in hours, calendar days, working days, or milestones tied to a particular discipline. A supplier answering several customers may hold several different windows at once, each counted a different way.

There is no single number that fits every request, and a figure on a general web page describes someone else's customer.

This article shows where response windows are written, how to read and count them, and how to record them once per customer so each new request starts the right clocks.

Why there is no single 8D deadline

The 8D method is shared. The deadlines are not. Each OEM or tier-1 writes its own expectations into its supplier manual, and those documents are revised over time. Two customers can use the same eight disciplines and still ask for different things at different moments: one wants a first response quickly and the full analysis later, another wants a single submission, and a third ties timing to the severity of the problem.

For IATF 16949 suppliers, the standard supports answering in the customer's way. Clause 10.2.3 says that where a customer has prescribed processes, tools or systems for problem solving, the organization uses them unless the customer approves otherwise (IATF 16949:2016 with Sanctioned Interpretations, Nov 2025). The same clause expects a documented problem-solving process that covers containment and interim actions, root cause analysis and systemic corrective actions. The standard describes the process. It does not set a number of hours or days.

Problem solving is also where auditors find gaps. Simple analysis of IATF nonconformance data by simpleQuE found clause 10.2.3 was the most frequent major nonconformance, at 10.06% of major nonconformances as of November 25, 2024 (simpleQuE, 2024). That figure describes what auditors found across the industry. It says nothing about how any one supplier's clocks are run.

AS9100 suppliers work from a similar idea in a different vocabulary. Aerospace customers send supplier corrective action requests (SCARs), and SAE AS13000A, "Problem Solving Requirements for Suppliers", describes the process a supplier uses to respond (SAE International, 2024). Again, a given prime or tier-1 sets its own response expectations in its own documents. For a wider view of how these requests arrive and what the supplier owes, see the supplier corrective action request guide.

Where response windows live in your customer's paperwork

Response requirements are rarely in one place. Expect to look in several documents, and expect them to disagree on small points.

  • The supplier quality manual. This is usually the main source. It often has a section on nonconformance notification, problem reports or corrective action requests, and a separate section on charges.
  • CSRs for your certification scheme. For IATF 16949 suppliers, customer-specific requirements add to the standard. Our article on IATF 16949 customer-specific requirements covers how to find and track them.
  • Purchase order terms and quality clauses. Some windows or fee terms ride on the order rather than the manual.
  • The notification itself. A request may state its own due date, or reference a severity level that determines the window.
  • The customer's portal. Portals can display a due date, and sometimes the date shown reflects an agreement made by email. Treat the portal as the channel the customer runs, and confirm any difference with the customer's supplier quality engineer (SQE).
  • Your own agreements. A written extension or a negotiated plan for a long-running issue belongs on the record next to the standing rule.

When two sources conflict, do not pick the one you like. Ask the SQE or buyer which one governs, and keep the answer in writing.

Finding the 8D response time customer requirement in the document

Reading a manual for response rules is a small, repeatable job. A checklist keeps it from depending on whoever happens to remember. Work through it once per customer, then again at each new revision.

  1. Record the document and revision. Note the manual title, revision letter or date, and where you downloaded it. A window without a revision is a rumor.
  2. Find the trigger. What starts the clock: the date the customer issued the request, the date it reached you, a portal posting time, or a shipment event? Wording like "upon notification" needs a question to the SQE if the manual does not define it.
  3. List every milestone. Containment, root cause, corrective action plan, implementation, verification and closure may each have a separate deadline. Some customers ask for an initial response and a full response. Write down each one.
  4. Check the unit. Hours, calendar days, working days or business days are different things. Note whether the manual says which calendar it uses and whose holidays count.
  5. Check how severity changes the window. Many manuals tier their expectations by problem level, field issue or line stoppage. Capture the levels and what moves between them.
  6. Find the "or sooner" language. Some manuals allow the customer to ask for faster action depending on the situation. Note it, because it means the standing window is a ceiling and not a promise.
  7. Find extension rules. Does the manual allow extension requests, who approves them, and how must they be made? See 8D extension requests and due dates for how to ask.
  8. Find fee and escalation terms. Administrative charges, late-response fees, scorecard effects and new-business consequences sit near the timing language, or in a different chapter. Copy the terms exactly as stated and keep the page reference.
  9. Find format requirements. Note any required template, field order or portal entry.
  10. Confirm with a person. Email the SQE with your reading and ask them to correct it. Keep the reply.

The answer is a short summary for each customer: a few lines you can pull up within a minute when a request arrives. For the 8D response time customer requirement, that summary is the most useful artifact you can build before the next rejection.

Calendar days, working days and when the clock starts

Two suppliers can read the same sentence and arrive at different due dates. The usual causes are the unit, the starting point and the holidays.

Here is an invented example, not any customer's rule. Suppose a manual says a response is due "within three working days" of notification, and a request reaches you at 4:40 pm on a Thursday, with the following Monday a plant holiday.

Question Reading A Reading B
Does the day of receipt count? No, day one is Friday Yes, Thursday is day one
Does the holiday count? Skipped as a non-working day Counted if the customer's calendar differs
Resulting due date Wednesday Tuesday or earlier

The same notice yields at least two dates. Neither is wrong until someone confirms the customer's reading. If the manual does not define the counting, ask. Until you have an answer, plan to the earlier date.

A second example shows a different trap. A manual states a window "within ten calendar days." Calendar days include weekends, so the usable working time is shorter than the number suggests, especially if the root cause work needs a metrology lab or a supplier of your own to respond. Ten calendar days is not ten working days, and a record that counts only one of the two will mislead.

A short list of counting decisions to settle for each customer:

  • Start event: issue date, receipt date or portal posting.
  • Day one: the day of receipt or the next day.
  • Unit: hours, calendar days or working days.
  • Calendar: whose holidays, and whether shutdown weeks count.
  • Time of day: whether a notice received late counts as that day.
  • Time zone: relevant when the customer and plant are in different regions.

Containment deserves extra care because the clock is shortest and the pressure highest. Containment is the set of actions that protect the customer, and your own downstream processes, from further nonconforming parts. It is separate from the corrective action that removes the cause. The 24-hour containment guide walks through what to contain. For this article, the point is narrower: the containment window is a customer's own, found in its documents, and you should know it before the notice arrives.

Takeaway: a response window is only usable once you know the unit, the start event and the calendar your customer uses.

Recording the rules once, per customer

The checklist produces a summary. A record turns that summary into something every engineer uses the same way. A spreadsheet tab, a page in a binder or a record in a tool can all hold it. What matters is that it exists per customer, names its source, and gets updated when the manual changes.

A useful layout has one row per customer and these fields:

Field What to capture
Customer and plant Which customer, and which of your plants it applies to
Source and revision Manual or CSR title, revision, date checked
Start event What starts each clock, as the manual states it
Containment window Value and unit, plus any "or sooner" language
Plan or root cause window Value and unit
Implementation and closure milestones Value and unit for each
Counting rules Calendar, working days, holidays, day one
Severity levels How the levels change the windows
Extension rules Who approves and how to ask
Fee and escalation terms Copied as written, with page reference
Format and channel Template, field order, portal
SQE contact and last confirmed Name, date of the last written confirmation

Two habits keep the record honest. First, store the exact wording from the manual next to your interpretation, so a reader can see what was copied and what was inferred. Second, review the record when a customer issues a new revision, and at least on a schedule you choose. Manuals change, and a record that was right two years ago may no longer match.

When a request arrives, the first step is to open the record, pick the customer, and write the due dates on the request itself. The reader of the request should not need to know who did the reading.

Running the clocks after the request arrives

With the rules recorded, each request needs its own small set of dates.

  1. Log the request. Capture customer, part, severity, received date and time, and who received it.
  2. Compute each due date. Apply that customer's start event, unit and calendar. Write the dates down with the counting assumption beside them.
  3. Set the working target earlier than the due date. Many teams set an internal target a day or more ahead, so review and sign-off do not land on the deadline.
  4. Assign owners. Containment, root cause, plan and verification each need a named person and a date.
  5. Watch the clocks. Look at open requests daily during containment and at least weekly afterward.
  6. Log extensions in writing. If you ask for more time, record the request, the approver and the new date. See how to track 8D containment deadlines for a practical routine.
  7. Close with evidence. Keep verification data with the record, so the closure date and the supporting evidence travel together.

Once a few dozen requests have run this way, measures such as on-time response and days to close become possible. Our note on the corrective action response time KPI covers how to define them so that the numbers mean something.

What a supplier-side record should do

This is where a dedicated record starts to matter. A spreadsheet or document holds whatever you type into it. It does not start a clock, flag an overdue response or connect history across customers unless someone builds and maintains that by hand. That is a property of documents, not a criticism of the people who use them.

Supplier CAR Response Desk is designed to be the supplier's own record across all of its customers. It is pre-launch. The description below is what it is built to do, and it records and calculates; it is not advice or certification.

  • A request record holding customer, part, severity and received date.
  • Editable per-customer response rules that start a containment clock and a plan clock for each new request. The product's starting values of 24 hours for containment and 10 days for the plan are editable defaults, not a statement of any customer's rule, and you replace them with what your own customer's manual says.
  • Reminders and an overdue state so a slipping response is visible.
  • Guided D1–D8 entry with 5 Whys and fishbone fields, and action items with owner, due date and status.
  • Interim and final versions with revision history and reviewer sign-off before export.
  • PDF and Excel export in the customer's field order, with a generic 8D fallback, plus a copy-friendly field view for re-keying into a customer portal. Customers keep running their portals, and the Response Desk does not submit to them.
  • A dashboard showing open, due this week, overdue, on-time rate and average days to close.

Two further capabilities are tier-gated. A fee-exposure view, available on Professional and above, calculates from the fee terms you enter from your own customer's manual. The product does not know any customer's fees. Cross-customer search and repeat-failure flags, also Professional and above, let you look for the same cause across customers. A cross-plant view arrives on Business and above, for groups that need one picture across plants.

Pricing is one flat price per plant rather than per seat. The Response Desk does not write the analysis, and it does not decide what your customer requires. Reading the manual remains your job.

Questions people search for

When is an 8D report due? When your customer's documents say it is. Check the current revision of the supplier manual and CSRs, then confirm with the SQE. A number quoted on a website, including in this article's examples, is not a substitute.

How long does an 8D report take to complete? We do not publish a figure here, and no reliable one applies to all suppliers. The time depends on how quickly containment is in place, how hard the root cause is to find, how long a permanent fix takes to implement and how long you need to verify that it worked. Verification can run well beyond the first response, which is one reason customers often set separate windows for separate stages.

Is the plan due before or after containment? Usually containment comes first, but your customer decides the order and the timing. The milestone list from your reading checklist answers this for each customer.

What if the window is too short? Ask early and in writing. State what is done, what is outstanding and the date you can commit to. Whether the customer grants it is the customer's decision.

What if two customers use different windows for the same part family? Keep two records and two sets of dates. A common root cause can feed both responses, but each answer is due on its own schedule.

Start with one customer

Pick the customer that sends you the most requests. Read the current revision of its manual with the checklist above, write the summary, send it to the SQE for correction and file the reply. Then repeat for the next customer. After a handful, your response clocks stop depending on memory.

If you would like 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.