An out-of-specification result
The default position is the uncomfortable one: the result is real until an assignable laboratory cause is demonstrated. Not suspected — demonstrated.
An OOS result stands as valid unless a documented, assignable laboratory cause explains it.
Roughly the first working day
- Preserve the preparation and the sequenceWhere possible retain the sample preparation, the instrument sequence and the surrounding runs before anything is discarded.
- Begin the Phase I laboratory investigation promptlyMethod, calculation, instrument, standards and analyst execution, examined while the material and context still exist.
- Do not retest before the rules are appliedRetesting should follow pre-defined rules on number, authorisation and treatment of results — not be decided in the moment.
- Notify QA and consider batch statusEnsure the batch cannot proceed to release while the investigation is open.
- Widen to Phase II if no laboratory cause is foundManufacturing process, materials, batch records and related batches. This is the phase most often truncated under commercial pressure.
What must not be lost while people react
- The original result and its full electronic record, including any reprocessing history.
- The sample preparation and remaining solution where retention is possible.
- Instrument logs, calibration and system suitability data.
- The analyst's contemporaneous record of what was performed.
What shapes the investigation
- 01Is there a demonstrated assignable cause, or a plausible explanation nobody has evidenced?
- 02Were retest rules defined before this event, and were they followed?
- 03What does the result imply for other batches tested in the same sequence or period?
- 04Does the trend show this result is an outlier, or the visible end of a drift?
Things to consider, not conclusions to adopt
- Invalidating a result requires a documented assignable cause; a passing retest alone does not invalidate a failing original.
- Averaging a failing result with passing retests, or selecting among results, is a well-recognised data integrity concern.
- The FDA guidance on investigating OOS results is the most detailed public treatment and is a useful reference regardless of market.
- Where affected product has been released, consider whether quality defect and recall processes are engaged.
What sites commonly get wrong
- Invalidating on a suspected rather than demonstrated cause.
- Testing into compliance — repeated injections until one passes, earlier ones unexplained.
- Truncating Phase II because the batch is commercially needed.
- Failing to consider other batches tested in the same analytical sequence.
Ten steps, in this order
- 01
Contain
Stop the situation getting worse. Quarantine affected material, halt the process step if continuing would compound the problem, and secure the area or system involved.
- 02
Assess
Establish what is known versus assumed. What happened, when, to what, and who observed it. Resist the pull to conclude a cause in the first hour.
- 03
Escalate
Notify according to your own procedure. Getting the right people informed early costs little; discovering later that QA or the QP was not told is itself a finding.
- 04
Investigate
Establish the cause with evidence rather than plausibility. Depth should be proportionate to risk, but the standard for a confirmed cause does not move.
- 05
Document
Record contemporaneously as you go. Reconstructing a record afterwards converts a quality problem into a data integrity problem, which is a different order of seriousness.
- 06
Determine impact
Assess product impact beyond the batch in front of you — other batches sharing equipment, materials, personnel or time window, and material already released.
- 07
Correct
Fix the immediate instance, and separately address the cause. Conflating correction with corrective action is the most common weakness in a response.
- 08
Prevent recurrence
Address why the process permitted the event. Where the design invites the error, training a person not to make it is a delay rather than a correction.
- 09
Verify effectiveness
Check against a criterion defined before implementation. This is the step most often skipped, and the one that decides whether the event returns as a repeat finding.
- 10
Close and monitor
Close with evidence attached, and keep the indicator under review long enough to know the fix held rather than merely completed.
Background and next steps
This is quality guidance, not legal advice
This is practical quality guidance, not legal or regulatory advice. Whether a specific event triggers a particular regulatory obligation depends on the product, the market, the marketing authorisation and the facts. Assess against your own procedures, and take qualified advice where the situation may involve notification, recall or a deliberate act.
A date you did not choose
If there is a response deadline or an investigation that has to hold up under scrutiny, a short call is the fastest route to a view on what to do first.