Batch record review software — built for review by exception.
V5 surfaces only what QA needs to see — missing signatures, out-of-spec readings, deviations, skipped steps — instead of forcing a page-by-page review of every batch. The clean batches release in minutes; the exceptions get the attention they deserve.
What breaks without this.
Page-by-page paper review burns QA hours
A 40-page batch record reviewed line by line costs 2–4 hours of senior QA time — every batch, every day.
Exceptions hide in the noise
When everything looks the same, the missing initials and the OOS reading slip through to release — and the FDA finds them.
Release backlogs delay shipment
Paper review queues build up over the weekend; product sits in quarantine costing working capital and customer service-levels.
Records-by-execution. Compliance, by design.
Exception-only review queue
V5 only puts a batch in front of QA when something needs attention: missing signature, OOS, deviation, skipped step, out-of-sequence event. Clean batches auto-route for release.
Side-by-side exception evidence
Each flagged item opens with the rule it broke, the evidence (scan, e-signature, sensor reading), and the linked deviation/CAPA in one pane.
E-signature release in two clicks
QA reviews the exception, applies the disposition, and Part 11-compliant e-signs the release — without leaving the screen.
Audit trail that survives inspection
Every review action — open, comment, accept, reject, escalate — is captured with user, time and reason in the immutable Part 11 trail.
What to look for when you're buying.
Review-by-exception either accelerates release or hides risk. Criteria below tell the two apart.
Exception definition transparency
What it tests: Is what counts as an exception (missing sig, OOS, deviation, skipped step, aged data) explicit and versioned?
Why it matters: Silent exception rules become the next 483.
V5: Exception logic is a controlled configuration under change control.
Reviewer workspace
What it tests: Does the reviewer land on a single screen with only the exceptions and one-click drill-down?
Why it matters: Page-by-page review is the failure mode.
V5: Exception-first workspace with cross-record navigation.
QP / QA e-sign at release
What it tests: Is the release signature Part-11 and per-record?
Why it matters: Batch-level release without step-level attestation is challenged.
V5: Per-record e-sig with two-factor and reason-for-signature.
Right-first-time metric
What it tests: Is RFT computed live and trended?
Why it matters: You improve what you measure.
V5: RFT per line, product, shift and operator; feeds Q10 review.
Exception-to-CAPA emission
What it tests: Does an exception route to deviation/CAPA when required?
Why it matters: Otherwise exceptions accumulate silently.
V5: Configurable routing to deviation and CAPA with SLA.
Spreadsheet vs legacy QMS vs V5.
Review by exception in V5 vs paper vs legacy EBR.
| Capability | Spreadsheet | Legacy QMS | V5 Ultimate |
|---|---|---|---|
| Page-by-page burden | Full | Full | None for clean batches |
| Exception rules versioned | N/A | Static | Under change control |
| RFT metric | Ad-hoc | Quarterly | Live |
| QP/QA e-sign | Wet ink | Add-on | Native Part-11 |
The clauses, verbatim — and how V5 answers each.
Batch release clauses and V5's answer.
All drug product production and control records... shall be reviewed and approved by the quality control unit to determine compliance with all established, approved written procedures before a batch is released or distributed.
V5: QA sees every batch; only exceptions require deep review; release e-signed per record.
Batch production and control records shall be prepared for each batch...
V5: eBR is the record — captured contemporaneously.
Written procedures should be established and followed for the review and approval of batch production and laboratory control records...
V5: Approval workflow with attributable e-sig.
Step by step on the floor.
Review by exception in five steps.
- 1Produce
eBR captured at execution
Kiosk enforces steps and signatures inline.
- 2Screen
Rules classify batch
Exceptions or clean.
- 3Review
Exceptions surfaced
Reviewer workspace only shows what needs eyes.
- 4Route
Deviations opened
Where required, exceptions raise deviation / CAPA.
- 5Release
QA/QP e-signs
Per-record with reason-for-signature.
The math, with the assumptions visible.
Cycle-time compression is the headline ROI.
Clean-lot review time
Zero page-by-page for clean lots.
Time to release
Exception queue only.
Cost per released lot
QA capacity redirected to real risk.
Sites usually redirect 40-60% of QA review capacity to prevention within a quarter.
What changed on the floor.
Setting
A CDMO releasing 40 lots/week.
Before
Average release lead-time 6 days; QA overtime routine.
After
Clean-lot release same-day; QA overtime eliminated within two months.
Proof points
- Review-by-exception queue auto-built from MBR rules
- Part 11 e-signature on every disposition
- Linked deviation / CAPA / OOS records in one pane
- Typical QA release time drops from hours to minutes per batch
Built to satisfy
- 21 CFR 211.192 (Production record review)
- 21 CFR 211.188 (Batch production and control records)
- 21 CFR Part 11 / EU Annex 11
- EU GMP Chapter 4 (Documentation)
- ICH Q7 §6.7 (Batch production record review)
Related on V5
Frequently asked questions
What is review by exception?+
An FDA- and EMA-endorsed model where only batches with exceptions (missing data, OOS, deviation, skipped step) are routed for full QA review. Clean batches release automatically against pre-approved rules in the MBR.
Is review by exception compliant with 21 CFR 211.192?+
Yes — provided the exception-detection rules are documented in the validated MBR, the exception list is reviewed and signed by QA, and the audit trail captures every decision. V5 enforces all three.
How fast can we deploy?+
Most sites move from paper batch review to exception review in 7–14 days once the MBR is digitised.
See V5 on your own line.
Free trial, no card. Live in 7 days with guided onboarding.