Skip to content
Complaint Management | Part 3 of 6

From Complaint to Corrective Action: Two Causes, One Proof

How the complaint process hands a case to your problem solving method, why every complaint has two causes, and when an action counts as verified.

This is the point where the complaint process hands the case over. The analysis itself belongs to the problem solving standard of your plant, whether that is a structured eight step report, a cause and effect sketch with a few why questions, or something your customer requires. The complaint record points to the analysis, it does not repeat it.

What the complaint process still owns is the handover in both directions.

What the complaint process owes the analysis What the analysis owes the complaint process
The intake record with the real finding and the quantities A cause in one sentence that a reader outside the plant understands
The bad parts, kept and marked, and the sorting results The escape point: why the fault left the plant
The lot history, the settings and the records of that day One action per cause, with an owner, a date and the document it changes
A deadline that comes from the class, not from the analysis Evidence that the action works, with quantity, result and date

Two causes, not one

Every complaint has two. The first explains why the fault happened. The second explains why nobody found it before the parts left the plant. Answering only the first is the most common reason for a repeat case.

In case CPL-2026-012 the analysis at the drilling station took half a day with the setter, the toolmaker and the quality engineer.

Question Answer in this case
Why did the fault happen? A locating pin in the drilling fixture had worn down, so the bore moved by 0.8 mm over the run
Why did it leave the plant? The setup check measured the first part only, and there was no gauge for the pin itself
What changes the first cause? Hardened pin, a wear limit in the setup sheet, replacement at a planned interval
What changes the second cause? A pin gauge at every setup and a check of the bore position on the last part of the run

Four actions, two owners, two changed documents. Nothing in that list needed a project, and nothing in it depends on somebody remembering to be careful. If an action only works when a person remembers it, the action was the fault.

How much analysis a case deserves

Match the effort to the class. An S3 case about a scratch does not need a full structured report, and forcing one teaches the team that the method is paperwork. A case with safety relevance, a case that stopped a customer line and every repeat case deserve the full analysis of your standard, with the team in the room where the part was made.

Look for the cause where the part was made, with the people who made it. A cause written at a desk from a production order usually names a person. A cause found at the machine names a condition that can be changed.

Verified, not reported

An action is done when it is in place and verified when somebody has seen it work on real parts. Write both into the action line: what was checked, how many, the result, the date and who checked.

In the example the pin gauge was verified on 300 parts from the next three runs with no deviation, 23 working days after the complaint arrived. The case closed on that date, not on the day the answer was sent. That single rule, a case closes only when the action is verified, moved the repeat share of the plant from 31 percent of complaints in the baseline year to 8 percent in the last quarter of the program.

Keep the action list in one place

Every corrective action from every complaint belongs in one list with the cause group, the document it changes, the owner, the due date and a status from open to verified. Twelve actions came out of the first six complaints in the example, seven of them verified within three months. That list, not the stack of reports, is what a customer auditor should see first.

Newsletter

One Lean idea.
Every two weeks.