Nonconforming Material Report (NCMR)

Nonconforming Material Report (NCMR) – Rapid Containment, Disposition Discipline, and Digital Traceability from Receipt to Release

This topic is part of the SG Systems Global regulatory & operations glossary.

Updated October 2025 • Quality Control & Disposition • QMS, LIMS, MES, WMS, Supplier Quality

Nonconforming Material Report (NCMR) is the controlled record used to document, evaluate, disposition, and trend any raw material, in-process item, packaging component, or finished good that fails to meet a requirement at any point in the flow—Incoming Inspection, WIP checks, In-Process Controls (IPC), or final release. A proper NCMR does three things simultaneously: it freezes risk through quarantine and hold/release; it drives a traceable decision through defined MRB pathways; and it feeds learning loops via CAPA, supplier scorecards, and CPV trending. In regulated manufacturing, an NCMR is not a “paper trail for scrap”—it is a safety valve that prevents defective, misidentified, adulterated, or mislabelled material from contaminating genealogy, confusing CoA status, or escaping into commerce.

“An NCMR is a speed bump by design: it slows the process exactly where risk spikes, so the organization never accelerates into a recall.”

TL;DR: NCMR documents and controls any material that fails a requirement. It creates immediate containment (quarantine and status blocks), routes to an MRB for disposition (rework, use-as-is, return, scrap), and ensures traceability across WMS, MES, and LIMS. Digital audit trails, Part 11/Annex 11 e-signatures, MRB rules, and NOC/MOC feedback loops make it enforceable; hard gates block production or shipment until disposition is approved and executed.

1) What Triggers an NCMR

NCMRs trigger whenever a requirement is not met—identity, potency, dimensions, torque, sterilization indicator, barcodes, label verification, packaging integrity, or documentation completeness. Triggers come from goods receipt checks, MSA-qualified gauges and balances, machine vision stations, IPC sampling by AQL, lab results in LIMS, or complaints/returns that retroactively flag lots. An NCMR is also appropriate for suspected issues (mix-ups, temperature excursions, wrong artwork version) when risk is high and time matters. The rule of thumb: if a reasonable person would hesitate to blend, consume, or ship the item without additional scrutiny, raise the NCMR and let the process decide.

2) Containment First: Quarantine, Status, and Segregation

Once opened, an NCMR enforces containment. In WMS, the lot flips to Quarantine or Hold and directed put-away moves it to secure bins; pick paths no longer present the lot to jobs. In MES, any eBMR step that references the lot is blocked; dual verification cannot override the systemic stop. In LIMS, results remain preliminary or “OOS pending” and release rules cannot execute. Physical segregation and label overlays reinforce the system state. If containment is soft—emails and tape instead of status interlocks—you do not have a compliant NCMR process; you have a wish.

3) The NCMR Record: What Must Be Captured

At minimum: item and lot identifiers, supplier and PO, receiving/inspection dates, spec/version, requirement violated, measured values and units, instruments and calibration status, sample size and method, photos/attachments, and immediate containment actions. Add links to CoA, DHR or eBMR if the lot is already in WIP, plus references to any related deviation or complaint. The record must be attributable (who did what, when), contemporaneous, and immutable per Data Integrity and Audit Trail principles. If you can’t reconstruct the evidence and decisions six months later, the NCMR failed its real purpose.

4) Disposition Paths and MRB Authority

Disposition should be tightly defined and enforced by MRB rules: Rework (with validated method and measurables), Use-As-Is (documented risk justification and customer/regulatory allowances), Return to Supplier (with NOC implications), or Scrap (irreversible and recorded). Each path should drive system actions: WMS move tasks and status changes; MES route updates or additional IPC steps; LIMS re-sampling or new studies; finance cost capture; and QMS approvals. “Use-as-is” should be rare and policy-gated—otherwise NCMRs become a quiet side door for spec erosion. MRB membership (Quality, Operations, Engineering, Regulatory) must be explicit, and authority should be digital—no wet signature should overrule a system stop in a validated environment.

5) Lab Involvement: OOS, OOT, and Method Fitness

When an NCMR stems from test results, the LIMS process for Out-of-Specification (OOS) or Out-of-Trend (OOT) kicks in. Confirm sample integrity, instrument status, and analyst training; then perform structured phases (hypothesis testing, re-measurement under controlled conditions, root cause analysis). Link the OOS investigation to the NCMR so MRB can see scientific evidence and decide. If method weakness is found, escalate through MOC to update specifications, calculations, or sampling plans; enforce re-validation as needed, with knock-ons to IQ/OQ/PQ. An NCMR that ends with “analyst error, proceed” but never improves the method leaves the trap armed for next time.

6) Manufacturing Impact: WIP, Rework, and Genealogy

Nonconforming material already used in WIP demands genealogy reconstruction. Use Batch Genealogy reports to list affected orders, units, and customers. If rework is viable, define it as an approved route in MES with instrument checks, additional IPCs, and SPC tight limits. If scrap is required, MES should block forward steps until removal and reconciliation are executed; release must remain unavailable. Every action must be captured back into the eBMR with e-signatures per Part 11/Annex 11. The gold standard is simple: no unit created from nonconforming material can progress or ship without MRB-approved, system-enforced rework or disposition.

7) Supplier Dimension: NOC, Returns, and Prevention

An NCMR involving purchased goods should feed supplier management. If the cause is upstream (material purity drift, dimensional shift, artwork error), issue a Notification of Change (NOC) requirement and capture supplier corrective actions. Scorecard the impact—quarantine hours, rework cost, customer risk—and use it in sourcing and audit plans. Where the supplier initiated a change without notice, update contracts and approved vendor lists via MOC and require evidence (process capability, CSV/equipment validation, APR/PQR trend data). An NCMR without supplier feedback is an invitation to repetition.

8) Data Integrity and Electronic Controls

NCMR data must be ALCOA+: attributable, legible, contemporaneous, original, accurate, complete, consistent, enduring, and available. Enforce unique logins, role-based access, reason-for-change prompts, and time sync. Use audit trails that capture field changes and attachments. Block “delete” and “overwrite” behaviors; use superseding revisions with cross-links. If the system allows a user to silently relabel status or backdate a check, you’re not compliant—you’re vulnerable.

9) Metrics that Matter

Track containment lead time (detection to quarantine), NCMR cycle time (open to disposition), MRB aging, repeat NCMR rate by item/supplier/cause, use-as-is frequency, rework success rate, scrap cost, and downstream impact (orders affected, release delays). Trend by instrument, shift, and station; compare against SPC control charts to spot systemic drift. If “use-as-is” is climbing, specs or capability likely diverged; if containment lead time is long, your status interlocks are soft.

10) Common Failure Modes & How to Avoid Them

  • Status without segregation. Lot flagged in the system but physically still on open shelves. Fix: WMS move tasks + controlled quarantine bins + label overlays.
  • MRB by email. Decisions scattered across threads without authority. Fix: QMS workflow with role-based approvals and e-signatures.
  • Rework invented on the floor. Ad hoc fixes. Fix: validated rework routes in MES with IPC checks and documented acceptance criteria.
  • Use-as-is inflation. Habitual “waive it through.” Fix: policy thresholds, customer/regulatory concurrence, and trending with executive review.
  • No genealogy back-trace. Affected WIP unknown. Fix: mandatory scan-based consumption and genealogy reports.
  • Instrument error disguised as product defect. Poor MSA. Fix: gauge R&R, calibration interlocks, and challenge tests.
  • Audit trail gaps. Handwritten tally sheets, later transcribed. Fix: direct device integration and eBMR data capture.

11) Regulatory Anchors

Across FDA and global standards, NCMR expectations repeat: maintain procedures for control of nonconforming product; document evaluation, segregation, and disposition; and analyze data for improvement. Electronic records require 21 CFR Part 11/Annex 11 controls; device and lot records tie back to DHR or eBMRs; and APR/PQR compiles the story annually. If an auditor asks, “show me every lot touched by this defective label roll,” your systems must answer in minutes, not days.

12) Integration: QMS, MES, WMS, and LIMS Working as One

An NCMR is cross-system by nature: QMS holds the record and workflow; WMS applies location/status and blocks picking; MES gates eBMR steps and enforces rework routes; LIMS drives testing and OOS logic. Barcode scanning and device drivers eliminate re-typing errors; EPCIS events log movement and consumption. The integration principle is ruthless: every status in the NCMR must have a machine-enforced consequence in execution and logistics, not a reminder.

13) From Incident to Improvement: Deviation, CAPA, and CPV

Not every NCMR triggers a deviation or CAPA, but repeat patterns, high severity, or compliance risk should. Investigations should include 5-Why or fishbone analysis and attach evidence (photos, instrument logs, supplier statements). Preventive actions often land in MOC: tighter specs, new sampling plans, new vision checks, or revised scheduling to de-risk bottlenecks. CPV trends confirm effectiveness; if metrics revert, reopen the loop.

14) How This Fits with V5 (Module-by-Module with Hard Gates)

V5 by SG Systems Global makes NCMR enforcement systemic, fast, and audit-proof. Explore the modules here: V5 Solution OverviewQMSMESWMSLIMS Integration.

V5 QMS — NCMR Workflow & MRB Governance. QMS is the system of record for NCMR creation, routing, and approval with configurable categories, severity matrices, e-signatures, and audit trails. Hard gates: until MRB approves disposition, QMS signals to MES/WMS keep jobs and shipments blocked.

V5 MES — eBMR Locks, Rework Routes, and Evidence Capture. MES binds NCMR status to eBMR availability. It prevents consumption of affected lots, generates validated rework routes with IPC checkpoints, and requires photos, notes, and reason codes. Hard gates: nonconforming lots cannot be started, backflushed, or signed until clearance.

V5 WMS — Quarantine, Directed Moves, and Scan-Back Proof. WMS auto-creates directed moves to quarantine locations, prints HOLD overlays, and blocks Directed Picking visibility for affected lots. Hard gates: pick screens simply do not surface nonconforming stock; ship confirmations are disabled.

V5 LIMS — OOS/OOT Investigations and Release Logic. LIMS structures OOS/OOT phases, links instruments and calibration, and controls result release. Hard gates: “Approved” status in LIMS is a precondition for QMS disposition and MES release; absent approval, everything stays on hold.

Outcome. V5 eliminates the reliance on emails and post-it notes. If a control is not configured, the system won’t let the product pass—no exceptions, no drama, no recalls born of optimism.

15) FAQ

Q1. When should we open an NCMR versus a deviation?
Open an NCMR whenever material fails a requirement or its status is uncertain. Use a deviation when the process deviates (missed step, environmental excursion). They frequently link; the NCMR contains the material, the deviation explains the process failure.

Q2. Who sits on MRB and how fast should they decide?
Quality, Manufacturing, Engineering, and Regulatory as core; Purchasing joins for supplier cases. Targets: immediate containment in minutes; preliminary disposition in hours; final disposition within defined SLA (e.g., 3–5 business days) with clock-stopping only for required testing.

Q3. Can we allow “use-as-is” for critical product?
Only with documented risk assessment, customer or regulatory concurrence when required, and trend controls. If UAI becomes common, re-center specs or improve capability—do not normalize risk.

Q4. How do we prevent recurring NCMRs from the same cause?
Trend NCMR causes and severities; tie thresholds to automatic CAPA creation and MOC for specs, methods, or process steps. Verify effectiveness through CPV and audit readiness checks.

Q5. What proves our NCMR process is effective during audits?
Show closed-loop examples: containment timestamps, MRB decisions with signatures, WMS move logs, MES route blocks, LIMS OOS phases, and final disposition—plus trending that led to CAPA/MOC and measurable reductions in recurrence.


Related Reading
• Quality Backbone: MRB | Deviation/Nonconformance | CAPA | MOC | NOC
• Execution & Release: MES | WMS | LIMS | eBMR | Hold/Release
• Compliance & Data: 21 CFR Part 11 | Annex 11 | Data Integrity | Audit Trail (GxP)
• Traceability & Labeling: Lot Traceability | Batch Genealogy | Label Verification | CoA
• Recently Updated Topics: New Product Introduction (NPI) | NDC | NIST | Nitrosamine Risk Assessment