An NCR is raised on the shopfloor. It sits in a folder until the quality manager finds it.
Non-conformances are raised throughout the manufacturing day — a weight check failure, a seal integrity issue, a label defect, an in-process parameter deviation. Each one needs to be reviewed, investigated, and dispositioned: release, rework, or reject. The decision affects production continuity, material usage, and regulatory compliance.
In most operations, NCRs are raised on paper or in a standalone form and reviewed in the next quality meeting. The batch or product in question sits in limbo — cannot be released without disposition, cannot be reworked without a decision, cannot be rejected without a cost approval. The delay between the NCR being raised and a decision being made is where production bottlenecks and compliance gaps are created.
A non-conformance is a decision that needs to be made quickly, by the right person, with the right information. HublerX routes every NCR to the appropriate reviewer based on the product, the failure type, and the severity — immediately on raising. The reviewer sees the NCR details, the affected batch, the production context, and the disposition options in a single screen. The decision is made once and propagates to the ERP, the production team, and the quality record simultaneously.
Live workflow view
The step-by-step sequence
- 1
Non-conformance detected and logged
The production operator or QC technician logs the non-conformance in HublerX — failure type, affected batch or WO, quantity, measurement value, and specification limit. Photos or measurement data can be attached. The NCR is timestamped and assigned a reference number automatically.
On detection · immediate - 2
Affected product quarantined
The affected batch or WO quantity is automatically flagged in the WMS for quarantine — preventing it from being picked, dispatched, or used in a downstream process until disposition is confirmed. The quarantine flag is applied in the system without a manual WMS update.
Immediately on NCR raise - 3
NCR routed to appropriate reviewer
HublerX routes the NCR to the appropriate reviewer based on configured rules — minor in-process deviations go to the line QC technician, major failures go to the quality manager, food safety failures go to the food safety team lead. The reviewer receives the NCR with full context and a response deadline.
Within seconds of NCR raise - 4
Investigation and disposition decision
The reviewer investigates the non-conformance and records the root cause in HublerX. The disposition decision — release with concession, rework, or reject — is made in the same interface. For disposition decisions above a configured value threshold, a second approval is required before the decision is executed.
Within configured response window - 5
Disposition executed and ERP updated
The disposition decision is executed in the ERP automatically — released batches have their quarantine flag lifted and become available for picking, rework batches generate a rework work order, rejected batches are written off with the reason code. No separate ERP update by the quality or production team required.
On disposition approval - 6
CAPA triggered on repeat or severe NCRs
Where an NCR is classified as severe or where the same failure type has occurred more than a configured number of times, a CAPA is triggered automatically. The NCR is linked to the CAPA record, and the root cause investigation feeds directly into the CAPA workflow.
On severity or frequency threshold
Results are directional. Disposition cycle time depends on the complexity of the investigation and the severity of the non-conformance.
See how non-conformance resolution works in your operation
30 minutes. Your quality process. Your compliance requirements.