markdowneditor

Nonconformity & Corrective Action (CAPA)

NC + root cause + effectiveness check

ISO y cumplimientoEstándarcapanonconformity

Cómo usar: Root cause must not read "human error"; 5-Whys should end at a system fix. Effectiveness verification is the step orgs skip and audits catch.

Vista previa

Nonconformity & Corrective Action (CAPA)

Mandatory record – ISO 9001/27001 cl.10.2. The improvement engine: every NC needs root cause (not just a fix) + effectiveness check.

FieldValue
CAPA IDNC-YYYY-NNN
OpenedYYYY-MM-DD
SourceAudit / incident / complaint / review
Detected by@name
Owner@name
StatusOpen / Root cause / Implementing / Verify / Closed

1. Nonconformity description

What requirement was not met, where, when – factual, evidence-based.

  • Requirement: clause / policy / spec violated
  • What happened: observed condition
  • Evidence: record/photo/log reference

2. Immediate correction (containment)

The quick fix to stop the bleeding – done first, does NOT close CAPA.

ActionByDate
Containment step@name

3. Root cause analysis

The most-failed step – auditors check that root cause ≠ symptom.

flowchart LR
    P[Problem] --> W1[Why 1] --> W2[Why 2] --> W3[Why 3] --> W4[Why 4] --> W5[Why 5: root cause]
  • Method: 5 Whys / fishbone / fault tree
  • Root cause: systemic reason, not "human error"

4. Corrective action

Address the ROOT cause so it cannot recur:

ActionEliminates root cause?OwnerDueDone
Systemic fixyes – how@name

5. Effectiveness verification

  • Check date: YYYY-MM-DD (≥ enough time to show recurrence stopped)
  • Evidence: metric / re-audit / observation
  • Result: effective – close / not effective – reopen at step 3

6. Closure

SignedRoleDate
Quality/ISMS manager

7. Linkages

  • Feeds management review input (cl.9.3)
  • Updates risk register if new risk surfaced
  • Procedure change if root cause was process gap

Plantillas relacionadas