Skip to content
Complaint Management | Part 6 of 6

Complaint Rate, Lead Time and Repeat Cases

Five figures that run a complaint process, twelve months of real movement, and the rule that turns a closed case into a changed document.

A complaint count on its own says nothing. Five complaints in a month is good news for a plant that ships 400 deliveries and bad news for one that ships 40. Measure against a volume figure, and measure the two things that are entirely in your own hands: how fast you answer and how often the same fault comes back.

Five figures

Key figure Formula Baseline After twelve months
Complaint rate Complaints / deliveries x 100 2.0 1.0
Complaint ppm Parts rejected / parts shipped x 1,000,000 800 300
Lead time to the answer Working days from intake to the answer sent 19 8
Answers on time Answers by the agreed date / answers sent 42 % 92 %
Cost per complaint Cost of the cases / number of cases EUR 3,200 EUR 2,850

All five come out of one register. If you cannot produce them in ten minutes, that is the first finding of the month.

Twelve months

Period Cases Per 100 Repeat Days EUR total
Baseline year 96 2.0 31 % 19 307,200
Quarter 1 26 2.2 31 % 18 83,200
Quarter 2 21 1.8 24 % 14 63,000
Quarter 3 16 1.3 19 % 11 46,400
Quarter 4 12 1.0 8 % 9 34,200

The lead time moves first, because it needs organization and no engineering. The complaint rate follows two quarters later, when the first corrective actions are verified. At the end the plant runs at 48 complaints per year instead of 96, and at EUR 136,800 instead of EUR 307,200.

Read the causes two ways

Group the cases by cause and you get the usual picture: dimensions out of tolerance 28 cases, documentation and labeling 17, surface and weld appearance 15. Three groups carry almost two thirds of the cases.

Now group the same cases by cost. Dimensions are 29 percent of the cases and 42 percent of the cost. Missing operations are 8 percent of the cases and 18 percent of the cost, because they stop customer lines. The two lists do not have the same order, and the second one decides where the engineering time goes.

Repeat cases get a different conversation

A first case is a fault. A repeat case is a process that did not learn. Count repeats per part and per cause, and treat them differently:

  • A repeat case goes to the plant manager meeting, not back to the person who closed the first one.
  • Look at the first case first. Was the action ever in place, was it verified, was the document changed, was the training done?
  • Ask about the escape point again. A repeat almost always means the first analysis stopped at the cause.

Four parts carried 27 of the 96 complaints and 12 of the 30 repeat cases. Those four got the gauges, the fixture work and the boundary samples.

Where the learning has to land

A case is not closed by an answer. It is closed when something in the plant is different, and the difference is visible in a document: a characteristic or a reaction in the control plan, a limit and a photo in the work instruction, a wear limit in the setup sheet, a count check in the packing instruction, a line in the training record. If no document changed, nothing changed.

The monthly review

Thirty minutes, one page, three questions every time. Are we in control of the open cases: open cases by class, cases past their due date, the oldest case. What is the pattern: cases per cause group and per part, repeat cases. What did it cost and what did we change: cost of the closed cases, actions verified this month. Each question ends with one decision, and the first one ends with an owner or a new date for every case that is past due.

Newsletter

One Lean idea.
Every two weeks.