Quality and inspection

Non-conformance reports and 8D: containment, cause and closure

The fields that make an NCR usable, the containment that protects the customer, and the eight disciplines that stop the same defect returning.

QKQumek Quality Desk··9 min read·Updated
A⌖ 0.05

Key takeaways

  • An NCR records one nonconformance; an 8D is the process used when the cause is not obvious or the risk is significant.
  • Containment has to cover stock, transit, work in progress and the customer, not just the finished goods in the warehouse.
  • Root cause and escape point are two different questions, and both need an answer.
  • A finding is closed by evidence that the action worked over time, not by a meeting or a promise.

The report and the process are different

A non-conformance report records a single event: what was required, what was found, where it was found, how much is affected and what happened to it. The 8D is the problem solving process that follows when the cause is not obvious or the risk is significant. The two documents serve different purposes and should not be merged into one form.

An NCR without a disposition is an open hole in the system. An 8D without an NCR has no factual base. Keep the NCR short enough to be completed at the point of detection, and put the analysis in the 8D.

The fields that make an NCR usable
FieldWhat it recordsWhy it matters
Part and revisionThe drawing and the level that was madeSeparates a design issue from a process issue
RequirementThe specification or drawing calloutShows what the part was supposed to do
Actual resultThe measurement or the observed defectMakes the gap visible and testable
Lot and quantityThe lot code and the affected quantitySets the containment boundary
Detection pointWhere and when the defect was foundIdentifies the escape route
ContainmentWhat was done to protect the customerPrevents further use before the fix
DispositionAccept, reject, rework, return or use as isCloses the material question with a signature
Owner and dateWho is responsible and by whenMakes the next step traceable

A photograph and a measurement are stronger than an adjective. Write what was measured, not that the part looked bad.

Containment in the first day

Containment protects the customer while the cause is unknown. It has to cover stock at the supplier, stock in transit, stock at your warehouse, work in progress and product already at the end customer. The instinct is to sort the finished goods and stop there, which leaves the other locations open.

Write the containment as quantities: how many pieces were checked, how many were found, where they are, who checked and where the cutoff sits. A statement that all suspect stock was sorted is a conclusion, not evidence. The sort record should let someone else repeat the check.

Containment is temporary. It adds cost and fixes nothing. Leaving it in place after the cause is removed hides the real process and trains the line to inspect around a problem.

The eight disciplines

The eight disciplines give a problem a sequence. The value is not the numbering. It is that each step produces something the next step can use.

  1. 01

    D1 Team

    Name a cross functional team, a leader and a sponsor. Include the process owner and the person who can change the process.

  2. 02

    D2 Problem

    Describe the part, lot, requirement, actual result, quantity and detection point. Use data, not opinion.

  3. 03

    D3 Containment

    Protect the customer at every location, verify the sort and record the quantities.

  4. 04

    D4 Root cause

    Explain why the defect was made and why it escaped. Verify the cause against the evidence.

  5. 05

    D5 Corrective action

    Choose actions that remove the cause, with an owner, a date and a way to test the result.

  6. 06

    D6 Implementation

    Implement, validate and check that the action did not create a new failure mode.

  7. 07

    D7 Prevention

    Update the PFMEA, control plan, work instruction and training, and check similar parts and lines.

  8. 08

    D8 Closure

    Confirm effectiveness over a defined period, record the evidence and close the file.

Root cause that survives a challenge

A root cause has to explain the evidence, not just be plausible. Use the five whys to move from the defect to the process condition, and a cause and effect list to widen the search across machine, method, material, measurement, people and environment.

Then test the cause. Turn it on and off, check the data, and look at the lots that passed. A cause that cannot be demonstrated is a hypothesis. The 8D should show how it was verified, not only how it was found.

The escape point

The escape point answers why the customer saw the defect. It might be a sampling plan that could not detect the feature, a gauge that was out of calibration, a control plan that omitted the check, or a containment step that was skipped.

If the escape is not addressed, the same defect can be made again and still reach the customer. The corrective action for the escape is often a control change rather than a process change, and it belongs in the same file.

Corrective action and effectiveness

Choose actions that remove the cause. Retraining alone is weak unless the cause was genuinely a missing skill. A poka-yoke, a tool change, a parameter change or a supplier change is stronger because it does not depend on memory.

Validate before closure: run the process, inspect the output, check the capability where relevant, and confirm the action did not create a new failure mode. Update the PFMEA and control plan in the same revision, or the documents and the process will disagree.

Effectiveness is a period, not a moment. Define how many lots or how long the process will be watched, and what evidence closes the loop. A single good lot after a change is a start, not proof.

Closing the file

Close only when containment can be removed, the corrective action is implemented, the effectiveness evidence is in and the documents are updated. The file should show the timeline from detection to closure, including any delay.

A closure meeting is not evidence. The record is: the revised instruction, the training record, the updated control plan, the inspection results and the signature of the person who verified them.

The failures that repeat

The same weaknesses appear across industries: root cause recorded as operator error, corrective action recorded as retraining, containment that covers only finished goods, no escape analysis, actions with no owner or date, and a PFMEA that is never updated.

Review the 8D library periodically for repeat causes. A cluster of similar reports is a process problem, not eight separate mistakes. That review is where an 8D programme turns into a lower defect rate.

Write the containment for the person on the night shift

Name the location, the quantity, the label and the person who can release the stock. A containment instruction that assumes context will be applied differently at 2am.

Frequently asked questions

When is an 8D needed instead of a simple NCR?

Use an 8D when the cause is not obvious, the defect affects a customer or a safety characteristic, or the same issue has happened before. A simple NCR with a clear disposition is enough for an isolated, well understood nonconformance.

How quickly should containment be in place?

Before the next shipment or use of the suspect material. Many programmes set a target within one working day for the initial containment, then verify it. The exact deadline should come from the customer requirement or the risk of the defect.

Is operator error an acceptable root cause?

It is a description of where the defect appeared, not why the process allowed it. Ask what made the error possible: unclear instruction, a tool that invites a wrong fit, a check that cannot detect the result, or a target that rewards speed over sequence.

What evidence closes an 8D?

The implemented action, the revised documents, the training record, the verification results over the agreed period and the removal of containment. The file should let a new auditor follow the logic from the defect to the evidence without asking for context.

Sources and further reading

  • IATF 16949:2016, clause 10.2 on nonconformity and corrective action
  • AIAG CQI-20, Effective Problem Solving Practitioner Guide
  • VDA QMC, 8D Problem Solving in 8 Disciplines
QK

Qumek Quality Desk

Quality team

The quality team responsible for first article inspection, PPAP packs, supplier audits and the records shipped with production parts.

Reviewing an 8D before you accept it?

Send the report and the supporting records. The quality desk will check the containment, the cause and the evidence behind the closure.

Send the 8D

The Qumek dispatch

One useful email a month

Drawing notes, supplier checks, tariff changes and the questions buyers keep asking. No newsletter filler, no daily drip.

One email a month. No spam, no list sharing.