What an electronic batch record is
An electronic batch record (EBR) is the digital version of the batch production and control record that every drug manufacturer must keep for each batch. In the US, 21 CFR 211.188 requires a record for each batch that includes “complete information relating to the production and control of each batch.” The rule does not say the record must be on paper. An EBR system captures the same content (steps, materials, equipment, weights, in-process results, signatures) in a validated computer system instead of on printed forms.
Most EBR systems sit inside, or connect to, a manufacturing execution system (MES). The MES guides operators step by step, checks entries against limits as they are made, and pulls data straight from scales, sensors and equipment. A simpler form, often called “paper on glass,” puts the paper form on a tablet without adding much logic. Both are EBRs. Only the first gives you most of the quality benefit.
The acronym is ambiguous. “EBR” also means evidence-based reading, a school program, so a quality team searching for it will see mixed results. In GMP the acronym always means electronic batch record, and in a few companies “eBMR” (electronic batch manufacturing record) means the same thing.
What regulators require from an EBR
No regulation is written for EBRs alone. An EBR has to meet the same batch record rules as paper, plus the electronic record rules that apply to any computer system holding GMP data.
The batch record content rules still apply
Under 21 CFR 211.188(b), the record must document, among other things:
- The dates of each significant step
- The identity of major equipment and lines used
- The batch numbers of components and in-process materials
- Weights and measures of components used
- In-process and lab control results
- Inspections of packaging and labeling areas before and after use
- Actual yield and the percentage of theoretical yield
- Complete labeling control records
- Who performed each significant step, and who directly supervised or checked it
- Any investigation made under 211.192
The EBR has to produce every one of these. A common gap is the “checked by” requirement. Section 211.188(b)(11) says that where a step is performed by automated equipment under 211.68, the record must identify the person who checked the step. Teams sometimes remove the second-person check because the system now captures the weight, and then cannot show who verified the automated step.
Electronic record controls under Part 11
If the EBR replaces paper as the official record, 21 CFR Part 11 applies. The controls that matter most for an EBR are:
- Validation (11.10(a)): the system must be shown to work as intended and to detect invalid or altered records.
- Audit trails (11.10(e)): computer-generated, time-stamped audit trails must record who created, changed or deleted an entry, and “record changes shall not obscure previously recorded information.”
- Sequencing checks (11.10(f)): the system should enforce the permitted order of steps where that matters, which is exactly what an MES-driven EBR does well.
- Authority checks (11.10(g)): only authorized people can sign, alter records or run operations.
- Signature manifestation (11.50): each signature shows the printed name, date and time, and its meaning, such as review or approval.
In the EU, the same ground is covered by EudraLex Volume 4 Annex 11. A revised Annex 11 went to public consultation from July 7 to October 7, 2025. Its draft section 12 says audit trail review “should be conducted prior to batch release, unless the risk of a later detection of any unwarranted changes can be justified,” and that reviews affecting release “should be available to the QP at the time of batch release.” That is a stronger timing expectation than the current Annex 11, and EBR projects starting now should design for it.
The audit trail is part of the batch record
FDA’s data integrity Q&A (December 2018) states that “all production and control records, which includes audit trails, must be reviewed and approved by the quality unit.” It also says that where the regulations set a review frequency, the audit trail follows it, and 211.192 requires record review before release. In practice, an EBR is not fully reviewed until the relevant audit trail entries have been reviewed too. That has to be built into the EBR review workflow, not handled as a separate periodic task.
How electronic batch record review works
Paper review is page by page. A reviewer reads every entry, checks every calculation and looks for missing signatures. An EBR changes this in three ways.
First, many errors are prevented at entry. The system can block an out-of-range weight, force a deviation record before the operator continues, and calculate yields automatically. Fewer errors reach the reviewer.
Second, review can focus on exceptions. When the system has already enforced limits and sequence, the reviewer can concentrate on the entries flagged as exceptions: alarms, overrides, deviations, comments, out-of-limit values and audit trail events such as data changes. This is called review by exception (RBE). A 2023 EY article on EBRs describes RBE as able to “reduce a 150-page batch record review to a three-page exception report.” That is a vendor-neutral consultancy view, not a regulatory figure, but it shows the scale of change companies aim for.
Third, review can run in parallel. QA can review completed sections while the batch is still running, so the release clock does not start only when the last page is signed.
RBE is only defensible when the system has been validated to catch every exception type that matters. If the validation does not show that, the reviewer still has to look at the full record. Our article on review by exception covers that justification in detail.
Paper, hybrid and full EBR compared
| Model | How it works | Main review risk |
|---|---|---|
| Paper | Printed master record, handwritten entries, wet-ink signatures | Missed entries, illegible corrections, calculation errors, slow review |
| Hybrid | Paper record plus printouts or data from instruments and systems | Data exists in two places; the paper may not match the electronic source, and audit trails are often not reviewed |
| Paper on glass | Electronic form on a tablet, limited logic | Same errors as paper, now harder to see without good audit trails |
| Full EBR with MES | Guided workflow, enforced limits, direct equipment data, exception flags | Over-trust in the system; exceptions it was never designed to catch |
Hybrid systems deserve the most attention. FDA’s data integrity Q&A states that “when generated to satisfy a CGMP requirement, all data become a CGMP record.” If an EBR pulls a value from a balance or a historian, the source data is part of the record too. Reviewers who check only the EBR screen, and never the source, are reviewing a summary.
Planning an EBR implementation
EBR projects fail more often on process than on software. These steps keep the project focused on the record, not the tool.
- Fix the master record first. An EBR built on a weak master production record (211.186) will enforce the wrong things. Clean up instructions, limits and yield ranges before you configure anything.
- Define exceptions before you build. List every event that must reach a reviewer: out-of-limit values, overrides, manual entries where automatic capture failed, comments, deviations, late entries, and audit trail changes to critical data.
- Use risk-based validation. FDA’s final guidance on Computer Software Assurance for production and quality system software (issued September 2025) supports focusing testing effort on features with high process risk. Exception capture is one of them.
- Map each 211.188 element to a field. Show an inspector where each required element lives in the system, including who checked automated steps.
- Plan the audit trail review. Decide which audit trail events are reviewed with each batch and how they appear to the reviewer. Draft Annex 11 section 12.5 states that “the use of tools to help conduct audit trail reviews is encouraged.”
- Run paper and electronic in parallel for a defined period. Compare review findings to confirm the EBR catches what the paper review caught.
- Train reviewers, not only operators. Reviewers need to know what the system enforces and what it does not.
Common EBR findings
The patterns below show up in FDA warning letters and audit reports, whatever the system:
- Records released without full QA review. Section 211.192 was cited 164 times in FDA Form 483 observations in FY2025, according to a GMP Insiders analysis of FDA data.
- Audit trails never reviewed. The system has them, but no procedure says who reviews which events before release.
- Shared logins or generic accounts. These break 11.10(g) and make every signature questionable.
- Manual overrides without justification. The system allows an override, but the reason field is optional or free text that nobody reads.
- Uncontrolled master record changes. The electronic master record is edited without change control, so batches run under different instructions.
EBR readiness checklist
- Master production records are approved, current and checked by a second person (211.186)
- Every 211.188(b) element maps to a field or report in the EBR
- The “checked by” step for automated operations is defined
- Part 11 controls (validation, audit trails, authority checks, signatures) are verified
- Exception types are defined and validated as complete
- Audit trail review is part of batch review, before release
- Source data from instruments and historians is linked to the record
- Override and late-entry reasons are mandatory and reviewed
- Reviewers are trained on what the system does and does not enforce
- A parallel run compared EBR and paper review findings
Check your batch records with AskDona
An EBR changes where errors hide, not whether they exist. AskDona reads batch records, deviation reports, SOPs and audit trail exports, and checks them against 21 CFR 211, Part 11 and your own procedures. It links each finding to the page and clause behind it, so reviewers can confirm or reject it quickly. Run a sample batch record assessment on a completed record or an EBR export. AskDona shows the evidence; your quality unit decides.
FAQ
What does EBR stand for in pharma? Electronic batch record: the digital form of the batch production and control record required by 21 CFR 211.188 and the EU GMP guide.
Is an electronic batch record required by FDA? No. FDA requires a complete batch record, not a specific format. Paper, hybrid and electronic records are all acceptable if they meet 211.188 and, for electronic records, Part 11.
What is electronic batch record review? The quality unit’s review of the EBR before release, required by 211.192. With a validated EBR it can focus on exceptions, but it must include relevant audit trail entries.
What is the difference between an EBR and an MES? An MES runs and controls manufacturing operations. The EBR is the record those operations produce. Most EBRs are a module of an MES.
Does an EBR remove the need for second-person checks? Not entirely. Where automated equipment performs a step, 211.188(b)(11) still requires the record to identify the person who checked it.
References
All pages opened and checked by October 14, 2026.
| Source | Type | Used for |
|---|---|---|
| 21 CFR Part 211 Subpart J (eCFR) | US regulation | 211.186, 211.188, 211.192 requirements |
| 21 CFR Part 11 (eCFR) | US regulation | 11.10(a), (e), (f), (g) and 11.50 controls |
| FDA, Data Integrity and Compliance With Drug CGMP: Q&A (Dec 2018) | FDA guidance | Audit trails as part of the record; all data become CGMP records |
| EC consultation on Chapter 4, Annex 11 and Annex 22 (2025) | EU consultation page | Consultation dates |
| Draft revised Annex 11 (consultation text) | EU draft guideline | Section 12 audit trail review timing and tools |
| RQA, FDA issues final guidance on Computer Software Assurance | Professional association news | CSA final guidance, September 2025 |
| GMP Insiders, FY2025 FDA inspection observations | Industry analysis of FDA data | 211.192 citation count |
| EY, How electronic batch records can improve pharma manufacturing | Consultancy article | RBE review-time illustration |