8D :CORRECTIVE ACTIONS REQUEST

Claim N° : Quality Matters №: Issued Date :

D0 - CA Information

Issuer : RTS №: Issuer Email :

Supplier : Addressee of the 8D :

Location of the Supplier :

Part Number : Part Description :

Supplier Part № : Serial № :

Order № : Delivery № :
Team Created To Solve The Problem
D1 - Team

Name Department
Leader : Member 2:

Member 1: Member 3:
Description Of The Problem (Explain WHAT is the problem, WHY it is a problem, WHEN and by WHOM it has been discovered)

Recurrent Problem ? YES NO Comments :

Products Affected ?
D2 - Issue / Concern

(Photo/Sketch) (Photo/Sketch)

Containment Actions (within 24h)

Details:

ISOLATION OF POTENTIAL FAULTY PRODUCTS Comments (mandatory if answer No) & Qty if yes
AT CUSTOMERS YES NO
D3 - Containment Actions

WORK IN PROCESS YES NO

IN SHIPPING YES NO

ITEMS IN STOCK YES NO

AT SUPPLIERS YES NO

Potential faulty products in TRANSIT YES NO Delivery № ? :

 D3 - Containme DELIVERY OF FAULT - FREE PRODUCTS details of the delivery (new parts or part sorted out, several deliveri

Date Qty Delivery № ? :

Indicate date of shippment & qty shipped

Markings on delivered OK parts ? YES Description of the marking:

OTHER POSSIBLE IMPACTS OF THE PROBLEM

Indicate if the problem could have impact : On the safety ? : YES NO On the environment ? :

If answer is yes, please give details :

Root Cause(s) Of The Occurence

Details:
D4 - Root Cause

Root Cause(s) Of Non Detection

Details:

Corrective Action(s) Retained

D5 - Corrective Actions

Details:

Planned Implement. Date ? : By Whom ? :

Implementation Of The Corrective Action And Controls
CA Implementation

Details:
Indicate which controls (with records)
have been put in place to verify the
efficency of the corrective action:
D6 -

Preventive Action(s) To Prevent Recurrence Of The Problem ?

Details:

Describe specific preventive

actions :
entive Actions

Date:
 D7 - Preventive Actions Can this problem occur on other If yes, describe what, who is taking care and
YES NO
Products or processes ? when ?:
Comments :

Review existing FMEAs ? YES NO

Review existing Engineering documents? YES NO

Review work instructions & control plan? YES NO

Review existing Procedures ? YES NO

New documents Customer approval ? YES NO

Validation Of The Answer + Implementation & Effectivness Verification

D8 - Handicare Validation

D8a :Initial validation of Root cause Approved ? Comments :

research & of corrective/preventive
actions (D3 -> D7) by issuer YES NO

Verification of Implementation - by whom ?

Efficiency check - by whom ?
Comments :
8D closure - by whom ?
Comments (other documents to close)

Document completed (as described in sheet "how to fil the 8D") to be returned within 10 days to the issuer identified in § D
REQUEST

Quantity :

Rejected

Reworked by Handicare

Concession /
Concession № №:

Name Department

WHOM it has been discovered)

(Photo/Sketch)

Date :
mandatory if answer No) & Qty if yes

Quantity ? :
ew parts or part sorted out, several deliveries ?)

Product Serial № ? :

YES NO

Date :

Date :

Serial № ?:
Batch № ?

Date :

Implement Date:
Batch № ?
Serial № ?
Delivery № ?
 Implement. Date:

Implement. Date:

Implement. Date:

Implement. Date:

Implement. Date:

Name Date

Date :
Date :

Date :

hin 10 days to the issuer identified in § D0

5/16/2016
 What
Who
(8d How
has to fill in
section)

Fill in all the fields of this section (do not forget the claim Nr and the
Issuer D0
issuing date)

Indicate the name and the dpt of the 4 main persons who have been
receiving
D1 designed to solve this NC and particularly the team leader
company/dpt
(responsible for achievement)

Describe clearly and shortly the problem in indicating What is the

problem, why it is a problem, When and by whom it has been
discovered and explaination of the Qty given on D0.
Issuer D2 Indicate (in dedicated fields) if the problem is recurrent (with
possible comment about recurrence)
2 photos/sketch explaining the problem can be added in the
foreseen fields of this section D2

Indicate all actions necessary to stop extension of the revealed

dysfunction (for example, blocking the production / delivery,
blocking / recall of stock, customers information, etc ...) and to avoid
any production stop due to the issue of this 8D.in indicating :
Details of the next deliveries fault-free (When they will be shipped,
what quantities, if it is sorting from the faulty batches or a new
production, what special marking(s) is made on the products of the
new deliveries to distinguish their products from the risky or faulty
ones not under control.

receiving Indicate, in the dedicated field, which special marking has been
company/dpt D3 defined and applied on the products which have been corrected or
(team leader) which have been proved as free of the dysfunction.
Tick "yes" or "no" on all questions for the quarantine of possible
faulty products in giving a comment when answer "no" is ticked
(mandatory)
Do not forget to answer also to the question concernng possible
impact on safety or environement. Tick Yes or No and give details if
Yes.
These emergency measures should be defined and communicated
to the issuer of 8D within 24 hours after issuing date (unless
otherwise agreed with the issuer of the 8D)
 Indicate in this field the real root cause(s) of the problem. This root
cause(s) has to be searched (and validated) in using one or several
quality tools, like 5 why, Cause&Effect analysis, Is-Is not, …For your
research of root cause, use the list of possible sources of fault
receiving indicated at the top of this section (People ?; Material ? Methods ?
company/dpt D4 Equipment ? Measurement ? Environment ?) and tick the one(s)
(team leader) linked to the root cause(s) retained.
The validity of the finding of the real root cause(s) will be quoted by
the issuer.
After searching the real root cause of the problem, pass to the section
D4b for the root cause of non-detection of the problem

Indicate in this field the real root cause(s) of the non-detection of

the fault before delivery of the product. As for D4 This root cause(s)
has be searched (and validated) in using one or several quality tools,
like 5 why, Cause&Effect analysis, Is-Is not, …For your research of
receiving root cause, use the list of possible sources of fault indicated at the top
company/dpt D4b of this section (People ?; Material ? Methods ? Equipment ?
(team leader) Measurement ? Environment ?) and tick the one(s) linked to the root
cause(s) retained.
The validity of the finding of the real root cause(s) will be quoted by
the issuer.
After searching the real root cause of the problem, pass to the section
D4b for the root cause of non-detection of the problem

Indicate in this section the corrective actions decided to solve the

problem.
receiving
At the bottom of this field, indicate (in the dedicated fields, the
company/dpt D5
date(s) planned for the implementation of the corrective action(s) as
(team leader)
well as the owner of this implementation and the batch nr on which
the first implementation will be done

receiving Indicate which control(s), with records, are put in place to verify the
company/dpt D6 efficiency of the corrective action(s) described on D5 . The records of
(team leader) these control will have to be at the disposal of the 8D issuer

Indicate in this section the preventive actions decided to prevent

recurrence of the problem or of this type of problem on all products
and processes which can be affected. (not only on the product or the
process object of this 8D).
receiving
In most of the cases, the documentations of the QMS will have to be
company/dpt D7
updated in order to prevent recurrence (e.g. : new risks have been
(team leader)
highlighted => FMEAs need to be updated) : Indicate the updates of
all documentations listed in this section in ticking the right answer
(yes or No), indicating the date of the update and in giving
comments if necessary : these informations are not optional.
 The issuer of the 8D has to check the validity of the answers given in
sections D4 to D7. If the root cause(s) researchs and/or the
corrective & preventive actions are judged incomplet to solve the
problem permanently, he has to tick "NO" at the question validated,
to put the reason of "NO" in dedicated field, and put his name and
Issuer D8a
date of this refuse ; afterwards, he returns the 8D to the supplier
asking for complementary actions / updates
If the issuer is satisfied with the answer, he ticks "YES" at the
question "validated", puts his name and date and records the answer
for further follow-up.

The issuer of the 8D must ensure, within a reasonable time after the
date planned, the implementation of actions, The audit will be
recorded in this section in the relevant fields.
Similarly, it should verify, a few months later (and no later than
within the next fiscal year) the efficiency of the actions and record
Issuer D8 (rest) this validation (including any comments) in this section in the
relevant fields.
For 8D to supplier, these verification can be done by at least 3
consecutive incoming good controls without any fault.
After these 2 audits, the 8D must be closed by signing and dating the
relevant fields
when

Immediatly when
NC is confirmed

24h after 8D
issuing date (with
D3)

At the same time

as D0 (Immediatly
when a NC is
confirmed)

24 hours after 8D
issuing date
Answers of D4,
D4b, D5, D6& D7
to be sent to the
issuer within 10
days after 8D
issuing date

Answers of D4,
D4b, D5, D6& D7
to be sent to the
issuer within 10
days after 8D
issuing date

Answers of D4,
D4b, D5, D6& D7
to be sent to the
issuer within 10
days after 8D
issuing date

Answers of D4,
D4b, D5, D6& D7
to be sent to the
issuer within 10
days after 8D
issuing date

Answers of D4,
D4b, D5, D6& D7
to be sent to the
issuer within 10
days after 8D
issuing date
Directly after
receiving the
complete answer
fo the 8D

at latest during
next FY after 8D
issuing
 5 WHY
1 2
WHY: WHY:

WHY: WHY:

WHY: WHY:

WHY: WHY:

WHY: WHY:

DATE:

RESP.
Y
3
WHY:

WHY:

WHY:

WHY:

WHY:

DATE: DATE:

RESP. RESP.
 4
WHY:

WHY:

WHY:

WHY:

WHY:

DATE: DATE:

RESP. RESP.
How to Complete the 5 Whys
1. Write down the specific problem. Writing the issue helps you formalize the problem and
describe it completely. It also helps a team focus on the same problem.
2. Ask Why the problem happens and write the answer down below the problem.
3. If the answer you just provided doesn’t identify the root cause of the problem that you wrote
down in Step 1, ask Why again and write that answer down.
4. Loop back to step 3 until the team is in agreement that the problem’s root cause is identified.
Again, this may take fewer or more times than five Whys.