Regulations and compliance · Practical guide

21 CFR 11.100(c): certifying electronic signature equivalence

The organisation's certification concerns the intended legal effect of its electronic signatures. The accuracy of a specific workflow and the lasting link between signature and record require their own controls and supporting evidence.

Table of contents

At a glance

What does certification under 21 CFR 11.100(c) mean?

Organisations using electronic signatures under Part 11 must certify to FDA before or at the start of use that those signatures are intended as the legally binding equivalent of handwritten signatures. The certification under § 11.100(c)(1) includes a traditional handwritten signature and may be submitted electronically or on paper. Under (c)(2), further certification for a specific signature is required on request. FDA does not thereby certify the software. Verify identities, individual attribution and the other applicable controls.

Scope and Applicability

First, the applicability of Part 11 to the relevant records and signatures must be established. For the specific submission, current FDA guidelines and the specific submission context are decisive; ESG registration and general Part 11 requirements must not be equated.

Sources: [1] [2]

Declaration, identity, and system control are distinct responsibilities

The identity of the signing individual must be verified prior to assignment or implementation of the electronic signature. Furthermore, unique signatures and the management of access credentials must be established. A shared account is not suitable for uniquely representing different individuals.

Review the current FDA information for your submission pathway. The FDA also explains non-repudiation in the context of ESG NextGen. A submission instruction described for this service should not be presented as the sole rule for any conceivable Part 11 context without proper evaluation.

Sources: [1] [2]

Statement on Separating Binding Effect and System Validation Proof

21 CFR 11.100(c) addresses the affirmation to the FDA that electronic signatures in the specified system are intended to serve as a legally binding equivalent to traditional handwritten signatures. The timing is prior to or at the commencement of such use. This statement is not a FDA certification of the software and does not serve as a substitute for technical or organizational requirements applicable to electronic signatures.

First, assess the Part 11 applicability scope for the relevant records. Not every digital click within an organization constitutes an equivalent electronic signature. Identify which documents and decisions are involved. The specific legal application is derived from the applicable regulatory framework, not solely from the product name of a DMS or QMS.

In addition, separate general Part 11 requirements from specific registration steps for ESG NextGen. The FDA has established its own NRL procedures and templates for this purpose. These guidelines are to be used in this context. A successful Gateway registration does not automatically validate the suitability of all internal electronic signatures.

Sources: [1] [2]

What requirements, aside from the declaration, remain?

Part 11 addresses, among other things, unique personal assignment, identity verification, signature manifestation, and linkage to the record. The declaration in 11.100(c) does not elevate these requirements. A file bearing company letterhead does not establish that the application appropriately represents the actual signature.

Review specific signature actions. Which individual confirms which content and what purpose? Is the name, date, time, and intent clearly identifiable in the required context? Is the link to the record maintained? The exact implementation depends on the system, signature type, and intended use.

Own work aid: What additional requirements remain besides the declaration?
LevelQuestion to investigateWhat is not replaced by this
Scope Which records and signatures are involved? No blanket categorization of all applications
Declaration Is the scope and authorized approval clarified? Technical Signature Verification
Identity Is the actual person appropriately assigned? Record and Meaning Reference
Manifestation Are required signature details visible? Integrity and permanent linkage
Operation How are access and changes controlled? Subject Matter Expert Approval Decision

Sources: [1] [2]

Properly use current ESG-NextGen guidance notes

The FDA page outlines individual and enterprise-wide NRLs for ESG NextGen. New users can generate or upload an electronic NRL via the Unified Submission Portal. The page also states that physical delivery is no longer required—this statement specifically applies to the registration process described.

A company-wide explanation requires an authorized signature and a clear company scope after the FDA help. Individual explanations refer to designated persons. Use the current official information and check the actually suitable way. Do not copy outdated postal address or previous portal instructions from a foreign blog.

Document which context has been examined and which documents are available. The organizational decision on authorised signatories and scope is not just a technical administration task. In case of uncertainty, the competent professional or legal body is included. This article does not replace this concrete evaluation.

Sources: [1] [2]

Example: NRL available, signature indicates incorrect record version

A company holds a relevant statement. In an application, a document is confirmed, but subsequently replaced by a different version, without the signature reference remaining unambiguous. The statement on binding effect does not address this technical gap.

Prepare a known document version and perform the intended signature using an authorized individual. Verify the visible person, timestamp, significance, and relevance to the content. Subsequently, modify the record via the intended pathway in a controlled test environment. The existing rule must specify how the prior signature and the new version shall be handled.

Add an unauthorized test and an exported certificate. The signature should not be replaced by a mere name display without necessary context. The test report links actual actions to the specifically referenced record. It is not a general certificate certifying the system's functions.

Own work aid: Organizational statement and actual signature attribution
Test caseActionExpected finding
Authorized Signature Confirm the current status Assigned to person, time, and significance
Unauthorized attempt Same action without authorization Selected access control is effective
Record amendment Change content after signature Earlier and newer relationships traceable
Output Export batch release signature information The required manifestation remains understandable
Historical Access Investigate previous decisions Damaliger content and signature reference available

Sources: [1] [2]

Build an internal verification record

The record may integrate scope, declaration, responsibility, signature process, and system documentation. Identify where the current declaration and its extent are located. A retained copy lacking a clear reference to organization and usage is weak. Similarly, no outdated registration pathway should be maintained as a permanently valid instruction.

Distinguish the formal certification from the tested function. An auditor or internal reviewer should be able to establish both whether the organisation's certification is in place and whether signing works in the intended system. Each needs its own evidence.

When changes occur to organisation, system, or signature process, the affected scope is assessed. A new application may require different forms of validation evidence. A new technical login does not automatically constitute a fully evaluated signature change. Document the specific decision instead of making general statements about all electronic signatures.

Sources: [1] [2]

Consider historical signatures during migration

A transferred historical signature is not automatically equivalent to a newly executed target system action. Ensure that identity, intent, timestamp, and record reference are clearly established and traceable within the appropriate target or archive pathway. An import account must not be ambiguously presented as the original decision-maker. The required statement shall be evaluated based on specific investigation cases.

If native data transfer is technically infeasible, the required traceability must still be addressed. An appropriate alternative solution may be necessary. The inability to perform an import does not relieve the need for documentation. Shutdown and archiving decisions must take into account the actual historical access requirements.

Sources: [1] [2]

Working template: Detach explanation and concrete signature function separately

Enter the organisational statement and the specific signature function separately for your actual application scenario. Specify the scope, responsible party, and documentation support for each. If the two signature trails do not align, the relevant gap is addressed specifically; for example, a new statement does not correct a false record linkage.

Review the current submission pathway based on the official FDA information for the relevant registration process. Document the date and context. A previous template file or instruction for a different access method is not a reliable basis for this purpose.

Sample filling example – internal work aid
Document fieldExample entryAcceptance question
Scope Designated electronic records and signatures. Has the application of the framework been clarified?
Declaration Authorized approval with clearly defined scope. No software certification derived from this?
Person Actual authorized signatory. Is identity appropriately assigned?
Content Document in a definitive state. Which version is confirmed?
Significance Visible approval or other action. Do the signature manifestation and link to the record meet the requirements?
Change The following content is subject to review. Don't you think it's unclear how to transfer your earlier signature?

Sources: [1] [2]

Next steps

  • Clarify the applicability of Part 11 for records and signatures.
  • Responsibility for the declaration and current FDA instructions to be verified.
  • Define identity and access controls.
  • Signature display, record binding, and process documentation assessment.
Further reading:

Project experience and collaboration

Verify the certification statement and signature function separately

With your owners, we examine both the organisation's declaration and an actual signing event. Who confirms which document version, with what meaning and under whose identity? Existing documents may need clarification, whereas a broken link to the signed record requires a process or technical correction. We distinguish these tasks and identify current official guidance for the relevant submission route. Your authorised parties provide the necessary legal and organisational confirmations.

Frequently asked questions about Certifying electronic signature equivalence to FDA

Does certification of electronic signature equivalence mean that FDA has approved the software?

No. The statement relates to the intended legal binding effect of electronic signatures within the applicable framework. It is not a software approval and does not automatically confirm identity, technical signing function, or record linkage. These aspects require separate, appropriate evidence for the specific use case.

Sources: [1] [2]

Are electronic signatures always subject to Annex 11 requirements?

No. The specific regulatory applicability must first be assessed. Not every digital signature within every organization automatically falls within this scope.

Sources: [1] [2]

Does the declaration suffice without identity verification?

No. 21 CFR 11.100 addresses both the certification and the unambiguous assignment and verification of identity.

Sources: [1] [2]

Must NRLs for ESG NextGen be mandatorily shipped by post today?

No. § 11.100(c)(1) has allowed electronic or paper-bound submissions since the amendment of March 2, 2023; the declaration remains to be signed by hand. For ESG NextGen, the FDA describes the generation or upload of an electronic declaration when registering in the Unified Submission Portal. An additional mail shipment is only optional there. For the respective submission process, use the current FDA notes.

Sources: [1] [2]

Why should the significance of a signature be explicitly visible?

She specifies the action the individual confirms, such as inspection or approval. A name and timestamp alone may leave the statement open. Verify the required manifestation and linkage to the correct record within the applicable framework. The specific implementation follows the intended signature process.

Is a company login automatically an appropriate electronic signature?

No. Registration is not yet a signature action. Within the scope of Part 11, personal assignment, name, date, time, and the meaning of the signature in legible form must be included in the signed record, along with a link to the record (§§ 11.50, 11.70, 11.100). Non-biometric signatures must utilize at least two distinct identification components as specified in the session rules under § 11.200(a)(1). Therefore, verify the specific signature workflow rather than merely confirming the presence of an enterprise login.

Sources: [1]

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements.

  1. eCFR: 21 CFR Part 11 – Electronic Records; Electronic SignaturesCurrent regulatory text. Applicability and additional documentation obligations must be assessed on a process-by-process basis.
  2. FDA: Letters of Non-Repudiation Agreement – ESG NextGenFDA Guidance in the ESG Context; for the general requirement, see 21 CFR 11.100(c).

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

From an open point to a traceable approach.

We support you in assessing the current situation, clarifying responsibilities, and implementing appropriate evidence within operations. The type of support that is most effective depends on your system, your team, and the specific objective.

  • 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 →