12.4 Drafting Nonconformity Reports

12.4 Drafting Nonconformity Reports

Quick Answer: A strong nonconformity report states the requirement, the nonconformity statement (what failed), and the objective evidence, plus classification and traceability fields required by the audit scheme. Write factually, cite criteria precisely, avoid blame and speculation, and ensure the auditee can understand exactly what must be corrected and investigated.

Drafting NCs is a scored skill in Lead Auditor performance. Many candidates can spot a problem verbally but lose marks when the written NC is vague, criterion-free, evidence-light, or argumentative.

---

1. Purpose of the Nonconformity Record

The NC record communicates to:

• The auditee — what requirement was not met and what evidence shows it
• The audit team / CB — basis for conclusions and certification decisions
• Follow-up reviewers — whether correction and corrective action address the right issue

If a competent third party cannot understand the unmet requirement from your write-up alone, the NC is not ready.

---

2. Essential Elements

Most schemes expect at least the following (labels vary):

Some forms also include auditor name, clause list, and related aspect/obligation IDs. Follow the CB or course template, but never omit requirement–evidence linkage.

---

3. Writing the Three Critical Sentences

Think in three blocks:

1) Requirement
"ISO 14001:2015 Clause 8.1 / Operational Control Procedure OC-11 requires that significant aspects related to hazardous waste storage be controlled, including labeling of containers with contents and hazards."

2) Nonconformity
"Hazardous waste containers in the East Yard were not labeled with contents and hazards as required."

3) Evidence
"On 26 Jul 2026 at 10:40, six 200 L drums in East Yard bay 2 (observed with Warehouse Supervisor Lee) had no content/hazard labels. Waste inventory INV-17 still listed the drums as solvent waste. Interview with operator Ruiz confirmed labels were removed during a clean-up on 20 Jul and not replaced."

This structure prevents the classic failure mode: storytelling without a criterion, or criterion citation without proof.

---

4. Style Rules That Protect Impartiality

• Factual tone: describe what was evidenced, not motives ("failed to," not "deliberately ignored," unless evidence proves intent — and intent is rarely required)
• No sarcasm or lectures
• No mixing multiple unrelated requirements into one NC unless they are truly one system failure you can defend
• One NC, one clear problem statement (related evidence bullets are fine)
• Avoid prescribing the detailed solution in the NC text (e.g., "buy Brand X software"); state the unmet requirement so the auditee owns correction and corrective action
• Do not invent root cause in the NC; root cause analysis belongs to the auditee's corrective action process (Clause 10.2 thinking)

You may note immediate correction observed (e.g., "labels applied during the audit") as evidence of correction, while still recording the NC if the requirement was unmet when found — depending on scheme rules and whether the lapse indicates a deeper control failure.

---

5. Common Drafting Defects (Exam and Field)

---

6. Linking EMS Context Without Overwriting the NC

Helpful context can appear in supporting fields or report narrative:

• Related significant aspect (e.g., hazardous waste)
• Related compliance obligation (permit condition ID)
• Whether similar issues appeared in internal audits

But context does not replace the three critical elements. "This could pollute the river" without a requirement and evidence is not a complete NC — though risk relevance supports classification and audit emphasis.

---

7. Team Consensus and Communication

Before presenting NCs at the closing meeting:

1. Review each draft in the team meeting
2. Confirm evidence and criterion citations
3. Agree classification
4. Ensure no contradictory NCs from different auditors
5. Prepare to answer factual questions; do not debate personalities

Present NCs calmly, read the requirement and evidence, and allow clarification. If new evidence invalidates an NC, withdraw or amend it — fair presentation beats defending a weak write-up.

---

8. From NC to Corrective Action Expectations (Awareness)

Auditees typically must:

• Correct the immediate issue (correction)
• Investigate cause(s)
• Implement corrective action to prevent recurrence
• Review effectiveness

Your NC quality determines whether they fix the real problem. A fuzzy NC produces fuzzy CARs. A precise NC enables effective follow-up verification in surveillance or special audits.

---

9. Mini Exemplars

Acceptable minor NC (summary form):
Requirement: Competence procedure COMP-04 §6 requires role-based EMS training before independent operation of the wastewater sampling task.
NC: A technician performed compliance sampling without completing required sampling competence training.
Evidence: Training matrix shows module WS-02 incomplete; sampling log 18–19 Jul lists Tech. Nguyen as sampler; supervisor confirmed no waiver process used.
Classification: Minor (isolated to one person; program otherwise implemented for other technicians sampled).

Acceptable major NC (summary form):
Requirement: ISO 14001:2015 9.1.2 requires evaluation of fulfillment of compliance obligations.
NC: The organization has not evaluated fulfillment of identified compliance obligations.
Evidence: Legal register lists 22 obligations; no evaluation records since EMS launch 14 months ago; EHS manager stated evaluations are "planned later"; management review minutes omit compliance evaluation results.
Classification: Major (absence of a required system activity).

---

10. Exam Traps

• Writing "improve awareness" when the evidence shows a clear unmet shall-requirement
• Citing Clause 5.1 for every problem
• Forgetting objective evidence details
• Prescribing root causes and product solutions in the NC body
• Using emotional language that undermines impartiality

Draft every NC so it stands alone: requirement, failure statement, objective evidence, and classification — clear enough for the auditee to act and for another auditor to verify closure later.