Nonconforming work: the laboratory workflow that exposes disconnected quality data

What ISO/IEC 17025 nonconforming-work investigations reveal about methods, equipment, results and CAPA
Table of Contents
5
min read

Nonconforming work is any laboratory activity or result that does not conform to the laboratory's own procedures or agreed customer requirements, and it is one of the most revealing laboratory workflows. Investigating it shows whether a laboratory's methods, equipment, people, results and corrective actions are actually connected.

When everything works as intended, disconnected systems can remain hidden. A method sits in one location, calibration records in another, technical data in a laboratory information management system (LIMS), training in a learning management system (LMS) and corrective and preventive action (CAPA) records in a quality management system (QMS). People know where to look, and routine work continues.

When something goes wrong, the gaps become visible.

A laboratory may need to determine whether an equipment issue affected prior results, whether a method deviation invalidated work, whether an analyst was authorized, whether a sample was handled correctly or whether customers need to be informed. That requires evidence across several systems and functions.

ISO/IEC 17025:2017 requires laboratories to have a procedure implemented when any aspect of laboratory activities or results does not conform to their own procedures or agreed customer requirements. The laboratory must take appropriate action based on risk, evaluate the significance of nonconforming work, decide on acceptability, notify the customer where appropriate and authorize resumption of work where needed.

The precise workflow depends on the laboratory and its accredited scope. The information challenge is common: can the laboratory connect the event to the technical work it affects?

‍

What a nonconforming-work record needs to answer

A quality record should do more than describe the incident. It should establish scope.

A table showing what a nonconforming-work record needs to answer: what happened, what work is affected, which method applies, who was involved, what equipment is involved, what the impact was, and what action followed, each mapped to the specific evidence it should connect to.

Without structured links to this information, the laboratory may have to rebuild scope manually each time an event occurs.

‍

Example: assessing the impact of an equipment issue

Imagine an instrument is found to have been operating outside an expected condition.

The immediate question is not only whether the instrument needs repair or recalibration. The laboratory may need to identify:

  • When the issue began or could have begun.
  • Which methods use the equipment.
  • Which tests/calibrations were performed in the relevant period.
  • Which analysts and samples/items were involved.
  • Which results or reports may require review.
  • Whether customers need communication.
  • Whether a broader system issue requires corrective action.

If equipment records and technical work records are disconnected, the impact assessment becomes a spreadsheet exercise. It may be completed successfully, but it will be slower and more vulnerable to omission.

‍

Example: assessing a method deviation

A method deviation can have similar consequences. A laboratory may need to determine:

  • Which approved method/version should have been used.
  • What actually happened.
  • Whether the deviation affects validity of the result.
  • Which samples/items and reports are in scope.
  • Whether the person was trained/authorized.
  • Whether the deviation reflects a procedure, training, equipment or planning issue.
  • What correction and preventive action are required.

The laboratory needs the original technical evidence, not merely a narrative after the fact.

‍

A connected workflow supports faster, more disciplined assessment

A practical workflow can follow this sequence:

1. Capture the event and immediate containment: Record what was observed, when, by whom and what immediate action was taken. Preserve the original technical context.

2. Identify affected entities: Link the event to relevant methods, equipment, people, samples/items, activities, results and reports.

3. Assess significance and impact: Use the connected evidence to determine what work may be affected, what needs review and whether customer communication or work suspension is required under the laboratory’s procedures.

4. Investigate and determine action: Identify cause where appropriate, define corrections and corrective actions, assign owners and retain supporting evidence.

5. Verify effectiveness and close: Confirm that actions were completed, assess effectiveness and authorize return to normal activity where required.

This structure keeps the technical scope and quality response together without requiring all source data to be copied into one system.

‍

Common weaknesses in nonconforming-work records

Weak nonconforming-work records tend to fail in the same few ways, and each one makes the next investigation harder.

  • Narrative instead of links. The record describes the event in free text but does not reference the specific methods, equipment, samples or reports involved, so scope has to be rebuilt by reading it.
  • No defined impact period. For equipment issues in particular, the record does not state when the problem could have begun, which leaves the set of affected results open to interpretation.
  • Correction confused with corrective action. Repeating a test or repairing an instrument fixes the immediate problem. A corrective action addresses the cause so the event does not recur. Records that stop at the correction miss the second step.
  • Closure without an effectiveness check. Actions are marked complete, but nobody confirms they worked.
  • No link to earlier events. Similar events are recorded separately, so a recurring pattern in one method or instrument is not visible.

For example, a testing laboratory that finds a balance out of tolerance during a routine check might repair it and record the repair, but not list the tests performed on that balance since its last acceptable check. The record looks complete, yet the question an assessor or customer will ask, which results were affected, is still unanswered.

‍

How to test your current nonconforming-work process

Select a completed nonconforming-work event and ask:

  • Can we identify every affected result without manual searching?
  • Can we retrieve the methods, people and equipment linked to those results?
  • Can we show the immediate impact assessment and decision rationale?
  • Can we connect corrective action to the original technical issue?
  • Can we identify whether similar events have occurred before?

If the answer depends on experienced staff remembering which folders or systems to search, the laboratory has identified a valuable improvement opportunity.

‍

Nonconforming work is a learning workflow

The purpose is not only to close an incident. It is to understand whether the event reveals a broader weakness in method control, competence, equipment management, sample handling, data review or quality-system design.

When nonconforming work is connected to methods, equipment, results, CAPAs and audits, the laboratory can detect recurring patterns and use them in management review and continual improvement.

FAQs

What is nonconforming work under ISO/IEC 17025?

ISO/IEC 17025:2017 requires laboratories to have a procedure for when any aspect of laboratory activities or results doesn't conform to their own procedures or agreed customer requirements. The laboratory must act based on risk, evaluate the significance of the nonconforming work, decide on acceptability, notify the customer where appropriate, and authorize resumption of work where needed.

What does a nonconforming-work record need to capture?

A nonconforming-work record needs to establish scope, not just describe the incident. It should capture what happened, what work is affected, which method applies, who was involved, which equipment was used, what the impact was and what action followed, with each item linked to the underlying technical evidence rather than summarized in narrative after the fact.

Why do disconnected lab systems make nonconforming-work investigations harder?

When a method sits in one system, calibration records in another, technical data in a LIMS, training in an LMS and CAPA in a QMS, routine work can hide the gaps. When something goes wrong, the lab has to manually rebuild scope, for example tracing which tests used a given instrument or which analysts and samples were involved, which is slower and more vulnerable to omission.

What does a connected nonconforming-work workflow look like?

A connected nonconforming-work workflow follows five steps: capture the event and immediate containment, identify the affected methods, equipment, people, samples, results and reports, assess significance and impact using that linked evidence, investigate and determine corrective action, and verify effectiveness before closing. Source data can stay in its own systems as long as the links are kept.

What is the difference between a correction and a corrective action?

A correction deals with the immediate problem, such as repeating an affected test or repairing an instrument. A corrective action addresses the cause of the nonconforming work so it does not happen again, for example by changing a procedure, retraining staff or adjusting equipment checks. A complete nonconforming-work record covers both and confirms the corrective action was effective.