Usage Examples
- We have an OOS on the assay for lot 4471, and the batch already shipped.
- The OOS investigation found a transcription error in the calculation, not a product failure.
- Do not close that OOS at the lab bench; it has to extend to the other lots on that line.
What is Out of Specification (OOS)?
Out of Specification (OOS) is a laboratory test result that falls outside an established specification or acceptance criterion, obligating a documented investigation and a batch disposition decision before the material can be released.
Out of Specification results exist as a regulated category because a failing test is ambiguous: it can mean the batch is bad or that the laboratory made an error. 21 CFR 211.192 removes the discretion to guess. Any failure of a batch or its components to meet specification must be thoroughly investigated, whether or not the batch has already been distributed.
Out of Specification covers any result compared against an established specification: release testing, in-process checks, stability time points, components and raw materials, and retained samples. It does not cover results that merely look unusual while still passing, and it is not the same as a manufacturing deviation. An OOS is a measurement failing an acceptance criterion, not a procedural departure from an approved instruction.
Out of Specification results are handled as a documented investigation with a defined endpoint. In practice the laboratory record is examined first, because 211.194(a)(4) requires a complete record of all data secured in each test, including graphs, charts, and instrument spectra. The investigation must extend to other batches and products that may share the failure, and close with a written conclusion and followup.
Not to be confused with
- Out of Trend (OOT)
- an OOT result still meets the specification and only departs from the historical pattern. An OOS is a pass/fail verdict against a fixed limit, which is the condition 21 CFR 211.192 names directly.
- Deviation
- a deviation is a departure from an approved procedure or process; an OOS is a number that fails a limit. A batch can deviate and still test in specification, and can test OOS with every step performed correctly.
- Atypical or out-of-expectation result
- firm-defined internal categories, not regulatory ones. Relabelling a failing result does not move it out of 211.192; the comparison against the specification decides, not the wording in the SOP.
- CAPA
- CAPA is what may follow once a cause is established. The OOS is the trigger and the investigation is the obligation; corrective and preventive action is a separate downstream commitment with its own record.
The obligations attach the moment a result fails a specification, not when the investigation concludes.
What you must do
- 1Determine conformance to final specifications by laboratory testing for each batch, including identity and strength of each active ingredient, prior to release21 CFR 211.165(a)
- 2Investigate thoroughly any failure of a batch or any of its components to meet any of its specifications, whether or not the batch has already been distributed21 CFR 211.192
- 3Extend the investigation to other batches of the same drug product and other drug products that may have been associated with the specific failure or discrepancy21 CFR 211.192
- 4Make a written record of the investigation that includes the conclusions and followup21 CFR 211.192
- 5Retain a complete record of all data secured in the course of each test, including all graphs, charts, and spectra from laboratory instrumentation, so the original OOS value survives the investigation21 CFR 211.194(a)
- 6Reject drug products failing to meet established standards or specifications and any other relevant quality control criteria21 CFR 211.165(f)
Common mistakes
Retesting until a passing result appears
Repeat testing without an established, documented cause substitutes a search for a better number in place of an investigation. It also fails on the record alone: 211.194(a)(4) requires a complete record of all data secured in the course of each test, so the failing result stays visible to every inspector who reads the file.
Closing the investigation at the laboratory bench
When no laboratory cause is found, the investigation is not finished. 211.192 requires it to extend to other batches of the same product and other products associated with the failure. Stopping at "no cause found, retest passed" leaves the product-quality question unanswered and the written conclusion indefensible.
Treating distributed batches as out of reach
211.192 requires investigation whether or not the batch has already been distributed. Teams routinely deprioritise an OOS on shipped material, which is precisely the scenario the clause was written for, and the one where an unfinished investigation forces a market-action decision made without data.
When This Matters
- We have an OOS on the assay for lot 4471, and the batch already shipped.
- The OOS investigation found a transcription error in the calculation, not a product failure.
- Do not close that OOS at the lab bench; it has to extend to the other lots on that line.
Frequently Asked Questions
An OOS result can never be deleted from the record. 21 CFR 211.194(a)(4) requires a complete record of all data secured in the course of each test, so the original value stays. An investigation can document a conclusion and followup that a laboratory cause produced it, but the result remains.
Related Use Cases
- Pharma Use Cases
Cut NDA and sNDA prep time by 60% with AI-assisted drafting and automated readiness checks
- Biotech Use Cases
Compress IND prep from 8-12 weeks to under 3 weeks with AI-assisted drafting and validation
- CMC Workflows
Track ICH quality guidelines automatically and get alerts when changes impact your products
- Quality/QA Workflows
Track GxP regulation changes and enforcement trends
