This playbook is for suppliers in automotive, aerospace, medical devices, electronics, food, and general manufacturing. Whether your customer calls it an 8D, a SCAR, or a CAPA response, the steps are the same. Their form and deadline come first. If the 8D answers an audit nonconformity, also see how to answer an audit finding with an 8D.
First day: protect the customer, then read
- Confirm containment is still running. A rejected report doesn’t pause the sort, the hold, or the extra check.
- Note the resubmission deadline.
- Copy every comment into one list: portal notes, email, and marks on the PDF.
- Ask your customer contact about any comment you don’t understand.
Build a response matrix
Give every comment one row: the comment in the customer’s words, the section it affects, and what changes. Rows below are illustrative.
| Customer comment | Section | What changes |
|---|---|---|
| “Root cause not verified.” | D4 | Add the test that reproduced the defect and the result with the cause removed |
| “How did this escape?” | D4, D5 | Add the escape cause and a detection action with its own owner and date |
| “Other lots and sites not covered.” | D3 | Add every location, quantity checked and NOK, and the break point |
| “Training is not a permanent action.” | D4, D5 | Name the process or detection change; keep training as support |
| “Effectiveness not shown.” | D6 | Add data after implementation, or the date results are due |
Then sort the rows. Completeness gaps mean the work exists but the report doesn’t show it; add the numbers and the evidence. Engineering gaps mean the analysis stopped too early; start those first. For the full list, see why customers reject 8D reports.
Common reasons and how to fix them
The examples are illustrative, not from real cases.
The cause is a person
Electronics (illustrative): “Operator placed the reel in the wrong feeder.” The reviewer asks why the line allowed it.
Fix: Find the condition that made the mistake possible, then fix that. Guide: Why operator error is not a root cause
No escape cause
Food (illustrative): the report explains the foreign body but not why the metal detector or final check didn’t catch it.
Fix: Write where the defect should have been caught and why it wasn’t. Guide: The escape point in 8D
Containment has gaps
Medical devices (illustrative): stock at the plant was held, but sterilized lots at the distributor were not mentioned.
Fix: List every location with quantity checked, NOK, and the break point. Guide: 8D containment actions examples
D5 is really containment
Aerospace (illustrative): “Added 100% torque audit at final inspection” listed as the permanent action.
Fix: Keep the audit in D3; in D5, change the process or the detection method. Guide: 8D corrective action vs containment
Most of these trace back to D4, so fix it first. See how to write D4 root cause.
Reworked the sections? Get a free Accept / Conditional / Reject advisory on the revised pack, with the gaps that are still open named, before you resubmit.
8D Gate is a free pre-send readiness advisory. It doesn't replace the customer's decision. We don't store your 8D body in our database; you can delete anytime. Anthropic processes the text for the review.
Rewrite sections, not sentences
Adding one line to D4 rarely answers a rejection. When D4 changes, D5 and D6 usually change with it.
- Raise the revision number and date, and keep the rejected version on file.
- Add a short change log at the top: comment, section, what changed.
- Put the evidence in the body: method, sample size, result.
- Give each new action an owner and a due date. If D6 data isn’t in yet, say when it will be.
To compare a thin draft with a fuller one, read the 8D report example. If the report is hard to repair, restart from the English 8D template (.docx).
Before you resubmit
- Every comment has a row in the matrix and a visible answer.
- Occurrence and escape causes are both named and verified.
- Each verified cause has a permanent action, not only training or inspection.
- Containment stays in place until D6 shows the fix works.
- Numbers, dates, and status match across D2, D3, D6, and D8.
- Someone who didn’t write it has read it as the customer would.
FAQ
- Should we argue with the rejection?
- If a comment is wrong, say so in the response matrix and show the evidence. Leaving it out reads as if you missed it.
- Do we send a new report or mark up the old one?
- Follow your customer’s portal or form. A new revision with a change log is usually easier to check than margin comments.
- Our customer calls it a SCAR or CAPA response, not an 8D. Does this still apply?
- Yes. The questions are the same: what happened, what is protected, why it happened and escaped, what changed, and how you know it works.
Free pre-send readiness check
Before it goes back, run the revised pack through the free supplier 8D readiness check.
Paste text or upload PDF, DOCX, or Excel. You get an Accept / Conditional / Reject advisory, a score, section ratings, missing evidence, and questions to close gaps, with a PDF download. It is a pre-send readiness check for your team, not a customer decision.
8D Gate is a free pre-send readiness advisory. It doesn't replace the customer's decision. We don't store your 8D body in our database; you can delete anytime. Anthropic processes the text for the review.
Get the free 8D / D4 checklist
Keep the one-page version next to the response matrix. It covers D1–D8 and goes deeper on D4 occurrence, escape, and verification.
Get the free 8D / D4 checklist