NCR: A Practical Non-Conformance Workflow for Small Factories

An NCR, short for non-conformance report, is the record that says: this product, material, or process deviated from spec, here is the evidence, here is the decision, and here is proof the loop closed. In many small factories the NCR is a Word template in a shared folder and a signature culture that varies by supervisor. That is a fine starting point. What matters is that the workflow behind the form is short enough that people actually use it, because a workflow nobody follows protects nobody.

When to Raise an NCR

Three triggers cover most cases. First, a failed critical check: a seal integrity test, a torque reading, a weight out of limits. Second, a customer return, which is the most expensive quality detector you own because it caught the defect after shipping. Third, scrap that repeats: the same defect three weeks running is not bad luck, it is a process signal. Non-critical cosmetic deviations usually do not need the full record; a note on the traveler, or in the digital logbook (we compare the two in paper travelers vs a digital logbook), is enough. Reserve the formal NCR for deviations that must be decided and traced.

The Minimum Viable Non-Conformance Workflow

Three steps, no committee:

Anything beyond these three steps is optional polish. Anything less, and the record cannot survive an audit, which is the standard your batch documentation has to meet anyway (see electronic batch records for BPOM audits).

The Four Dispositions and What Each One Triggers

Every NCR ends in one of four dispositions, and each has consequences beyond the form:

Dispositions Must Move Inventory

Here is where most paper NCR programs fail: the report closes, but the stock count never changes. Two thousand scrapped caps are still sitting in the ERP's inventory, costing still assumes they were good, and the next audit finds a system that disagrees with itself. An NCR that does not move inventory or reopen the order is a diary entry, not a control. The disposition is the moment the record becomes real: stock decrements, orders reopen, affected lots get held.

This is the part we built into Voltrus MES. When a critical inspection check fails, an NCR is drafted automatically with the inspection result attached as evidence. The dispositions are wired to the floor: scrap decrements stock, rework reopens the order, and every step lands in the same production log the operators already write to. The loop closes in software instead of in a signature chase.

Frequently Asked Questions

Who should raise an NCR?

Anyone who sees the problem: operator, inspector, supervisor. In practice the fastest programs let the system draft the report from the failed check and have a supervisor confirm it. If raising one requires a meeting, defects learn to hide.

Do we need NCR software for this?

No. Discipline with a shared folder beats software nobody opens. What software adds is enforcement of the last mile: the disposition actually decrementing stock and reopening the order, instead of relying on someone to re-key it into another system.

Is an NCR the same as a CAPA?

No. The NCR records one deviation and disposes of it. A CAPA (corrective and preventive action) asks why the deviation happened and what prevents recurrence. Small factories should get the NCR loop solid first; CAPA without a working NCR trail is a meeting about meetings.

How long should an NCR stay open?

Until verification is done, not until someone signs. If the disposition was scrap, verify the stock moved. If it was rework, verify the units passed the check on the way back through.

Close the Loop at the Terminal

Voltrus MES drafts the NCR when a critical check fails, and the dispositions move stock and orders for real. See what ships today.

See Voltrus MES