Governance DocsGovernance Docs
Browse Toolkits

CART

No products in the cart.

Skip to content

21 CFR Part 11 Electronic Signature Rules: 5 Clear Sections

21 CFR Part 11 electronic signature: Part 11 e-signature rules

A 21 CFR Part 11 electronic signature is more than a typed name on a screen: the rule sets conditions for what the signed record shows, how the signature is tied to it, who may hold one and how a person proves who they are each time. This post walks through the sections in the order you would build the controls, then shows where the July 2025 draft of Annex 11 is stricter and what the in-force 2011 Annex 11 says.

The draft is a consultation text and not adopted. Part 11 and the January 2011 Annex 11 are in force.

21 CFR Part 11 electronic signature: what counts and when it applies

Part 11 defines an electronic signature as any symbol or series of symbols that a person executes, adopts or authorizes so that it carries the weight of their handwritten signature (11.3). Where a signature and its record meet the rule, FDA treats the signature as equivalent to a full handwritten signature, initials or other general signing (11.1(c)).

Scope still comes from the predicate rules. If a regulation requires a signature on a record you keep electronically and rely on, the signature controls apply. FDA’s 2003 guidance narrows what Part 11 covers, and it exercises enforcement discretion on validation, copies, retention and audit trails. It does not do so for the signature sections: 11.50, 11.70, 11.100, 11.200 and 11.300 remain enforced, alongside predicate rules. The one exception is legacy systems that were operational before 20 August 1997 and meet the guidance’s conditions, for which FDA says it does not intend to enforce any Part 11 requirement. Our 21 CFR Part 11 requirements guide covers the scope decision in full.

One more anchor: the general controls in 11.10 say the procedures should stop a signer from plausibly denying that a signed record is genuine, and 11.10(j) expects written policies holding individuals accountable for actions under their signatures.

21 CFR Part 11 electronic signature manifestation and linking: 11.50 and 11.70

For every 21 CFR Part 11 electronic signature, 11.50(a) lists three items that must appear with the signed record: the printed name of the signer, the date and time of signing, and the meaning. Review, approval, responsibility and authorship are the examples the rule gives. Section 11.50(b) adds that these items are subject to the same controls as the record and must appear in every human-readable form, including the screen and the printout.

Build and test this literally:

  • The name, date, time and meaning show on screen and on a printed or exported copy.
  • The meaning is chosen or displayed at the point of signing, not inferred later.
  • No user can edit the signature items on a signed record.
  • When systems span time zones, the time zone reference is clear and documented. FDA’s 2003 guidance does not expect the signer’s local time, but it expects clarity.

Section 11.70 ties the signature to its record so that nobody can lift a signature out, copy it or move it to another record to falsify it by ordinary means. Test it by trying to copy a signature block to another record, and by changing a signed record. The draft Annex 11 is explicit about the outcome it wants: a signed record cannot be modified, or a later change makes the record clearly show as unsigned (13.8).

If you sign paper printouts of electronic records (a hybrid setup), the draft suggests a checksum of the electronic record printed on the signature page so any later change invalidates the link (13.9). Define which form is the record before you design the control.

Uniqueness and identity verification: 11.100(a) and (b)

Each 21 CFR Part 11 electronic signature must belong to one person only and may never be given to, or used by, anyone else (11.100(a)). In practice that means individual accounts, no shared signing credentials, and retired identifiers that stay retired. When someone leaves, their user ID is disabled, not recycled.

Before you issue, approve or otherwise sanction a person’s signature, or any part of it, you must verify that person’s identity (11.100(b)). Make that a written step with a record: who checked, against what evidence, when, and who approved the account. Without that record you can show a login, but not that the person behind it was verified.

The certification letter to FDA: 11.100(c)

Before or at the time you start using electronic signatures, you must certify to FDA that the signatures in your system, used on or after 20 August 1997, are meant to carry the same legal weight as handwritten signatures. The certification is signed with a traditional handwritten signature and may be submitted in paper or electronic form. A 2023 amendment changed how the rule points to the submission place: it now directs you to FDA’s web page on Letters of Non-Repudiation Agreement, so look there for current instructions instead of relying on an old address from an older template.

Two practical points. First, the certification is made by the persons using electronic signatures, so assign an owner and keep the signed copy where an inspector can find it. Second, FDA may ask for more: under 11.100(c)(2) you must give further certification or testimony, on request, that a particular signature carries that same weight.

Components, sessions and misuse: 11.200

For a 21 CFR Part 11 electronic signature not based on biometrics, 11.200(a) expects a minimum of two separate identification components, for example a user ID plus a password, signatures used only by their genuine owners, and an arrangement where an attempt to use someone else’s signature needs the collaboration of two or more people. Biometric signatures must be designed so that nobody but the genuine owner can use them (11.200(b)).

The session rules are where configurations drift. The table sets out the in-force rule.

Situation What Part 11 expects
First signing in a single, continuous period of controlled access All signature components are used
Later signings in the same continuous period At least one component that only the individual can execute and is designed for only that person
Signings outside a continuous period of controlled access All signature components are used for each signing

Define “continuous controlled session” in your procedure: it ends on logout, inactivity timeout or a workstation left unattended. Test that the signing prompt asks for the right components after each of these events. The collaboration requirement is also a design test: if one administrator can reset a password and sign as the user without a second person involved, the control fails (a)(3).

Identification code and password controls: 11.300

Where signatures use an ID code with a password, 11.300 lists five controls. Map each to a configured setting or procedure:

Section Control What to configure or document
11.300(a) Each ID and password combination is unique Unique user IDs, no duplicate accounts
11.300(b) Issuances are periodically checked, recalled or revised Password aging or another periodic check, set by risk
11.300(c) Lost or compromised tokens and cards are deauthorized and replaced under rigorous controls Loss management procedure, controlled replacement
11.300(d) Transaction safeguards prevent unauthorized use and urgent reporting of attempts reaches the security unit and, as appropriate, management Lockout, alerts on failed attempts, a named recipient and response routine
11.300(e) Tokens and cards are tested initially and periodically Test records for any device that holds or generates credentials

The rule gives no password length, lockout count or interval. Set those by risk and write the reasoning down. Do not copy numbers from a template without one.

Where draft Annex 11 13.3 is stricter

The July 2025 draft puts signing in its own section (13). The biggest change from a 21 CFR Part 11 electronic signature is re-authentication. The draft expects a full re-authentication at every signing at a security level at least equal to login. Only for signatures in immediate sequence may a password or biometrics alone be used. It says authentication by smart card alone, by a PIN code alone, or by relying on the earlier login is not acceptable (13.3). Its identity section adds that a token or smart card alone is not sufficient if another user could use it (11.3).

Topic 21 CFR Part 11 (in force) Draft Annex 11 (not adopted)
Later signings in a session At least one component usable only by that person (11.200(a)(1)(i)) Re-authentication each time; in immediate sequence, password or biometrics only (13.3)
Smart card or PIN alone Non-biometric signatures need two distinct components (11.200(a)(1)); tokens and cards also need loss and testing controls (11.300(c), (e)) Not acceptable as the only means at signing (13.3); for login, not enough if another user could use it (11.3)
Reliance on the login session Later signings may use fewer components, but at least one personal component is still expected Not acceptable (13.3)
Manifestation Printed name, date and time, meaning (11.50) Full name, username, role where applicable, meaning, date and time, time zone where needed (13.6)
Signed record changes Linking so signatures cannot be transferred by ordinary means (11.70) Record cannot be modified, or later changes show it as unsigned (13.8)

So if you plan new configurations, avoid designs that depend on session reuse or a card with a PIN as the only factor. You can do that today without breaching Part 11, and it removes a rework item if the draft is adopted in a similar form. Do not assume it will be, and do not plan to a date: none has been announced. The EU GMP Annex 11 comparison tracks the draft against the 2011 text. Open systems also differ: the draft expects signatures to also follow relevant national or international rules, with trusted services as its example, where the system owner does not control access (13.2), while Part 11 requires added measures under 11.30.

EU Annex 11 (2011) on electronic signatures

The in-force Annex 11 is short on this topic. Section 14 expects electronic signatures to have the same impact as handwritten ones within the company, to be permanently linked to the record, and to include time and date. Section 15 covers batch release: where the system records certification, only Qualified Persons may certify, the releasing person must be clearly identified and recorded, and it must be done with an electronic signature.

Part 11 is far more prescriptive. A system built to meet the 21 CFR Part 11 electronic signature sections will largely cover section 14. The reverse is not true, because Annex 11 does not mention the FDA certification letter or the component rules. For an FDA-regulated product made in the EU, plan to the stricter text.

If you want the templates behind this, the 21 CFR Part 11 Toolkit includes an Electronic Signature Procedure, an Electronic Signature Identity Verification Record, an FDA Electronic Signature Certification Letter and an Electronic Signature Controls Verification Checklist, among 105 templates (68 Word and 37 Excel) for $99. The download is named “Computer System Validation Toolkit”. No template makes a system compliant; your configuration, validation and use do.

21 CFR Part 11 Toolkit sample page: GDL-CSV-075 - Electronic Signature Procedure
21 CFR Part 11 Toolkit sample page: GDL-CSV-078 - Electronic Signature Controls Verification Checklist
21 CFR Part 11 Toolkit sample page: GDL-CSV-098 - 21 CFR Part 11 Compliance Assessment Checklist

21 CFR Part 11 electronic signature FAQ

Do I have to send FDA a certification letter?

Yes, if you use electronic signatures covered by Part 11. 11.100(c) expects the certification before or at first use, signed by hand. Check FDA’s Letters of Non-Repudiation Agreement page for where to send it today.

Is a username and password enough for an electronic signature?

Part 11 expects a minimum of two separate components for non-biometric signatures, and a user ID plus a password gives you two. The session rules then decide what must be entered at each signing.

Can a user stay signed in and sign several records without re-entering anything?

Under Part 11, later signings in a continuous controlled session need at least one component only that person can execute. Under the draft Annex 11, relying on the login session is not acceptable, so a full re-authentication is expected.

What must appear on a signed record?

The printed name of the signer, the date and time, and the meaning, in screen and printed forms. The draft adds username, role where applicable and time zone where needed.

Does the 2003 FDA guidance relax the signature rules?

No, except for legacy systems operational before 20 August 1997 that meet the guidance’s conditions. It exercises discretion on validation, copies, retention and audit trails, but FDA still enforces the signature sections and the predicate rules. Discretion is not an exemption.

When a standard changes, know first

One email a month: edition changes, new deadlines, and what they mean for documentation you already have. No sales sequence.

We don’t spam! Read our privacy policy for more info.