EBRElectronic Batch Record

21 CFR 211.188 requires a batch production and control record for each batch with complete information, starting from an accurate reproduction of the approved master record (211.186). An EBR captures those same entries electronically, ideally directly from people and equipment at the time of performance, with metadata kept so the activity can be reconstructed.

• Dates, and identity of major equipment and lines used.
• Specific identification of each component or in-process batch used.
• Weights and measures of components.
• In-process and laboratory control results.
• Packaging/labeling area inspection before and after use.
• Actual yield and percentage of theoretical yield.
• Labeling control records, containers/closures and sampling performed.
• Who performed and who checked each significant step, or who checked automated steps under 211.68.
• Any investigation under 211.192 and examinations under 211.134.

211.192 requires the quality control unit to review and approve production and control records before a batch is released or distributed, and to investigate any unexplained discrepancy, including yields outside master-record limits. An EBR can highlight exceptions for review; the release decision remains the quality unit's.

21 CFR 11.1(b) applies Part 11 to records in electronic form that are created, modified, maintained, archived, retrieved or transmitted under any FDA records requirement — so an electronic 211.188 batch record is in scope. For closed systems, 11.10 lists the controls expected, including system validation (a), accurate and complete copies for inspection (b), record protection through retention (c), limited access (d), secure time-stamped audit trails that do not obscure earlier entries (e), operational checks to enforce permitted step sequencing (f), authority checks (g) and device checks (h).

Those controls are the user's obligation, met through a system plus procedures, training and validation; they are not a property a product carries on its own.

An operator scans a component lot, the system checks it against the master record, and the paired balance records 12.488 kg within tolerance under the operator's login. Yield ends at 96.8% against a 95–101% master-record range. QA reviews the record and its exceptions and signs the release decision.

Every executed batch record starts life as a copy of something else. 21 CFR 211.186 requires a master production and control record for each drug product and batch size, prepared, dated and signed by one person and independently checked, dated and signed by a second person in the quality control unit. Section 211.188(a) then requires that each batch record include an accurate reproduction of that master record, checked for accuracy, dated and signed. On paper, that check usually means someone compares a photocopy against the approved original before it goes to the floor. Electronically, the equivalent is that the batch record is generated from one specific, approved master version, and the system can show which version that was.

That link matters because 211.186(b) lists what the master must contain: the product name, strength and dosage form; the name and weight or measure of each active ingredient per dosage unit; a complete list of components; an accurate statement of the weight or measure of each component; theoretical yield with the percentages beyond which an investigation is required; a description of containers, closures and packaging materials; and complete manufacturing and control instructions, sampling and testing procedures, specifications, special notations and precautions. If the executed record cannot be traced back to the approved master, none of those limits can be relied on during review.

Version control in practice

• Only an approved master version can be used to open a new batch; drafts and superseded versions cannot.
• The master version identifier is printed or displayed on every page or view of the executed record.
• A change to the master after a batch has started does not silently change that batch's instructions; the batch keeps the version it started with unless a documented change says otherwise.
• The two signatures required by 211.186(a) — preparer and independent quality-unit checker — are recorded against that version.

Section 211.188(b) asks for documentation that each significant step in manufacture, processing, packing or holding of the batch was accomplished. The practical value of an EBR comes from how each of those entries is captured. Typed values carry the same transcription risk as handwriting. Values captured directly from a connected balance or instrument remove one copying step, and barcode or label scans tie the entry to a specific component lot rather than to a description someone typed.

FDA's 2018 data integrity question-and-answer guidance describes metadata as the contextual information needed to understand data — for example the date and time stamp, the user who performed the activity, the instrument identity and the parameters in use. In its words, data should be maintained with the metadata needed to reconstruct the CGMP activity. For an EBR, that means each significant entry should carry who made it, when, on which equipment and against which instruction step, not just the number itself.

Yield is one of the clearest places where an electronic record changes the review. 211.188(b)(7) requires a statement of the actual yield and of the percentage of theoretical yield at appropriate phases of processing. The master record under 211.186(b)(7) states the percentages beyond which an investigation is required. When the system holds both the limits and the recorded quantities, it can calculate the percentage and show immediately whether the batch is inside or outside those limits.

211.192 requires that any unexplained discrepancy — including a percentage of theoretical yield exceeding the maximum or minimum percentages established in the master record — or the failure of a batch or any of its components to meet specifications be thoroughly investigated, whether or not the batch has already been distributed. The investigation must extend to other batches of the same drug product and other drug products that may have been associated with the failure. A written record of the investigation is required, including conclusions and follow-up.

The batch record does not stop at the end of processing. 211.188(b) includes the inspection of the packaging and labeling area before and after use, complete labeling control records including specimens or copies of all labeling used, a description of drug product containers and closures, and any sampling performed. Mix-ups between products or label versions are a long-standing source of recalls, so these entries tend to receive close attention at review.

• Line clearance before and after the run is recorded as a step with the person who performed it and, where required, a checker.
• The label version issued for the run is tied to the batch, so the reviewer can see which approved artwork was used.
• Quantities issued, used, damaged and returned are recorded so the labeling can be reconciled.
• Container and closure lots are captured the same way as other components.

A full paper batch record review can take hours because every page has to be read for missing entries, late entries, corrections and out-of-range values. An EBR can enforce completeness as work happens — a step cannot be closed while a required field is blank — and can present the reviewer with a summary of exceptions: out-of-tolerance values, overridden prompts, corrections with their reasons, deviations raised and steps completed out of the expected sequence.

That summary is a review aid, not a replacement for the review 211.192 requires. The quality control unit still reviews and approves the production and control records, including the packaging and labeling records, to determine compliance with all established, approved written procedures before a batch is released or distributed. A sensible procedure defines what the reviewer must look at in full, what can be reviewed through the exception summary, and how the reviewer confirms that the audit trail for critical entries has been examined.

Audit trail review

Part 11 §11.10(e) requires secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify or delete electronic records, and record changes must not obscure previously recorded information. During batch review, the useful question is not whether an audit trail exists but whether the changes it shows are explained: who corrected a value, when, from what to what, and why.

• Recreating the paper form screen by screen, so the electronic record inherits every free-text field and none of the checks.
• Allowing values to be typed where a device connection exists, which keeps transcription risk while adding the burden of Part 11 controls.
• Shared logins on the shop floor, which defeat the 'performed by' and 'checked by' entries and the limited-access control in §11.10(d).
• Printing the record and signing the printout, leaving it unclear whether paper or electronic is the official record.
• Hybrid steps (a paper log for one task, electronic for the rest) without a written rule for how the paper is linked, retained and reconciled.
• Treating the exception summary as the whole review, so the full record is never read where the procedure says it should be.

The requirements cited on this page are those of 21 CFR Part 211 for finished pharmaceuticals. Dietary supplements, medical devices, food and other sectors have their own record rules — for example device history records for devices and batch production records for supplements — which were not reviewed for this article. The general ideas (generate from an approved master, capture at the time of the work, flag exceptions, keep human review and release) carry across, but the required contents differ and should be checked against the regulation that applies to the product.

• How is the record tied to a specific approved master version?
• Which entries are captured from devices vs typed?
• How are deviations and yield investigations linked?
• How does the reviewer see only the exceptions and changes that matter?
• What validation documentation is supplied, and by which plan?

V5's product reference lists work orders, two-signature formula approvals, device pairing for scales, a QA release queue and regulated BMR/eDHR reports. Customers decide which records and processes are in scope, write the procedures and approve the outcomes; using V5 does not by itself establish compliance or a validated state. IQ/OQ documentation and validation support are offered on the Enterprise plan; the customer performs PQ and owns validation and approvals.