← Guides

How do you automate batch record review when records are on paper?

By Savi C., Co-Founder · Published Nov 16, 2026

Why paper is the hard case

Most review automation was built for electronic batch records and MES, where entries are already structured data. Paper records hold the same information, but it is handwritten, spread across pages, corrected by hand and supplemented with glued-in printouts and attachments. Until those entries can be read reliably, a computer has nothing to check.

Replacing paper with an EBR solves this but is a large project of its own, touching every master record, the daily production routine and the validation of a new production system. The alternative is to leave production on paper and automate the review step, which is where QA time is spent after the batch is made. Operators keep the forms they know, and the change is confined to how QA receives and checks the record.

The steps

Capture
  • Scan each executed record at a resolution that keeps handwriting, strike-throughs and initials legible
  • Confirm every page is present against the record’s pagination
Extract
  • Read printed and handwritten entries, signatures, dates and corrections
  • Tie every value to the page and field it came from
Check
  • Compare each entry with the master record and specifications
  • Run calculations, time windows, signatures and GDP rules on every entry
Review
  • QA works through the exceptions, each linked to its source page
  • A qualified person approves the record before release

What to decide before you start

Records and copies

  • Whether scans are working copies for review, with the paper as the original, or controlled true copies under a documented procedure, as PIC/S PI 041-1 describes
  • How attachments, printouts and thermal paper are captured
  • How you confirm no page is missing before checking starts

The rulebook

  • Which master record version applies to each batch
  • Which entries are critical and need the strictest checks
  • What counts as an exception, and who resolves each type
  • How an entry the tool cannot read is reported: as unverified, never as passed

Control

  • Validation for intended use under your computerised system procedure, proportionate to risk
  • Part 11 controls for the electronic records and signatures the review creates, including audit trails
  • Change control for rules, models and master record updates
  • Performance measured on your own records before go-live and monitored after it

Reading handwriting is the step to test hardest

Every later check depends on extraction. If a value is misread, a correct entry may be flagged or, worse, an out-of-limit entry may be passed. Test extraction on a representative set of your own executed records, including poor handwriting, corrections and dense pages, and compare it against what your reviewers recorded. Every extracted value should link to its place on the page so a reviewer can confirm it in seconds.

Start narrow. Pick one product with a stable master record and a healthy volume of batches, and run the automated checks alongside your normal review for a defined period. Compare what each found, investigate every disagreement, and adjust the rules before you rely on them. That parallel run doubles as evidence for validation, because it shows performance on your records, your handwriting and your forms rather than on a vendor’s sample set.

Once the entries are reliable data, the review itself can work by exception, which we explain in a separate guide on review by exception for batch records.

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, it reached 99% data extraction accuracy and 85% faster batch disposition, with no eBPR migration. Litewave supports 21 CFR Part 11 electronic records, signatures and audit trails, and never dispositions a batch on its own.

Questions we get asked

Do we have to change our paper batch records to automate review?

Not necessarily. The approach above reads the records you already use. Improving form design where reviewers repeatedly find errors still helps, with or without automation.

Does Part 11 apply if production is on paper?

The paper record itself is not an electronic record. Part 11 applies to the electronic records and signatures the review system creates and relies on, such as extracted data, review findings and approvals, so those need Part 11 controls including audit trails.

Can we destroy the paper after scanning?

Only if your procedures establish the scans as true copies, verified as complete and accurate, and your retention requirements allow it. Otherwise keep the paper as the original record and treat the scans as working copies.

Sources

  1. 21 CFR 211.188, Batch production and control records (eCFR)
  2. 21 CFR 211.192, Production record review (eCFR)
  3. 21 CFR 11.10, Controls for closed systems, including audit trails (eCFR)
  4. PIC/S PI 041-1, Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments
  5. FDA, Data Integrity and Compliance With Drug CGMP: Questions and Answers (2018)