A customer complaint log entry should answer six questions in the first ten minutes: what part and lot, how many shipped and how many affected, what the customer saw, when it was received and found, what the customer expects and by when, and who owns the answer. Give the complaint a number (here RMA-031) that every later record carries.
It's 7:40 on a Tuesday morning. An email lands in the quality inbox. A customer found scratches across the finish on 14 of the 200 housings you shipped last week. They want an answer by Friday.
Most plants treat this as one problem. Call the shipping department, check the stock, send an apology. By Friday the email is answered and everyone moves on.
Look at what that single email has set off. The complaint record itself. A containment and corrective action report. A root cause analysis. A risk document that missed this. A control plan that didn't catch it. A work instruction that needs to change. An audit that should have seen it. And a check weeks from now to prove the fix held.
That is eight steps from one email. This book follows one complaint through every step, one chapter per step, with the tools that go with each.
Why the first record matters most
Every document after this one will lean on what you write in the first ten minutes. If the first record says "customer unhappy with finish," the root cause team will spend a week guessing. If it says "14 of 200, scratches on the top face, lot 2417, received Oct 6, found at their incoming inspection," they start with facts.
A good complaint record answers six questions the same way every time:
- What part and what lot?
- How many were shipped, and how many are affected?
- What exactly did the customer see?
- When was it received and when was it found?
- What does the customer expect, and by when?
- Who owns the answer?
Give the complaint a number at the top. In this book it's RMA-031. Every record that follows will carry that number, and it becomes the thread you pull to see the whole trail.
The mistake to avoid
Logging the complaint after the fix. By then the log is a history report instead of a starting point, and the details of what the customer actually saw are already blurred. Log it first, even if the entry is rough. You can improve an entry. You can't recover a detail nobody wrote down.
- Pull your last three customer complaints.
- For each one, check whether the part, lot, quantity, what the customer saw, and the due date are written in one place.
- If any live only in an email, move them into your log today.
Related on ShopFloorOps
The plant, the part and the complaint in this book (RMA-031) are a made-up example. The tool sidebars show ShopFloorOps tools, which I make and sell. Every chapter teaches the step itself, so you can use your own forms.