What is review by exception for batch records?
By Savi C., Co-Founder · Published Nov 16, 2026
How it works
In a traditional review, QA reads every page of an executed batch record and checks every entry by hand. In review by exception, a system checks every entry against defined rules first: limits, required fields, time windows, signatures and calculations. The reviewer then sees the entries that broke a rule, with the full record still available behind them.
The approach grew up around electronic batch records and MES, where the data is already structured. That is why many sites running on paper assumed it was not available to them.
What usually counts as an exception
Data and limits
- A value outside its specified limit or range
- A required entry left blank
- A calculation that does not carry through correctly
- A step performed outside its allowed time window
Signatures and documentation
- A missing or out-of-sequence signature or date
- A correction that does not follow good documentation practice
- An unexpected edit in an electronic record’s audit trail
- A deviation that is not referenced in the batch record, or a referenced deviation that is still open
Full review compared with review by exception
Full manual review
QA reads every entry on every page
Review by exception
Every entry is checked by rule, and QA reads the exceptions
Full manual review
Time scales with the size of the record
Review by exception
Time scales with the number of problems
Full manual review
Consistency depends on the individual reviewer
Review by exception
The same rules apply to every batch
Full manual review
Trends across batches are hard to see
Review by exception
Exceptions can be counted and trended across batches
What regulators expect
21 CFR 211.192 requires the quality control unit to review and approve production and control records before release, and to investigate unexplained discrepancies. It does not prescribe how that review is performed. What matters is that the review is complete and that the tool doing the screening is fit for its intended use.
In practice that means the exception rules are documented and validated under your computerised system procedure, following a risk-based approach such as GAMP 5, and that the full record remains available to the reviewer and to an inspector. ISPE GAMP 5 second edition also advises that routine audit trail review focus on audit trails linked to GxP records.
Review by exception on paper records
Paper records can be reviewed by exception once the entries can be read reliably, including handwriting. Litewave reads scanned paper and electronic batch records, checks every entry against your master record and specifications, and presents QA with the exceptions, each linked to its source page. At a leading global generic API manufacturer running 100 to 150 page paper batch records, batch disposition time fell by 85%, with no eBPR migration. Litewave proposes, qualified people approve.
Questions we get asked
Does FDA accept review by exception?
The regulation does not prescribe a review method. It requires the quality control unit to review and approve production and control records before release. Review by exception is a way of performing that review, and it holds up when the screening rules are validated and the full record remains available.
Does QA still need to look at the whole record?
QA stays responsible for the whole record and approves it. Review by exception changes where the reviewer spends time, not what they are accountable for, and the complete record remains available for any entry they want to see.
Do we need an electronic batch record system first?
Not necessarily. Review by exception needs the entries to be readable as data. That can come from an EBR or MES, or from software that reads scanned paper records reliably.
