Chapter 7: Nonconformity, Corrective Action, and the Automotive 8D Discipline

Clause 10.2 requires correction, root cause analysis, and effectiveness verification — automotive customers (Ford Q1, GM BIQS, Stellantis SQ.AS) mandate the 8D problem-solving discipline (8 Disciplines: containment, team, problem definition, interim containment, root cause, permanent corrective action, prevention, recognition) for every customer-reported nonconformity. Standard automotive timeline: D1-D3 within 24 hours, D4-D5 within 48 hours, D6 (root cause) within 14 days, D7 (preventive action) within 30 days, D8 (recognition + closure) within 60 days. Plants that miss these gates trigger customer-controlled shipping (CS-1, CS-2) which suspends new business until corrective action is verified.

For North American automotive suppliers pursuing or maintaining ISO 9001 — and especially those with IATF 16949 certification — 8D is not an optional methodology. It is the lingua franca of OEM quality engineering. A weak 8D submission tells a customer that the plant cannot be trusted with new program awards. A strong 8D, executed on the OEM clock, demonstrates the kind of disciplined problem-solving that earns Q1, Supplier of the Year, and preferred-source status. The eight steps below describe how PinnacleQMS clients run 8D from the moment a customer rejection email lands in the quality manager's inbox to the moment the OEM closes the concern in their portal.

D1 — Form the team

The 8D clock starts the moment the customer issues a Supplier Problem Report (SPR), Supplier Concern (GM), Supplier Deviation Report (Ford SDR), or equivalent. Within four hours, the plant quality manager assembles a cross-functional team and names a champion. The team is not a committee — it is the smallest group capable of solving the problem with authority to change processes.

A defensible D1 team for a customer-reported defect on a stamped bracket from a Tier 1 in Windsor includes: the quality engineer assigned to the customer account (champion), the manufacturing engineer responsible for the press cell, the production supervisor on the affected shift, a maintenance technician familiar with the die, the materials/logistics lead handling sort-and-rework, and an APQP engineer who can update the control plan and PFMEA. Six people, named individuals, with phone numbers and email addresses listed on the 8D form. OEM portal screens reject 8Ds that list "Quality Department" instead of a person.

D2 — Describe the problem (5W2H)

D2 separates strong 8Ds from weak ones. The discipline is 5W2H: What, Where, When, Who, Why (the customer says it is a problem), How, How many. The output is a single problem statement that any engineer at the OEM can read in 30 seconds and understand exactly what shipped, when, and how it failed.

Weak D2 looks like: "Bracket failed dimensional check at customer." Strong D2 looks like: "Part 47821-A, lot codes 2604-A through 2604-F (8,400 pieces) shipped from Plant 2 between March 14 and March 19, exhibits flange angle 88.2-88.6 degrees against print spec of 90.0 +/- 0.5 degrees, detected by customer at incoming inspection on April 2, affecting 612 pieces of 980 inspected (62 percent reject rate), causing line stop on the customer's Brampton assembly line for 47 minutes."

That paragraph contains every data element an OEM quality engineer needs to assess severity, trace the affected population, and decide whether to escalate to controlled shipping. PinnacleQMS clients keep a 5W2H template inside the PinnacleQMS Quality Issue module so that nothing gets shipped to a customer without all seven fields populated.

D3 — Implement interim containment (within 24 hours)

D3 is the firewall. Within 24 hours of the customer notification, the supplier must demonstrate that no further defective product can reach the customer line. Interim containment has three layers, and OEM portals expect all three documented.

First, contain in transit and at customer. Send a sort team (in-house, third-party, or both) to the customer's dock, sequencing center, and assembly line within hours. Sort 100 percent of suspect inventory. Issue a green-tag/red-tag system so the customer can visually distinguish sorted-good parts from suspect parts.

Second, contain at the supplier. Quarantine all on-hand finished goods, WIP, and raw stock with the suspect lot codes. Sort 100 percent before any further shipment. The 8D document the date, time, sort yield, and disposition of every container.

Third, contain in the field. Trace shipments back through the dispatch log for the affected period, identify every customer location that received product, and arrange sort coverage at each one. For a JIT supplier feeding three OEM plants and two sequencing centers, that means five sort teams stood up inside 24 hours.

Customer-controlled shipping (CS-1) typically activates when D3 is incomplete or when defective product reaches the customer a second time. CS-1 requires a third-party sort firm at the supplier dock validating every shipment. CS-2 adds a second containment layer at the customer dock. Both are billed back to the supplier and remain in place until effectiveness verification (D8) is accepted.

D4 — Identify root cause (5-Why, fishbone, fault tree)

D4 separates the cause of the defect (why the part is wrong) from the cause of the escape (why the plant did not detect it). Both must be addressed. OEM 8D forms have separate fields for occurrence root cause and escape root cause, and reviewers reject 8Ds that fill in only one.

The standard toolkit is fishbone (Ishikawa) for cause categorization across Man, Machine, Method, Material, Measurement, Environment, followed by 5-Why drilling into the most probable branch, supported by fault tree analysis when the failure mode involves multiple simultaneous conditions. PinnacleQMS clients are coached to keep asking "why" until the answer points to a system or process gap, not a person.

Weak 5-Why: "Operator did not catch defect → operator was not trained → corrective action: retrain operator." Strong 5-Why: "Operator did not catch defect → check sheet did not require flange angle measurement at this station → control plan was updated for engineering change but check sheet was not → engineering change procedure does not link control plan revisions to shop-floor work instructions → no system control to ensure document downstream propagation. Root cause: missing system link between control plan and operator instructions. Corrective action: update document control procedure to require linked-document verification before any control plan revision is released."

The second version exposes a system gap that, once fixed, prevents the same escape pattern across hundreds of part numbers. That is what OEM reviewers are looking for.

D5 — Choose and verify permanent corrective action

D5 names the permanent corrective action and demonstrates, before implementation, that it will work. Verification before implementation is the gate that prevents 8D recurrence — the leading reason OEMs reject 8Ds is that D5 was assumed effective rather than proved.

Verification methods include: design of experiments (DOE) confirming that a process parameter change holds tolerance under worst-case input variation; capability study (Cpk ≥ 1.67) on the modified process before it goes live; poka-yoke validation runs intentionally injecting defective input to confirm the error-proof rejects it 100 percent of the time; and PPAP-style production trial run of 300 consecutive parts demonstrating zero recurrence.

D5 also addresses both occurrence and escape. If the occurrence cause was insufficient die maintenance interval, the corrective action is a maintenance schedule change with verification via accelerated wear testing. If the escape cause was a missing inspection step, the corrective action is an updated control plan with verification via attribute gauge R&R on the new check.

D6 — Implement permanent corrective action

D6 turns the verified D5 into operational reality. That means updating every controlled document, training every affected operator, modifying every affected fixture or program, and confirming the change is live on every shift. The 8D documents revision numbers, training records, and effective dates.

A complete D6 record for a control plan change typically includes: PFMEA update (with revised RPN), control plan revision, work instruction revision, operator training sign-off (signature + date for every operator on every shift), gauge or fixture modification with calibration record, ERP routing update, and quality alert posted at the workstation for 30 days. PinnacleQMS clients run D6 through the Document Control and Training modules in the platform so the linkage between the 8D, the revised documents, and the training records is automatic and auditable.

D6 is also the point at which the supplier validates that no customer-line disruption will occur during the cutover. For sequenced parts, the supplier coordinates with the customer's plant scheduler so that the changeover happens between shifts, not mid-build.

D7 — Prevent recurrence (system-level)

D7 is where most 8Ds fail their effectiveness review. D6 fixed the part. D7 must fix the system so the same failure mode cannot occur on any other part number, line, or plant.

The D7 question is: "What other parts, processes, or sites are exposed to the same root cause, and what system-level change closes the exposure?" If the occurrence cause was a die maintenance gap, D7 reviews die maintenance schedules across every die in the plant — and across sister plants if applicable — and updates the maintenance management system. If the escape cause was a missing control plan review trigger, D7 updates the change management procedure so every engineering change forces a control plan and work instruction review.

D7 deliverables are typically: read-across analysis showing every part number reviewed against the same failure mode (with results), procedure or system update with revision number, lessons-learned bulletin distributed to other plants, PFMEA template update so the failure mode is now considered for every new part launch, and APQP checklist update so future programs are screened against this failure pattern.

OEM reviewers read D7 carefully. A D7 that says "We retrained the operator" is a D6 written into the wrong field. A D7 that says "We updated the change management procedure (Doc QM-403 Rev 7), reviewed all 247 active part numbers against the same failure mode (12 flagged for control plan update, all completed), and added the failure mode to our APQP risk template" is a D7 that earns supplier-status credit.

D8 — Recognize team and close out (with effectiveness verification)

D8 closes the 8D after effectiveness verification — typically 30, 60, and 90 days of zero recurrence with documented production volume. The supplier submits final D8 to the OEM portal with: production quantities by lot, customer receiving inspection results, internal SPC charts showing process stability, and any customer line-feedback during the verification window.

D8 also formally recognizes the team. The signed 8D form, with team-member names, becomes part of the supplier's quality history and is referenced during customer audits, sourcing decisions, and Q1/BIQS reviews. PinnacleQMS clients who treat D8 as a real recognition event — not a checkbox — build a problem-solving culture that compounds across hundreds of issues per year.

OEM 8D submission portals (Ford SDR, GM Concern, Stellantis IPM, Toyota TS3, Honda PNCR)

Each OEM operates a dedicated supplier-quality portal with format-specific 8D templates. Suppliers must submit through the portal — emailed PDFs are rejected.

Ford uses the Supplier Deviation Report (SDR) inside the Q1 system, with mandatory fields for occurrence/escape root cause separation and a 60-day effectiveness window. GM uses Supplier Concern in the GlobalConnect portal, integrated with BIQS scoring; missed timing gates auto-deduct BIQS points. Stellantis uses the Issue Problem Management (IPM) module in eSupplierConnect with mandatory D1-D8 sequencing — the portal will not accept D5 if D4 is incomplete. Toyota uses the TS3 (Tiered Supplier Submission System) with strict 24/48-hour gates and direct line to plant quality engineering. Honda uses the Part Non-Conformance Report (PNCR) in the iN portal with a separate continuous-improvement loop after closure.

Suppliers shipping to multiple OEMs need a single internal 8D record that maps to all five external formats. PinnacleQMS clients run a unified Issue Management module that exports OEM-specific templates so the same root cause analysis is not retyped five times.

Common 8D execution failures and how to avoid them

Five recurring failure patterns trip up suppliers across PinnacleQMS engagements:

Jumped to root cause without containment. Engineers love analysis and dislike sort work. The result is a brilliant D4-D5 submitted on day three while defective parts continued to ship for two more days. Containment always comes first; the OEM cares about stopping the bleed before it cares about understanding the wound.

Single root cause for a multi-cause failure. Most field defects have one occurrence cause and one escape cause; some have multiple of each. Forcing every 8D into a single 5-Why chain hides causes that the read-across in D7 then misses. Use fishbone first to enumerate, then 5-Why each branch.

Effectiveness "verified" by absence of complaints. Thirty days with no customer call is not verification. Verification requires documented production volume, internal SPC data, and customer receiving feedback during the window. Suppliers that confuse silence with success see the same defect return at month four.

No read-across in D7. The team fixes the part that failed and ignores the 50 similar parts on adjacent lines. Twelve months later the same failure appears on a different part number, the customer notices the pattern, and the supplier is invited to controlled shipping.

Operator-blame closure. "Retrained the operator" written in D6 with nothing in D7 is the single most common OEM rejection reason. Operators do not write control plans, do not specify gauges, and do not approve PFMEAs. If the system allowed the operator to err, the system is the root cause.

Late submission with no interim communication. The OEM portal clock runs whether or not the supplier is responsive. A D6 submitted on day 32, with no interim notes, costs more BIQS/Q1 points than a D6 submitted on day 35 with daily progress updates from day one.

PinnacleQMS configures the PinnacleQMS Issue Management module against each client's OEM mix so that timing gates, format templates, and read-across triggers are automatic. For automotive suppliers under active SDR/Concern/IPM cases — or planning a Q1, BIQS, or SQ.AS push — contact PinnacleQMS to walk through an 8D maturity assessment. The methodology is documented in AIAG's CQI-20 Effective Problem Solving Practitioner Guide, aligned to the corrective action requirements published by ISO and audited under the IAF MLA framework at iaf.nu.