There is no single universal classification of non-conformance that applies to every regulated manufacturer. The exact types and definitions should be set in your QMS, procedures, and electronic systems (QMS/MES/ERP) and then validated and trained against. That said, most organizations use a consistent set of dimensions to categorize non-conformances.
1. Product vs. system non-conformance
Product non-conformance typically covers issues where a specific part, batch, lot, or unit does not meet a defined requirement, such as:
- Dimensional or functional out-of-tolerance
- Wrong material, component, or revision used
- Contamination, cosmetic defects, or damage
- Labeling, traceability marks, or documentation missing for a given lot
System or process non-conformance usually refers to failures of the management system or process rather than one specific unit:
- Procedure not followed or unclear work instructions
- Calibration system lapse, expired tooling, or unqualified equipment usage
- Training gaps or personnel working without required qualification
- Breakdown in document control, change control, or record retention
In practice, product and system non-conformances often coexist: a product issue frequently exposes an underlying process weakness that should be addressed via CAPA.
2. Critical, major, and minor non-conformance
Many regulated plants use a severity scale. The exact criteria must be defined locally, but a common pattern is:
- Critical non-conformance: Could reasonably lead to unsafe product, regulatory breach, or major customer impact if not detected (e.g., wrong material in a safety-critical component, missing required inspection on serialized aircraft parts).
- Major non-conformance: A significant requirement is not met, but immediate safety impact is controlled (e.g., incomplete batch records, wrong revision of a non-safety drawing, repeated minor defects indicating process drift).
- Minor non-conformance: Low risk, localized, often cosmetic or administrative (e.g., isolated labeling error with easy recovery, minor cosmetic defect within customer-accepted ranges).
Severity levels affect required actions, approvals, documentation detail, and sometimes customer notification. In a brownfield environment, these categories often need to be mapped consistently across multiple legacy systems (QMS, MES, LIMS, ERP) to avoid conflicting severity logic.
3. Internal vs. external non-conformance
Another common dimension is where the issue is detected or originates:
- Internal non-conformance: Found within your own operations (in-process checks, final inspection, in-house audits, lab testing, maintenance). These usually allow more controlled handling and rework options.
- External non-conformance: Involves parties outside your direct control, such as:
- Supplier non-conformance: Incoming material or components that fail specification.
- Customer-returned non-conformance: Complaints, returns, or field failures.
- Regulatory or third-party audit non-conformance: Observations against standards or licenses.
External non-conformances typically trigger additional requirements such as supplier corrective action requests, customer communication, or formal CAPA, and they must be carefully linked to contracts, specifications, and regulatory submissions.
4. Conforming vs. nonconforming material disposition types
While not strictly “types of non-conformance,” many plants classify nonconforming material by its disposition category, because this drives risk, cost, and system configuration:
- Use as is: Deviation/waiver is granted to accept the nonconformance without change. In regulated environments, this generally needs strong justification, risk assessment, and traceable approval.
- Rework: Material can be brought into full conformance using an approved, validated process.
- Repair: Material is made fit for use but may not fully meet original specifications; may require engineering justification and, in some industries, customer or regulatory approval.
- Scrap: Material is not recoverable or not acceptable to rework/repair.
- Return to supplier: Nonconforming items are sent back with appropriate records.
In brownfield environments, you often have to align these disposition types across MES, ERP inventory statuses, and QMS workflows. Misalignment here is a frequent source of traceability gaps and audit findings.
5. Process, equipment, and documentation non-conformance
Many QMS frameworks further distinguish by the element of the system that failed:
- Process non-conformance: Process parameter outside limits, uncontrolled change in sequence, or missing required verification. Example: heat treatment cycle not meeting specified time/temperature profile.
- Equipment non-conformance: Equipment out of calibration, operating outside validated range, or maintained late. Example: CNC machine with overdue calibration producing unknown number of parts.
- Documentation non-conformance: Incomplete, inaccurate, or obsolete records, drawings, procedures, or work instructions. Example: operator used a superseded work instruction revision.
These categories are useful for trend analysis and for linking non-conformances to CAPA, maintenance, and change control records.
6. Regulatory or standard-specific non-conformance types
Some standards and regulators define additional or specific non-conformance categories that you may need to mirror or map in your systems. Examples include:
- Audit findings categorized as critical/major/minor or similar wording.
- Labeling and traceability non-conformances treated separately due to regulatory exposure.
- Data integrity or record-keeping non-conformances called out explicitly.
Where this is the case, your internal types usually need to be traceably mapped to the external categories for reporting and audit readiness. This mapping is a common integration challenge when you have multiple legacy QMS or point solutions still in use.
7. How to define types in a brownfield, regulated environment
In practice, your “types of non-conformance” should be defined and maintained through controlled documents and validated systems, not ad hoc lists. When updating or harmonizing types across plants or systems, consider:
- Alignment with existing procedures and records: Changing types affects trending, historical metrics, and audit trails. You may need a transition plan and clear mapping.
- System constraints: Legacy MES/QMS/ERP tools may limit field types, dropdown values, or workflows. Full replacement just to change categories is rarely justified given validation and downtime burdens.
- Risk-based clarity: Types should support risk assessment and decision-making, not just reporting. If users cannot reliably distinguish between categories, the scheme is too complex or poorly defined.
- Traceability: Ensure that non-conformance types can be linked to batches, serial numbers, equipment, documents, and changes. Incomplete linkage is a common failure mode in audits.
For most sites, the practical solution is to standardize a small, well-defined set of non-conformance types across systems, then map historical and site-specific variants into that model through controlled change.
