8D Reports
IATF 16949 10.2.3 Problem Solving: What It Means for Customer 8Ds
IATF 16949 expects suppliers to use the problem-solving approach their customer prescribes, which is why every customer's 8D looks different. This piece explains that in plain terms and what it means for your record.
Rovaryn Digital · · 7 min read

A Rejection Arrives, and the Customer's Format Comes With It
Why does one standard seem to produce so many different response forms? A customer's rejection notice comes with a blank form that has its own section order, its own labels, and a note pointing to the supplier manual. A different customer's request about a similar burr on a related part wants a different layout entirely.
The problem to be solved is the same in both. The short answer sits in one clause of IATF 16949, and understanding it changes how you build and keep your records.
This article reads the problem-solving clause in plain terms, explains why customer formats differ, and shows how to keep one underlying record behind every layout.
What IATF 16949 10.2.3 Problem Solving Actually Asks For
Clause 10.2.3 of IATF 16949:2016 requires an organization to have a documented problem-solving process. Paraphrased, that process has to cover several things: containment and interim actions, root cause analysis along with the methodology used and its results, and systemic corrective actions. The clause also addresses verifying that actions worked and reviewing and updating the relevant documented information. (International Automotive Task Force, IATF 16949:2016 with Sanctioned Interpretations, November 2025.) Check the current edition for the exact wording and sub-clause lettering, because this article paraphrases rather than reproduces it.
The clause does not name a method. It does not say "use 8D," and it does not set a response window. It asks for a process that works and can be shown to work. The method, the form, and the deadlines come from somewhere else, which is the next point.
Why Every Customer's 8D Looks Different
The same clause also says that where a customer has prescribed particular processes, tools, or systems for problem solving, the organization uses them unless the customer approves otherwise. That single idea explains most of the variety you see. Your own documented process is the baseline, and each customer can layer its prescribed format on top of it.
In practice that means:
- One customer wants an 8D with a D0 step, another starts at D1.
- One uses its own portal, another accepts a spreadsheet, another wants a specific PDF.
- Field order and labels differ even when the content is the same.
- Response windows and any administrative terms are set in each customer's supplier manual or customer-specific requirements (CSRs), not in the standard.
The windows deserve one more sentence. There is no single industry-wide containment or plan deadline, and none is set by the clause itself. Each customer sets its own, and it can change when the manual is revised. Read the current revision of every customer's supplier manual and CSRs, and ask the supplier quality engineer (SQE) when something is unclear. For more on where those requirements live, see how IATF 16949 customer-specific requirements work.
The 8D Is a Common Vehicle, Not the Requirement
The 8D method is widely used for customer problem solving, and it is a natural fit for the clause's elements. Ford developed the process and published it in its 1987 manual, Team Oriented Problem Solving, and later added a D0 planning step in the mid-1990s (Mind Tools, 8D Problem Solving Process, 2025). Many customers still ask for it today, sometimes under their own name for it.
The eight disciplines map onto the clause's elements roughly like this:
| Clause element (paraphrased) | Where it usually lands in an 8D |
|---|---|
| Containment and interim actions | D3 |
| Root cause analysis, method and results | D4 |
| Systemic corrective actions | D5 through D7 |
| Verification that actions worked | D6 and D7 |
| Review and update of documented information | D7 and D8 |
Treat the table as a guide, not a rule. Your customer's form may split or merge steps. If you want the discipline-by-discipline walkthrough, start with the 8D report guide. If you are sorting out how 8D relates to a general corrective action process, see 8D versus CAPA.
What Auditors Tend to Find in This Area
Problem solving is a frequent audit topic. According to a simpleQuE analysis of IATF nonconformance data, clause 10.2.3 was the most frequent major nonconformance in IATF 16949 audits, at 10.06% of major nonconformances as of November 25, 2024, with clause 10.2.1 (nonconformity and corrective action) second at 5.65% (simpleQuE, 2024). At the 2025 AIAG Quality Summit, the IAOB ranked problem solving as the top major nonconformance, and sub-clause 10.2.3 f), reviewing and updating documented information, accounted for 40.83% of clause 10.2.3 nonconformances (simpleQuE, IAOB presentation, 2025).
The cited evidence in that presentation pointed to gaps such as follow-up, missing verification steps, and unclear accountability. These are industry-wide observations. They describe what auditors found across many sites, not what will happen at yours, and no record-keeping approach changes an audit outcome by itself.
Two Neighboring Clauses Worth Knowing
The row's secondary topics sit close to 10.2.3, so a quick orientation helps.
Clause 10.2.6, customer complaints and field failure test analysis. A customer complaint is often what triggers the problem-solving process in 10.2.3, so the two clauses are read together. Confirm the clause number, scope and wording in the current standard.
The wider clause 10.2 on nonconformity and corrective action. IATF 16949 clause 10.2 customer complaint requirements and corrective action requirements sit in the same family of clauses. Aerospace readers will find the parallel in AS9100 section 10.2, nonconformity and corrective action. For aerospace customers, SAE AS13000A, Problem Solving Requirements for Suppliers, from the G-22 Aerospace Engine Supplier Quality (AESQ) Committee, defines the process a supplier uses to respond to a customer request for corrective and preventive action (SAE International, 2024). Confirm which documents your prime or tier-1 customers cite.
If you hold both IATF 16949 and AS9100 sites, treat the two sets of requirements separately. Their certification counts and rules are not interchangeable.
Keeping One Record Behind Many Layouts
Here is the practical consequence. If the standard asks for a documented, working process and customers prescribe the layout, the sensible move is to keep your own record of each problem and re-present it in whatever format each customer wants. The facts do not change between layouts. The labels and order do.
A workable no-software approach:
- Capture a core record when the request arrives. Customer, part number, received date, severity, and where the response format and deadline are defined.
- Log the clock rules from that customer's current manual. Write down which revision you read.
- Hold the content once. Team, problem description, containment, root cause, actions, verification, and prevention live in one place.
- Map fields at the end. Re-key into the customer's form or portal from that single record.
- Keep the evidence together. Photos, data, and sign-offs stay attached to the discipline they support.
- Review before it goes out. Someone other than the author reads the response against the evidence.
Records have a retention side, too. Clause 7.5.3.2.1 sets minimum retention for certain quality records, and customers may specify their own periods. Check the clause and your customers' CSRs for the exact requirement.
Takeaway: The standard asks for a problem-solving process that works. Your customers decide what the form looks like. Keep the substance in one place and treat each customer layout as a presentation of it.
Root cause is usually where one record earns its keep, because the same cause can surface on a second customer's request. If that is your sticking point, read about 8D D4 root cause analysis. For the day-to-day handling of an incoming request, see the supplier corrective action request guide.
Where a Supplier-Side Record Fits
Supplier CAR Response Desk is designed to hold this kind of supplier-side record: one entry per request, editable per-customer response rules, a guided D1–D8, and PDF or Excel export in a customer's field order. Because it is pre-launch, that describes what it is built to do. It records and calculates; it is not advice or certification, and it does not make anyone compliant with IATF 16949.
If you want to hear when it opens, 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 an 8D Report? The Eight Disciplines from the Supplier's Desk
An 8D report is the record of eight disciplines, from forming the team to closing the request. Here is what each one asks of a supplier team answering a customer.
Rovaryn Digital · · 11 min read