What is a non-conformance? Types, examples and how to handle one

A non-conformance is a gap between what was required and what actually happened. It might be a part that is out of tolerance, a step skipped in a procedure, a missing record or a service that did not meet what was promised. The reason quality teams care about non-conformances is simple: each one is a signal about where a process is weak, and handled well it becomes a chance to fix the cause rather than just the symptom.

What counts as a non-conformance?

A non-conformance, sometimes shortened to NC or written up as a non-conformance report (NCR), is a documented instance of not meeting a specified requirement. The key word is requirement. For something to be a non-conformance, there has to be a defined expectation it failed against. That expectation can come from several places: a customer specification, a legal or regulatory rule, an industry standard such as ISO 9001, a contract, or your own internal procedure.

This is what separates a non-conformance from a vague complaint or a personal preference. “I do not like the colour” is an opinion. “The colour does not match the agreed specification” is a non-conformance, because there is a requirement to point to. Defining requirements clearly is therefore the quiet foundation of the whole thing. If nobody wrote down what good looks like, you cannot fairly say the work was non-conforming.

What are the main types of non-conformance?

Non-conformances are usually grouped in two useful ways: by severity and by what they relate to. Both groupings help you decide how urgently to respond and who needs to be involved.

By severity, most quality systems distinguish between major and minor non-conformances:

• Major non-conformance: a significant failure that affects the product’s fitness for use, breaches a regulation, or shows that part of the quality system has broken down. A major NC usually needs containment, investigation and formal corrective action.
• Minor non-conformance: an isolated lapse that does not, on its own, undermine the product or the system. It still needs correcting and recording, but the response is lighter. The watch-out is that a cluster of minor non-conformances pointing at the same cause can add up to a major problem.

By what they relate to, common categories include:

• Product non-conformance: the item itself fails a specification, for example a dimension out of tolerance or a failed test.
• Process non-conformance: a procedure was not followed, or a step was done out of sequence, even if the output happened to be acceptable.
• Documentation non-conformance: a record is missing, incomplete or inaccurate, such as an unsigned inspection sheet or an out-of-date work instruction in use.
• System non-conformance: a requirement of the quality management system itself is not being met, for example internal audits not being carried out at the planned intervals.
• Supplier non-conformance: goods or services received from a supplier fail to meet the agreed requirement.

Non-conformance, defect or near miss?

These terms get tangled, so it helps to keep them straight. A non-conformance is the broadest: any failure to meet a requirement. A defect is a specific kind of non-conformance, one in a product or service that affects its intended use. So every defect is a non-conformance, but a missing signature, which is a documentation non-conformance, is not a defect.

A near miss is different again. It is an event that could have caused harm or a failure but did not. In quality terms, a near miss is often the early warning that precedes a non-conformance, and treating it as seriously as an actual failure is one of the cheapest forms of prevention there is.

Some worked examples

Examples make the categories concrete. A batch of bolts measures 0.3 mm under the specified diameter: that is a major product non-conformance, because the bolts may not hold. An operator runs a machine without completing the start-of-shift checklist, but the parts pass inspection: that is a process non-conformance, minor in this instance, but worth tracking because the checklist exists for a reason. A calibration certificate for a measuring gauge has expired but the gauge is still in use: that is a documentation and system non-conformance with real consequences, because every measurement taken with it is now in doubt. A supplier ships material with the wrong grade certificate: a supplier non-conformance that may need the whole delivery quarantined.

How to handle a non-conformance, step by step

Handling a non-conformance well follows a consistent sequence. The order matters: you contain the immediate risk before you spend time investigating the cause.

1. Identify and record it. Capture what happened, where, when and against which requirement, with evidence such as a photo or measurement. The quality of everything that follows depends on this record being clear.
2. Contain it. Stop the problem spreading. Quarantine affected stock, mark it clearly, and check whether other batches, sites or customers are affected. Containment is about limiting harm now, not finding fault.
3. Assess severity. Decide whether it is major or minor, who needs to know, and whether it must be reported externally to a customer or regulator.
4. Disposition the affected item. Decide what happens to the non-conforming product: rework it, repair it, scrap it, return it, or formally accept it under concession if it is fit for purpose despite the deviation.
5. Investigate the root cause. For anything beyond a trivial one-off, find out why it happened. This is the step that turns a non-conformance into corrective and preventive action.
6. Act and verify. Implement the fix, then check it actually worked before closing the record. An action that is implemented but never verified is just a hope.

Steps five and six are where a non-conformance connects to the wider improvement loop. The investigation and the lasting fix are covered in full in CAPA explained: corrective and preventive action. For how this sits inside the bigger picture, see the quality management guide.

Why capturing non-conformances consistently matters

A non-conformance recorded nowhere is a lesson lost. The single biggest factor in whether a quality system improves is how reliably small failures get logged in the first place, because the trends only appear once you have enough of them in one place. That is why fast, low-friction capture matters so much: when reporting a non-conformance takes seconds on a phone rather than a trip to find a paper form, far more of what really happens gets recorded. Logincident’s digital reporting is built for exactly that, and the quality solution tracks each non-conformance from the moment it is logged through to closure.

By Shannon Hamming, Communications and Community