Regulations and compliance · Practical guide

Part 11 electronic signatures: meaning, identity and record linking

A button marked “Approve” does not show which declaration a person made or which record version they signed. For an electronic signature in Part 11 scope, connect purpose, identity and technical implementation. First establish the need for the signature, then test the controls in the configured product.

Table of contents

At a glance

When is an electronic confirmation a Part 11 signature, and what controls does it need?

Under § 11.3(b)(7), an electronic confirmation is an electronic signature when an individual executes, adopts or authorises it as the legally binding equivalent of a handwritten signature. Part 11 applicability depends on the record and underlying FDA requirements. Where it applies, link the signature uniquely to an identified individual (§ 11.100). Show the name, time and meaning in each human-readable form of the signed record (§ 11.50), and link the signature to the record (§ 11.70). Non-biometric signatures are also subject to the component and session rules in § 11.200.

  • A status change may facilitate a signature, but it does not prove it alone.
  • Importance and signed data are part of the requirements.
  • Authentication, signature representation, and record binding are distinct control questions.

1. Determine which statement is actually required

Begin with the technical process: Should a person certify, assume responsibility, or authorize a specific state? Clarify the applicable documentation and signature requirements. Part 11 does not make every action involving electronic execution automatically signature-required.

An internal confirmation can be a pure workflow act or can be used as a signature. The meaning, actual use and controls are decisive. Neither the button text nor the advertising statement of a platform suffices as classification. Describe in the procedure which declaration is made with the action.

Sources: [1] [2]

2. Distinguish click, signature, and visible display

The following three cases represent intended scenarios. No actual software has been evaluated. The initial assumption for Cases B and C is an applicable Part 11 context with intended electronic signature.

Own decision matrix for electronic confirmations
SituationProvides evidence for the action takenWhat still needs to be clarified
A: Employee marks a task as reviewed; no signature required A status change assignment can document progress in activities. Verify record requirements and history; do not derive a signature solely from the status name.
B: Auditor confirms review of Record Version 3 with defined significance Should a personal electronic signature be used for exactly this version? Demonstrate identity, authentication, timestamp, significance, binding, and subsequent representation.
C: PDF shows a inserted signature under version 3 First, only a visible representation in the document. Without additional evidence, no credible assertion can be made regarding signature authenticity or a secure connection to the record.

Sources: [1]

3. Clarify identity and authorization prior to usage

§11.100 requires the uniqueness of the electronic signature to a specific individual and the verification of their identity prior to assignment or recognition. The signature must not be reassigned to another person or reused by them. Organizational responsibility and technical account management must be aligned.

In addition, verify the authorization for the specific activity. A correctly identified employee is not automatically authorized for the technical approval of every record. Within your own role model, clearly define who is authorized to explain the significance of records at each level and how removal or substitution shall be organized. Shared signature accounts are not compatible with individual assignment.

Sources: [1]

4. The session rules apply specifically to non-biometric signatures

§11.200 distinguishes between non-biometric and biometric signatures. Non-biometric signatures must utilize at least two distinct identification components. During a series of signatures within a single continuous controlled session, all components are required for the first signature; for subsequent signatures, at least one component that can be used exclusively by the actual holder is required.

Outside of a continuous controlled session, all components must be applied each time. This does not imply a blanket requirement to re-enter two components every time a field is edited. Similarly, a browser session that has remained open for an extended period must not be automatically considered a controlled session without proper verification. Describe and evaluate the session start, continuity, and end in alignment with implementation requirements.

Sources: [1]

5. Review and verify the representation and linkage to the record separately

§11.50 specifies the name of the signatory, date, and time, as well as the meaning of the signature. These details are subject to applicable record controls and must be presented in human-readable formats, such as display or print. A green checkmark alone does not satisfy these requirements.

Section 11.70 requires the linkage between signature and electronic record to be such that it cannot be cut, copied, or transferred using ordinary means, to prevent falsification of another record. Therefore, verify which version was signed and how subsequent modifications or exports can be detected to maintain the integrity of this linkage. A signature graphic is not a substitute for proof of linkage.

Sources: [1]

6. Verify a complete signature event rather than just the login

Example: Record R-17, version 3, contains an approved setpoint value of 12.0. The examiner explicitly declares verification completed for this stand. Later version 4 is created with the value 12.5. These numbers are not product specification. The own setpoint requirement is that the previous statement does not appear tacitly as a test of the new version.

The change from 12.0 to 12.5 does not, by itself, indicate criticality nor impose a new regulatory signature requirement. What is decisive is that the subject matter of the declaration has changed. Whether a renewed assessment or signature is required follows from your process and the applicable requirements.

Example: Should the record R-17 be reviewed?
Test stepExpected findingFailure scenario and response
Version 3 with 12.0 sign-off Person, time, significance, and version 3 clearly linked. Visible only: username; clarify missing additional signature details.
Version 4 with 12.5 generate Change remains understandable; explanation for version 3 is not transferred tacitly to version 4. Unchanged release note suggests review of the new value: correct the process and presentation.
Generate a human-readable output of version 3 Required signature details and record assignment remain identifiable. Name reference without significance or timing: Batch release requirement not met.
Want to transfer signature display to a foreign record Standard copying does not generate a valid signature binding for a foreign record. Image can be copied: do not derive a valid electronic signature of the target record; assess binding separately.

Sources: [1]

7. Do not overlook certification and operational controls

§11.100(c) addresses certification to the FDA that electronic signatures used are intended to serve as a legally binding equivalent to traditional handwritten signatures. The current text permits certification using either electronically or paper-transmitted traditionally handwritten signatures. The current FDA guidance on ESG Next Gen outlines the specific procedure for this approach; legacy paper-only instructions are not reliable for generalization.

Section 11.300 adds controls for identification codes and passwords, such as unique combinations, regular review or audits, procedures for password loss, and measures to prevent unauthorized use. The text does not specify a universal number of days for password change. Product certificates or other signature schemes do not substitute for the evaluation of these specific Part 11 requirements.

Sources: [1] [3]

8. Define the signing process in coordination with the department and IT

In a SME, the subject-matter expert should first define the significance and the specific scope to be signed off. IT is responsible for identity management, session handling, and data connectivity. The responsible quality function assists in translating applicable requirements into verifiable criteria. The exact approval structure must align with the respective responsibilities.

Evaluate targeted changes to roles, authentication, export, or record model subsequently. A successful login test alone provides little assurance that after an update, the signature remains correctly associated with the intended version and is properly issued.

  • Define the record scope and purpose of professional signature.
  • Demonstrate personal identity and specific authorization.
  • Implement non-biometric session and component rules appropriately.
  • Verify the name, timestamp, and significance in display and relevant output.
  • Verify binding to the correct record version including changes.
  • Organize certification and ongoing access controls appropriately.
  • Assess changes to signing workflows and outputs and record the rationale.

Sources: [1]

Project experience and collaboration

Preserve the meaning of the signed record after a change

What statement is a person confirming with their signature? With process owners, we start there. In a controlled test, we trace whether identity, meaning and the signed version remain linked when a record is changed or exported. A defined approval workflow may need a targeted test. Several signature types or separate systems need additional handover checks. We distinguish the legal applicability of Part 11 from the statement being signed and how the system implements it.

Frequently asked questions about Electronic signatures

Is every click on "Release" already a Part 11 signature?

No. A click can serve as a signature if it is associated with the intended personal declaration and the required controls. A pure workflow status alone does not constitute this. First determine the purpose, record, and signature intent, followed by the technical implementation.

Sources: [1]

Is a status change fundamentally inappropriate as a signature?

That would be too generalised. An application can link a status change to an appropriate signature process. Key factors include identity, required authentication, significance, timestamp, and connection to the signed record. The status field alone is not sufficient validation evidence.

Sources: [1]

Do we need two new entries for each signature?

§11.200 distinguishes, for non-biometric signatures, between the first and subsequent signatures within a continuous, controlled session, treating them as separate processes. This differentiation must be reflected in your implementation. A blanket two-factor rule per field does not align with this differentiated requirement.

Sources: [1]

Does the same component rule apply to biometric signatures?

The component and session rules described in §11.200(a) do not apply to non-biometric signatures. Biometric signatures are separately addressed in paragraph (b). Therefore, an assessment must specify the actual method being used, rather than indiscriminately mixing requirements for different methods.

Sources: [1]

Does a name with a timestamp in PDF suffice?

Not solely. Section 11.50 also highlights the importance of signature; additionally, the linkage to the record as specified in Section 11.70 must be considered. Review the complete signature process and the release procedure. A neatly presented name endorsement provides neither identity verification nor an appropriate record linkage.

Sources: [1]

Must every subsequent modification be automatically re-signed?

The previously signed version must not be misleadingly interpreted as a statement regarding a different version. Whether and by whom a renewed signature is required shall be determined by purpose, changes, and applicable documentation requirements. This decision shall be established within the procedure and the system behavior shall be reviewed.

Sources: [1] [2]

Is a specific European signature level automatically compliant with Part 11?

A designation from a different signature regime does not automatically address the individual Part 11 questions. Verify the actual coverage of identity, significance, timing, record linkage, and operational controls. This article does not constitute a standalone legal assessment of European signature levels.

Sources: [1]

Must we always send the FDA certification as a paper letter?

The current §11.100(c) permits the electronic or paper-based submission of traditionally manually signed certifications. The FDA provides a distinct digital workflow for ESG Next Gen. Evaluate the currently applicable submission pathway for your specific process; a legacy paper-only instruction is not a general standard.

Sources: [1] [3]

Does Part 11 require a password change every 90 days?

Section 11.300 requires relevant controls, including regular reviews or audits, but does not specify a universal daily frequency. Define appropriate measures for the specific user identification and password procedure. Considerations should include password loss, unauthorized use, and, if applicable, token controls.

Sources: [1]

Can a software vendor assume full signature responsibility?

It can provide appropriate functions and supporting evidence. However, your organization must, among other things, understand personnel identity, authorizations, intended signature purpose, and actual usage. Review purchase order receipts based on their specific coverage and supplement any organizational or project-specific gaps that are not addressed.

Sources: [1]

Sources and review date

Source status: October 6, 2026: 21 CFR Part 11 in the eCFR display up to October 2, 2026 and FDA Scope and Application 2003. The FDA website guidance page is dated September, while the PDF is dated August 2003. The current ESG-Next-Gen information outlines its own submission process; therefore, no universal portal mandate is implied.

  1. 21 CFR Part 11 — Electronic Records; Electronic SignatureseCFR: Title 21 consolidated through 02.10.2026; Title 21 last amended on 30.09.2026. The display does not constitute a claim of a Part 11 amendment on this date. Citations: §11.1(a)–(e) and sector-specific exemptions (f)–(p); §11.2; §11.3(b)(4),(5),(6),(7),(9); §11.10(a)–(k); §11.30; §§11.50, 11.70, 11.100, 11.200, 11.300
  2. FDA: Part 11 — Scope and Application, Original-PDFOriginal cover page August 2003, Pharmaceutical CGMPs; Contains nonbinding recommendations. Currently listed by FDA as Final. Reference locations: I. Introduction, printed pages 1–2; III.A, page 4; III.B.1–2, pages 5–6; III.C.1–5, pages 6–8
  3. FDA: Letters of Non-Repudiation Agreement — ESG Next GenCurrent ESGNext gene page, retrieved06.10.2026; no separate standard text. Findings: Individual vs. Company-Wide Letters; Physical Letters Are No Longer Required; Letter Review Requirements; Samples

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Applicability and targeted review of evidence

Daniel Herrmann Consulting supports you in defining your specific process and the appropriate documentation requirements. The scope and responsibilities are aligned with actual needs.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →