8D report

Fill in the nine disciplines below. The form saves itself in this browser as you type; nothing is sent anywhere. Print it or save it as a PDF when the report is ready, or copy it as text. Not sure what belongs in a box? See what each discipline must show.

8D report no.Date openedLast updatedCustomerCustomer complaint / reference no.Part numberPart nameSupplier / sitePrepared by

Status

D0 Emergency response

Protect the customer the same day, then decide whether a full 8D is needed.

Symptom as reportedCustomer impact

Emergency response actions
Action	Owner	Date	Result

Full 8D required?

Customer notified onNotified by

D1 Establish the team

A small, dedicated team: a leader who drives the investigation, a sponsor who removes roadblocks and keeps the customer informed, experts only when needed. Review the team at the start of each discipline.

Team
Role	Name	Function / title	Contact (phone, email)
Sponsor
Team leader
Member
Member
Member
Member

D2 Describe the problem

One failure mode in measurable terms: what is wrong with what, where it is first seen, since when, how many parts, what it costs.

Problem statementWhere first observed (discovery point)Effect at the customer

IS / IS NOT
	IS	IS NOT
What
Where
When
How many

Parts affectedParts produced in the same periodShare affected, %Impact: quality, reliability, productivity, cost

Failure mode listed in the FMEA / control plan?

Recurring problem?

Evidence attached

D3 Interim containment

Sort suspect parts as far upstream as possible, on a criterion that demonstrably predicts the customer’s experience, and name the breakpoint from which shipments are clean.

Sorting criterion

Measurement system checked for the sort?

Checked on

Containment actions
Action (sort, 100% inspection, rework, certified stock)	Process step / location	Owner	Implemented on	Effective?

BreakpointParts inspected / rejected so far

D4 Root cause and escape point

The cause–effect relationship that explains the difference between good and bad parts, proved by switching the problem on and off — and the control that should have caught it.

Root causeVerification: how the cause was proved

Root cause verified?

Verified onMethods usedEscape pointSystem cause

D5 Choose and verify the permanent corrective action

Set a tolerance or control for the proven cause, choose the action with the people who will live with it, and show in a trial that it improves the output before it is implemented.

Corrective actions
#	Corrective action	Addresses	Owner	Planned date	Verification before implementation	Verified?
1
2
3
4

Tolerance or setting for the cause, and how it will be controlledExpected effect

D6 Implement and validate

Implement as a project, prove the effect with a before-and-after run chart, update standard work, and remove the containment once it stops finding suspect parts.

Implementation
#	Action	Implemented on	Validation evidence (run chart before/after, capability, audit)	Result
1
2
3
4

Containment removed onDefect-free production fromCustomer concurrence

D7 Prevent recurrence

Fix the system that allowed the cause, update the documents, and read across to similar products, processes and plants.

Systemic change

Read-across
Similar product / process / site	Action	Owner	Date

Documents updated
Document	Change	Owner	Date
Process FMEA
Control plan
Work instructions
Inspection standard
Drawing / specification
Training records
Other

Lessons learned

D8 Close and recognize the team

Record the business result, recognize the team, and get the customer’s sign-off.

Results achievedTeam recognition

Sign-off
Role	Name	Signature	Date
Team leader
Sponsor
Quality manager
Customer representative

Date closed

Customer sign-off received?

8D report template · 8dtemplate.com/ · Stuck at D4? Talk to a Shainin expert: shainin.com/contact-us

What you type stays in this browser’s local storage until you clear the form. It is never sent to us or to anyone else. About the template