Batch records: the contemporaneous account of what happened to a production lot

Recorded as it happens, or it is a reconstruction

Entries made at the time carry weight; entries made at the end of a shift from memory and a scrap of paper do not, however accurate the person tries to be. The practical requirements are that the record is at the point of work, that the operator records the value observed rather than the value expected, and that the entry is attributable to a person and a time. Transcription is where records fail: copying figures from a notebook into the official document introduces error and destroys the contemporaneous quality that makes the record evidence rather than testimony.

What the record has to carry

The core is the same across sectors: the lot identity and quantity, the materials and their supplier lot numbers with quantities actually used, the equipment and lines involved, the process parameters achieved with the limits they were checked against, the personnel who performed and verified key steps, in-process and final test results, a reconciliation of input against output including scrap, and any deviation with its disposition. What varies is depth and formality. The reconciliation deserves particular attention, since an unexplained gap between material issued and product accounted for is a genuine signal, not a paperwork nuisance.

Deviations belong inside the record

Something departs from the intended process in a meaningful proportion of batches: a parameter briefly outside range, a delay between steps, a substituted piece of equipment, an addition made in two parts. The failure is not the deviation but handling it in conversation while the record shows a clean run. Every departure needs recording as it occurs, with what happened, when, what was done and who authorised continuing. This is uncomfortable because it makes problems visible, and that visibility is precisely the value — a pattern of the same deviation across many batches is a process that needs changing rather than repeated ad hoc approval.

Review before release and what the reviewer is actually looking for

Someone independent of the production of that lot checks the record before the product goes anywhere. They are looking for completeness, for entries that contradict each other, for results outside limits that were signed as acceptable, for a reconciliation that does not close, for signatures missing or applied by someone not trained for that step, and for deviations without a documented disposition. Review by exception — where the system flags anomalies and the reviewer concentrates on those — is faster and generally better than a page-by-page read, provided the flags are defined properly and somebody periodically checks what the flagging misses.

Retention and the retrieval you will need under pressure

The record will be wanted at the worst possible moment: a customer complaint, a field failure, an inspection, a supplier issue affecting several lots. Retention periods are usually set by regulation or by product life, and the operational question is not how long you keep it but how quickly you can produce a specific lot's complete record, including the attachments, charts and certificates that go with it. Test that. A plant that takes days to assemble one batch record has an archive rather than a retrieval system, and will discover this while a customer is waiting.

Frequently asked questions

How should an error in a batch record be corrected?

Never obscured. Strike a single line through the wrong entry so it remains readable, write the correct value beside it, and add the initials, the date and a short reason. Overwriting, erasing or using correction fluid destroys the credibility of the whole record, and an inspector who finds it will look much harder at everything else. Electronic systems achieve the same through an audit trail that keeps the original value visible, which is why the audit trail must not be switchable off.

Is an electronic batch record better than paper?

It removes whole classes of problem — illegible entries, missing signatures, calculation errors, forgotten steps — and enforces sequence, which paper cannot. It adds validation effort, access control obligations, an audit trail that has to be reviewed, and a real dependency on system availability during production. Plants with high volume and repetitive processes usually gain most. A plant with few, complex, variable batches often gets more from redesigning its paper record than from a system project.

Do non-regulated manufacturers need batch records?

They need the equivalent, whatever it is called. Any plant that may have to answer which material lot went into a shipment, what settings were used, or who performed a critical step needs that information recorded at the time. Customers increasingly ask for it in supply agreements, and a defect discovered in the field is far more expensive to contain without it. The formality can be much lighter than in pharmaceutical production; the underlying record cannot be absent.