What failed?
Capture the requirement, inspection evidence, product, supplier, and severity.
Nonconformance and CAPA
Do not close the defect before the learning is proven.
Preserve detection, containment, approved cause, accountable action, and effectiveness evidence as one controlled chain.
Context survives containment
A failure opens work, not a dead-end record.
When an inspection fails, the nonconformance retains the affected product, supplier, released plan, result, severity, and exact problem statement.
Containment protects output now. Root cause and CAPA prevent the same condition from returning.
Major · Under investigation
ProblemDrive shaft runout exceeds released tolerance
CauseFixture wear allowed inconsistent seating during supplier inspection
ActionReplace fixture and submit capability evidence
ReviewInitial samples comply; extended evidence remains pending
Partially effectiveFollow up
The accountable sequence
Every handoff changes the question.
The process moves from what failed, to what is protected, to why it happened, to what prevents recurrence.
What is protected?
Control affected material or output and name the immediate accountable owner.
What changes?
Approve root cause and assign correction, corrective action, or preventive action.
Did it work?
Review objective evidence after completion and judge whether recurrence stopped.
The evidence spine
Closure does not erase the path.
Effectiveness review still links to CAPA, approved root cause, the originating nonconformance, inspection, product, and supplier.
Inspection
What was checked, against which released plan, and with what result.
Failure
The exact unmet requirement, severity, containment, and status.
Action
Approved change, accountable owner, due date, and completion state.
Evidence
Reviewer, review date, objective evidence, and effectiveness outcome.
Run Nonconformance and CAPA in ERP.ai.
This feature page explains the process. The working records, approvals, and evidence open inside ERP.ai.