Electronic Batch Records Under 21 CFR Part 11

A batch production record is not one signature. It's a chain of them, stacked on top of a master record that has its own separate signature requirement, on top of an equipment layer that has to be validated before anyone signs anything at all. Electronic batch records 21 CFR Part 11 requirements sit across three regulations at once: 21 CFR 211.186 for the master record, 211.188 for the batch record itself, and Part 11's own 11.10(e) for the audit trail underneath both. Most e-signature vendor content collapses this into one generic "batch record signature" feature. The actual text doesn't.

This post works through what an electronic batch record (EBR) or manufacturing execution system (MES) actually has to sign, log, and verify under 21 CFR Part 211 Subpart F and Part 11, what EU GMP Annex 11 adds for manufacturers subject to it, and what to ask before you trust a system with this part of the record.

Two Records, Two Separate Signature Requirements

The master production record and the batch production record are not the same document with two names. They're two different records with two different signature rules, and an EBR system has to keep them distinct.

21 CFR 211.186(a) covers the master record: "To assure uniformity from batch to batch, master production and control records for each drug product, including each batch size thereof, shall be prepared, dated, and signed (full signature, handwritten) by one person and independently checked, dated, and signed by a second person." Read literally, that parenthetical requires ink on paper. What makes an electronic signature acceptable at all here is Part 11 itself. 21 CFR 11.1(a) states that Part 11 sets out "the criteria under which the agency considers electronic records, electronic signatures, and handwritten signatures executed to electronic records to be trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper," and 11.1(c) states that where an electronic signature meets those criteria, "the agency will consider the electronic signatures to be equivalent to full handwritten signatures, initials, and other general signings as required by agency regulations." That's the specific mechanism that lets an EBR satisfy 211.186(a)'s literal "handwritten" language electronically: not by reading past the word, but by meeting the bar Part 11 sets for equivalence.

211.188(a) covers the batch record, and its wording is narrower. It requires "an accurate reproduction of the appropriate master production or control record, checked for accuracy, dated, and signed." No "(full signature, handwritten)" qualifier appears in that clause. The explicit handwritten language is specific to the master record in 211.186(a); the batch record provision doesn't repeat it. Either way, both signatures fall under Part 11 once they're captured electronically, and an EBR needs to keep the two signing events, and the two documents they attach to, clearly separated in its workflow and its audit trail.

What Counts as a "Significant Step," and Who Has to Sign It

211.188(b) sets the content requirement for the batch record itself: "Documentation that each significant step in the manufacture, processing, packing, or holding of the batch was accomplished, including" a list of specific elements. The one that defines an EBR's signature architecture is 211.188(b)(11): "Identification of the persons performing and directly supervising or checking each significant step in the operation, or if a significant step in the operation is performed by automated equipment under § 211.68, the identification of the person checking the significant step performed by the automated equipment." That's a per-step identification requirement, not a single sign-off at the end of the batch record. An EBR that only captures one signature covering the whole record, rather than an attributed signing event tied to each significant step, is not matching what 211.188(b)(11) actually asks for.

A related two-person rule sits earlier in Subpart F, at the component stage. 21 CFR 211.101(c) requires that "each container of component dispensed to manufacturing" be "examined by a second person" to confirm the component was released by the quality control unit, the weight or measure matches the batch production record, and the containers are properly identified, "unless the weighing, measuring, or subdividing operations are performed by automated equipment under § 211.68," in which case one person is sufficient. 211.101(d) adds the same structure to the actual addition step: "Each component shall either be added to the batch by one person and verified by a second person or, if the components are added by automated equipment under § 211.68, only verified by one person." An EBR that automates weighing and dispensing through validated equipment can legitimately collapse this to one verifying signature. One that still routes weighing through manual entry needs to enforce the two-person pattern as two distinct, attributable signing events, the same distinction we cover for laboratory results in our LIMS Part 11 guide.

The Equipment Layer Underneath the Signature

Before any of those signatures happen, the equipment producing the data they're signing off on has its own requirement. 21 CFR 211.68(a) allows "automatic, mechanical, or electronic equipment or other types of equipment, including computers, or related systems" in manufacturing, provided it's "routinely calibrated, inspected, or checked according to a written program designed to assure proper performance," with written records of those checks maintained. An MES pulling data from scales, filling lines, or environmental monitoring sensors is exactly the "related systems" this covers.

211.68(b) is the part that governs the computer system itself, not just the instruments feeding it: "Appropriate controls shall be exercised over computer or related systems to assure that changes in master production and control records or other records are instituted only by authorized personnel. Input to and output from the computer or related system of formulas or other records or data shall be checked for accuracy... A backup file of data entered into the computer or related system shall be maintained except where certain data... are eliminated by computerization or other automated processes." For an EBR, that means the software isn't just recording signatures; it's itself a piece of regulated equipment with its own change-control and backup obligations, sitting underneath the signature layer.

Written Procedures Have to Be Followed at the Time of Performance

21 CFR 211.100(a) requires "written procedures for production and process control designed to assure that the drug products have the identity, strength, quality, and purity they purport or are represented to possess." 211.100(b) adds the timing requirement an EBR has to enforce operationally: "Written production and process control procedures shall be followed in the execution of the various production and process control functions and shall be documented at the time of performance. Any deviation from the written procedures shall be recorded and justified." That "documented at the time of performance" phrase is the contemporaneousness principle applied specifically to manufacturing: an EBR that allows a step to be signed off hours or days after it was actually performed, without capturing that gap and its justification, is building a data integrity problem into the workflow rather than preventing one.

The Audit Trail: Part 11's Own Requirement, Applied to Every Signed Step

21 CFR 11.10(e) requires "secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records," with record changes not obscuring previously recorded information, and the audit trail retained at least as long as the record it covers. For a general document platform, that's satisfied by logging edits and approvals on a single document. For an EBR, the scope is wider because the record itself is wider: 211.188(b)(11)'s per-step identification requirement means the audit trail has to capture who performed and who checked each significant step separately, not just who signed the batch record as a whole at the end. We cover the general structure of that requirement, including retention and review-frequency obligations, in 21 CFR Part 11 audit trail requirements.

Before Release: The Quality Control Unit Review

21 CFR 211.192 requires that production and control records be "reviewed and approved by the quality control unit to determine compliance with all established, approved written procedures before a batch is released or distributed," with any unexplained discrepancy or failure investigated, including its potential extension to other batches. That review is the point where an incomplete EBR audit trail becomes visible. If a significant step's identification, per 211.188(b)(11), or a component verification, per 211.101(c) and (d), never got captured as an attributable signing event, the reviewer either can't complete the 211.192 review properly or has to sign off on a record with a gap in it. We cover the release signature itself, and the role of the Qualified Person or equivalent release authority, in GMP batch release e-signatures.

EU GMP Annex 11: The Same Ideas, in Different Clauses

EU GMP Annex 11, the annex to EudraLex Volume 4 that came into operation on 30 June 2011 and remains the currently in-force text (not the 2025 draft revision, which is covered separately elsewhere on this site), sets out several requirements that map directly onto an EBR's design.

Clause 6, Accuracy Checks, is Annex 11's version of the two-person pattern in 211.101: "For critical data entered manually, there should be an additional check on the accuracy of the data. This check may be done by a second operator or by validated electronic means." Clause 8.2, under Printouts, is specific to batch release records: "For records supporting batch release it should be possible to generate printouts indicating if any of the data has been changed since the original entry." Clause 9, Audit Trails, states that "consideration should be given, based on a risk assessment, to building into the system the creation of a record of all GMP-relevant changes and deletions," with the reason documented "for change or deletion of GMP-relevant data," and the trail "regularly reviewed." Clause 15, Batch Release, is the release-specific signature rule: "the system should allow only Qualified Persons to certify the release of the batches and it should clearly identify and record the person releasing or certifying the batches. This should be performed using an electronic signature." We cover the full set of Annex 11's computerized-system obligations in our guide to EU GMP Annex 11.

A Vendor Checklist Specific to EBR and MES Systems

A generic e-signature checklist covers audit trails, unique credentials, and signature meaning. For an EBR or MES specifically, add these:

• Does the system capture a separate, attributed signature for each significant step, per 211.188(b)(11), rather than one signature covering the entire batch record?
• Does the master record signature workflow satisfy 211.186(a)'s two-signature requirement (preparer plus independent checker), distinct from the batch record's own signature under 211.188(a)?
• When components are weighed or added manually rather than through validated automated equipment, does the system enforce the two-person verification in 211.101(c) and (d) as two separate, attributable events?
• Can the system produce a printout showing whether batch-release-supporting data has changed since original entry, matching Annex 11 clause 8.2?
• Does every deviation from written procedure get recorded and justified at the time it occurs, per 211.100(b), rather than reconstructed later?
• Is there a written program and validation data on file for anything 211.68(b) allows an automated system to eliminate the manual, backed-up version of?

None of these are answerable from a product page. They're answerable from the vendor's own validation documentation, which is the kind of evidence a supplier qualification assessment is meant to produce before deployment, covered in more general terms in our guide to validating an e-signature system.

Where This Leaves the E-Signature Layer

Klyverity doesn't run your MES, integrate with plant-floor equipment, or perform the IQ/OQ/PQ that validates an EBR's manufacturing logic. That work belongs to the EBR vendor and your own validation team. What Klyverity secures is the signature layer on top of that record once a step, a batch record, or a master record is ready to be signed: unique two-component credentials at the moment of signing, a signature manifestation showing who signed, when, and what the signature meant, and an audit trail permanently linked to the exact record version it was applied to. That's the piece of the chain 211.186(a) and 211.188(b)(11) describe, captured as attributable, non-repudiable signing events instead of a shared terminal login and a checkbox. We cover the broader QA signature landscape, SOPs, deviations, and CAPA, in e-signatures for pharmaceutical QA. If you're evaluating how that layer fits alongside an EBR or MES you already run, talk to us.

FAQ

Does 21 CFR Part 11 require electronic batch records to use a specific software product?

No. Part 11 sets criteria for the electronic records and signatures themselves; it doesn't name or endorse any product. An EBR system has to satisfy Part 11's controls (audit trails, access controls, signature manifestation) alongside the predicate-rule content requirements in 21 CFR Part 211 Subpart F, primarily 211.186, 211.188, 211.192, and 211.101.

Is the master production record signature the same as the batch record signature?

No. 21 CFR 211.186(a) requires the master record to be prepared and signed by one person and independently checked and signed by a second, with the text specifying "full signature, handwritten." 211.188(a) requires the batch record to be "an accurate reproduction of the appropriate master production or control record, checked for accuracy, dated, and signed," without repeating that handwritten qualifier. They are two separate documents with two separate signing events.

What does 211.188(b)(11) require for identifying who performed a manufacturing step?

It requires "identification of the persons performing and directly supervising or checking each significant step in the operation," or, where automated equipment under 21 CFR 211.68 performs the step, identification of the person who checked it. That's a per-step requirement, which means an EBR's signature architecture needs to capture attribution at each significant step, not just once for the whole batch record.

When can a single person verify a component instead of two?

21 CFR 211.101(c) and (d) permit a single verifying person only when the weighing, measuring, subdividing, or addition of the component is performed by validated automated equipment under 21 CFR 211.68. When those operations are performed manually, both subsections require a second person to examine or verify the step.

How does EU GMP Annex 11 handle batch release electronically?

Annex 11 clause 15 states that where a computerized system is used for certification and batch release, "the system should allow only Qualified Persons to certify the release of the batches and it should clearly identify and record the person releasing or certifying the batches," performed using an electronic signature. This is the 2011 version of Annex 11, currently in force.