RSC Colour: Red

  • non-conformance report

    A non-conformance report (NCR) is a formal record used to document and manage any product, process, service, document, or supplier output that does not meet a defined requirement. It is a core quality and compliance artifact in regulated manufacturing, providing traceable evidence that nonconforming conditions were identified, evaluated, and addressed under controlled procedures.

    What a non-conformance report includes

    While formats vary by organization and system, an NCR commonly includes:

    • Identification details such as NCR number, date, originator, and affected site or line
    • Description of the nonconformance, including what failed, how it was detected, and observed condition
    • Reference requirements such as drawings, specifications, procedures, contracts, standards, or control plans
    • Scope and impact, for example affected batches, serial numbers, lots, or time windows
    • Initial containment actions, such as segregation, status labeling, and holds in MES/ERP
    • Disposition decision, for example rework, repair, use-as-is under deviation, scrap, or return to supplier
    • Approvals from authorized roles such as quality, engineering, production, or customer representatives
    • Links to follow-on actions such as root cause analysis, CAPA records, or change controls when required

    Operational use in manufacturing environments

    In industrial operations, NCRs are typically triggered when a nonconformity cannot be corrected immediately without risking traceability, compliance, or consistent treatment. NCRs may be generated from:

    • In-process or final inspection results that do not meet acceptance criteria
    • Deviations from work instructions, validated processes, or standard operating procedures
    • Supplier nonconforming material, certificates, or documentation
    • Audit findings related to execution of manufacturing or quality processes

    NCR workflows are often implemented in MES, QMS, or ERP systems, with defined rules for initiation, review, disposition, and closure. These workflows support segregation and release of material, documentation of rework instructions, and visibility of open nonconformances across sites and functions.

    Relationship to CAPA and other quality records

    An NCR documents the occurrence and handling of a specific nonconforming condition. It does not necessarily include full root cause analysis or long-term corrective and preventive actions. When a pattern of similar NCRs is observed, or when risk or impact is high, an organization may initiate a separate CAPA record and link it to one or more NCRs.

    Other related records can include:

    • Deviations or concessions, which may authorize temporary use or rework of nonconforming items under defined conditions
    • Rework instructions, which specify controlled steps to bring nonconforming items back into conformance
    • Supplier corrective actions, which may be requested based on supplier-related NCRs

    Common confusion

    • NCR vs. nonconforming product: The product or process condition is the nonconformance; the NCR is the documented record of it.
    • NCR vs. CAPA: An NCR captures and dispositions a specific nonconformance. A CAPA addresses underlying causes to prevent recurrence or occurrence and may reference multiple NCRs.
    • NCR vs. audit nonconformity: Audit nonconformities may be recorded in separate audit tools. Some organizations convert relevant audit findings into NCRs when they affect product, process, or documentation requirements.

    Link to the provided context

    In practice, organizations define in procedures when a non-conformance report must be issued, how thresholds are applied across products and sites, and how NCRs interface with MES, QMS, and ERP. This supports consistent treatment of nonconformances, traceable decision-making, and alignment with customer and regulatory expectations.

  • Quality Escape

    A quality escape is a defect, nonconformance, or incorrect condition that passes through a manufacturer’s normal quality controls and is only detected after it has moved to the next internal process step, to the customer, or into service in the field.

    Key characteristics

    In industrial and regulated manufacturing environments, a quality escape typically:

    • Originates in design, manufacturing, inspection, documentation, or supplier processes
    • Bypasses or is missed by in-process checks, inspection plans, or automated controls
    • Is discovered downstream, often during later operations, customer receipt, product use, service, or investigation
    • Triggers formal nonconformance, containment, and corrective action activities

    A quality escape can involve physical characteristics (dimensions, materials, assembly), documentation (incomplete travelers, missing certifications), configuration and traceability errors, or software and firmware issues embedded in products or tooling.

    Operational context

    In operations, quality escapes are usually handled through structured processes such as:

    • Creation of a nonconformance report and, when needed, Material Review Board (MRB) disposition
    • Containment actions, such as lot holds, recalls, field inspections, or rework campaigns
    • Root cause and corrective action (for example, 8D or RCCA) to prevent recurrence
    • Updates to control plans, inspection and sampling, work instructions, and training

    Digital systems such as MES, QMS, and ERP may track quality escapes using specific defect codes, customer complaint records, or escape incident records, often linked to traceability and genealogy data to identify impacted parts and customers.

    Common confusion

    • Nonconformance vs. quality escape: A nonconformance is any failure to meet a requirement. It becomes a quality escape only when it passes beyond the controls or process step where it should reasonably have been detected.
    • Internal vs. external escape: An internal escape is found at a later in-house operation. An external escape is found by the customer or in the field after shipment or release.

    Relation to risk and compliance

    In regulated industries, quality escapes are often treated as significant risk events. They can drive additional documentation, risk assessments, audits, and updates to quality management system controls, especially when safety, regulatory, or contractual requirements are affected.

  • 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.