Key takeaways
  • A nonconformance record captures what was wrong, what was decided about the affected material, and what is being done about the cause.
  • Disposition and corrective action are separate decisions. Conflating them is why NCR systems fill up and stop being useful.
  • Every NCR needs an owner and a due date, or the log becomes a graveyard.
The distinction that keeps the log clean
Disposition is about the material; corrective action is about the cause

Deciding to rework a batch answers what happens to those parts. It says nothing about why they were wrong. Recording both in one field is how a system ends up with a thousand entries and no learning.

What a nonconformance record needs

  • What was found, described physically, with the specification it violates.
  • Where and when it was detected, and by whom.
  • Quantity affected and the traceability needed to bound it: batch, heat, serial range, date and shift.
  • Immediate containment and where the material is now.
  • Disposition decision and who authorised it.
  • Whether corrective action is required, and if not, why not.
  • Cost, where it can be estimated.

Disposition options

  • Use as is. Requires a documented technical justification and, for customer-specified characteristics, customer concession.
  • Rework. Return to conformance by a defined method, then re-inspect.
  • Repair. Made acceptable but not conforming; needs the same authority as use-as-is.
  • Regrade. Suitable for a different application or lower grade.
  • Scrap. Ensure it cannot re-enter the flow, which means physical control, not just a status change.

Deciding when corrective action is needed

Not every nonconformance warrants a full investigation. A sensible trigger set: anything reaching the customer, anything safety-related, anything recurring, and anything above a cost threshold. Write the triggers down, so the decision is a rule rather than a mood, and record the reasoning when action is not taken.

Why NCR systems decay

  • No owner on each record, so nothing moves.
  • Corrective action required on every entry, which overwhelms the team and trains people not to raise NCRs.
  • Free-text descriptions that cannot be analysed, so recurrence is invisible.
  • Closure that means the form was completed rather than the problem verified.

Making the data usable

Structured fields for defect type, process step and detection point turn a log into a Pareto. Without them you have a filing cabinet. The categories should be short enough that people pick the right one without thinking hard, which usually means fewer than fifteen.