What is 21 CFR Part 11?

21 CFR Part 11 is the U.S. Food and Drug Administration regulation that sets the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records and handwritten signatures. It covers records that other FDA regulations require organizations to create, keep, or submit.

Also known as Part 11 · FDA Electronic Records; Electronic Signatures rule

Who Part 11 applies to

Part 11 was published in March 1997 and took effect that August. It applies to any organization that keeps FDA-required records in electronic form or submits them to FDA electronically: drug, biologic, and medical device manufacturers, clinical trial sponsors, nonclinical (GLP) laboratories, and the contract research and manufacturing organizations that work for them.

Part 11 doesn't create new record-keeping obligations on its own. It attaches to the predicate rules — the underlying regulations that say which records must exist. Common examples include the drug current good manufacturing practice regulations (21 CFR Parts 210 and 211), good laboratory practice for nonclinical studies (21 CFR Part 58), and the medical device quality system regulation (21 CFR Part 820). If a predicate rule requires a record and you keep it electronically, Part 11 applies to it. The regulation also states that it does not apply to paper records that are merely transmitted by electronic means.

Because those predicate rules span research, manufacturing, and quality, Part 11 sits underneath most of the GxP landscape.

How the regulation is organized

Part 11 is short — three subparts and ten sections:

SubpartSectionsWhat they cover
A — General provisions11.1 – 11.3Scope, how the rule is implemented, and definitions (including closed vs. open systems)
B — Electronic records11.10, 11.30, 11.50, 11.70Controls for closed and open systems, how signatures appear on records, and how signatures are linked to records
C — Electronic signatures11.100, 11.200, 11.300General requirements, signature components and controls, and controls for ID codes and passwords

Key requirements

Controls for closed systems (§11.10)

Most regulated systems are "closed": access is controlled by the people responsible for the records. For these, §11.10 requires procedures and controls that include:

  • Validation to ensure accuracy, reliability, consistent intended performance, and the ability to detect invalid or altered records.
  • Accurate and complete copies in human-readable and electronic form for FDA inspection and review.
  • Record protection so records can be retrieved accurately throughout their retention period.
  • Limited system access to authorized individuals, with authority checks governing who can sign, alter, or use the system.
  • Audit trails that are secure, computer-generated, and time-stamped, independently recording when operators create, modify, or delete records. Changes must not obscure what was recorded before, and the audit trail must be kept at least as long as the record itself.
  • Operational system checks that enforce the permitted sequence of steps, and device checks that confirm the validity of data and instruction sources.
  • Qualified people: those who build, maintain, or use the system need the education, training, and experience for their tasks.
  • Written accountability policies that hold individuals responsible for actions taken under their electronic signatures, and control of system documentation.

Open systems (§11.30) need the same controls plus additional measures, such as encryption and digital signature standards, to ensure authenticity and confidentiality.

Electronic signatures (§11.50 – §11.300)

  • A signed record must show the signer's printed name, the date and time of signing, and the meaning of the signature, such as review, approval, responsibility, or authorship (§11.50).
  • Signatures must be linked to their records so they can't be cut, copied, or transferred to falsify another record (§11.70).
  • Each electronic signature must be unique to one person and never reused or reassigned, and the organization must verify the person's identity before issuing it. Organizations must also certify to FDA that their electronic signatures are intended to be the legally binding equivalent of handwritten signatures (§11.100).
  • Non-biometric signatures need at least two distinct components, such as an ID code and a password. Within one continuous session, the first signing uses all components and later signings can use at least one (§11.200).
  • ID codes and passwords need controls for uniqueness, periodic review, loss management, and detection of unauthorized use (§11.300).

FDA's narrower reading: the 2003 scope and application guidance

Early interpretations of Part 11 were broad enough to slow the adoption of electronic systems. In 2003 FDA issued guidance, Part 11, Electronic Records; Electronic Signatures — Scope and Application, that narrowed how the agency reads the rule. Under that guidance, Part 11 applies to records that predicate rules require and that are kept electronically instead of on paper, or kept electronically alongside paper and relied on to perform regulated activities.

FDA also said it would exercise enforcement discretion over certain specific requirements — validation, audit trails, record retention, and record copying — and over legacy systems that were in operation before Part 11 took effect, while it re-examined the rule. That discretion was never a free pass: the predicate rules still apply in full, FDA still expects a documented, risk-based justification for the controls you choose, and the agency continues to enforce Part 11's other provisions, such as access limits and electronic signature controls.

Part 11 and data integrity

Part 11 provides much of the technical backbone for data integrity. Unique logins and signatures make data attributable; time-stamped audit trails make it contemporaneous and traceable; validation and record protection keep it accurate and enduring. Those are the ALCOA+ principles that FDA's data integrity guidance and other regulators' guidance build on.

The failures that show up in inspection findings and warning letters are usually practical rather than exotic:

  • Shared or generic logins that make it impossible to tell who did what.
  • Audit trails that are disabled, can be edited, or are never reviewed.
  • Users with permissions to delete data or change system clocks.
  • Results recorded on scrap paper or uncontrolled spreadsheets, then transcribed.
  • Aborted or repeated runs that are not documented, which can hide "testing into compliance."

Each of those also tends to surface later as a deviation that is hard to investigate, because the evidence to reconstruct what happened was never captured.

A practical readiness checklist

This isn't legal or regulatory advice, but these are the questions quality and IT teams typically work through for each system that holds GxP records:

  • Have you identified which records in the system are required by a predicate rule, and documented that assessment?
  • Is the system validated for its intended use, with a risk-based rationale for the depth of testing?
  • Does every user have a unique account, with roles that separate who can enter, review, approve, and administer?
  • Are audit trails on, protected from modification, and reviewed as part of record review?
  • Can you produce complete, accurate copies of records and their audit trails for an inspector?
  • Are electronic signatures manifested with name, date and time, and meaning, and linked to their records?
  • Has your organization submitted its electronic signature certification to FDA?
  • Are backup, retention, and retrieval tested for the full retention period, including after system upgrades or retirement?

Where execution data fits

Part 11 governs records, but a great deal of hands-on lab and manufacturing work still reaches the record secondhand: an analyst performs a step, then writes it down or types it in later. That transcription gap is where contemporaneity and attribution break down.

Systems built for execution observability narrow the gap by capturing step-level events — who did what, when, with which materials and instruments — as the work happens, so the record is generated by the work itself. QURE Science is designed for this, with governed capture from instruments and operator actions and integration with ELN and LIMS systems.

One point is worth stating plainly: no software is "Part 11 certified." FDA does not certify products. Compliance comes from how a regulated company validates, configures, and controls a system in use. Vendors can supply technical controls and validation support, but the responsibility stays with the organization that owns the records.

Frequently asked questions

Is there such a thing as Part 11 certified software?

No. FDA does not certify or approve software for Part 11. A system can provide the technical controls Part 11 calls for — audit trails, access control, electronic signature features — but compliance depends on how the regulated organization validates, configures, and governs that system in its own environment.

Does Part 11 apply to every electronic record?

No. It applies to records that FDA's predicate rules require you to create or keep, when they are maintained electronically or submitted to FDA electronically. Under FDA's 2003 scope and application guidance, it also applies when you keep paper records but rely on the electronic version to perform regulated activities.

How long must Part 11 audit trails be kept?

At least as long as the electronic records they describe, and they must be available for FDA to review and copy. The retention period for the records themselves is set by the applicable predicate rule.

What is the difference between 21 CFR Part 11 and EU GMP Annex 11?

Part 11 is a U.S. regulation focused on electronic records and signatures across FDA-regulated activities. Annex 11 is part of the EU's GMP guidelines and covers computerised systems used in GMP more broadly, including risk management, supplier oversight, and lifecycle validation. Companies that serve both markets usually design one set of controls that satisfies both.

Do electronic signatures need to be registered with FDA?

Organizations must send FDA a certification, before or at the time electronic signatures are put into use, stating that the electronic signatures used in their systems are intended to be the legally binding equivalent of handwritten signatures. Individual signatures are not registered with FDA one by one.

Sources

  1. 21 CFR Part 11 — Electronic Records; Electronic Signatures (eCFR)
  2. FDA guidance: Part 11, Electronic Records; Electronic Signatures — Scope and Application (2003)
  3. FDA guidance: Data Integrity and Compliance With Drug CGMP — Questions and Answers (2018)
Keep exploring

Related terms: ALCOA+, GxP, Deviation management, Execution observability. Browse the full glossary, read field notes in the QURE Journal, or request a demo to see execution intelligence on your own procedures.