Out of Tolerance: how to manage the impact on batches already released

Why an OOT is the moment of truth for the system

In the metrological management of a GMP site, the Out of Tolerance event is the one that puts every component of the system to the test: the robustness of the procedures, the discipline of the inventory, the quality of the historical records, the ability to retroactively trace the batches, the maturity of the deviation and change control process. A site that manages OOTs well typically has a solid metrological system. A site that manages them as "an administrative event to close" almost always has substantial shortcomings upstream.

The reason is simple: the OOT is retroactive by definition. The instrument is out of tolerance today, but when did it become so? Yesterday? A month ago? Six months ago? All the data generated in the meantime are in question, and with them the batches that were released on those data.

What an Out of Tolerance is (and is not)

An Out of Tolerance is the result of an As Found calibration that shows the instrument outside the accuracy limits required by its GMP function. It is raw data, obtained before any adjustment, and this is what makes it relevant: it represents the instrument's state during the previous period of use.

These are not Out of Tolerance:

• a routine adjustment that brings the instrument back to the center of the scale (if the As Found was still within tolerance);
• a system non-conformity not linked to accuracy (e.g. damaged cable, power supply problem);
• a calibration with an acceptable result on the GMP tolerance even if outside the manufacturer's tighter tolerance.

The distinction is important because the management flow changes. Only the true OOT — As Found, outside the GMP tolerance — triggers the retroactive impact procedure.

The formal management flow

A mature GMP system manages every OOT with a defined sequence:

1. Immediate recording

The OOT is recorded at the same time as the calibration, with all the raw data: As Found values for each calibration point, deviations from the reference, environmental conditions, instrument identifier, technician identifier, reference of the standard used.

No "we'll open it tomorrow". The contemporaneous record is one of the ALCOA+ requirements and a deferred entry is already in itself a problem.

2. Notification to quality

The OOT is a potential quality deviation. The site's procedures must provide for a formal notification to the quality department within defined times (typically 24–48 hours). The quality manager opens the formal case (event record, deviation, according to the site's nomenclature).

3. Deviation analysis

The event is characterized:

• magnitude: by how much it is out of tolerance, in absolute and percentage value;
• direction: was the instrument reading higher or lower than the true value;
• persistence: does the OOT recur over several calibration points or is it isolated;
• plausible cause: natural drift, impact, electronic problem, out-of-spec use, abnormal environmental conditions.

This characterization guides everything that follows. An OOT of +0.1°C on a probe with a tolerance of ±0.5°C is an observation; an OOT of +3°C on the same probe is a serious problem.

4. Retroactive impact assessment

This is the heart of GMP management. You have to answer:

• which processes used the instrument since the last in-tolerance calibration?
• which batches were produced, processed or tested with data generated by the instrument?
• which batch specifications may have been influenced by the deviation?
• would the deviation, applied to the real recorded data, have driven critical process or product parameters out of specification?
• are there redundant data (other instruments, analytical controls, environmental data) that can confirm or refute the validity of the batches?

The assessment produces a formal conclusion: the batches remain valid, are to be reassessed, are to be rejected, are to be recalled from the market.

5. Decision and actions

Based on the conclusion:

• valid batches: case formally closed with documented justification;
• batches to be reassessed: additional tests, documentary analysis, and a possible product OOS (Out of Specification) are triggered;
• unreleased batches: release is blocked pending further investigation;
• already released batches with suspected impact: a recall is assessed, with notification to the competent regulatory authority and a recall procedure.

Each of these paths is a GMP process in its own right with defined timelines and responsibilities.

6. Actions on the instrument and on the system

The instrument is:

• adjusted (As Left in tolerance) if possible and appropriate;
• repaired if the problem is structural;
• replaced if not repairable or no longer suitable;
• reclassified if the actual use does not match the assigned GMP classification.

The calibration interval is reviewed: if the OOT suggests a faster drift than expected, the interval must be shortened. This is a point often overlooked: the lesson learned from an OOT must change the system, not just close the case.

7. Closure and documentation

The case is closed with a complete record reporting all the steps above, the decisions taken, the supporting evidence, and the signatures of those who analyzed and approved. It is the document that will remain available for future audits.

The recurring errors

In GMP audits, inspectors encounter some typical shortcomings in OOT management:

The As Found data is missing. The instrument was "adjusted and recalibrated" without recording the raw value before the adjustment. The retroactive assessment is impossible.

The impact assessment is missing. The OOT is recorded, the instrument is recalibrated, but there is no trace of any analysis of the batches generated during the drift period. The system is not closed.

Generic impact assessment. "It is considered that the deviation has no significant impact" without reference to specific batches, specific data, specific tests. It is a signature, not an analysis.

No interval review. An OOT leads to no change in the calibration interval. The same event will recur.

Long closure times. The OOT stays open for months, perhaps beyond the next calibration. The system is out of control.

The Eurosystem experience

In the sites where we manage calibration, the OOT is the point at which a mature metrological system distinguishes itself from one that is formally compliant but operationally fragile. Dimacs is designed so that every OOT automatically triggers the complete flow: recording the As Found data is impossible to skip, notification to quality is automatic, the list of potentially impacted batches is generated by the system on the basis of the instrument's usage data, and every step stays traced through to closure. It is the way we translated the discipline of OOT management — the kind we would want every site to have — into software constraints that make it unavoidable.