Quality & Continuous Improvement

Non-conformity: what it is and how to manage it

By Claudia · · 6 min read

Non-conformity: what it is and how to manage it

Non-conformity: what it is and how to manage it

In any food-industry quality management system, non-conformity is one of the most important concepts — and also one of the most confusing in day-to-day practice. Knowing how to identify it correctly, log it rigorously and close it with verified evidence is what separates a company that learns from its mistakes from one that simply files them away. In this article we explain everything you need to know to make your non-conformity management genuinely effective.

What a non-conformity is, and how it differs from an issue or a complaint

A quality non-conformity is the failure to meet an established requirement. That requirement can be legal, regulatory, internal, or agreed with the customer. What matters is that a defined standard exists and the product, process or service didn't meet it.

This is where many quality teams get confused. An issue is an anomalous event detected in the process that may or may not turn into a non-conformity. For example, a temperature fluctuation in a cold room is an issue; if that fluctuation exceeds the limit set in the control plan and affects the product, it then becomes a non-conformity.

A customer complaint, on the other hand, is an expression of dissatisfaction coming from outside the organization. In many cases, a complaint is the visible consequence of a non-conformity that went undetected internally. It makes operational sense to manage them separately, but both should feed the same continuous improvement system.

As set out in Regulation (EC) No 178/2002 (Regulation [EC] 178/2002, 2002), food business operators are responsible for ensuring that the food they place on the market meets the requirements of food law, which means having mechanisms in place to detect and manage any deviation from those requirements.

In short: every non-conformity is a deviation from a requirement, but not every issue is a non-conformity, and not every complaint is either — though all three deserve attention and follow-up.

How to log a non-conformity properly: the data it needs for the corrective action to make sense

The non-conformity record is the starting point of the whole cycle. An incomplete or vague record makes it impossible to correctly analyze the root cause and, as a result, undermines any corrective action implemented afterward. These are the fields that can't be missing:

  • Date and time of detection: lets you correlate the non-conformity with batches, shifts or specific conditions.
  • Detailed description of the finding: exactly what was observed, without subjective interpretation or vague language.
  • Detection point: which stage of the process or which area the deviation was identified in.
  • Requirement not met: a specific reference to the procedure, specification, legal limit or customer criterion that wasn't met.
  • Impact on the product: the batch or batches involved, quantity of product, its current status, and the immediate decision on its disposition (quarantine, reprocess, reject).
  • Person responsible for detection: who identified it and who is responsible for following it up.
  • Severity classification: minor, major or critical, based on the potential impact on food safety, legal compliance or customer satisfaction.

When this record is filled out properly, root cause analysis has a solid foundation to work from. Without that data, the quality team ends up repeating the same corrective actions over and over without ever getting to the bottom of the problem.

The most common mistake: non-conformities closed without verifying that the root cause is actually gone

This is, without a doubt, the most frequent failure in non-conformity management in the food industry. Operational pressure pushes teams to close records quickly: a corrective action is documented, marked as resolved, and everyone moves on. But nobody verifies whether the problem has actually disappeared.

The result is predictable: the same non-conformity resurfaces weeks or months later. And when that happens, the credibility of the quality system takes a hit. Auditors spot it easily, customers notice it in recurring complaints, and the internal team loses confidence in the usefulness of the process itself.

Proper non-conformity closure has to include at least three distinct steps:

  1. Immediate action or correction: what's done urgently to contain the problem (segregate product, inform the team, block shipment, etc.).
  2. Corrective action: the measure that eliminates the root cause, not just the symptom. It may involve revising a procedure, training staff, changing a supplier, or adjusting a process parameter.
  3. Effectiveness verification: confirming, within a defined timeframe, that the corrective action has worked. This can be done through indicators, internal audits, testing, or any objective evidence showing the problem hasn't recurred.

Without that third step, the cycle is incomplete. Many reference standards, including those recognized under the Global Food Safety Initiative (GFSI) (GFSI, n.d.), explicitly require effectiveness verification to be documented before a non-conformity can be considered truly closed.

You can dig deeper into how to design corrective actions that actually work in our article on corrective and preventive actions that work.

How to digitize the full cycle, from detection to verified closure

Managing non-conformities on paper or in spreadsheets has a clear ceiling: traceability gets lost, deadlines slip, and information isn't available in real time to the people who need to make decisions. Digitizing the full cycle completely transforms how effective the system is.

Quality management software like Solved lets you log the non-conformity the moment it's detected, from any device, right at the point where it happens. The system automatically assigns the person responsible, triggers the relevant notifications, and opens the workflow that runs from immediate correction through to effectiveness verification.

The benefits of digitizing this process are concrete and measurable:

  • No non-conformity goes untracked: the system flags when a deadline is approaching and escalates the alert if no action is taken.
  • The full history is always accessible: any internal or external auditor can review the complete record, with evidence for every step of the cycle.
  • Trend analysis becomes possible: with all the data centralized, it's easy to identify which areas, suppliers, shifts or products concentrate the most non-conformities and act preventively.
  • Verified closure is documented: the platform won't let you close a non-conformity until effectiveness verification has been completed and validated by the person responsible.

The goal isn't simply to digitize paperwork. It's to build a system where non-conformity management becomes a real engine of continuous improvement, not a bureaucratic formality. When quality managers have full visibility into the status of every non-conformity, they can get ahead of problems instead of reacting once it's too late.

Managing non-conformities well is, ultimately, a way of protecting food safety, the company's reputation and customer trust. And with the right tools, that work becomes far more agile, traceable and effective.

References