Batch Record Review · RBE · QA release
Batch record review by exception.
QA sees the exceptions first, with the full record one tap away.
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.
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.
What goes wrong today3 common problems
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.
Everything V5 does here4 capabilities
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.
How it works, step by step5 steps
Review by exception in five steps.
- eBR captured at execution. Kiosk enforces steps and signatures inline.
- Rules classify batch. Exceptions or clean.
- Exceptions surfaced. Reviewer workspace only shows what needs eyes.
- Deviations opened. Where required, exceptions raise deviation / CAPA.
- QA/QP e-signs. Per-record with reason-for-signature.
What to look for when choosing
Review-by-exception either accelerates release or hides risk. Criteria below tell the two apart.
Exception definition transparency
Is what counts as an exception (missing sig, OOS, deviation, skipped step, aged data) explicit and versioned? Exception logic is a controlled configuration under change control.
Reviewer workspace
Exception-first workspace with cross-record navigation.
QP / QA e-sign at release
Is the release signature Part-11 and per-record? Per-record e-sig with two-factor and reason-for-signature.
Right-first-time metric
Is RFT computed live and trended? RFT per line, product, shift and operator; feeds Q10 review.
Exception-to-CAPA emission
Does an exception route to deviation/CAPA when required? Configurable routing to deviation and CAPA with SLA.
V5 compared with other approaches
Review by exception in V5 vs paper vs legacy EBR.
| capability | spreadsheet | legacy Qms | v5 |
|---|---|---|---|
| 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 |
Regulations this supportsYour quality team stays responsible for compliance
Batch release clauses and V5's answer.
21 CFR 211.192
QA sees every batch; only exceptions require deep review; release e-signed per record.
21 CFR 211.188
eBR is the record — captured contemporaneously.
ICH Q7 §6.7
Approval workflow with attributable e-sig.
Standards referenced
- 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)
Common questions3 answers
- 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.