OOS Investigations: What FDA Expects and Where Programs Break Down

VaLogic a GxP compliance service provider's logo

Contact Us

OOS Investigations: What FDA Expects and Where Programs Break Down

OOS Investigations: What FDA Expects and Where Programs Break Down

An out-of-specification result is not itself a compliance failure. How you investigate it determines whether you have a defensible quality system or a vulnerability waiting to be cited.

FDA’s guidance on investigating OOS laboratory test results, first issued in 2006 and still the authoritative reference, lays out a two-phase structure that many organizations follow in principle but struggle to execute consistently under pressure.

Phase 1: The Laboratory Investigation

The first phase of an OOS investigation belongs entirely to the laboratory. Before any conclusion about the product is drawn, the lab must examine whether the result could be attributed to analyst error, instrument malfunction, sample preparation problems, or calculation mistakes.

This phase must be documented in real time. The investigation cannot begin retroactively after a retest has already been run. If Phase 1 identifies an assignable laboratory cause, the original result can be invalidated, but only with documented justification. “We retested and the result was within spec” is not a justification.

Phase 2: The Full-Scale Investigation

If Phase 1 finds no assignable lab error, the investigation must expand. Phase 2 involves the manufacturing side: batch records, raw material testing, environmental conditions, equipment history, and process parameters.

Phase 2 requires a root cause conclusion. Investigations that end with “no assignable cause found” are not compliant conclusions. They signal that the investigation was not thorough enough.

Where OOS Programs Break Down

The most common failure modes in OOS investigations follow a recognizable pattern:

Pressure to release product leads to early retesting before Phase 1 is complete. Inconclusive Phase 1 findings are treated as sufficient to close the investigation. Phase 2 root cause analysis is shallow, citing “human error” without examining why the error occurred or what system allowed it. And retest results that happen to pass are used to invalidate the original result without documented scientific justification.

Each of these patterns is visible in audit trail data and in investigation records. Inspectors know what to look for.

Building a Defensible OOS Program

A strong OOS program starts with a clear, step-by-step procedure that analysts understand before an OOS result ever occurs. It includes decision trees for when to escalate, defined timelines for each phase, and a review process that separates the analyst conducting the investigation from the supervisor approving the conclusions.

When an OOS investigation is thorough, documented, and reaches a genuine root cause conclusion, it demonstrates that your quality system is working. That is the outcome the process is designed to produce.

Facebook
Twitter
LinkedIn

Have a question or need a quote? Give us a call!

VaLogic a GxP compliance service provider's logo

Maryland Offices

Frederick Office (HQ)

  • Mon-Fri (8AM-5PM) EST
  • 21 Byte Ct, Frederick, MD
  • contactus@valogicbio.com

  • (240) 529-1673

Burtonsville Office

  • Mon-Fri (8AM-5PM) EST
  • 3901 National Drive, Burtonsville, MD
  • contactus@valogicbio.com

  • (240) 560-5588

Texas Office

  • Mon-Fri (7:30AM-4:30PM) CDT
  • 7255 Helix Park Avenue, Portal Innovations Suite 300, Houston, TX
  • contactus@valogicbio.com

  • (713) 477-9247

Join Our Newsletter

© 2025 All rights reserved


Linkedin


Youtube