Out-of-specification software that survives an FDA lab-data inspection.
V5 runs OOS investigations exactly as FDA's 2006 guidance requires: Phase I laboratory assessment first, Phase II manufacturing investigation only if lab error is disproven, hypothesis testing with pre-approved retest justification, and every decision e-signed with rationale.
What breaks without this.
Retesting into compliance
Analysts retest until they get a passing result — with no documented hypothesis, no pre-approved justification, and no idea the FDA calls that a 483 waiting to happen.
Phase I skipped
Everyone jumps to manufacturing investigation before ruling out lab error, so the real root cause is buried under process theories.
Trends invisible
Individual OOS records close in isolation. Nobody sees the same assay drifting across three batches until the FDA does.
Records-by-execution. Compliance, by design.
Enforced Phase I / Phase II sequence
V5 blocks Phase II from opening until Phase I lab-error assessment is closed with signed rationale.
Pre-approved hypothesis testing
Any retest requires a written hypothesis, an approver signature, and a documented sampling plan — before the second injection runs.
Automatic trending across batches, assays, analysts and instruments
OOS records link to the assay, the column, the analyst and the equipment — trends surface at review, not at inspection.
MHRA / FDA / EMA decision tree built in
Confirmed OOS routes to batch rejection or investigation extension automatically; invalid OOS requires documented invalidation criteria.
Full linkage to deviation, CAPA and batch record
One OOS opens the deviation, holds the batch, links to the CAPA and appears in the APQR — no separate systems.
What to look for when you're buying.
OOS management is one of the most-cited lab investigation topics. Criteria below distinguish real Phase I/II workflow from a checkbox tracker.
Phase I / Phase II gating
What it tests: Are Phase I (lab error investigation) and Phase II (manufacturing) enforced as sequential gates with defined evidence?
Why it matters: MHRA and FDA cite conflated phases regularly.
V5: Phase I completes with signed rationale before Phase II opens; skipping is blocked.
Result invalidation authority
What it tests: Is invalidation restricted, e-signed and requires objective evidence?
Why it matters: Result testing-into-compliance is the classic finding.
V5: Invalidation requires objective evidence and quality-unit e-sig; audit trail immutable.
Retest and resample rules
What it tests: Are retest/resample rules formalised in the workflow?
Why it matters: Ad-hoc retests are the fastest way to a 483.
V5: Retest/resample rules configured per method; violations blocked.
Batch impact assessment
What it tests: Does OOS drive an impact assessment across other batches on the same equipment/reagent/method?
Why it matters: Missed forward impact widens recalls.
V5: Live impact assessment across analytical genealogy.
MHRA / FDA guidance alignment
What it tests: Are the workflow steps aligned to FDA Guidance for Industry: Investigating OOS Test Results?
Why it matters: Deviating from published guidance means explaining yourself.
V5: Workflow mirrors FDA guidance steps.
Spreadsheet vs legacy QMS vs V5.
OOS handling: paper vs QMS module vs V5.
| Capability | Spreadsheet | Legacy QMS | V5 Ultimate |
|---|---|---|---|
| Phase I / II gating | Manual | Sometimes | Enforced sequential |
| Invalidation control | Signature | Optional | Enforced with objective evidence |
| Batch impact | Manual | Report | Live from genealogy |
| Guidance alignment | Author-dependent | Static | Native workflow |
The clauses, verbatim — and how V5 answers each.
OOS clauses inspectors cite.
Any unexplained discrepancy... shall be thoroughly investigated...
V5: OOS opens investigation; closure requires rationale.
Phase I includes assessment of the accuracy of the laboratory's data...
V5: Phase I gate with defined evidence.
Any out-of-specification result obtained should be investigated and documented...
V5: Full investigation record with document trail.
OOS/OOT results should not be retested to obtain a passing result...
V5: Retest requires objective justification captured in-system.
Step by step on the floor.
OOS lifecycle in V5.
- 1Detect
Result flagged OOS
LIMS/instrument capture triggers investigation.
- 2Phase I
Lab investigation
Method, equipment, analyst, standards reviewed and signed.
- 3Phase II
Manufacturing investigation
Only if Phase I complete; process, materials, environment reviewed.
- 4Impact
Forward assessment
Other batches on same context surfaced.
- 5Close
Disposition & CAPA
Batch disposition e-signed; CAPA raised if warranted.
The math, with the assumptions visible.
OOS ROI: shorter investigations, fewer repeat findings, tighter release.
OOS cycle time
Structured phase gating and pre-linked data.
Repeat OOS on same context
Impact assessment surfaces systemic cause.
OOS-related audit findings
Guidance-aligned workflow.
Most labs cut OOS cycle time in half within a quarter.
What changed on the floor.
Setting
A QC lab handling ~200 OOS/year across three sites.
Before
Average OOS cycle 28 days; two consecutive inspections cited testing-into-compliance patterns.
After
Cycle 9 days; testing-into-compliance patterns eliminated; last inspection closed without OOS findings.
Proof points
- FDA Phase I → Phase II sequence enforced by workflow, not policy
- Retest justification signed BEFORE the retest runs — Barr Labs proof
- Cross-batch, cross-analyst trending surfaces drift early
- Every decision Part 11 e-signed with rationale
Built to satisfy
- FDA Guidance for Industry: Investigating OOS Test Results (2006)
- 21 CFR 211.192 (production record review)
- US v. Barr Laboratories (foundational OOS case law)
- MHRA OOS Guidance 2017
- EU GMP Annex 11 (computerised systems)
Related on V5
Frequently asked questions
How does V5 stop 'testing into compliance'?+
Any retest requires a written hypothesis and an approver e-signature before the second injection runs — the retest cannot be recorded without them. The audit trail proves the hypothesis existed before the result did.
Does V5 enforce Phase I before Phase II?+
Yes. Phase II (manufacturing investigation) cannot be opened until Phase I (laboratory assessment) is closed with signed rationale for confirmed or invalidated OOS.
Can V5 trend OOS across products and analysts?+
Yes — every OOS is tagged with assay, method, column/instrument, analyst and batch. Trending dashboards surface drift before it becomes an inspection finding.
See V5 on your own line.
Free trial, no card. Live in 7 days with guided onboarding.