A rejection note, and a deadline
The customer's quality engineer emails a rejection: twenty parts returned, thread gauge no go on the M6 tapped holes. They want containment within two days, an initial 8D within a week and the full report with root cause and corrective action within a month. Their form is attached.
The quality manager now has to find the job, the inspection records, which operator and machine ran it, whether the tap was changed, whether other batches used the same tap, and what stock is still on the shelf or in transit. That is before the actual investigation starts.
Why complaints stall
Root cause analysis is a thinking job. The problem is the gathering that comes before it. In most shops the job record, the check sheets, the tool usage and the dispatch notes all live in different places, some on paper.
- Complaints arrive by email and are tracked in someone's inbox.
- Evidence is spread across the MRP, paper check sheets and folders.
- Containment actions, such as checking stock and parts in transit, are not recorded.
- 8D steps have no owners or due dates, so they drift.
- Every customer wants the answer on their own form.
What late replies cost
Customers score suppliers on how quickly and how well they respond to rejections. A late or thin 8D can hurt your rating as much as the defect. Open complaints also tie up the quality manager for weeks, and corrective actions that are agreed but never completed tend to cause the same problem again.
The complaints and 8D log we build
- A rejection email or portal notification opens a case, with the customer, part number, revision, quantity, defect and the customer's reference.
- The case pulls in the job history automatically: batch, dates, machine, operators, program version, material certificate, inspection records and dispatch notes.
- A containment checklist lists other batches of the same part in stock, in work and in transit, so each can be checked and the result recorded.
- The 8D steps are laid out with an owner and due date for each. Reminders go out as dates approach.
- An AI step drafts the problem description and the timeline from the gathered evidence. The quality manager writes the root cause and corrective actions, which stay a human judgement.
- The reply is produced on the customer's own form, and the case stays open until corrective actions are checked as done.
| 8D stage | What the log provides |
|---|---|
| Describe the problem | Customer details and job history in one place |
| Containment | Checklist of stock, work in progress and transit |
| Root cause | Evidence gathered; analysis by your team |
| Corrective action | Owners, dates and reminders |
| Verify and close | Follow up checks recorded against the case |
How complaint handling feels afterwards
The quality manager starts from a case file rather than an empty form. Containment is recorded as it is done, which is what the customer's first question will be about. Corrective actions do not quietly lapse. Over time the log shows which parts, machines and processes cause repeat complaints, which is a better place to spend improvement effort than wherever the last complaint happened to be.
It also helps when a customer's supplier development engineer visits. Instead of a folder of replies, you can show every rejection in the last year, how quickly each was contained, what the cause was and whether the corrective action held. That is a stronger conversation than one about a single bad batch.
Is your 8D process slower than it should be?
- Complaints are tracked in an inbox or spreadsheet.
- Gathering evidence takes longer than the investigation.
- Customers chase you for 8D replies.
- Corrective actions are agreed and then forgotten.
- Each customer's form is filled in from scratch.