21 CFR Part 11
21 CFR Part 11 is the FDA regulation that sets when electronic records and electronic signatures are treated as trustworthy and equivalent to paper and handwritten signatures. It applies to records kept under other FDA requirements (the predicate rules); FDA's 2003 guidance narrows how it enforces some Part 11 controls but keeps the predicate rules fully enforced.

On this page · 12 sections
- 1What Part 11 covers
- 2Controls for closed systems (11.10)
- 3Electronic signature requirements
- 4How FDA enforces it: the 2003 scope guidance
- 5Common failure modes and how to evaluate controls
- 6How the regulation is organised
- 7Working out which records are in scope
- 8Hybrid systems: paper signatures on electronic records
- 9What compliant signing looks like on screen
- 10Audit trails in day-to-day use
- 11Building a Part 11 programme
- 12Where V5 fits
How does 21 CFR Part 11 apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What Part 11 covers
Part 11 sets the criteria under which FDA considers electronic records, electronic signatures, and handwritten signatures executed to electronic records to be trustworthy, reliable and generally equivalent to paper (11.1(a)). It applies to electronic records created, modified, maintained, archived, retrieved or transmitted under any FDA records requirement, and to electronic records submitted to FDA under the FD&C Act and PHS Act (11.1(b)). It does not apply to paper records merely transmitted electronically.
Part 11 does not itself say which records you must keep. That comes from the predicate rule for your product, for example drug CGMP in Part 211. Part 11 governs how those records are trustworthy when kept electronically.
02Controls for closed systems (11.10)
| Clause | Control |
|---|---|
| 11.10(a) | Validation to ensure accuracy, reliability, consistent intended performance and the ability to discern invalid or altered records |
| 11.10(b) | Accurate and complete copies in human-readable and electronic form for FDA inspection |
| 11.10(c) | Protection so records can be accurately and readily retrieved throughout the retention period |
| 11.10(d) | Access limited to authorised individuals |
| 11.10(e) | Secure, computer-generated, time-stamped audit trails of entries and actions that create, modify or delete records; changes must not obscure earlier information; retained at least as long as the records |
| 11.10(f) | Operational system checks to enforce permitted sequencing of steps, as appropriate |
| 11.10(g) | Authority checks so only authorised individuals can use the system, sign, alter records or perform operations |
03Electronic signature requirements
- 11.50: signed records show the signer's printed name, date and time of signing, and the meaning (such as review, approval, responsibility or authorship), and these appear in any human-readable form.
- 11.70: signatures are linked to their records so they cannot be excised, copied or transferred to falsify a record by ordinary means.
- 11.100: each signature is unique to one person and never reused or reassigned; identity is verified before a signature is issued; organisations certify to FDA that their electronic signatures are intended as the legally binding equivalent of handwritten ones.
- 11.200: non-biometric signatures use at least two distinct components (such as ID and password); in one continuous session the first signing uses all components and later signings at least one; outside a continuous session every signing uses all components.
04How FDA enforces it: the 2003 scope guidance
FDA's Scope and Application guidance states that FDA intends to exercise enforcement discretion for the Part 11 requirements on validation, audit trails, record retention and record copying, as explained in the guidance, and for all Part 11 requirements on legacy systems operational before 20 August 1997. FDA says it will enforce all predicate rule requirements, including predicate rule recordkeeping.
05Common failure modes and how to evaluate controls
| Failure mode | How to evaluate |
|---|---|
| Shared or generic logins | Check user lists against people; confirm no account is used by more than one person (11.100(a), 11.10(d)). |
| Audit trail off, editable or not reviewed | Make a test change and confirm the original value, user and time are retained and cannot be altered. |
| Signature lacks meaning or time | Inspect printed and on-screen records for name, date/time and meaning (11.50). |
| Signature can be copied between records | Ask the supplier how signatures are bound to record content (11.70) and test it. |
| No certification letter to FDA | Confirm the 11.100(c) certification has been submitted. |
| Validation assumed from vendor | Confirm your own intended-use validation evidence exists; supplier documents can support but not replace it. |
06How the regulation is organised
Part 11 is short. Subpart A (11.1 to 11.3) sets the scope, implementation and definitions. Subpart B covers electronic records: controls for closed systems in 11.10, controls for open systems in 11.30, signature manifestations in 11.50 and signature/record linking in 11.70. Subpart C covers electronic signatures: general requirements in 11.100, signature components and controls in 11.200, and controls for identification codes and passwords in 11.300. Most practical questions about a manufacturing or quality system land in 11.10, 11.50, 11.70, 11.100 and 11.200.
Reading it in that order helps. First decide whether a record is in scope (11.1). Then decide which controls apply to the system that holds it (11.10 for closed systems, where access is controlled by the people responsible for the records). Only then look at signatures, because a signature requirement exists only where a predicate rule calls for a signature or the organisation chooses to sign electronically.
07Working out which records are in scope
Because Part 11 attaches to records required by other FDA regulations, the first job in any Part 11 programme is an inventory: which records does the predicate rule require, and which of those are created or kept electronically? The 2003 guidance explains that FDA interprets Part 11 narrowly and that records which happen to be produced on a computer but where paper is the record relied on for regulated activities are treated differently from records maintained electronically in place of paper. The guidance asks organisations to document, for example in an SOP, whether they rely on the electronic or the paper record.
| Example predicate rule | Typical records | Part 11 question |
|---|---|---|
| 21 CFR 211 (drug CGMP) | Master and batch production records, lab records, distribution records | Is the batch record kept and signed electronically? |
| 21 CFR 820 (device QMSR) | Records required by the quality management system regulation | Which records live only in the electronic system? |
| 21 CFR 111 (dietary supplements) | Master manufacturing and batch production records | Are approvals captured electronically? |
| 21 CFR 117 (human food) | Preventive control monitoring and verification records | Are monitoring entries recorded on tablets rather than paper? |
The table lists illustrative record types only; each predicate rule sets its own required contents and retention, and should be read directly for the products you make.
08Hybrid systems: paper signatures on electronic records
Many sites start with a hybrid: the record is created electronically, printed, and signed in ink. 11.1(b) still brings the electronic record into scope when it is the record maintained under a predicate rule, and 11.70 applies to handwritten signatures executed to electronic records just as it does to electronic signatures — the signature must be linked to its record so it cannot be removed, copied or transferred to falsify a record by ordinary means.
- Decide in writing which version is the official record: the printout or the electronic file.
- If ink signatures are applied to a printout of an electronic record, the procedure should explain how the printout is tied to the exact electronic version it represents.
- If the electronic file can still change after printing, the signed printout may no longer represent it; controls should prevent or detect that.
- Hybrids often double the work: paper handling plus the electronic controls. Moving signatures into the system is usually simpler once the 11.50, 11.70 and 11.200 controls are in place.
09What compliant signing looks like on screen
11.200(a) describes how a non-biometric signature is executed. Consider a QA reviewer who signs three batch records in a row without logging out. The first signature uses all components, typically the user ID and password. The next two, in the same continuous period of controlled access, may use at least one component that is executable only by that person and designed to be used only by them, often the password. If the reviewer leaves, the session ends, and later signs again, that next signature uses all components again.
Each of those signed records must then show the reviewer's printed name, the date and time of signing and the meaning of the signature, such as 'approved' (11.50(a)), and those items are subject to the same controls as the record and appear in any human-readable form, including printouts and on-screen views (11.50(b)).
Identity and uniqueness
Before issuing an electronic signature, the organisation verifies the person's identity (11.100(b)). The signature is unique to one individual and is not reused by, or reassigned to, anyone else (11.100(a)). In practice that means accounts are personal, leavers' accounts are disabled rather than handed on, and temporary staff get their own credentials.
10Audit trails in day-to-day use
11.10(e) requires audit trails that are secure, computer-generated and time-stamped, that independently record the date and time of operator entries and actions that create, modify or delete electronic records, and that do not obscure previously recorded information when records change. Audit trail documentation is retained at least as long as the subject records and is available for agency review and copying.
The regulation describes what the audit trail must capture; it does not by itself say how often it must be reviewed. Review frequency is normally set in the site's procedures, driven by the risk of the record and by predicate rule expectations — for example reviewing changes to critical batch entries as part of batch record review before release. A useful audit trail answers four questions for every change: who, when, what changed from what to what, and why.
11Building a Part 11 programme
- Inventory systems and the predicate-rule records each holds; record whether paper or electronic is relied on.
- Classify each system as closed or open and identify the applicable controls.
- Assess risk to product quality and record integrity, which the 2003 guidance recommends as the basis for decisions on validation, audit trails and copies.
- Configure access, roles and authority checks (11.10(d), (g)) and remove shared accounts.
- Confirm audit trails are on, protected and reviewed under a written procedure.
- Confirm signature manifestation and linking (11.50, 11.70) on screen and in printouts.
- Verify identities, issue unique credentials and submit the 11.100(c) certification.
- Validate the system for its intended use and keep that evidence with change control.
- Train users, and write the procedures that hold people accountable for actions under their signatures.
12Where V5 fits
V5 provides 21 CFR Part 11 e-signatures, an immutable audit trail and two-signature formula approvals, and Enterprise may include IQ/OQ documentation and validation support. Using these features does not make a site compliant: your procedures, user administration, FDA certification letter, PQ and validation for your intended use remain your responsibility.
Frequently asked questions
Q.Does Part 11 tell me which records to keep?+
No. Predicate rules such as 21 CFR 211 define which records are required. Part 11 sets how those records and signatures are trustworthy when electronic.
Q.Is Part 11 still enforced?+
Yes. FDA's 2003 guidance describes enforcement discretion for validation, audit trail, record retention and record copying requirements, and for legacy systems, but Part 11 remains in effect and predicate rules are fully enforced.
Q.What must an electronic signature show?+
The signer's printed name, the date and time of signing, and the meaning of the signature, in both electronic and printed forms of the record (11.50).
Q.Do I need to notify FDA before using electronic signatures?+
Under 11.100(c), you certify to FDA that your electronic signatures are intended to be the legally binding equivalent of handwritten signatures, using a handwritten-signed certification.
Q.Is Part 11 the same as EU Annex 11?+
No. They overlap in intent but are separate documents from different regulators; check each for the markets you supply.
Primary sources
Further reading
Explore this topic
21 CFR Part 11 sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
HCT/Ps, blood cGMP, donor eligibility, ISBT 128 labeling and forward-tracing lookback.
Want to see how 21 CFR Part 11 could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
