21 CFR Part 11 is intended to let FDA-regulated companies use electronic records and electronic signatures in place of paper, provided the system can prove the records are trustworthy, reliable, and equivalent to paper documentation. The regulation sets the criteria: validated systems, secure audit trails, controlled access, and signed records that can be attributed to a specific person. Part 11 does not require electronic records; it permits them, and it applies only to records the FDA's predicate rules already require you to keep.

What Part 11 Permits: Electronic Substitutes for Paper Records and Signatures

Part 11 answers a narrow question: when can an electronic record stand in for a paper record, and when does an electronic signature carry the same legal weight as a handwritten one? The FDA published the final rule in the Federal Register on March 20, 1997, and it took effect on August 20, 1997. The regulation lives in Title 21 of the Code of Federal Regulations, Parts 11.10 through 11.300.

The scope is defined by the predicate rule, not by Part 11 itself. If a regulation such as 21 CFR 211.100 requires a master production record, Part 11 governs how that record may be kept electronically. If no predicate rule requires a record, Part 11 does not reach it. This boundary trips up companies that build Part 11 compliance into systems holding records nobody asked them to keep.

Part 11 uses "predicate rule" to mean any FDA regulation that establishes record or signature requirements. Good Manufacturing Practice for drugs sits in 21 CFR Parts 210 and 211. Medical device quality systems sit in 21 CFR Part 820. Clinical trial records sit in 21 CFR Part 312. Each of those rules supplies the "what"; Part 11 supplies the "how" for the electronic version.

The FDA has issued relatively little binding sub-regulatory guidance on Part 11. The most cited is the August 2003 guidance "Part 11, Electronic Records; Electronic Signatures — Scope and Application," which narrowed enforcement to records submitted to the FDA and records used to satisfy predicate requirements. It also stated the agency's intent to exercise enforcement discretion for certain Part 11 provisions during a transition period, which is why Part 11 compliance today is often assessed through the lens of data integrity guidance rather than Part 11 alone.

The Core Controls: Validation, Audit Trails, Access, and Signature Attribution

Section 11.10 lists the controls a closed system must have if it creates, modifies, maintains, or transmits electronic records. The list is short but demanding. Each item addresses a way an electronic record could be unreliable or could be altered without detection. The FDA's own guidance and inspection practices treat these as the baseline, not aspirational goals.

Validation tops the list at 11.10(a). The system must be validated to ensure accuracy, reliability, consistent intended performance, and the ability to discern invalid or altered records. The phrase "ability to discern invalid or altered records" is the thread running through the rest of the section. A system that cannot distinguish an original entry from a later edit fails the intent of the regulation even if every other control is in place.

Section 11.10(e) requires secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify, or delete electronic records. The audit trail must be retained for at least as long as the underlying record, and it must be available for agency review and copying. A common inspection finding is an audit trail that exists but cannot be produced in a readable, complete form when requested.

Access control sits at 11.10(d) and 11.10(g): limit system access to authorized individuals and use authority checks to ensure only authorized persons can use the system, electronically sign a record, or alter a record. Section 11.10(h) adds device checks where appropriate to determine the validity of the source of data input. Sections 11.10(i) and 11.10(j) require documented training and written policies holding individuals accountable for actions taken under their electronic signatures.

Open Versus Closed Systems: Why the Boundary Changes Your Controls

Part 11 defines a closed system as one where record access is controlled by the people responsible for the content. An open system is one where that is not true. The distinction matters because open systems carry an extra requirement at 11.30: you must use procedures and controls, such as encryption and digital signature standards, to ensure authenticity, integrity, and confidentiality of the records from the point of creation to the point of receipt.

System type Definition under 11.3 Core controls Extra control
Closed Access controlled by record owners 11.10 controls apply None beyond 11.10
Open Access not controlled by record owners 11.10 controls apply where relevant 11.30 procedures for authenticity, integrity, confidentiality
Hybrid (paper and electronic) Both formats in the same workflow Part 11 applies to the electronic portion Reconciliation procedures between formats

A vendor-hosted clinical trial platform accessed by investigators, sponsors, and the FDA is a classic open-system scenario. Encryption and digital signature verification become part of the compliance case. An on-premise manufacturing execution system behind a controlled network is closer to a closed system, though remote maintenance access can pull it toward open.

Most real deployments are hybrid. Batch records are partly electronic and partly paper, or signatures are captured electronically while a paper attachment carries supplementary data. Part 11 does not prohibit hybrid workflows, but the reconciliation between formats becomes an inspector's focus. If the paper and electronic portions disagree, the audit trail must explain why.

Electronic Signatures: What 11.100, 11.200, and 11.300 Actually Require

Electronic signatures under Part 11 come in two flavors. Section 11.200(a)(1) covers signatures executed with at least two distinct components, such as an identification code and a password. Section 11.200(a)(2) covers signatures executed with a biometric or other non-repeating method that can only be used by the genuine owner. The two-component type is the dominant practice because it is cheaper to deploy and easier to reissue.

The signature must include the printed name of the signer, the date and time of execution, and the meaning of the signature, such as review, approval, responsibility, or authorship. Section 11.50 requires that signed electronic records carry this information associated with the signature. A signature that records only a username and timestamp without the meaning of the signature is incomplete.

Section 11.300 adds controls for identification codes and passwords: uniqueness, periodic checks and recalls, loss management procedures, and safeguards against unauthorized use. It also prohibits sharing identification codes and passwords. An inspection that finds a shared login on a validated system has found a Part 11 failure, regardless of how clean the audit trail looks.

Section 11.100 requires that electronic signatures be unique to one individual and not reused or reassigned. It also requires verification of the person's identity before the signature is established, and it requires that anyone using an electronic signature certify to the FDA that the signature is intended to be the legally binding equivalent of a handwritten signature. The certification requirement is often overlooked; a company can hold the certification internally and produce it on request.

Section 11.10(k) requires controls over the distribution of, access to, and use of documentation for system operation and maintenance. The documentation must be current. A validated system whose SOPs describe a previous version of the software is not compliant in operation even if the software itself was validated at release.

Where Part 11 Stops: Records It Does Not Cover and the 2003 Enforcement Shift

Part 11 is about records and signatures, not about every electronic artifact a company produces. Emails, meeting notes, and internal reports that no predicate rule requires fall outside its scope. The FDA's 2003 guidance made this explicit and also announced a policy of enforcement discretion during a transition period for certain provisions, which companies sometimes read as a rollback. The agency did not withdraw Part 11; it narrowed the enforcement focus toward records that support regulatory decisions.

The shift moved much of the practical compliance conversation toward data integrity. The FDA's 2018 guidance "Data Integrity and Compliance With Drug CGMP: Questions and Answers" is the most direct expression of current thinking. It addresses audit trail review, shared logins, and the practice of deleting or overwriting data, which are Part 11 concerns in substance even where the guidance does not cite Part 11 by section.

A regulatory boundary worth stating plainly: Part 11 is a records and signatures rule, not a product safety rule. A Part 11 failure does not by itself make a product unsafe, and compliance does not guarantee quality. The FDA's inspection observations during the 2010s frequently cited 21 CFR 211.68 for back-up procedures alongside Part 11 concerns, which suggests inspectors treat the electronic record controls as part of the broader CGMP picture.

For legal and regulatory strategy, this is not legal advice and should not be treated as a legal opinion. The applicability of Part 11 to a specific record depends on the predicate rule, the record's role in a regulatory submission, and the agency's current enforcement posture, and a qualified regulatory professional should review your specific case.

A Worked Compliance Sequence: Steps From Scope to Signature

Teams that start with the software usually end with a rework. The sequence below moves from the predicate rule outward, which is how a defensible Part 11 case is built. Each step produces a document that an inspector can review.

1: List the records the predicate rule requires you to keep, and mark which will be electronic. Name each predicate citation next to the record. 2: Determine whether each electronic system is closed or open under 11.3, and note any hybrid workflows that need reconciliation procedures. 3: Validate the system for its intended use under 11.10(a), including the ability to detect invalid or altered records. 4: Configure access controls, authority checks, and device checks under 11.10(d), (g), and (h), with named owners for each role. 5: Enable and test the audit trail under 11.10(e), and confirm it can be produced in readable form for the full retention period. 6: Implement signature controls under 11.200 and 11.300, including uniqueness, non-reuse, and periodic credential checks. 7: Train users under 11.10(i), and write the accountability policy under 11.10(j) so the signature's legal weight is stated. 8: Document the system under 11.10(k), including current SOPs, version records, and change control. 9: Establish the open-system procedures under 11.30 if applicable, and the electronic signature certification under 11.100 if signatures are used. 10: Review the audit trail on a defined cadence and retain the review evidence for inspection.

Failure handling matters as much as the sequence. If step 5 reveals an audit trail that cannot be produced, the fix is not to disable it; it is to remediate, document the gap, and assess whether any records were affected. A remediation that deletes the evidence of the defect is itself a finding.

Common Failure Cases and How Inspections Find Them

The FDA has cited Part 11-adjacent failures repeatedly in warning letters and Form 483 observations, usually in language that ties the failure to a predicate rule. The patterns below are drawn from public enforcement documents and from the data integrity guidance the agency published in 2018.

A shared login is the most common. Two operators use one account, so the audit trail attributes every entry to a single user. The finding is not just an access control issue under 11.10(g); it invalidates the signature attribution under 11.200 when the shared account is used to sign. Remediation requires re-credentialing, retrospective review of which records were touched under the shared account, and a documented assessment of affected batches or submissions.

A disabled audit trail is the second pattern. Systems shipped with audit trails off because the feature costs storage or slows transactions, and the site never enabled it. Regulators treat this as a deliberate limitation of the record's traceability. The FDA's 2018 data integrity guidance specifically addresses audit trail review expectations and rejects the argument that review is too burdensome.

An incomplete or non-reviewable audit trail is the third. The trail exists but is in a proprietary format, or review is not documented, or the retention period is shorter than the underlying record's. Section 11.10(e) requires availability for agency review and copying, which an unreadable export fails.

A fourth pattern is signature meaning omitted. The signature record shows who and when but not what the signature meant. Section 11.50 requires the meaning, and inspectors look for it in the signature manifest. Fixing it after the fact requires retrospective documentation, which is far costlier than capturing it correctly.

Vendor Systems, Cloud Hosting, and the Responsibility Question

Part 11 does not run with the software vendor. The regulated entity remains responsible for the record, even when the system is hosted by a third party. That principle is stated plainly in the FDA's 2003 guidance and reinforced in inspection practice. A vendor's "Part 11 compliant" marketing claim is not a substitute for your own validation and controls assessment.

Cloud hosting changes the technical controls but not the legal allocation. If the vendor manages the audit trail and access controls, the regulated entity still needs to verify that the trail meets 11.10(e), that access is restricted under 11.10(d), and that the record can be produced on demand. Vendor audits, service-level agreements that name the audit trail retention period, and contractual rights to export the audit trail are the practical instruments that make this verifiable.

A practical test: request the audit trail export for a single record, in a readable format, without a support ticket, and see whether it arrives within a timeframe that satisfies your retention and review procedures. If it does not, the controls exist on paper but not in operation. That is a failure case worth catching before an inspection does.

A second practical test concerns vendor mergers and migrations. When a hosting vendor changes ownership or moves platforms, the retention of audit trails and signatures across the migration is a Part 11 question the vendor contract should already answer. Many do not.

How Part 11 Relates to EU Annex 11 and Other Analogues

Companies often compare Part 11 with the EU's Annex 11 to GMP, which covers computerized systems in scope of EU GMP. The two are close in intent but differ in structure. Annex 11 is broader in scope, addressing supplier assessment, data flow, and periodic evaluation, and it cites risk management more directly. Part 11 is narrower, tied to FDA predicate rules, and anchored in specific sections.

Dimension US 21 CFR Part 11 EU GMP Annex 11
Legal basis Federal regulation with predicate rule scope Annex to EU GMP directive
Scope trigger FDA predicate rule record requirements Computerized systems in GMP scope
Risk management Implicit in validation and controls Explicit, cited in the annex
Data integrity guidance 2018 FDA Q&A guidance EU data integrity guidance and PIC/S PI 041
Signature framework Sections 11.50, 11.100, 11.200, 11.300 Annex 11 clauses on electronic signatures

A system built to Annex 11 usually meets Part 11 in substance, but the documentation set differs. Annex 11 asks for a supplier assessment that Part 11 does not name, and Part 11 asks for a signature certification under 11.100 that Annex 11 does not. Companies operating in both jurisdictions should map each Part 11 section to its Annex 11 counterpart rather than treating one as a stand-in for the other.

Japan's ERES guidance (issued by the Ministry of Health, Labour and Welfare) and PIC/S PI 041 add a third and fourth reference point. A multi-region compliance file is common at large manufacturers, but the specific controls rarely conflict; the obligations accumulate.

FAQ

Does Part 11 apply to paper records?

No. Part 11 governs electronic records and electronic signatures only. If a record is kept on paper, Part 11's controls do not apply, though the predicate rule's requirements for that paper record still do. Hybrid workflows are permitted, and the electronic portion of a hybrid record falls under Part 11 while the paper portion does not.

Is a vendor's "Part 11 compliant" claim enough?

No. The regulated entity remains responsible for the record even when a vendor hosts the system. Compliance requires your own validation, controls assessment, and vendor oversight. Ask the vendor for the specific controls it provides, the audit trail retention period, and the export format, then verify them in operation.

Can an electronic signature be reassigned to a new employee?

No, section 11.100 requires signatures to be unique to one individual and prohibits reuse or reassignment. When an employee leaves, the account should be deactivated and a new credential issued to the replacement. Inspectors look for evidence that old accounts were not reused or left active.

What happens if the audit trail was never enabled?

That is a failure under section 11.10(e), and it can affect every record created on the system. Remediation requires enabling the trail, documenting the gap, and assessing whether any records or batches were affected. The assessment is reviewed at inspection, and a remediation that destroys evidence of the defect makes the finding worse.

Does Part 11 require a specific software product?

No. Part 11 sets criteria rather than naming products, and the FDA does not certify software as Part 11 compliant. Any system that meets the applicable sections for its intended use can support compliance. The validation file, not a product label, is the evidence an inspector reviews.

How long must audit trails be retained?

At least as long as the underlying record, under section 11.10(e). The predicate rule sets the record retention period, and the audit trail follows it. A trail that is deleted when the record is archived fails the retention requirement even if the record itself is kept.

Can an electronic signature be a scanned handwritten signature?

Generally no for Part 11 purposes. A scanned image of a handwritten signature is not unique to one individual in the way section 11.100 requires, and it can be copied. Part 11 signatures use either two distinct components such as an identification code plus password, or a biometric method that can only be used by the genuine owner.

Does Part 11 cover email and chat records?

Not unless a predicate rule requires those communications to be kept. Emails and chat logs that support a regulatory decision can be relevant as evidence, but the record requirement comes from the predicate rule, not from Part 11. The 2003 FDA guidance made this scope limit explicit.

This article is general educational information about FDA recordkeeping and electronic signature regulation. It is not a legal opinion, a compliance certification, or a substitute for advice from a qualified regulatory or legal professional familiar with your specific products, systems, and jurisdictions. Regulatory requirements and agency enforcement practices change, so confirm current expectations with the FDA and applicable authorities in your region before relying on any statement here. If you are facing an immediate safety or compliance emergency, contact your local regulatory counsel or emergency services.