
Document Control
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
ExploreThe record that tells one batch's whole story — and the document set that governs it.
Master batch record, executed batch production record, eBMR — the terms blur together until an inspector asks for one of them specifically. Here is how they differ and where each lives.

A batch record is the documentation that tells the complete story of one batch of product. In US GMP the term splits into two distinct records: the master batch record (MBR) — the approved template of instructions, materials, and specifications for a product (required by 21 CFR 211.186, "master production and control records") — and the batch production record (BPR) — the executed copy filled in during manufacture of one specific batch (required by 21 CFR 211.188, "batch production and control records").
An eBMR (electronic batch record) is the executed record captured electronically — typically by a manufacturing execution system (MES) on the shop floor — with enforced step sequencing, in-process checks, and electronic signatures replacing handwritten initials.
In the EU, the same expectations live in EU GMP Chapter 4 (manufacturing formula, processing/packaging instructions, and batch records) — and the documentation must satisfy ALCOA+ data integrity expectations regardless of medium.
The MBR is the recipe under document control; the BPR is the diary of one batch executed against that recipe. The MBR is governed like a controlled document; the BPR is a GMP record that must be reviewed before release.
Batch records sit at the centre of two unforgiving processes. First, batch release: the qualified reviewer (and in the EU, the Qualified Person) releases against the executed record — every deviation, every out-of-specification investigation, every signature gap in it delays or blocks release. Second, inspections: 21 CFR 211.188 and 211.192 (record review) are perennially among the most-cited drug GMP observations, and a batch record that cannot be retrieved quickly, reconciled completely, or read cleanly is a finding regardless of how the batch was actually made.
The recurring failure modes are documentation failures, not manufacturing failures: an outdated MBR version still circulating on the floor, handwritten entries that fail contemporaneous recording, deviations handled outside the record with no link back to the batch, and review backlogs that turn release into archaeology.
In a typical pharma system landscape, the batch story spans systems on purpose: the MBR and its supporting master documents (specifications, SOPs, processing instructions) live under document control; the executed record is captured on paper or in an MES/eBMR system with enforced workflow; deviations and investigations raised during manufacture live in the quality system, linked to the batch; and review and release pulls all of it together. Mature eBMR setups add review by exception — reviewers concentrate on flagged deviations from the master rather than re-reading every line.
The integrity of the whole chain depends on unglamorous controls: one effective MBR version in circulation, training tied to the procedures in force, deviations that reference the batch they came from, and retrieval that works at inspection speed.
Complere is an eQMS, not an MES — it does not execute eBMRs on the shop floor. What it governs is the documentation and quality layer around the batch: master batch documents and processing instructions as version-controlled, Part 11-aligned controlled documents in Document Control (one effective version, controlled prints with reconciliation for paper-executed records), deviations and investigations linked from CAPA & Deviations, and training evidence tied to the procedure revisions in force. For shop-floor execution, Complere's integrations cover lab and MES systems so the quality layer and the execution layer stay connected.
Common questions about Batch Record sourced from regulatory references and inspection patterns.
The master batch record (MBR, 21 CFR 211.186) is the approved template — instructions, materials, specifications — governed like a controlled document. The batch production record (BPR, 21 CFR 211.188) is the executed copy for one specific batch, completed during manufacture and reviewed before release.
When batch records are created or maintained electronically, yes — the e-record and e-signature controls apply: audit trails, access control, and signature binding. Paper-executed records governed by controlled printing carry the equivalent expectations through GMP documentation rules and ALCOA+.
An eBMR practice where the system flags deviations from the master record — missed checks, out-of-range values, sequence breaks — and reviewers concentrate on the flagged exceptions instead of re-reading every executed line. It depends on a validated eBMR system with enforced workflow.
No — and a vendor who says otherwise should worry you. Shop-floor execution of eBMRs belongs to MES. An eQMS governs the layer around the batch: master documents under version control, deviations and investigations linked to the batch, training evidence for the procedures in force, and the document trail batch-record review depends on.
Walk through the modules and workflows that address this area inside a controlled, validation-ready quality system.
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.

Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore