Nonconformance (NCR)

A nonconformance is a documented instance where a product, process, service, or system does not meet specified requirements. These requirements can come from engineering drawings, specifications, customer contracts, internal procedures, or applicable standards.

What a nonconformance includes

In industrial and regulated manufacturing environments, a nonconformance commonly refers to:

• Product characteristics out of tolerance (dimensions, material properties, surface finish, etc.)
• Process deviations (wrong routing, skipped operation, unapproved setup, missing inspection)
• Documentation or records that do not meet defined requirements
• Supplier-delivered items that fail incoming criteria or specifications

Nonconformances are typically logged and controlled using a Nonconformance Report, often abbreviated as an NCR. The NCR record usually captures the problem description, affected parts or lots, traceability data (work order, serial/lot number, revision), and the immediate actions taken.

Operational meaning and workflows

In day-to-day operations, an NCR is both the event (the nonconforming condition) and the formal record used to manage it. Typical steps in an NCR workflow include:

• Detection of the issue during inspection, testing, production, or receiving
• Creation of an NCR record in a QMS, MES, ERP, or dedicated NCR system
• Containment actions to prevent unintended use or shipment of nonconforming material
• Disposition by an authorized group, often a Material Review Board (MRB), such as rework, repair, use-as-is under deviation, scrap, or return to supplier
• Linkage to corrective or preventive actions (CAPA or RCCA) when systemic issues are identified

In aerospace and other highly regulated sectors, NCRs are tightly tied to configuration control, routing, and inspection records (such as First Article Inspection reports) to maintain traceability and audit-ready evidence.

What a nonconformance is not

• It is not the same as a corrective action or CAPA. The NCR identifies and controls the specific nonconforming instance; CAPA addresses underlying causes.
• It is not limited to physical defects. Process, documentation, and system deviations can also be nonconformances.
• It is not, by itself, an indication of compliance status. It is a record used within a quality management system to manage deviations.

Common confusion

• Nonconformance vs. defect: A defect usually refers to a specific flaw in a product. A nonconformance is broader and can include process, documentation, or system issues, even when the final product still functions.
• Nonconformance vs. CAPA: An NCR documents what went wrong and how that specific case was handled. CAPA investigates why issues occur and defines actions to prevent recurrence or occurrence.
• NCR number vs. part nonconformance: In many systems “NCR” is shorthand for the record or identifier, not only the condition itself.

Link to FAI and configuration control

In environments using AS9102 First Article Inspection (FAI), nonconformances and NCRs are closely connected to configuration and routing control. A nonconformance on a part or process that was previously covered by an approved FAI can trigger review of whether that FAI remains valid, whether a partial or full re-FAI is required, and how the change is documented in the digital or paper traveler. Keeping NCR workflows integrated with FAI, routing, and revision control systems supports consistent traceability of design changes, dispositions, and repair or rework actions.