Electronic Batch Record (eBR): What It Is and Why It Matters
A real eBR is written as the work happens, by the person doing it. What it must hold, which rules apply, and where it saves time.
In Short
- Batch record rules come from the product's own regulation; Part 11 applies once they are electronic.
- Signed steps, enforced order, linked deviations and lot capture make it defensible.
- Review starts from exceptions; a person still decides release.
Electronic Records & Inspection Readiness Buyer Guide
For quality, regulatory, validation and IT teams evaluating electronic records, signatures and inspection readiness. Use it with or without V5.
- See what a signature must show.
- Check corrections keep the original.
- Know where Part 11 applies.
We ask for your name and email so we can handle this request. The full guide then opens on this site, ready to translate, print or save. Privacy policy. Practical orientation, not legal advice; your quality unit decides which rules apply.
UltimateFree guide
Electronic Records & Inspection Readiness Buyer Guide
For quality, regulatory, validation and IT teams evaluating electronic records, signatures and inspection readiness. Use it with or without V5.
An electronic batch record (eBR) is the signed system record of how a specific batch was made: steps, signatures, weights, checks, deviations and the release decision. A good one is written as the work happens; a weak one is scanned paper. This guide explains what an eBR is, the rules behind batch and device production records (21 CFR 211, 212 and 111, Part 820 under QMSR, EU GMP Chapter 4 and Annex 11), what makes one defensible, and where it saves time.
What an eBR actually is
An eBR is the complete, structured, signed record of a single batch's manufacture — from material issue through every recipe step, every in-process check, every signature, every deviation, every yield reconciliation, to release or rejection. The defining property is that it is *the* record, not a representation of one: an inspector reviewing the eBR is reviewing the original.
Worked example: one signed step
Step 7 of batch B-2291 (invented): what a defensible eBR step holds.
| Field | Entry |
|---|---|
| Instruction | Add binder solution over 5 to 8 minutes, revision 4 |
| Material | Binder lot BS-0918, 12.40 kg issued, 12.38 kg added |
| Equipment | Mixer MX-02, cleaning status verified |
| Result | Addition time 6 min 30 s, within limits |
| Signed | Performed by operator; verified by second person |
| Change | None; any correction would show old value, new value and reason |
- Instruction
- Entry
- Add binder solution over 5 to 8 minutes, revision 4
- Material
- Entry
- Binder lot BS-0918, 12.40 kg issued, 12.38 kg added
- Equipment
- Entry
- Mixer MX-02, cleaning status verified
- Result
- Entry
- Addition time 6 min 30 s, within limits
- Signed
- Entry
- Performed by operator; verified by second person
- Change
- Entry
- None; any correction would show old value, new value and reason
More on what an eBR actually is
In a real eBR every step is signed at the moment it happens by an authenticated user; the audit trail captures before-and-after values with mandatory reason-for-change; deviations are linked structured records, not free-text notes; the eBR cannot be edited after release except through formal change control. A scanned PDF of a paper traveller is not an eBR — it's a digital photocopy.
The Regulatory Basis
Batch record rules come from the product's own regulation. For drugs, 21 CFR 211.188 requires batch production and control records documenting each significant step.
More on the Regulatory Basis
PET drugs (Part 212) and biologics (Parts 600 onward) add their own records. Dietary supplements need a batch production record under 21 CFR 111.255 and 111.260. Medical devices need production records under Part 820, which since 2 February 2026 incorporates ISO 13485 (the former 820.184 DHR section no longer exists). In the EU, GMP Chapter 4 and Annex 11 apply. Part 11 applies when any of these records is kept electronically. Food plants under 21 CFR 117 keep preventive-control records, not drug-style batch records; an eBR can help there but is not required.
What makes an eBR defensible
Six properties separate a real eBR from compliance theatre. (1) Step-by-step e-signature with structured meaning (Author / Reviewer / Approver / QA Release), not free-text checkboxes.
Defensibility Checks
More on what makes an eBR defensible
(2) Out-of-sequence enforcement: the operator can't sign step 7 before step 6. (3) Live audit trail with before / after values and mandatory reason-for-change on every regulated edit. (4) Structured deviation capture at the point of failure, linked to the eBR step that triggered it. (5) Material lot identity captured at consumption — every input lot traceable forward to this eBR and every output lot traceable back. (6) Review-by-exception: the reviewer sees only the steps that deviated or need attention, not 200 pages of healthy sign-offs. Strip any of these out and the eBR is harder to defend than the paper traveller it replaced.
Where an eBR saves time
Three areas usually matter most. Release review: the record is complete when the batch finishes, so review starts sooner and can focus on exceptions.
More on where an eBR saves time
Right-first-time records: missing entries and out-of-order steps are caught as they happen instead of during QA review. Inspection requests: a batch record with its audit trail can be found and exported rather than assembled from binders. How much time this saves depends on your products, review practice and starting point.
eBR vs eDHR — the device equivalent
More on eBR vs eDHR — the device equivalent
The device record emphasises acceptance records, labels and UDI; a drug batch record emphasises yield, in-process specifications and reconciliation. The discipline is the same: signed steps as work happens, structured deviations, linked lot or serial identity, review by exception and controlled corrections.
Common Implementation Mistakes
Five mistakes cost the most. (1) Treating eBR as a document module rather than as the way production runs — if operators still fill paper and someone re-types it, you bought a digital filing cabinet, not an eBR.
Is it really an eBR?
- A copy of a paper record; the paper is still the evidence.
- Review effort stays the same.
More on common Implementation Mistakes
(2) Skipping out-of-sequence enforcement to 'avoid annoying operators' — the enforcement is the value. (3) Not capturing reason-for-change on edits — the audit trail becomes uninspectable. (4) Free-text deviations instead of structured ones — the link to CAPA breaks. (5) Not linking the eBR to live ERP inventory write-back — finance and operations diverge. The unifying mistake is buying eBR as a compliance bolt-on rather than as the operating system of the floor. Buy it that way and it pays back; buy it as a documentation tool and it doesn't.
Questions
Is a scanned paper batch record an eBR?
No. Scanning paper into a PDF makes the record digital but does not make it an electronic record under 21 CFR Part 11 — the e-signatures aren't bound to the record, the audit trail doesn't exist, and the underlying captures are still on paper. Regulators look at scanned paper as 'paper with a digital photocopy' — the same review burden, none of the live-record benefits.
Do we need 21 CFR Part 11 validation for an eBR?
If the eBR holds records required by a predicate rule, Part 11 applies, so the system must be validated for its intended use. A risk-based approach focuses on audit trail completeness, signature linkage, access control, backup and restore, and operational checks. How much evidence is enough is your quality team's decision.
Can the same eBR platform run multiple sites and multiple products?
Usually yes. Using one system across sites with site-specific versions of a master recipe keeps records consistent and audits comparable. Confirm in scoping how your sites, products and contract manufacturers would be set up.
How does review-by-exception work?
The reviewer sees first the steps that need attention: deviations, out-of-specification results, missed checks and anything the procedure flags. Steps completed normally are collapsed but one click away. The reviewer still decides whether to release; how long review takes depends on the batch and your procedure.
Practical orientation, not legal advice. Rules differ by jurisdiction; your quality and compliance team decides what applies.
Keep reading
- Electronic Batch Record (EBR) System Readiness Guide
Radiopharmaceutical Release Before All Tests Finish: PET Evidence
Batch Traceability Software: How Batch Genealogy Works
Dietary Supplement Master and Batch Records: Execution Guide
Document Control Process Explained: Lifecycle and Audits
IVD Manufacturing Record Dossier: A Worked Evidence Index