A nonconformance is a failure to meet a requirement — a product, process, or system that doesn’t match its specification, procedure, or standard. Catching, documenting, and resolving nonconformances is one of the most basic jobs of a quality system, and how you handle them is something auditors check closely. This guide explains what a nonconformance is, how it differs from related terms, the steps for handling one, how it connects to corrective action, and how software keeps the process under control.

What is a nonconformance?

A nonconformance is any instance where a requirement isn’t met. The requirement might be a product specification, a work instruction, a customer expectation, or a clause of a standard like ISO 9001. When something falls short — a part out of tolerance, a step skipped, a document unsigned — that’s a nonconformance, and the quality system needs to capture it, decide what to do with the affected item, and (where warranted) find out why it happened.

Nonconformance vs nonconformity vs defect

• Nonconformance / nonconformity — used interchangeably in practice; both mean a failure to meet a requirement. ISO standards tend to use “nonconformity”; many manufacturers say “nonconformance” (and log an “NCR,” a nonconformance report).
• Defect — a nonconformity related to an intended use; every defect is a nonconformance, but not every nonconformance is a defect (a paperwork miss is a nonconformance, not a product defect).
• Deviation — usually a planned, pre-approved departure from a requirement, versus a nonconformance, which is an unplanned failure found after the fact.

Types and examples

• Product — a dimension out of tolerance, a failed test, wrong label.
• Process — a procedure not followed, a missed inspection step.
• System — a required record missing, training not completed, a document used past its revision.

Nonconformances are also often graded major (a significant failure, or a systemic breakdown) versus minor (an isolated lapse) — the same grading auditors use for findings.

How the nonconformance process works

• 1. Identify and document — raise a nonconformance report (NCR) describing what failed and against which requirement.
• 2. Contain — quarantine or flag the affected item so it isn’t used or shipped by mistake.
• 3. Disposition — decide what happens to the item: use-as-is (with justification), rework, repair, scrap, or return to supplier.
• 4. Investigate if warranted — for significant or recurring issues, run root cause analysis and open a corrective action.
• 5. Close — record the disposition and any actions, with the full trail.

Nonconformance vs CAPA

These work together but aren’t the same. A nonconformance (and its NCR) deals with the specific thing that went wrong — this batch, this part — and what to do with it. A corrective action (CAPA) goes after the cause, so the problem doesn’t recur. Not every nonconformance needs a CAPA (a one-off, low-risk miss may just be dispositioned), but a recurring or serious one should trigger root cause analysis and corrective action. In short: the NCR handles the bad output; the CAPA fixes the system that produced it.

How QMS software manages nonconformances

On paper, nonconformances get lost — items ship before they’re contained, dispositions go unrecorded, and nobody sees the pattern until an audit. QMS software runs each one through a controlled workflow: capture, containment, disposition with approval, an escalation path to CAPA when needed, trending to surface recurring issues, and a complete audit trail. Because it’s connected, a nonconformance can flow into corrective action, a document change, and retraining — one traceable chain. That’s how TLM handles nonconformances as part of a connected eQMS for small-to-mid regulated teams. To see the flow from NCR to disposition to verified corrective action, book a demo.

Frequently asked questions

What is a nonconformance?

A nonconformance is a failure to meet a requirement – a product, process, or system that doesn’t match its specification, procedure, standard, or customer expectation. Examples include a part out of tolerance, a skipped process step, or a missing required record. The quality system captures it, decides what to do with the affected item, and investigates the cause where warranted.

What is the difference between a nonconformance and a nonconformity?

They mean the same thing – a failure to meet a requirement – and are used interchangeably. ISO standards tend to use ‘nonconformity’; many manufacturers say ‘nonconformance’ and log a nonconformance report (NCR). Either way it’s the same concept.

What is the difference between a nonconformance and a defect?

A defect is a nonconformity related to intended use. Every defect is a nonconformance, but not every nonconformance is a defect – a missing signature or an unfollowed procedure is a nonconformance without being a product defect.

What is the nonconformance process?

Identify and document the issue (an NCR); contain the affected item so it isn’t used or shipped; disposition it (use-as-is with justification, rework, repair, scrap, or return); investigate with root cause analysis and open a corrective action if the issue is significant or recurring; then close with the disposition and actions recorded and traceable.

What is the difference between a nonconformance and a CAPA?

A nonconformance (and its NCR) deals with the specific item that failed and what to do with it. A CAPA goes after the underlying cause so the problem doesn’t recur. Not every nonconformance needs a CAPA, but a recurring or serious one should trigger root cause analysis and corrective action. The NCR handles the bad output; the CAPA fixes the system that produced it.