When should a supplier NCR be raised?

Written by

in

A supplier NCR should be raised when purchased material, outsourced services, supplier documentation, or a supplier-controlled process is suspected or confirmed to violate a flowed-down requirement. That requirement may come from the purchase order, drawing, specification, quality clause, approved process, revision level, certification package, packaging requirement, or traceability obligation. The NCR should be opened early enough to control the item and preserve evidence, not delayed until root cause or final disposition is known.

The purpose is not simply to assign blame to the supplier. It is to create a controlled quality record that prevents unintended use, supports material review, protects traceability, and gives the organization a basis for supplier communication, disposition, and possible corrective action.

Common triggers

A supplier NCR is commonly appropriate when the issue appears to have originated before receipt or during supplier-performed work. Examples include:

  • Dimensional, visual, functional, material, or test results outside drawing or specification requirements.
  • Incorrect part number, revision, configuration, quantity, serialization, lot identification, or shelf-life information.
  • Missing, incomplete, or incorrect certificates of conformance, material certificates, special process certifications, test reports, or inspection records.
  • Use of an unapproved supplier, process, material substitution, manufacturing location, or special processor where approval was required.
  • Damage, contamination, FOD concern, packaging failure, preservation failure, or handling issue attributable to the supplier or shipping terms.
  • A supplier escape discovered later in production, assembly, test, FAI, MRO, or customer return activity.
  • Repeat issues that indicate supplier process breakdown and may require SCAR, CAPA, or supplier development activity.

Raise it on suspicion if product control is needed

In regulated operations, the threshold is often suspected nonconformance, not proven nonconformance. If the material could be used, installed, shipped, or mixed with conforming inventory before the issue is resolved, a controlled NCR or equivalent hold record is usually needed.

Final responsibility can be corrected later if the investigation shows the supplier was not at fault. What matters first is containment, identification, segregation, and traceability. Waiting for engineering, purchasing, or supplier debate can create a larger problem if the part is consumed or the evidence is lost.

When a supplier NCR may not be the right record

A supplier NCR should not be used as a catch-all for every problem involving purchased material. It may be the wrong record if the issue was caused by internal handling after receipt, an internal planning or kitting error, a buyer purchasing to the wrong revision, an engineering change that was not flowed down, or ambiguous requirements that were not contractually imposed on the supplier.

If a supplier asks for permission before delivering nonconforming product, many organizations use a deviation, waiver, concession, or supplier change request process rather than an NCR. If nonconforming product has already been delivered or accepted into inventory, an NCR is typically more appropriate. The exact distinction is site-specific and should be defined in the quality procedure.

Do not wait for MRB disposition

The NCR should normally be raised before MRB disposition. MRB may later decide whether the item is returned to supplier, reworked, repaired, used as-is, scrapped, or submitted for customer approval where required. The NCR is the record that controls the nonconformance through that decision path.

In aerospace-grade and similarly regulated environments, some dispositions require customer, design authority, or regulatory involvement. An internal MRB decision does not automatically make the product acceptable for all programs or customers.

Evidence matters

A weak supplier NCR creates disputes and poor supplier metrics. The record should identify the requirement and the observed condition clearly. Typical evidence includes the purchase order, drawing or specification revision, lot or serial number, inspection result, measurement method, calibrated gage reference where applicable, photographs, certificate discrepancies, packaging condition, and where in the process the issue was found.

If the requirement cannot be cited, the organization should be cautious about calling it a supplier nonconformance. It may still be a risk or usability issue, but the supplier cannot be held to a requirement that was not defined or flowed down.

System and integration considerations

In a mature digital process, the supplier NCR should connect to the purchase order, receipt, lot or serial record, inspection plan, inventory status, work order, FAI record, QMS workflow, supplier scorecard, and any SCAR or CAPA activity. In brownfield environments, those links often span ERP, MES, PLM, QMS, receiving inspection tools, and spreadsheets.

Integration gaps are common. If systems do not share status reliably, manual controls may still be required to prevent use of suspect material. Examples include physical quarantine, ERP inventory hold, MES consumption block, traveler annotation, and quality approval checks before release. Full system replacement is often unrealistic because of validation cost, qualification burden, downtime risk, integration complexity, and long asset lifecycles.

Practical rule

Raise a supplier NCR when a supplier-related requirement failure could affect product conformity, traceability, acceptance, delivery, or customer obligations. If there is uncertainty, control the material first and classify responsibility through investigation. Under-reporting creates escape risk; over-reporting creates noise and supplier friction. The balance depends on clear procedures, disciplined evidence, and consistent disposition control.

Content classification

Visible verification fields for authorship, dates, taxonomy, and ST assignments.

Author:

Published:

Updated:

Categories:

Tags:

Glossary category:

Glossary tag:

Colour:

Content type:

Location:

Audience:

Intent:

Dev-only relationship debug

Content relationships

Rendered from saved content and bridge metadata. Nothing in this panel writes back to WordPress.

Inline glossary links

No inline glossary links found in saved content.

Attached glossary terms

No glossary bridge terms attached.

Attached FAQs

No FAQ bridge items attached.

Diagnostics

Inline glossary links
0
Attached glossary terms
0
Attached FAQs
0
  • No glossary or FAQ relationships found for this item.