e-Signature: Electronic Signatures in GMP Records
Understand how electronic signing connects a person, a record and a stated decision across batch execution and quality review.

On this page · 12 sections
- 1What an e-signature means in a GMP record
- 2US and EU: match the record to the applicable framework
- 3What Part 11 requires for the signature-to-record link
- 4Signature manifestation: signer name, execution time and signing meaning
- 5Components, controlled sessions and identification-code/password security
- 6Where to sign: execution, checks, QA review and decisions
- 7From proposed record to executed signature and later amendment
- 8Closed and open systems: integration boundaries and interrupted signing
- 9Worked cases: session reuse, revised records and transmission recovery
- 10Failure modes: detectable symptoms, containment and prevention controls
- 11Implementation and review checklist for people, procedures and records
- 12Where V5 fits in the batch-record evidence picture
How does E-Signature apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What an e-signature means in a GMP record
An e-signature is an electronic signing action that associates a person with a specific record and a stated signing meaning. This operational definition distinguishes a deliberate signing decision from simply accessing a system, entering data or generating a technical event.
| Term | Function | Boundary |
|---|---|---|
| Electronic signature | Associates a signer with a record and meaning. | Signing does not necessarily mean approval. |
| Electronic record | Holds information electronically. | A record can exist without being signed. |
| Login | Authenticates a user for system access. | Access alone does not express a signing decision. |
| Audit-trail event | Records activity affecting a record or system. | An activity entry is not itself a signature. |
| Digital signature | Uses cryptography to support identity and data-integrity verification. | Cryptographic protection alone does not explain the business meaning of signing. |
| Scanned handwritten signature | Stores an image of handwriting. | The image alone does not establish who applied it or why. |
For US drug GMP records within Part 11 scope, 21 CFR 11.1(a) establishes criteria for FDA to consider electronic records and signatures trustworthy and reliable.
In practice, review these functions separately: authentication establishes access, an audit event records activity, and cryptographic protection addresses a different technical function from a person's signing decision. The later sections on signature manifestation and components and controlled sessions develop these distinctions. Related concepts include the signature meaning statement and password-plus-token authentication.
02US and EU: match the record to the applicable framework
Scope the record before choosing signature controls. The table is a practical scoping aid, not a declaration that every GMP record follows the same electronic-signature rule. Map each record to its product, market and underlying recordkeeping obligation; document the applicability decision separately from the operational meaning of signing.
| Jurisdiction and product | Record-scope question | Regulatory framework | Operational consequence |
|---|---|---|---|
| US drugs | Which FDA obligation calls for this electronic record? | Assess underlying drug-record rules and Part 11. | Identify the regulated record rather than classifying the entire application. |
| US supplements and devices | Which product-specific obligation applies to this record? | Assess supplement or device record rules, then Part 11 scope. | Avoid importing a drug-record workflow without a product-specific assessment. |
| US food | Is the record required under Part 117, another obligation, or both? | Assess Part 117 and the Part 11 exclusion below. | Document overlapping obligations before deciding applicability. |
| EU medicinal products | Which medicinal-product GMP records and systems are involved? | Check current EudraLex Volume 4 Annex 11. | Keep the EU assessment distinct from the US assessment. |
| Chemical operations | What markets, intended uses and record obligations apply? | Identify the actual market-specific framework. | Do not select Part 11 merely because an operation uses GMP terminology. |
For US drug, supplement, food and device records, 21 CFR 11.1(b) includes electronic records created or maintained under FDA recordkeeping requirements. Use the Part 11 overview alongside the product-specific assessment.
For US food-manufacturing records, 21 CFR 11.1(i) excludes records required under Part 117, but records also required under other applicable statutory provisions or regulations remain subject to Part 11. The Part 117 overview provides related food-manufacturing context.
For US drug GMP electronic records, FDA’s Part 11 guidance does not establish legally enforceable responsibilities. For those US drug records, the guidance states that Part 11 remains in effect and that enforcement discretion applies only as identified in that guidance—not as a blanket exemption.
For EU medicinal-product GMP records, check the current text of EudraLex Volume 4 Annex 11 — Computerised Systems for applicable electronic-signature expectations and scope. Keep this jurisdictional check separate from the US provisions.
For EU medicinal-product GMP, Annex 11 is guidance-strength text within EudraLex Volume 4. Section 14 states that electronic signatures are expected to "have the same impact as hand-written signatures within the boundaries of the company", to "be permanently linked to their respective record" and to "include the time and date that they were applied." Section 15 adds a conditional expectation: when a computerised system is used for recording certification and batch release, the system "should allow only Qualified Persons to certify the release of the batches" and should clearly identify and record the person releasing or certifying, using an electronic signature. Sites selling into both markets usually design one signature control set that satisfies the Part 11 manifestation and linking requirements and these Annex 11 expectations together.
03What Part 11 requires for the signature-to-record link
For US drug GMP records within Part 11 scope, 21 CFR 11.70 requires signatures to be linked to their respective electronic records so they cannot be excised, copied or otherwise transferred to falsify an electronic record by ordinary means.
A practical implementation uses stable record identifiers, explicit revision references and preserved signed content to make that relationship intelligible. These are suggested evidence patterns, not a prescribed database, hash algorithm or storage technology. In an electronic batch record, the useful question is not simply whether a signature exists, but which content that signing event concerned.
An illustrative evidence model
The following field names illustrate design relationships; they are neither a regulatory schema nor a description of a particular product.
| Evidence object | Illustrative join and purpose |
|---|---|
| Signer | signer_id connects the signature event to the identified person. |
| Record revision | record_id + revision_id resolve to the preserved content signed. |
| Signature event | signature_id connects signer_id, revision_id and signing_meaning: who signed what, and why. |
| Authentication context | authentication_context_id connects the signing event to its authentication evidence. |
| Integration receipt | Where transfer occurs, source_signature_id and destination_revision_id connect the receipt to the destination association. |
For interface review, a receipt is useful only if it helps establish whether the destination retained the signature’s association with the intended revision and meaning, rather than merely acknowledging delivery.
For later amendments, a version-aware design preserves the earlier signed content and records the change separately instead of overwriting what the signer saw. The amendment can then be assessed for its own review or approval needs without treating the earlier signature as approval of changed content. Use the failure-mode checks to examine broken associations; transmission recovery is addressed in the worked cases.
Signer
Connects the person to their account context.
- signer_id
- printed_name
- account_status
- role_id
Record revision
Identifies the content associated with the decision.
- record_id
- record_version
- record_type
- content_reference
- audit_trail_reference
Signature Event
Links signer, revision, execution time and meaning.
- signature_id
- record_id
- record_version
- signer_id
- session_id
- signed_at_utc
- signing_meaning
Session Evidence
Records authentication context without retaining signing secrets.
- session_id
- auth_event_id
- signer_id
- component_check_result
- controlled_access_state
Transfer receipt
Supports reconciliation when signed records cross systems.
- transfer_id
- signature_id
- source_record_id
- target_record_id
- transfer_status
04Signature manifestation: signer name, execution time and signing meaning
The signature manifestation is the readable presentation of who signed, when they signed and what their signature means. It gives reviewers a way to interpret the signing decision without treating every signature as an approval.
For US drug GMP records within Part 11 scope, 21 CFR 11.50(a) requires signed electronic records to identify the signer’s printed name, execution date and time, and signature meaning. For those US drug GMP records, 21 CFR 11.50(b) requires this information in any human-readable form, including electronic displays and printouts, and subjects it to the same controls as electronic records.
As an implementation practice, use a specific signature meaning statement tied to the task. Distinguish the decisions rather than using a generic signed status:
- Execution: the operator attests to performing the identified activity.
- Verification: the checker attests to checking the specified result or activity.
- QA approval: the authorised reviewer approves the identified record or decision within their assigned responsibility.
For practical review of an electronic batch record, compare the on-screen manifestation with its readable export. Check that the printed name remains visible rather than being replaced by an account identifier, and that the meaning remains attached to the relevant signing event.
As a presentation design choice, make the time-zone reference understandable across displays and exports; this does not prescribe a universal timestamp format. A readable signature block is not, by itself, proof of the underlying signing event: inspect the linked record evidence as covered above.
05Components, controlled sessions and identification-code/password security
Binding US requirements
For US drug GMP records within Part 11 scope, 21 CFR 11.200(a)(1) requires non-biometric electronic signatures to employ at least two distinct identification components, such as an identification code and password.
For US drug GMP records within Part 11 scope, 21 CFR 11.200(a)(1)(i) requires the first signing in a series during a single, continuous period of controlled system access to use all electronic signature components. For US drug GMP records within Part 11 scope, that same provision requires subsequent signings in that period to use at least one component executable only by, and designed for use only by, the individual.
For US drug GMP records within Part 11 scope, 21 CFR 11.200(a)(1)(ii) requires all signature components for each signing outside a single, continuous period of controlled system access.
For US drug GMP records within Part 11 scope, 21 CFR 11.300 requires security and integrity controls for identification-code/password signatures. For US drug GMP records within Part 11 scope, 21 CFR 11.200(b) requires biometric signatures to be designed so that only their genuine owners can use them.
Implementation choices, not universal settings
In authentication design, identification components and authentication-factor categories are different concepts. An identification code names the account; a password supplies a secret. Their combination should not be described as multifactor authentication merely because both appear on a signing screen. Assess a password-plus-token design by what each element actually proves.
- Shared-terminal handover: define how the departing operator's signing context ends before another operator takes control.
- Session expiry: document what ends controlled access and which authentication steps follow; use the worked signing cases for continuity reasoning.
- Credential recovery: establish identity checks and how restored credentials affect existing sessions.
- Failed attempts and account disabling: define escalation, blocking and restoration responsibilities, including effects on active signing sessions.
These are implementation questions, not universal password intervals or timeout values. As a security practice, preserve authentication outcomes in signature evidence, not passwords. Review the configuration against actual terminal use, including shift changes and unattended workstations.
06Where to sign: execution, checks, QA review and decisions
Start with US and EU scope to identify applicable record obligations. A signing-point matrix typically separates execution, checking, review and disposition. These are risk- and procedure-based examples, not universally mandated signature points; routine data entry need not become an approval.
| Record or action | Decision being expressed | Responsible role | Record boundary | Supporting evidence |
|---|---|---|---|---|
| Dispensing execution | Dispensing completed as recorded | Dispensing operator | Defined material-dispense step | Material identity, weights, variances |
| Equipment check | Equipment suitable for intended use | Assigned checker | Equipment and pre-use check | Cleaning status, inspection results |
| QC result review | Results reviewed and assessed | QC reviewer | Identified sample and result set | Raw data, calculations, exceptions |
| Deviation assessment | Impact and proposed action assessed | Designated quality reviewer | Defined assessment revision | Investigation, affected records, rationale |
| Batch-disposition decision | Disposition authorised | Authorised disposition role | Batch and reviewed record collection | Production review, QC conclusions, deviations |
For grouped sign-off, identify the covered records, revisions and attachments in the review statement or an associated index. A signature on that defined collection expresses a bounded decision; an ambiguous batch-level status change does not explain what was reviewed. Grouping a batch record review does not establish that one signature satisfies every underlying record obligation.
For US drug GMP records, FDA's Part 11 guidance, Section III.C.5, describes hybrid coexistence of record and signature components where predicate requirements are met and record content and meaning are preserved. This is official guidance, not a universal signing-point mandate.
07From proposed record to executed signature and later amendment
A practical signing lifecycle keeps preparation, human review and signature execution distinct. Start with the signature-point decisions: what decision is being made, by whom, and over which content? The workflow below illustrates a suggested operational sequence, not a prescribed regulatory architecture.
Identify intended record revision → establish signer identity and authority → review content → select signing meaning → execute signing action → confirm recorded outcome → preserve evidence for later review.
Before the signing decision, make the review boundary visible: the record identifier, revision, included activities and unresolved items. For an assembled batch record, distinguish the assembly’s review state from each contributing source record’s state. A reviewed source record does not, by itself, establish that the assembled record has been reviewed. Present the content covered by the decision before asking the signer to select the signature meaning.
Proposed interface states can make confirmation actionable:
- Recorded: show the saved signature against the intended revision.
- Rejected: explain why the signing attempt was not accepted.
- Outcome uncertain: indicate that confirmation is unavailable and route the attempt to reconciliation, rather than inviting blind repeated submission.
Preserve the signed revision and its associated evidence so a later reviewer can reconstruct the decision. The worked cases address recovery from uncertain outcomes.
For later amendments, use the record-version relationship covered above: identify what changed and assess which decisions need renewed review. Do not treat every amendment as automatically invalidating every earlier signature, or present an earlier signature as approval of newly changed content. Keep the historical decision distinguishable from the current revision’s review status.
- Select recordIdentify the content and revision being presented.
- Establish authorityCheck the signer and permitted decision.
- Review contentExamine the record and relevant supporting evidence.
- Express MeaningIdentify the decision this signature will represent.
- Execute signingApply the appropriate controlled-access signing route.
- Confirm outcomeResolve uncertain outcomes before repeating submission.
- Preserve contextRetain the signed revision and subsequent amendments.
08Closed and open systems: integration boundaries and interrupted signing
For US drug GMP records within Part 11 scope, 21 CFR 11.3(b)(9) defines an open system by access not being controlled by those responsible for the records’ content. For the same US drug GMP scope, 21 CFR 11.3(b)(4) defines a closed system by access being controlled by those responsible for that content.
For US drug GMP records handled through open systems within Part 11 scope, 21 CFR 11.30 requires procedures and controls designed to ensure authenticity, integrity and, as appropriate, confidentiality. For those US drug GMP records, that provision identifies document encryption and appropriate digital-signature standards as examples of additional measures.
Practical boundary and interface checks
Assess actual access responsibility and transmission boundaries rather than classifying a system solely as cloud or on-premises. Map connections among manufacturing, laboratory, quality and document systems. For example, an MES–QMS interface needs an explicit account of which system holds the signed decision and what the other receives; this is an architecture check, not a product capability claim.
A suggested interface evidence checklist covers:
- Source and destination record references, with revision mapping.
- Signing meaning and timestamp interpretation, including time-zone handling.
- Transfer status and reconciliation of missing, duplicated or mismatched messages.
A receiving system’s approved status is not a substitute for understanding the originating decision. As a recovery practice, distinguish interrupted signature execution from interrupted transmission of an already signed record. Before retrying, establish whether the source committed the signature and whether the destination received it. Reconcile uncertainty rather than treating a timeout as proof of failure or success.
Use the implementation and review checklist for ownership, testing and retrieval preparation.
09Worked cases: session reuse, revised records and transmission recovery
These hypothetical cases illustrate implementation practice, not additional regulatory requirements. Each decision depends on the recorded circumstances rather than the workstation display alone.
Controlled-session signing
- Assumptions: A named operator uses an individually attributable account on a shared workstation, signing a dispensing record and then a checklist during a demonstrably continuous controlled-access period. Units: signing events and sessions.
- Observed state: The account remains logged in, but login status alone does not establish that the operator retained control between signatures.
- Decision: Compare the authentication events with the component rules covered above. Select the continuous-session route only with evidence of continuity; after handover or interrupted access, use the separate-session route rather than inheriting the previous operator’s signing context.
- Retained evidence: Preserve signer identity, authentication events, session boundaries, access interruptions and the record associated with each signature. These support attributable recording.
- Unresolved condition: If continuity cannot be demonstrated, do not justify reduced authentication from the still-active screen.
Correction after QA review
- Assumptions: A reviewed batch-record revision contains an incorrect equipment reference, subsequently corrected. Units: record revisions and review decisions.
- Observed state: The original QA signature concerns the earlier content; the corrected reference may change the basis of review.
- Decision: Assess whether the correction merely fixes transcription or changes equipment suitability, traceability or the review conclusion. A designated human reviewer determines and documents the further review needed; neither blanket signature carry-forward nor blanket invalidation is assumed.
- Retained evidence: Keep the original signed revision, amendment, reason, supporting equipment evidence, significance assessment and subsequent review decision connected through the audit trail.
- Unresolved condition: If the equipment actually used remains uncertain, resolve that uncertainty before treating the correction as clerical.
Interrupted transmission
- Assumptions: An approval request is submitted; connectivity fails before confirmation. Units: submission attempts, recorded signature events and transfer receipts.
- Observed state: The client cannot determine whether signing completed. A missing response is not evidence of a missing signature.
- Decision: Reconcile the authoritative signature event, signer and record revision before authorizing another attempt. Apply the approach to integration boundaries covered above.
- Retained evidence: Preserve request identifiers, submission status, recorded events, receipts and the reconciliation decision.
- Unresolved condition: If status remains ambiguous, hold the retry pending investigation rather than generating another potentially duplicate approval.
10Failure modes: detectable symptoms, containment and prevention controls
Use these hypothetical conditions in operational qualification and recovery testing. They are suggested manufacturing-workflow tests, not observed product defects. Assign each control an owner and retain its test result.
| Symptom | Exposure | Immediate containment | Preventive test | Evidence retained |
|---|---|---|---|---|
| Cached authority survives role revocation | Withdrawn signing permission remains usable | Access administrator: suspend affected access | System owner: revoke permission during an active session; confirm signing is blocked | Permission history, attempted action, pass/fail result |
| Time-zone display misleads reviewers | Apparent event sequence differs | QA: pause chronology-dependent decisions | System owner: compare screen and export against the documented time reference | Paired displays, reference, comparison result |
| Destination-record reference is stale | Approval points to an obsolete revision | Process owner: isolate affected approval | Interface owner: change destination revision; confirm stale-reference rejection | Record identifiers, revisions, rejection result |
| Restoration leaves signing context incomplete | Decision cannot be reliably interpreted | QA: withhold reliance on approval | Recovery owner: restore a signed test record; compare context before enabling use | Baseline, restored record, comparison result |
Detection is not prevention: a report can expose a mismatch without stopping it; an execution control can block an action without explaining the incident. Test both purposes separately.
Where signing context is uncertain, contain the issue before relying on the approval. Preserve relevant records and route the issue through the site's exception process, using a validation deviation report for test failures rather than silently reconstructing a signing event.
11Implementation and review checklist for people, procedures and records
For US drug GMP records within Part 11 scope, 21 CFR 11.1(e) requires computer systems, controls and attendant documentation maintained under that part to be readily available for, and subject to, FDA inspection.
Use the following practical readiness checklist to organise preparation; it is not a claim that every item is independently mandated by Part 11:
- Define intended use and identify which records fall within the applicable framework.
- Name process owners and confirm signing authority for each decision.
- Test representative workflows using realistic record content, roles and handoffs.
- Test exceptions, including interrupted signing, rejected decisions and retrieval failures.
- Check that training covers the configured workflow and escalation routes.
- Assess configuration changes for effects on signing, evidence preservation and retrieval.
- Demonstrate readable retrieval of retained records and their supporting context.
For acceptance and periodic review, walk a representative record end to end: connect the content reviewed, the human signing decision, supporting context and retained output. Capture results in the validation record. Assign unresolved issues to named process owners for resolution and follow-up testing; a feature list alone is not acceptance evidence.
Next, consider where V5 fits, keeping application support separate from legal applicability and human approval authority.
12Where V5 fits in the batch-record evidence picture
For implementation planning, distinguish the contents of the electronic batch record from the site's authority to act on them. The practical question is not simply whether signatures appear in the assembled record, but who is authorized to review the evidence and make the resulting quality decision.
Frequently asked questions
Q.Can a login or an audit-trail entry substitute for a person's signing decision?+
Not by itself: operationally, authentication establishes access, while an event log records activity; neither necessarily expresses a deliberate signing decision. For US drug records subject to Part 11, 21 CFR 11.50(a)(3) requires signed electronic records to identify the signature's meaning. A practical design presents the record and intended action before confirmation. The signature meaning statement should distinguish performing work from reviewing or approving it, rather than treating every saved entry as approval.
Q.Does a digital signature solve the same problem as an electronic signature?+
They overlap, but address different questions. In technical practice, a digital signature uses cryptography to support checking data integrity and the association with a signing key. An electronic-signing workflow also addresses what a person intended to sign and what that action meant. Cryptographic verification alone does not establish that a reviewer examined the batch or had approval authority. Evaluate attributable recording, key ownership, record presentation and approval permissions together, rather than treating a valid cryptographic result as proof of a sound review.
Q.When can a single sign-off cover several batch steps or supporting records in the [batch execution history](/glossary/batch-execution-history)?+
As workflow design practice, grouped sign-off is appropriate only when its scope is explicit and the signer can examine the included records. Check applicable product-specific signing obligations before adopting it. Identify the covered steps, supporting results and record versions; distinguish package review from witnessing an individual operation. For an eBMR, a useful test is whether a later reviewer can reconstruct exactly what the signer approved without guessing from screen layout, folder membership or the batch's current contents.
Q.How can operators use a shared [shop-floor terminal](/glossary/shop-floor-terminal) without sharing signing identities?+
Treat the workstation as shared equipment, not as a shared person. Common operating controls include individual accounts, deliberate user handover, session locking and a signing prompt that identifies the current signer. Keep credentials personal; avoid a supervisor entering credentials so another operator can continue. A password-plus-token arrangement can support individual authentication, but its usefulness depends on configuration and handling. Test handover during interruptions and shift changes, especially whether an unfinished signing screen remains associated with the previous operator.
Q.What should a reviewer examine through the [audit-trail review workflow](/glossary/audit-trail-review-workflow) when a record changes after it has been signed?+
Compare the signed version with the changed version, then assess whether the original decision still applies. For EU medicinal-product GMP systems, Annex 11, section 9 recommends documenting the reason for changes or deletions of GMP-relevant data. In practical review, examine the changed values, actor, timing, explanation and downstream effects. Use a deviation workflow where appropriate to assess impact and determine whether further review or approval is needed; do not silently treat the earlier signature as approval of revised content.
Q.How can a site recover from a lost signing confirmation without creating a duplicate approval?+
Treat a missing confirmation as an uncertain transaction outcome, not proof that signing failed. A practical recovery procedure checks the authoritative record for the signer, intended action, record version and transaction status before anyone retries. If the signature exists, reconcile the display or notification failure without signing again. If it does not, an authorised person can execute the intended action after checking the record. Route unresolved cases through the site's data integrity incident process and preserve the investigation history.
Q.Can paper signatures and [electronic batch records](/glossary/electronic-batch-record) coexist in a batch-review workflow?+
Yes, with a deliberately defined boundary. For US drug records required to be maintained but not submitted to FDA, 21 CFR 11.2(a) permits electronic replacement in whole or in part, provided Part 11 requirements are met. As operating practice, a hybrid record system should identify the electronic version covered by each paper signature and preserve their association. Avoid a signed cover sheet whose referenced attachments can change without showing which content the reviewer actually approved.
Q.Does choosing an e-signature feature establish that a site's configured process is compliant?+
No. A feature selection is not a conclusion about the site's configured process. A practical assessment examines intended use, signing authority, record scope, identity controls, change handling, recovery and staff procedures against applicable obligations. Test realistic failure cases as part of paperless validation, including interrupted signing and changes after approval. Software supports execution and evidence capture; authorised humans still make review, approval and release decisions. Acceptance should rest on demonstrated operation of the configured workflow, not the feature's name.
Primary sources
Explore this topic
E-Signature sits inside this topic cluster in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
Want to see how E-Signature could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
