21 CFR Part 11 is the FDA regulation that sets the conditions under which electronic records and electronic signatures are treated as trustworthy, reliable and generally equivalent to paper records and handwritten signatures. It applies to any record that an FDA regulation requires you to keep, once you keep it electronically, and to records you submit to the FDA in electronic form. It has been in effect since 20 August 1997.
This guide goes through the regulation section by section, explains which parts the FDA actively enforces today, and shows what a compliant system looks like in practice, including the failure modes inspectors find most often.
What 21 CFR Part 11 covers
Part 11 applies to electronic records that are created, modified, maintained, archived, retrieved, or transmitted under FDA GxP requirements, including 21 CFR Parts 210, 211 (GMP), 820 (device QSR), and GCP regulations. If a regulation requires a record, and you keep that record electronically, Part 11 applies. The regulation has two main components: requirements for the electronic records themselves (Subpart B) and requirements for electronic signatures applied to those records (Subpart C). Predicate rule records kept only on paper, or hybrid systems where electronic records are printed and signed on paper, still exist but carry their own compliance burden.
A critical point the FDA has repeatedly clarified: Part 11 does not require organisations to use electronic signatures or electronic records. It sets the standards those systems must meet if you choose to use them. Many organisations still use paper in certain contexts because the validation and compliance burden of a Part 11-compliant electronic system outweighs the benefit for that record type.
21 CFR Part 11 section by section
Part 11 is short. It has three subparts and ten sections, and most compliance questions come back to one of them. The summaries below follow the current text in the eCFR. To check one system against them, run the free 21 CFR Part 11 checklist.
| Section | Title | What it requires |
|---|---|---|
| 11.1 | Scope | Sets the criteria for electronic records and signatures to be treated as equivalent to paper. Covers records kept under any FDA records requirement and records submitted to the FDA, but not paper records that were only transmitted electronically. |
| 11.2 | Implementation | Allows electronic records and signatures in place of paper where the requirements of Part 11 are met. |
| 11.3 | Definitions | Defines terms such as closed system, open system, electronic record, electronic signature, digital signature and biometrics. |
| 11.10 | Controls for closed systems | Eleven controls, (a) to (k): validation; accurate and complete copies for inspection; protection and ready retrieval of records for the retention period; limited access; secure, computer-generated, time-stamped audit trails that do not obscure earlier entries; operational system checks; authority checks; device checks; training and experience of the people involved; written policies holding individuals accountable for their electronic signatures; and controls over system documentation, including change control. |
| 11.30 | Controls for open systems | The 11.10 controls as appropriate, plus measures such as document encryption and digital signature standards to protect records from creation to receipt. |
| 11.50 | Signature manifestations | A signed record must show the printed name of the signer, the date and time of signing, and the meaning of the signature (such as review, approval, responsibility or authorship), including on any printout or display. |
| 11.70 | Signature/record linking | Signatures must be linked to their records so they cannot be excised, copied or transferred to falsify another record by ordinary means. |
| 11.100 | General requirements | Each electronic signature is unique to one person and never reused or reassigned. Identity is verified before a signature is issued, and the organisation certifies to the FDA that its electronic signatures are the legally binding equivalent of handwritten ones. |
| 11.200 | Electronic signature components and controls | Non-biometric signatures use at least two components, such as an ID and a password. The first signing in a session uses all components and later signings in the same continuous session at least one. Signatures may be used only by their owners. |
| 11.300 | Controls for identification codes and passwords | Unique ID and password combinations, periodic checking or revision (for example password ageing), procedures for lost or compromised tokens, safeguards that detect and report attempted misuse, and periodic testing of tokens and cards. |
What the FDA enforces today
Since August 2003 the FDA has applied its guidance Part 11, Electronic Records; Electronic Signatures: Scope and Application. In it the agency says it interprets the scope of Part 11 narrowly and exercises enforcement discretion over four requirements: validation, audit trails, record retention and record copying. The same guidance says the agency does not intend to enforce Part 11 for legacy systems that were operational before 20 August 1997, under the circumstances it describes.
That discretion is narrower than it sounds. The guidance states that records must still meet the underlying predicate rules (21 CFR 211 for drug GMP, for example, or 820 for devices), and that the FDA intends to enforce the other controls: limiting system access, operational system checks, authority checks, device checks, training, written accountability policies, controls over systems documentation, open-system controls and the electronic signature requirements. In practice predicate rules such as 211.68 and 211.194 still require validated systems and complete, retrievable records, so a system without an audit trail or validation evidence is still a finding. Treat the 2003 guidance as describing how the FDA reads Part 11, not as permission to skip those controls.
The core controls for electronic records
- System validation. Any system that creates or manages Part 11 records must be validated under GAMP 5 or equivalent, documented evidence that it consistently does what it is intended to do. See Cybroscape GxP Copilot for the validation package.
- Audit trail. The system must generate a computer-generated, time-stamped audit trail that records the date and time of operator entries and actions that create, modify, or delete electronic records. The audit trail must be available for review and must not be modifiable by the user whose actions are being recorded.
- Access controls. System access must be limited to authorised individuals. User IDs must be unique. Shared logins are a direct Part 11 violation. Access logs must be maintained.
- Operational system checks. The system must enforce the sequencing of steps and events where required, for example, preventing a document from moving to Approved status unless all required review steps have been completed.
- Authority checks. The system must ensure that only authorised individuals can use the system, electronically sign a record, access the operation, or enter or modify a record.
- Device checks. Where appropriate, the system must check the validity of data sources, for example, the source of a computer terminal or scanner.
- Training. Personnel using Part 11 systems must be trained, and that training must be documented in the personnel training records.
What a compliant audit trail looks like
The audit trail requirement is the most commonly inspected Part 11 control and the one most organisations fail to implement correctly. A compliant audit trail captures: who took the action (unique user identifier, not a shared login), what the action was (creation, modification, deletion, retrieval, signature), when it happened (timestamp in a controlled time zone, not client-local time), and what changed (for modifications, the old value and the new value). The audit trail must be computer-generated, not a manually maintained log, and must be retained for at least as long as the records it documents.
Common failures: audit trails stored in the same table as the records they document (making them deletable alongside the records); audit trails that only log who approved a document, not who edited it; timestamps from client browsers rather than the server; and no integrity check to detect whether audit trail entries have been modified after the fact. Audit Readiness in GxP Copilot uses a tamper-evident, append-only structure with a hash-chain integrity check that flags any retrospective modification.
What compliant electronic signatures require
Part 11 Subpart C governs electronic signatures. The requirements are specific and non-negotiable. Each electronic signature must be unique to one individual and must not be reused by or reassigned to anyone else. Organisations must verify the identity of each individual before assigning them an electronic signature. Signatures applied to records must contain the signer's printed name, the date and time when the signature was executed, and the meaning of the signature (for example: reviewed, approved, witnessed).
The re-authentication requirement catches many systems off guard. When a person signs for the first time in a session, Part 11 requires re-authentication, the signer must re-enter their password or equivalent credentials, not simply click an "I approve" button. Where two or more signatures are applied, only the first requires a re-authentication; subsequent signatures in the same session can use one component (typically the ID or password, but not both). The signature must be linked to the specific record being signed such that it cannot be transferred to another record.
GxP Copilot enforces all of these at the data layer: re-authentication is required at signing, the ceremony records name, timestamp, and meaning, the signature is cryptographically bound to the document version being signed, and authors cannot approve their own drafts. See 21 CFR Part 11 for the full Part 11 feature detail.
What Part 11 looks like in a validated GxP system
In practice, a Part 11-compliant system presents several visible and invisible controls. Visibly: every record shows a version history with timestamps and user identifiers; the approval workflow enforces role separation (author, reviewer, approver are distinct); signing requires a password prompt with a meaning field; and signed versions display the signature block with name, date/time, and meaning. Invisibly: the underlying records are immutable once signed, no silent edits are possible; the audit trail is stored separately from the record and verified on read; and access is governed by role-based permissions with unique, non-shared credentials for every user.
What it does not look like: a checkbox labelled "I approve" that requires no re-authentication; a signature block added to a PDF as a text annotation; an admin account shared across the QA team; a database where records and audit logs are in the same table and can be deleted together; or a system where the audit trail only activates in "GxP mode" and can be switched off.
The ten Part 11 failure modes inspectors find most often
- Shared user accounts. Multiple people using a single login defeats the uniqueness requirement for electronic signatures.
- No re-authentication at signing. Clicking "approve" without re-entering credentials is not a Part 11-compliant signature.
- Mutable audit trails. If a database administrator can delete or overwrite audit trail entries, the trail is not tamper-evident.
- Audit trail not capturing old values. Recording that a field changed but not what it changed from leaves investigators unable to reconstruct history.
- Client-side timestamps. Timestamps generated by the user's browser or local PC can be manipulated. The server must set the authoritative time.
- No integrity check. Without a hash or checksum, modified records cannot be detected.
- Author self-approval. The same person who drafted a document approving it violates the operational system check requirement for segregation of duties.
- Inactive accounts not disabled. Departed employees whose accounts remain active represent an access control failure.
- Signed versions editable. Any system that permits editing a record after it has been electronically signed without creating a new version under change control is non-compliant.
- Audit trail not human-readable. If an auditor cannot read the audit trail without assistance from IT, it fails the intended purpose.
EU Annex 11 and how it compares to Part 11
EU GMP Annex 11 is the European equivalent of 21 CFR Part 11 and covers the same core topics: validation, audit trails, access control, electronic signatures, change management, data backup, and disaster recovery. Annex 11 is generally considered more prescriptive in some areas, it explicitly requires a documented system inventory, a formal risk assessment before validation, and clear procedures for data migration. The upcoming Annex 11 revision is expected to align more closely with FDA's risk-based CSA approach and to incorporate provisions from EU GMP Annex 22 on AI in GMP. Organisations operating in both US and EU markets should build their electronic records posture to satisfy the stricter requirement on each point rather than maintaining two separate compliance postures. Annex 11 / 22 covers both Annex 11 and Annex 22 in GxP Copilot.
Getting to Part 11 compliance without a remediation project
The fastest path to Part 11 compliance is to start in a system that is architected for it, where the audit trail is structural, re-authentication is enforced by the workflow, segregation of duties is a configuration not a policy, and signed versions are frozen at the data layer. Cybroscape GxP Copilot is built this way. Teams that start validation in GxP Copilot are Part 11 compliant from the first sign-off cycle without a separate remediation project. Teams inheriting legacy systems that have Part 11 gaps typically need a gap assessment, a remediation plan under change control, and re-validation of affected records. audit readiness services cover both scenarios.
Where to go next
Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.