OOS Investigation Checklist for GMP QC Laboratories
An out of specification result is any test result that falls outside the acceptance criteria in a specification or approved procedure. Regulators treat the handling of OOS results as a test of a QC lab's integrity, so the sequence matters. This checklist keeps the investigation in order.
0 of 37 items complete
15 critical items still open - these are the highest-risk gaps.
Immediate response (analyst and supervisor)
Phase I: laboratory assessment
Retesting and resampling rules
Phase II: full-scale investigation (production and QC)
Conclusion, disposition and closure
Every critical item must be ticked before the OOS report is closed. Phase I does not end with a retest unless a lab error is proven. Based on the structure of FDA guidance on investigating out of specification results (2006) and EU GMP Chapter 6, but your own SOP governs.
OOS history and related batches from ERP data
An optional outline for finding related batches and equipment history when an OOS is opened.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through the groups in order. Start the first group the moment a suspect result is seen, before any retest. Tick items as you complete them, and keep a note of where the evidence is, such as the notebook page or the audit trail ID. Export the checklist to PDF to attach to the investigation report. The critical items are the ones inspectors most often cite as failures, so none should remain open at closure.
- Do not retest before Phase I is done
- Never discard the original preparations
- Involve QA from the first day
- Keep a single OOS number from start to end
Phase I and Phase II
Phase I is the laboratory assessment, led by the analyst and supervisor, looking for obvious errors in calculation, instrument, standard or method execution. If a clear assignable cause is found and documented, the original result may be invalidated and a retest performed. If not, the investigation moves to Phase II, which is a full-scale investigation involving production, QA and possibly other batches. The FDA 2006 guidance sets out this structure.
Retesting without testing into compliance
The retest plan must be written before testing, with a fixed number of retests and rules for evaluating them. Repeating a test until it passes and ignoring the failing results is considered testing into compliance and is a data integrity violation. Averaging is acceptable only when averaging is the method's defined reporting rule. All results, valid and invalid, stay in the records with the reason for any invalidation.
Common mistakes and systems notes
Findings often cite informal retesting, late QA notification, missing audit trail review, investigation that ignores other batches and root cause stated only as analyst error. In LIMS and ERP quality modules, place the batch on quality hold when the OOS is registered. OOT (out of trend) results, which are inside the specification but atypical, need their own procedure but benefit from the same discipline.
Frequently Asked Questions
What is the difference between OOS and OOT?
An OOS result is outside the registered or approved specification. An OOT result is within specification but outside the expected trend, for example a stability result dropping faster than earlier lots. OOT is an early warning and should trigger a review.
Can I retest an OOS sample immediately?
Not before documenting why. A retest is justified when a laboratory error is confirmed or when the approved SOP defines a retest plan. Immediate unplanned repeating is a classic data integrity finding.
How long should an OOS investigation take?
Many SOPs set 30 working days for closure, with the FDA expecting investigations to be timely and documented. Extensions need written justification, and the batch stays on hold while the investigation is open.
Can an OOS be invalidated?
Yes, only when a documented, verified laboratory error is found as the assignable cause. Suspicion alone, or a later passing result, does not invalidate a failing result.
Netray can help build a private assistant that checks LIMS and ERP data for related batches when an OOS is opened. The checklist works fully on its own.
Related Tools
GMP Deviation Report Template
Write a structured pharmaceutical deviation report: event, immediate action, classification, impact, root cause, CAPA and QA approval.
Quality & InspectionStability Study Pull Schedule Worksheet
Plan stability pulls by condition and time point, calculate sample units needed and keep a clear pull calendar for each batch.
Compliance & ContractsGMP Change Control Form Template
Document a GMP change request with justification, impact on validation and filings, risk rating, implementation plan and QA closure.
ERP OperationsFDA 21 CFR Part 11 Readiness Assessment
Answer 8 questions on e-signatures, audit trails, access control, and validation status to see how ready your electronic records and systems are for FDA scrutiny.
More Quality & Inspection tools
See all- Cleaning Validation MACO Calculator
- ICH Q1A Stability Storage Conditions Reference
- Media Fill Contamination Rate and Confidence Limit Calculator
- Steam Sterilization F0 Lethality Calculator
- Accelerated Stability Arrhenius Shelf Life Calculator
- Content Uniformity Acceptance Value Calculator
- Endotoxin Limit and Maximum Valid Dilution Calculator
- SAP QM Process Capability Cp Cpk Calculator
- SAP QM Lot Rejection Rate, PPM and Sigma Level Calculator
Keep exploring
Free tools
- Pharma Batch Genealogy SQL Query GeneratorFill in plant, material and batch to produce SQL for forward and backward batch traces on SAP material documents.
- Pharma Data Integrity ALCOA+ Audit ChecklistWalk through ALCOA+ expectations for paper records, lab instruments and electronic systems in a regulated plant.
- Pharma GMP Inspection Readiness AssessmentScore how ready your site is for a regulatory GMP inspection and see where to focus first.
Guides
- SyteLine Non-Conformance Report (NCR) Management ConfigurationConfigure SyteLine non-conformance report tracking and disposition workflows. Set up NCR creation, investigation, and resolution processes in CloudSuite Industrial.
- ERP Security Incident Response PlanERP system forensics within an incident response plan: preserve audit logs and database snapshots, scope the breach, then contain, recover and review.
AI on your ERP
- AI for Oracle EBS in Pharmaceuticals: Batch Genealogy, Quality Data, and Validation-Aware DesignAI for Oracle E-Business Suite in pharma: batch records, lot genealogy, OPM quality results and deviations, private, read-only and designed for validated environments.
- AI for ERP in Pharmaceutical Manufacturing Under GMPPrivate AI on the ERP of a GMP pharmaceutical plant: batch genealogy, deviation and CAPA triage, release readiness and Part 11 aware, read-only access.