AI record review vs an EBR or MES: do you need both?
By Savi C., Co-Founder · Published Nov 16, 2026
What each one does
EBR or MES
Guides operators step by step during execution
AI record review
Works on records after or alongside execution
EBR or MES
Prevents some errors at entry: limits, required fields, sequence
AI record review
Finds errors in what was recorded, including on paper
EBR or MES
Needs every master record built in the system before use
AI record review
Reads your existing master records and specifications
EBR or MES
Covers what happens inside the system
AI record review
Can cover paper attachments, logbooks, certificates and other documents together
EBR or MES
A large implementation and validation project per site
AI record review
Can be scoped to one product or record type first
EBR or MES
Review by exception for data captured in the system
AI record review
Review by exception for paper and electronic records
Why they are not substitutes
An EBR or MES is an execution system. Its biggest benefit is prevention: a value outside its limit can be stopped at the moment it is entered, steps cannot be skipped, and signatures are enforced. That is something no review tool can do after the fact, and for high-volume products the case for it is strong.
An AI review tool is a checking system. It does not stop an error from being made, but it can check every entry in a record that already exists, whatever form it is in. For a site that runs on paper, it is a way to get the review speed of review by exception without the cost, time and validation effort of building every master record into an MES first.
Neither changes the requirement. Under 21 CFR 211.192 the quality control unit reviews and approves the production and control records before release, whether those records were produced in an MES, on paper, or both.
Which one fits your situation
An EBR or MES is the stronger first step when
- You are building a new line or site and can design the records in from the start
- Most errors you see are preventable at entry: skipped steps, out-of-range values, missing signatures
- You need tight equipment integration and real-time process control
AI record review is the stronger first step when
- Your records are on paper, or a mix of paper and electronic
- Release is held up by review time rather than execution errors
- An MES migration is years away, or not planned for every product
- Your review spans documents an MES does not hold: CoAs, logbooks, deviation reports
Both make sense when
- You run an EBR for some products and paper for others
- Your EBR batch record still carries paper attachments or printouts that someone reads by hand
- You want independent checks across systems, for example batch record against laboratory results and supplier certificates
Validation is different for each
Both are computerised systems and both are validated for intended use. The scope differs. An MES validation covers master recipe configuration, execution logic, interfaces and equipment, and Annex 11 expects built-in checks for data exchanged between systems. An AI review validation centres on accuracy: how well the tool reads records and how reliably it flags what it should, measured on your own records against your own reviewers.
Running both does not mean validating the same thing twice. Define which checks each system owns, so the AI review does not duplicate limits the EBR already enforces at entry, and so nothing falls between the two. 21 CFR 211.188 requires a complete record for each batch whichever system holds it, and the review has to cover all of it.
Review by exception without an EBR migration
At a leading global generic API manufacturer running 100 to 150 page paper batch records, with no eBPR migration.
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. It sits beside an EBR or MES rather than replacing one. Litewave proposes, qualified people approve.
Questions we get asked
Does AI record review replace an MES?
No. An MES controls execution and prevents some errors at entry, which a review tool cannot do. AI review checks records that already exist. Many sites will use both, for different products or different parts of the record.
We already have an EBR. Why would we need AI review?
You may not, for the data the EBR captures and checks well. The gaps are usually paper attachments, supplier certificates, logbooks and checks that span documents. Map what QA still reads by hand before deciding.
Can we do review by exception on paper?
Yes, if the entries can be read reliably as data, including handwriting. Review by exception needs structured data to check against rules, not a specific system of record.
Sources
- 21 CFR 211.188, Batch production and control records (eCFR)
- 21 CFR 211.192, Production record review (eCFR)
- 21 CFR 211.68, Automatic, mechanical and electronic equipment (eCFR)
- EudraLex Volume 4, Annex 11, Computerised Systems
- Litewave case study, batch disposition at a leading global generic API manufacturer
