In this guide 6 sections
Paper batch records work while volumes stay low and one QA person can read every page of every batch before release. Electronic records pay off when contract customers audit you, batches multiply, or errors surface weeks after the operator signed the page. Entries become timed, attributed and searchable. This is software guidance, not regulatory advice.
What a batch record has to prove
A batch manufacturing record shows that a batch was made as the master formula says, and it lists material codes, weights, equipment, operators, in-process checks and yield. Reviewers read deviations too.
Schedule M expects records that are contemporaneous, legible and traceable, and your regulator and your contract customers read the same pages with the same question. Who did what, and when?
Both formats can answer it. They differ in the effort each one demands from QA, production and the person pulling the file for an auditor on short notice.
Where paper holds up and where it strains
Paper is cheap on the shop floor at Verna, Kundaim or Corlim, where operators sign in ink, the QA head reviews and the file goes in a cupboard. For one slow product line, that suffices.
Strain shows in the details. A weight is overwritten without a single line and initials, a page goes missing between granulation and compression, and a blend time is entered after the fact. None of it shows until an auditor asks for every batch of one product in a year, and then each page must be found, read and compared by hand.
Retrieval costs the most, because finding a single batch from two years back can take an afternoon spent opening files and checking that every sheet is present.
- Overwriting and late entries
- Missing or swapped pages
- Calculation errors in yield
- Slow search across batches
- Handwriting that cannot be read later
What an electronic record changes
An electronic batch record turns each step into a field: the system refuses a weight outside its limit, stamps the time and ties the entry to a login. A deviation opens a form. Release stays blocked until QA closes it.
Printed output still exists, and QA reviews by exception, so a clean batch takes minutes and a flagged one gets full attention.
Material lot numbers link to the goods receipt, so a recall traces from the finished pack to the raw material, and equipment and cleaning records join the same file.
- Limit checks at the time of entry
- Timed entries tied to a user
- Deviation forms that block release
- Lot links from raw material to pack
- Search by product, date or operator
What changes in the audit file
The audit file stops being a stack and becomes a set of queries, such as every deviation for one product or every batch that used a given lot. Formula changes appear with their approvers.
Contract customers value that last item most, because a quiet formula change is exactly what they fear when they hand you a product to make. Electronic systems bring their own duties. Audit trails must not be editable, user roles need review, backups need testing and the software needs validation evidence that QA has read and filed beside the master formula.
Ask any vendor to show the validation documents rather than a promise, and read them line by line with QA beside you before you sign anything.
A sensible way to move
Do not convert every product at once. Pick one product with a steady schedule and a customer who audits often, then run paper and electronic side by side for three batches and compare what each caught.
Keep it small. Write a short plan with QA, production and the contract customer before you start, and agree which signatures are required and where printed copies are kept.
Ask your regulatory adviser to review the plan, the validation evidence and the signature rules, and keep paper as the record until they agree.
Batch record comparison worksheet
A table puts paper in one column and electronic in the other, with rows for entry errors, review time, deviation closure, retrieval time, audit trail, validation evidence and cost. A strip underneath names the pilot product, the three trial batches, the QA reviewer and the person who signs off before the pilot extends to a second product.
Open a blank worksheet to printQuestions owners ask
Is an electronic batch record required for a small pharma plant?
Not generally, because paper records are accepted when they meet GMP expectations, and the common reasons to switch are customer contracts or a growing batch count. Read your agreements.
Does Schedule M say anything about electronic records?
Ask your regulatory adviser for the current text of the schedule, because requirements change and this guide cannot quote them reliably. The software view is that, whichever format you use, entries must be timed, attributable and unaltered, with the history of each change visible to reviewers.
Can we go electronic for only some products?
Yes, and that is the usual route: start with one product, run it beside paper for a few batches and extend once QA is comfortable with the electronic review.
What should we ask a vendor first?
Ask for the audit trail design, the validation documents, a sample deviation form, and an explanation of how master formula changes are approved, recorded and shown to an auditor.