Customer Complaint Resolution (8D)

SEF Reference Guide G21 | Manufacturing OpEx Maturity Assessment

Supports criteria: PF-1 Customer Issue Resolution (8D is also an accepted method under OB-5 Structured Problem Solving)

Glossary terms covered: 8D, Customer Complaint Resolution Process

How to use this guide. This is SEF's standard method and the numbers we start from. Every operation is different, so treat the targets, timings, weightings, and templates here as a starting point and adjust them to your products, customers, and risk. Write your version down before you measure against it. Do not apply a tool just to apply a tool. Every method here carries a cost in time, attention, and discipline, and the benefit has to justify that cost in your operation. If it does not, leave it out and say why. A lower score on a criterion you have deliberately chosen not to pursue is an honest score, not a failure. One thing should not change: the maturity level definitions, because they are the scoring basis for the assessment.

What it is

A customer complaint resolution process is the standard path every complaint follows from the moment it arrives until it is closed: log it, protect the customer, find the root cause, fix it permanently, and prove the fix worked.

SEF builds this process on 8D (Eight Disciplines), a team-based problem solving method. Ford Motor Company published its Team Oriented Problem Solving manual in 1987; the method is often traced to an earlier U.S. military corrective action standard (MIL-STD-1520), and Ford later added a preparation step (D0) in its Global 8D version. It is now the default complaint format across automotive and much of general manufacturing.

8D works for complaints because it forces two things that firefighting skips. First, it separates protecting the customer today (containment) from fixing the cause (corrective action). Second, it asks not only why the defect was made but also why your own checks let it escape.

Why it matters

Keeps customers. A fast, visible response often does more for the relationship than the defect did damage. A slow or defensive one loses the next order.
Cuts cost of poor quality. Every complaint carries returns, sorting, freight, credits, and engineering time. Repeat complaints double all of it (see G25).
Stops repeat failures. A fix at root cause, with the escape point closed, means the same failure does not come back next quarter.

Key terms

Term	Meaning
8D	Eight Disciplines problem solving. D0 prepare, D1 form the team, D2 describe the problem, D3 contain, D4 find root cause, D5 choose corrective actions, D6 implement and validate, D7 prevent recurrence, D8 recognize the team.
Customer Complaint Resolution Process	The standard, documented process for receiving, containing, investigating, and closing customer complaints, with root cause and preventive action.
Complaint	Any customer statement that a product, delivery, document, or service did not meet what was agreed. Includes warranty claims and field returns.
Containment	Temporary action that protects the customer immediately (sort stock, quarantine, replace, add inspection) while the cause is found.
Occurrence root cause	Why the defect was made.
Escape point (non-detection root cause)	The earliest point in your process where the defect should have been caught but was not.
Systemic root cause	The management system gap that allowed the occurrence and escape (for example, no PFMEA review for new tooling).
Verification and validation	Verification proves, on a trial, that the action removes the cause. Validation proves, after rollout, that the problem is gone in production and at the customer.
Repeat complaint	A complaint with the same failure mode on the same product family within 12 months of a closed 8D.
8D champion	The manager who sponsors the 8D, removes barriers, and signs off closure.

How to do it

The SEF complaint process has five stages and uses the 8D disciplines inside them.

Stage 1: Intake (target: logged within 1 working day)

Every complaint enters one log, no matter who received it. Record customer, part number, quantity, lot or date code, symptom in the customer’s words, photos, and what the customer wants.
Assign a complaint owner (usually a customer quality engineer) and send the customer an acknowledgment with the owner’s name.
Decide the response level. Use a full 8D for safety issues, line stops, repeat failures, or anything the customer requests as an 8D. Use a short form (D2, D3, D4, D5 on one page) for minor, one-off issues. Never skip containment or root cause.

Stage 2: Contain (D0 to D3, target: within 24 hours, 48 hours maximum)

D0: Take emergency action if safety or the customer’s line is at risk. Check whether this is a known issue.
D1: Form a small cross-functional team (quality, production, engineering, and whoever owns the suspected process). Name a leader and a champion.
D2: Describe the problem as facts. Use Is / Is Not: what, where, when, how many. Get the returned parts in hand.
D3: Contain everywhere the defect could be: at the customer, in transit, in the warehouse, in WIP, and at suppliers. Record quantities sorted and found. Send the customer the D0 to D3 report.

Stage 3: Find the cause (D4, target: within 10 working days)

Find the occurrence root cause with 5 Whys or a cause map (see G05). Test it: can you turn the defect on and off?
Find the escape point. Walk the process and ask where the defect should have been detected.
Ask one more why: what in our system allowed both?

Stage 4: Fix (D5 and D6, target: implemented within 30 calendar days)

D5: Choose permanent actions for occurrence and for escape. Prefer error proofing over inspection, and inspection over training alone (see G08). Verify on a trial.
D6: Implement, remove the temporary containment only when the data says it is safe, and validate with at least one full production cycle of good results.

Stage 5: Prevent and close (D7 and D8, target: within 60 calendar days)

D7: Update the PFMEA, control plan, work instructions, and boundary samples. Check sister products and other lines with the same risk (read across).
D8: The champion reviews the evidence and closes the 8D. Thank the team by name. Send the customer the final report.
Review closed complaints 90 days later. If the failure mode returns, reopen the 8D rather than opening a new one.

Roles

Role	Responsibility
Customer service / sales	Passes every complaint to the log the same day. Owns customer communication about credits and replacements.
Complaint owner	Runs the process, keeps the customer informed, meets the time targets.
8D team leader and members	Leader runs D1 to D7 (often the complaint owner). Members bring process knowledge and do the analysis and fixes.
8D champion	Plant or quality manager. Provides resources, removes barriers, approves D8 closure.
Leadership team	Reviews complaint KPIs monthly and sets targets.

KPIs to publish monthly

KPI	Formula
Complaints received	Count per month, and per million units or per 1,000 orders shipped
Customer PPM	Rejected parts / parts shipped x 1,000,000
Containment on time	Complaints contained within 24 (48) hours / complaints received
Root cause on time	D4 completed within 10 working days / complaints due
Average days to close	Sum of days open for closed complaints / number closed
Fixed on time	D6 completed within 30 days / complaints due
Repeat complaint rate	Repeat complaints / complaints received (rolling 12 months)
Open and overdue	Count of open 8Ds past any stage target
Cost of complaints	Credits, returns, sorting, freight, and labor per month (feeds COPQ)

What each maturity level looks like

PF-1 Customer Issue Resolution

Level	Assessment wording	What it looks like on the floor	How to move up
1	No process for resolving customer issues.	Complaints live in individual inboxes. Sales promises a fix, production hears about it later. Nobody knows how many complaints came in last month.	Start one complaint log. Name a complaint owner. Adopt the 8D form.
2	A formal customer complaint resolution process (such as 8D) is used and performance statistics are published.	Every complaint gets a number and an 8D. A monthly chart shows complaints received, open, and closed.	Put the complaint KPIs on the leadership meeting agenda. Set targets for response time and repeats.
3	As Level 2, plus leadership reviews performance and sets improvement targets.	The leadership team reviews complaint trends every month, asks about overdue 8Ds by name, and has written targets (for example, containment within 24 hours on 95% of complaints).	Use the complaint Pareto to pick the top failure modes for dedicated improvement projects.
4	As Level 3, plus structured problem solving projects focus on customer issues.	Beyond single 8Ds, A3 or DMAIC projects attack the biggest complaint categories (for example, packaging damage across all products). Project status is on the boards.	Sustain the projects, track results against a 12 month baseline, and drive repeat complaints down.
5	As Level 4, plus trends are good and stable or improving.	Twelve or more months of data show complaint rate, PPM, and days to close holding at a good level or improving. Repeats are rare and investigated as system failures.	Keep raising targets. Share the method with suppliers and other sites.

Evidence to look for

Document

Written complaint procedure with stages, roles, and time targets.
Complaint log covering the last 12 months, with every entry closed or active.
A sample of 3 to 5 completed 8D reports: check that D3 has quantities, D4 has both occurrence and escape root causes, and D7 shows updated PFMEA or control plan.

Observation

Quarantine area with returned parts labeled and linked to a complaint number.
Complaint KPIs posted where the team can see them.
A changed control (poka-yoke, new check, updated instruction) that you can trace back to a closed 8D.

Statement (questions to ask and who to ask)

Customer service: “When a customer calls with a problem, what happens next? How long until they hear back?”
Complaint owner: “Show me your oldest open complaint. What is stopping it?”
Operator on a line with a recent complaint: “Did anything change at your station because of it?”
Plant manager: “What were your top three complaint causes last quarter, and what are you doing about them?”

Management report

Monthly quality report showing complaint count, PPM, response times, and repeats, with targets.
Trend charts for at least 12 months (needed to judge Level 5).

Common pitfalls

Containment treated as the fix. Extra inspection added at D3 becomes permanent. The cost stays and the cause stays.
Root cause is “operator error.” People make mistakes because the process allows them. Ask why the process allowed it, and find the escape point.
The 8D is written for the customer, not for the plant. A polished report with no change on the floor is paperwork. Check that D7 changed something real.
Complaints bypass the log. Sales handles a “small” issue with a credit and never tells quality. The data then understates the problem.
Closing on time instead of on evidence. A D8 signed before validation data exists is a guess.

Template

SEF 8D Report Outline

(copy into your document system or spreadsheet)

Section	Content required
Header	Complaint no., customer, customer reference, part no. and revision, date received, date closed, complaint owner, 8D champion
D0 Prepare	Emergency actions taken, safety check, known issue check, full 8D or short form
D1 Team	Names, functions, team leader, champion
D2 Problem	Customer description, Is / Is Not table (what, where, when, how many), photos, returned part findings
D3 Containment	Locations checked (customer, transit, warehouse, WIP, supplier), quantity checked and rejected per location, date contained, how contained stock is marked
D4 Root cause	Occurrence root cause, escape point, systemic cause, method used (5 Whys, cause map), verification evidence
D5 Actions chosen	Permanent action for occurrence, permanent action for escape, verification trial results
D6 Implement and validate	Implementation date, containment removal date and rationale, validation data
D7 Prevent recurrence	PFMEA updated (Y/N), control plan updated (Y/N), work instructions updated (Y/N), read across to other products or lines
D8 Recognize and close	Team recognition, champion sign-off, date sent to customer, 90 day recurrence check date

First 30 days

Week 1: Collect every complaint from the last 12 months from email, sales, service, and quality. Put them in one log. Count them and sort by failure mode.

Week 2: Write a one-page procedure using the five stages above. Name complaint owners and a champion. Agree the time targets with the plant manager.

Week 3: Train the owners and team leaders on the 8D report outline. Run the next incoming complaint through the full process as a pilot, with the champion attending D4.

Week 4: Publish the first KPI chart. Add complaint review to the monthly leadership meeting. Pick the top failure mode from the Pareto as the first improvement project.