When a non-conformance occurs, most organisations have a process for dealing with it. The event gets logged, a form gets completed, a corrective action gets assigned, and the NCR gets closed. From a compliance standpoint, the investigation is done. But if the same non-conformance appears again three months later, on the same line, with a different operator, or at a different site entirely, it raises an uncomfortable question:

Was that actually an investigation, or was it documentation?

There is a meaningful difference between the two, and understanding it is the first step towards building a quality investigation process that genuinely prevents recurrence.

What a quality failure investigation is supposed to do

At its most basic, a quality failure investigation is a structured process for understanding why a failure occurred so that it can be prevented from occurring again. That definition sounds obvious, but it contains a distinction that many organisations miss in practice.

The goal is not to explain “what happened”. It is to understand “why the system allowed it to happen”, and to identify the specific changes that would stop it from happening again.

This means a quality failure investigation needs to do more than identify the immediate cause, for example:

• A component failed inspection because it was out of tolerance.

• A batch was rejected because contamination was detected.

• A supplier delivered the wrong specification for the third time.

These are facts about what happened. They are not, on their own, sufficient to prevent the next failure.

To get to prevention, the investigation needs to go deeper: what barriers failed or were absent? What planning, training, communication, or supervision factors contributed? Was this a one-off event or the visible result of a systemic issue that has been building for some time?

Why most quality investigations stop too soon

The majority of quality investigation processes were designed around compliance, not learning. The NCR system exists to document non-conformances, demonstrate that they were reviewed, and show that an action was taken. For audit purposes, that is often sufficient.

The problem is that compliance-focused investigation and learning-focused investigation are not the same thing. A checklist-based process tells investigators what to record. It does not guide them to the underlying cause. A five-why exercise surfaces contributing factors but rarely reaches the systemic level, including the planning decisions, resource allocations, and procedural gaps that would need to change to prevent recurrence.

The result is that preventive actions tend to address symptoms, for example:

• Retrain the operator.

• Re-inspect the batch.

• Issue a non-conformance notice to the supplier.

These actions may prevent the exact same event from happening in exactly the same way, but they leave the systemic root cause intact. And root causes tend to express themselves in multiple ways.

The role of human factors in quality failure investigation

One of the most consistent gaps in quality investigation is the treatment of human error. When an operator makes a mistake that results in a non-conformance, it is tempting to record the cause as human error and move on. The action might be retraining. The investigation is closed.

But human error is not a root cause.

It is a symptom of the conditions in which people are working. Why did the operator make that decision? Was the procedure unclear? Was the workstation poorly designed? Was there time pressure that made shortcuts feel necessary? Was the training adequate for the actual complexity of the task? Or sometimes, was the decision wilful or malicious?

These are human factors questions, and they matter enormously in a quality investigation. The answers often point towards systemic changes in procedures, design, training, supervision, or workload that address the conditions producing errors rather than the individuals who make them.

Organisations that incorporate structured human factors analysis into their quality investigations consistently find that non-conformances attributed to human error are rarely random. They cluster around specific conditions, specific tasks, and specific points in the process where the system is not adequately supporting the people working within it.

What a structured quality failure investigation looks like in practice

A structured quality failure investigation follows a consistent methodology regardless of the failure type. It begins with a thorough data collection phase, gathering physical evidence, interviewing those involved, and reviewing relevant procedures and records, before moving to analysis.

The analysis phase is where methodology matters most. Rather than asking what went wrong, a structured investigation asks what barriers were in place and why they failed to prevent the outcome. It then works systematically through the contributing factors, covering equipment, environment, procedures, communication, human factors, and management systems, using a coded taxonomy to categorise each one.

That taxonomy is so important. When root causes are coded consistently, they become comparable. A quality manager can look across 200 investigations and see that a disproportionate number share the same root cause category, such as inadequate procedure, insufficient training, or poor task design, even when the surface-level events looked quite different. That pattern is where prevention happens.

The difference between closing an NCR and preventing the next one

There is nothing wrong with having a process for closing NCRs. Compliance documentation matters. But organisations that treat NCR closure as the endpoint of investigation are leaving their quality systems exposed to repeat failures that were, in principle, avoidable.

The question worth asking of any quality investigation process is not whether it closes the case, but whether it surfaces something actionable that prevents recurrence. If the answer is consistently no, the process is doing compliance work, not quality improvement work.

COMET brings the same structured, barrier-based methodology used in high-consequence industries to quality failure investigation, giving quality teams the tools to find root causes, code them consistently, and build the kind of organisational learning that prevents failures from recurring.

Book your discovery call and learn more about COMET for Quality failure prevention.