Document Control
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Glossary Term
Batch Record
The 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.
On this page
What a batch record is — three terms, three things
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, automated data capture from equipment, and electronic signatures replacing handwritten initials. The eBMR is the BPR rendered in software, with the MES enforcing the MBR's instructions in real time.
In the EU, the same expectations live in EU GMP Chapter 4: the manufacturing formula and processing instructions (the EU's MBR equivalent) and the batch processing and packaging records (the BPR equivalent). Whatever the medium, the documentation must satisfy ALCOA+ data integrity expectations, and the executed record must be reviewed and approved before the batch is released.
MBR versus BPR in one sentence
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 — versioned, approved, one effective version; the BPR is a GMP record that captures what actually happened and must be reviewed before release. Confusing the two is a common source of inspection findings.
Why batch records dominate inspections and 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 missing signature or unexplained gap in it delays or blocks release. A batch record review is where the cost of poor documentation becomes literal: product made and waiting, unable to ship until the record is clean.
Second, inspections: 21 CFR 211.188 (batch records) and 211.192 (production record review) are perennially among the most-cited drug GMP observations. A batch record that cannot be retrieved quickly, reconciled completely, or read cleanly is a finding regardless of how well the batch was actually made — because to an inspector, the record is the batch. If you can't show it, you didn't do it.
The recurring failure modes are documentation failures, not manufacturing failures: an outdated MBR version still circulating on the floor so operators work to a superseded recipe; handwritten entries that fail contemporaneous recording (filled in after the fact); calculation or transcription errors; deviations handled outside the record with no link back to the batch; and review backlogs that turn release into archaeology. The eBMR addresses many of these by construction — but only if the underlying master data and the system are validated and controlled.
Where the requirements live
- 21 CFR 211.186 — master production and control records: the approved master template, prepared, dated, and signed by qualified personnel
- 21 CFR 211.188 — batch production and control records: the executed record for each batch, including identification, weights/measures, in-process results, and signatures of performers and checkers
- 21 CFR 211.192 — production record review: QA review of every batch record before release, with investigation of any unexplained discrepancy or failure to meet specifications
- EU GMP Chapter 4 — manufacturing formula and processing/packaging instructions, plus batch processing and packaging records, as core GMP documentation
- EU GMP Annex 16 — certification by a Qualified Person and batch release; the QP certifies against the batch record
- 21 CFR Part 11 / EU GMP Annex 11 — when batch records are electronic, the e-record and e-signature controls apply: audit trails, access control, signature binding, validation of the eBMR system
- ALCOA+ / PIC/S PI 041-1 — the data-integrity expectations every batch record entry is judged against
Where each piece of the batch story lives
In a typical pharma system landscape, the batch story spans systems on purpose, and the integrity of the whole chain depends on each piece being controlled:
The master documents — the MBR, plus the specifications, SOPs, and processing instructions it references — live under document control: versioned, approved, with one effective version in circulation and superseded versions retired so no operator can work to an old recipe.
The executed record — the BPR or eBMR — is captured on paper or in an MES/eBMR system with enforced workflow. Mature eBMR setups enforce step sequencing, prevent out-of-order or skipped steps, capture equipment data automatically, and apply in-process check limits in real time, so deviations are caught as they happen rather than discovered at review.
Deviations and investigations raised during manufacture live in the quality system, linked to the batch they came from — so the reviewer (and the inspector) can trace from the batch record to the full investigation and back.
Review and release pulls it together. Mature eBMR programs add review by exception: rather than re-reading every executed line, reviewers concentrate on the steps the system flagged as deviations from the master — a major efficiency gain that depends entirely on a validated eBMR system and clean master data.
What strong batch-record control shares
Whether paper or electronic, batch-record programs that survive inspection and keep release moving share these controls:
The version that should never have been on the floor
A classic finding: an operator executed a batch against a superseded MBR version because document control didn't ensure the old version was withdrawn. The batch may be perfectly fine — but it was made to the wrong instructions of record, and now every unit is in question. One-effective-version control, enforced at the point of use, is the cheapest insurance against the most expensive kind of finding.
- One effective MBR version — controlled, approved, with superseded versions provably out of circulation
- Contemporaneous execution — entries made as the activity happens; no scratch paper, no later transcription
- Attributable entries — every entry and signature traceable to an individual; no shared accounts or shared initials
- In-process checks against limits — defined limits, second-person or system verification for critical steps
- Deviation linkage — every deviation captured and linked to the batch, investigated before release
- Reconciliation — materials, yields, and printed labels reconciled and documented
- Review-before-release discipline — QA review per 211.192, with review-by-exception only where the eBMR is validated
- Part 11 controls on electronic records — audit trail, access control, signature binding for eBMRs
- Retrievability — any batch record producible quickly and completely on request
Where Complere fits — stated honestly
Complere is an eQMS, not an MES — it does not execute eBMRs on the shop floor, enforce step sequencing in real time, or capture in-process equipment data. A vendor claiming an eQMS replaces an MES for batch execution should worry a manufacturing quality lead, and we won't make that claim.
What Complere governs is the documentation and quality layer around the batch — and that layer is substantial and directly inspection-relevant. Master batch documents and processing instructions live in Document Control as version-controlled, Part 11-aligned controlled documents: one effective version, full revision history, controlled prints with reconciliation for paper-executed records, and automatic retirement of superseded versions — directly addressing the “wrong version on the floor” failure mode. Deviations and investigations raised during manufacture are captured in CAPA & Deviations and linked to the batch, so the reviewer can trace from record to investigation. Training evidence ties operators to the procedure revisions in force, answering the “was the operator trained on the current instructions” question.
For the shop-floor execution layer, Complere's integrations connect to lab and MES systems, so the quality layer and the execution layer stay associated rather than siloed. The clean division: your MES executes and records the batch; Complere governs the controlled master documents, the linked deviations, and the training evidence that the batch-record review and the inspection depend on.
Frequently asked questions
Common questions about Batch Record sourced from regulatory references and inspection patterns.
What is the difference between an MBR and a BPR?
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.
Does 21 CFR Part 11 apply to batch records?
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+.
What is review by exception?
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.
Does an eQMS replace an MES for batch records?
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.
Continue Exploring
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.
Keep the documents behind every batch under control
Walk through the modules and workflows that address this area inside a controlled, validation-ready quality system.