In regulated manufacturing environments, a non-conformance is a documented instance where a product, material, component, process, or record does not meet an approved requirement. The requirement may come from a specification, drawing, work instruction, validated procedure, standard, or customer/contract requirement.
What a non-conformance is
A non-conformance typically means all of the following are true:
- A clear requirement exists (for example, tolerance limits, process parameters, cleanliness criteria, document format, or timing).
- Objective evidence shows the actual condition or result does not meet that requirement.
- The gap has been recorded in an approved system (for example, QMS, MES, CAPA or deviation module) according to local procedures.
Non-conformance is a status of non-fulfillment, not an explanation of why it occurred or what will be done to fix it.
What a non-conformance is not
- Not the root cause: The non-conformance describes what is wrong (for example, diameter out of tolerance). Root cause analysis is a separate activity.
- Not automatically a defect recall or compliance failure: Many non-conformances can be reworked, repaired, or accepted under deviation depending on risk, requirements, and approvals.
- Not the same as a CAPA: Corrective and preventive actions may be triggered by significant or repeated non-conformances, but the CAPA record is distinct from the initial non-conformance record.
Types of non-conformance you will see
Terminology varies by company and regulator, but common categories include:
- Product non-conformance: Physical product does not meet specification (for example, dimension out of tolerance, surface finish, missing feature, contamination).
- Process non-conformance: A step was not performed as required (for example, skipped inspection, uncalibrated gage, wrong torque sequence, unapproved software version).
- Documentation or data non-conformance: Records are incomplete, incorrect, missing, or not created under the approved procedure (for example, missing signatures, wrong revision of work instruction used, incorrect lot traceability linkage).
- Supplier non-conformance: Incoming material or documentation from a supplier does not meet purchase order or specification requirements.
How non-conformances are typically handled
In mature operations and quality systems, a non-conformance usually triggers a defined workflow:
- Detection and recording: The issue is identified (for example, by operator, inspector, automated check, or system rule) and logged in the designated system with traceable details.
- Containment: Affected parts, lots, or records are identified and controlled to prevent unintended use or shipment.
- Evaluation: Technical and quality review determines severity, risk, regulatory or customer impact, and whether product can be reworked, repaired, used-as-is under concession, or must be scrapped.
- Disposition: An approved disposition (for example, rework, repair, scrap, use-as-is with deviation) is documented and executed under change control.
- Escalation to CAPA (when warranted): Significant, systemic, or repeat non-conformances may feed into a CAPA process for deeper root cause analysis and longer-term corrective or preventive actions.
System and integration considerations
In brownfield plants with mixed MES, ERP, PLM, and QMS systems, the exact meaning and handling of non-conformance is often shaped by integration boundaries and validation constraints:
- Some plants record non-conformances primarily in the QMS, with limited visibility in MES or ERP, which can create gaps in traceability and containment.
- Others use MES for in-process non-conformance and QMS for formal investigation and CAPA, requiring reliable data integration and clear ownership between systems.
- Legacy systems and long-qualified equipment may restrict changes to how non-conformances are captured or categorized without revalidation and change control.
Because of these realities, the operational impact of a non-conformance depends not only on the technical issue but also on how well your systems, procedures, and roles are aligned around detection, documentation, and resolution.
