How long should batch record review take, and how do you shorten it?
By Savi C., Co-Founder · Published Nov 16, 2026
Why there is no standard answer
Regulators set what a review must achieve, not how long it takes. Under 21 CFR 211.192 the quality control unit reviews and approves all drug product production and control records, including packaging and labeling, before a batch is released, and investigates any unexplained discrepancy. A review that is fast but incomplete fails that requirement. A review that is complete but slow costs inventory, cash and shelf life.
Published figures for "typical" review time vary widely and are rarely sourced, so we do not quote one here. The more useful question is where the time in your own process goes. There are two different clocks: the hands-on time a reviewer spends reading the record, and the elapsed time from batch completion to disposition. The second includes every wait between hand-offs and is often far longer than the first.
To set a baseline, take a recent sample of batches for one product and record both clocks, the number of review findings per batch, and how many times each record went back to production. That gives you a target grounded in your own process rather than someone else’s average, and it shows which of the drivers below is costing you the most.
What drives review time
Driver
Record length and structure
Why it adds time
Every page and entry is read and checked, so a 150 page record takes longer than a 30 page one, especially if values are scattered across sections
Driver
Errors found in review
Why it adds time
Each missing signature, unexplained correction or calculation error sends the record back to production for an answer, and the clock keeps running
Driver
Open deviations and investigations
Why it adds time
Release waits for the investigation 211.192 requires, and for its conclusions and follow-up to be recorded
Driver
Hand-offs and queues
Why it adds time
Records wait between production review, QA review, laboratory results and the final approver
Driver
Attached and external documents
Why it adds time
Certificates of analysis, printouts, logbooks and labeling specimens have to be located and reconciled with the record
Driver
Reviewer variability
Why it adds time
Different reviewers check different things to different depths, so findings and rework are inconsistent
How to shorten it
Prevent errors upstream
- Trend the errors QA finds by type and by step, and fix the master record design where the same error recurs
- Give every entry a clear space, unit and expected format so operators are not left to interpret the form
- Make production review before QA a real check, as PIC/S PI 041-1 expects for critical steps, not a signature pass
- Train on good documentation practice using your own most frequent findings
Remove waiting time
- Review sections as they are completed instead of waiting for the whole batch
- Start deviation investigations as soon as the event is recorded, not when QA finds it in review
- Measure elapsed time at each hand-off so the longest queue is visible
- Agree turnaround targets between production, the laboratory and QA
Change where reviewers spend time
- Check routine entries by rule, so reviewers concentrate on what failed a rule
- Keep the full record one click or one page away from every finding
- Use one checklist for every reviewer so findings are consistent
Moving from reading to exceptions
The largest single change most sites can make is to stop asking reviewers to re-read correct entries. That is the idea behind review by exception, which we cover in its own guide: every entry is checked against defined rules first, and the reviewer works from the list of entries that broke a rule, with the full record still available. Hands-on time then scales with the number of problems, not the number of pages.
It does not remove accountability. The quality unit still approves the record before release, and the rules doing the checking are validated under your computerised system procedure.
How Litewave fits
Litewave reads paper or electronic records, checks every entry against your master record and specifications, and shows QA only the exceptions, each linked to the page it came from. At a leading global generic API manufacturer running 100 to 150 page paper batch records, hands-on review went from days to hours and batch disposition was 85% faster, with no eBPR migration. Litewave proposes, qualified people approve.
Questions we get asked
Is there a regulatory deadline for batch record review?
No. The regulation requires review and approval before release and a thorough investigation of unexplained discrepancies. It does not set a duration. Your own procedures may set internal targets.
Can we release a batch while the record review is still open?
No. 21 CFR 211.192 requires the quality control unit to review and approve production and control records before a batch is released or distributed.
What should we measure to shorten review time?
Measure hands-on review time and elapsed time to disposition separately, count review findings by type and process step, and track how long records wait at each hand-off. The biggest gains usually come from the waiting time and the recurring errors.
