5.2Nonconformities & corrective actions
The essentials in 30 seconds
- Correction vs corrective: correction treats the immediate case; corrective action treats the cause to prevent recurrence.
- Root causes first: analyse with 5 whys / Ishikawa instead of treating the symptom.
- Verified effectiveness: the nonconformity no longer recurs — otherwise the action did not work.
Threaded mini-case — Hakim handles the 200 nonconforming parts
After his audit, Hakim receives 200 nonconforming parts shipped to the customer: he quarantines the batch and organises replacement (immediate correction), then gathers the workshop to find the cause — a drifted setting and a missing instruction — instead of blaming the operator. He fixes the setting, reposts the instruction, then verifies three months with no recurrence. Sequel to case 5.1 — Hakim moves from findings to treating causes.
Sequel to case 5.1 — Hakim moves from findings to treating causes.
1. Nonconformity: the gap that teaches
Any failure to meet a requirement (customer, standard, internal): scrap, delay, narrowly avoided accident, complaint. NC form: what, where, when, how many, immediate containment (sort, repair, alert) then analyse. Hiding an NC schedules its repeat.
Faced with 200 parts at the customer, Hakim starts by protecting the customer: sorting the batch, replacement, information. Essential — but not enough.
2. Corrective vs correction: treat the cause
Correction fixes the case (re-sort the part); corrective action prevents recurrence (set the machine + instruction). The 5 Whys find the cause; the action is proportionate to the recurrence risk. Effectiveness is verified (3 months with no recurrence = closed).
Hakim traces back from the defect to the drifted setting, then to the missing instruction and the missed training — and acts on the cause: setting locked, instruction reposted, operators briefed.
3. The register that steers
A single table: NC, cause, action, owner, deadline, verification. Monthly review: late = escalation, not oblivion. Recurring NCs on the same workstation signal a system problem (training, equipment, workload).
Hakim tracks the indicator for three months: zero recurrence = effective action. Then he capitalises (instruction updated, lessons shared).
🔎 Concrete example — A complaint that never returns
The case that surprises the workshop.
NC: 200 nonconforming parts (dimension), customer X, 12/03
Correction: sort + express replacement (48 h)
Cause (5 Whys): worn tool, no wear monitoring
Corrective: counter + threshold + instruction, Karim, 30/03
Check: 3 months, zero recurrence → closedResult: the customer is protected AND the defect never returns.
Reflex: repetition = system problem, not individual fault.
Section vocabulary
- Nonconformity
- A gap against a requirement: the starting point of improvement, not a failure to hide.
Simple example: Hakim's 200 out-of-tolerance parts delivered to the customer.
What it is not: a vague remark with no reference requirement.
Reflex: is each gap tied to an exact requirement?
- Correction
- Treats the immediate case: quarantine, repair, replace, secure.
Simple example: Hakim sorts the batch and replaces the parts at the customer.
What it is not: analysing for three months without protecting the customer.
Reflex: is the customer protected right now?
- Corrective action
- Removes the cause to prevent recurrence; not to be confused with correction.
Simple example: Locked setting + reposted instruction + operator briefing.
What it is not: re-sorting the part and hoping it is enough.
Reflex: did I treat the cause or only the case?
- Root cause
- A deep cause (often systemic) revealed by 5 whys or Ishikawa (5M).
Simple example: Missing instruction + missed training behind the drifted setting.
What it is not: "it's the operator's fault" with no analysis.
Reflex: why five times in a row, down to the system?
- Effectiveness
- The nonconformity no longer recurs over time; to verify, then capitalise.
Simple example: Three months with no recurrence tracked by Hakim on the indicator.
What it is not: filing the action without checking recurrence.
Reflex: which indicator proves non-recurrence?
In practice — Handling a nonconformity
- Detect and record the nonconformity (trace it); correct immediately (limit effects, treat the case: quarantine, repair, secure).
- Analyse the root causes (5 Whys, Ishikawa): why did it happen? — don't stop at the symptom.
- Define and implement the corrective action (remove the cause to prevent recurrence) — that's what sets it apart from mere correction.
- Verify the action's effectiveness (does the NC recur?) and capitalise (update documents, share lessons).
Ready-to-say script — analyse without blaming (2 min)
"We are not looking for who failed: we are looking for why it could happen. The part is sorted and the customer protected. Now let us trace back together: why did the setting drift? Why was the instruction missing? What in our system let this through? We decide one action on the cause, with an owner and a date — and we will check it holds."
Say in the workshop, at the workstation; note each why on the board.
Copy-paste template — nonconformity sheet
NC FOUND (requirement + evidence + date): _______________
IMMEDIATE CORRECTION (case contained?): _______________
ROOT CAUSES (5 whys / 5M): _______________
CORRECTIVE ACTION + OWNER + DEADLINE: _______________
EFFECTIVENESS CHECK (indicator + duration): _______________Small business / tight budget
A one-page sheet is enough: case, cause, action, verification — reviewed in 1 month in the notebook.
Algeria SME
Hakim involves the workstation operators (they know the real cause) instead of analysing alone in the office.
Urgent customer NC
Correction within hours (sort, replace, inform), cause analysis within days: both, in that order.
Repeated NC ×3
A third identical one = system alert: widen to the 5Ms (training, equipment, workload) and audit the workstation.
✓ Best practices
- Protect the customer first (correction), then treat the cause.
- Analyse root causes as a team, without blaming.
- Always verify effectiveness before closing.
✗ Common pitfalls
- Settling for correction (the problem returns).
- Blaming the individual instead of treating the system.
- Forgetting the effectiveness check.
Key takeaways
- A nonconformity is a gap against a requirement, detected by inspection, audit, complaint, accident or malfunction.
- Key distinction: correction treats the immediate problem; corrective action treats the cause to prevent repetition.
- Corrective action requires analysing root causes (5 Whys, Ishikawa), then verifying effectiveness — a crucial, often forgotten step.
- Nonconformities are improvement opportunities: a culture that surfaces and treats them progresses (engine of PDCA).
48h challenge — apply tomorrow
Take 1 real nonconformity (workshop or office), fill the sheet above down to the root cause, and decide 1 corrective action with a deadline.
- I distinguish correction (case) from corrective (cause) in one sentence.
- I can run 5 whys without blaming.
- I opened 1 NC sheet down to the corrective action.
Frequently asked questions
What is the difference between a correction and a corrective action?
Correction treats the found case (quarantine a batch, repair, replace); corrective action treats the cause to prevent recurrence (set, train, change the instruction). Settling for correction lets the problem return: both are needed, in that order, then verify effectiveness.
What should you do about a third identical nonconformity?
Read repetition as a system signal, not bad luck or sabotage: insufficient training, unsuitable equipment, excessive workload, unclear method. Widen the analysis (5Ms), treat the system's deep cause, and verify over time.
200 nonconforming parts shipped to the customer. What order?