The 21 CFR Part 11 requirements run from section 11.1 to section 11.300, and the first question to settle is whether Part 11 applies to a given record at all. This guide answers that first, then walks every section in plain English. The regulation took effect on 20 August 1997 and is in force today. You can read the current text on the eCFR page for Part 11.
Two sources matter. The regulation says what must be true. FDA’s August 2003 guidance, Part 11, Electronic Records; Electronic Signatures, Scope and Application, says where FDA will and will not enforce. They are not the same thing.
How the 21 CFR Part 11 requirements are organized
Subpart A covers scope, implementation and definitions (11.1 to 11.3). Subpart B covers electronic records: closed system controls (11.10), open system controls (11.30), signature manifestations (11.50) and signature/record linking (11.70). Subpart C covers electronic signatures (11.100, 11.200, 11.300). Sections 11.50 and 11.70 are about signatures but sit in Subpart B because they describe what the signed record must carry.
Scope and predicate rules: when the 21 CFR Part 11 requirements apply
Section 11.1 sets the ground rules. It reaches any record in electronic form that an FDA regulation requires you to keep, and electronic records submitted to the agency. A paper record that was merely faxed or otherwise sent electronically is outside it.
Two other points in Subpart A are easy to miss:
- 11.1(e) makes your systems, controls and their documentation available to FDA inspectors.
- 11.1(f) to (p) carve out records kept under several other rules, such as parts 117, 507, 112 and 121 and certain subparts of Part 1, plus signatures obtained under two food labeling provisions. For most of these carve-outs, a record that is also required under another rule stays in scope.
Section 11.2 lets you go electronic in whole or in part. For records you submit, the submission type must also be one the agency has said it accepts electronically.
Predicate rules
Part 11 does not say which records you must keep. The underlying rules do: for example the drug CGMP regulations in Part 211, the device regulations in Part 820 and the good laboratory practice rules in Part 58. FDA’s 2003 guidance calls these the predicate rules.
The 2003 guidance also states FDA’s narrow reading of scope. Part 11 applies to:
- predicate-rule records kept electronically instead of paper;
- predicate-rule records kept electronically in addition to paper and relied on for regulated work;
- electronic records submitted to FDA in a form the agency accepts; and
- electronic signatures meant to be the equivalent of signatures a predicate rule requires.
If the paper printout meets the predicate rule and you rely on it, the computer that made it generally does not trigger Part 11. If you print but keep working from the electronic version, FDA may treat the electronic record as the real one. Decide per record which form you rely on, and write it down. A record inventory kept against the predicate rules is where that decision lives.
Closed vs open systems under the 21 CFR Part 11 requirements
Section 11.3 draws the line that decides which controls apply to your system.
| Closed system | Open system |
|---|---|
| Access is controlled by the people responsible for the content of the records on it. | Access is not controlled by the people responsible for the content of the records. |
| Controls in 11.10 apply. | Section 11.30 applies: the 11.10 controls as appropriate, plus measures such as document encryption and appropriate digital signature standards. |
Hosted and cloud services are where the closed-or-open question needs the most care. The test is who controls access to the records, not where the servers sit. Document your reasoning either way.
Section 11.3 also defines an electronic signature as a symbol or series of symbols adopted as the legally binding equivalent of a handwritten signature. A digital signature is a narrower kind, based on cryptography.
11.10(a) to (k): the closed-system controls
The lead-in to 11.10 asks for procedures and controls that protect authenticity, integrity and, when appropriate, confidentiality, and that stop a signer easily denying a signed record. The controls follow, with FDA’s 2003 stance in the last column.
| Section | What it asks for | 2003 guidance |
|---|---|---|
| (a) | Validation proving the system is accurate, reliable and performs as intended, and can spot invalid or altered records | Enforcement discretion |
| (b) | Accurate, complete copies, readable and electronic, for FDA | Enforcement discretion |
| (c) | Records protected and retrievable for the whole retention period | Enforcement discretion |
| (d) | System access limited to authorized individuals | Enforced |
| (e) | Secure, computer-generated, time-stamped audit trails | Enforcement discretion |
| (f) | System checks that force steps to happen in the permitted order, where appropriate | Enforced |
| (g) | Authority checks on who may use the system, sign, alter records or perform each operation | Enforced |
| (h) | Device checks that confirm data or instructions come from a valid source, where appropriate | Enforced |
| (i) | Education, training and experience of people who build, maintain or use the system | Enforced |
| (j) | Written policies holding people accountable for actions under their signatures | Enforced |
| (k)(1) | Controls over who gets and uses system operation and maintenance documents | Enforced |
| (k)(2) | Change control and a time-sequenced audit trail for system documents | Enforcement discretion |
A few of these hide more than the one-line summary shows.
- (a) Validation is the one most teams fixate on. How much to do depends on risk. See validation master plan for how to set that scope and IQ OQ PQ for what the testing proves. Keep requirements tied to tests, as covered in requirements traceability matrix.
- (e) Audit trails have four parts: secure and computer-generated; a record of who did what and when for create, modify and delete actions; changes that do not hide earlier values; and retention at least as long as the record, available to FDA. Audit trail review covers how to use them.
- (k) Documentation controls are two separate duties: who may see and use system documents, and change control over them.
- (d), (g) and (h) sound alike. (d) limits who gets in, (g) limits what each person can do once in, and (h) checks where data comes from.
The data integrity attributes behind these controls are in ALCOA+.
Electronic signature controls: 11.50 to 11.300
- 11.50 manifestations. A signed record must show the signer’s printed name, the date and time of signing, and the meaning, such as review or approval. These items are controlled like the record and appear in every human-readable form, on screen and in print.
- 11.70 linking. Signatures must be tied to their records so they cannot be excised, copied or moved to falsify a record by ordinary means. This covers handwritten signatures executed to electronic records too.
- 11.100 general. Each signature is unique to one person and never reassigned. Verify identity before issuing a signature or any element of it. Before or at first use, certify to FDA that your electronic signatures are the binding equivalent of handwritten ones; the certification is signed by hand, and FDA’s web page on letters of non-repudiation agreement says where to send it. On request, provide further certification for a specific signature.
- 11.200 components. Non-biometric signatures use at least two distinct components, such as an ID code and a password. In one continuous session, the first signing uses all components and later ones at least one component only that person can use; signings outside a session use every component each time. Misuse by anyone else must need two or more people to collaborate. Biometric signatures must work only for their genuine owner.
- 11.300 codes and passwords. Five controls: unique ID and password combinations; periodic checks, recall or revision; loss management that deauthorizes lost or compromised tokens and cards and controls replacements; transaction safeguards that detect and urgently report attempted misuse; and initial and periodic testing of tokens and cards.
Outside the narrow legacy-system case, none of these signature requirements has discretion in the 2003 guidance. The full treatment is in 21 CFR Part 11 electronic signature requirements.
What FDA’s 2003 enforcement discretion does and does not relax
The 2003 guidance says FDA will read scope narrowly and exercise enforcement discretion on a short list of requirements. It is non-binding, and Part 11 itself remains in effect. Discretion is not an exemption.
| FDA does not intend to enforce | FDA still enforces |
|---|---|
| 11.10(a) validation, 11.10(b) copies, 11.10(c) retention, 11.10(e) and (k)(2) audit trails, and the matching parts of 11.30 | 11.10(d), (f), (g), (h), (i), (j) and (k)(1), the matching parts of 11.30, and 11.50, 11.70, 11.100, 11.200 and 11.300 |
| All Part 11 requirements for legacy systems that were operational before 20 August 1997 and meet four stated conditions | Every predicate rule, including its record and recordkeeping requirements |
The limits matter more than the relaxations.
- Predicate rules still apply. The guidance says you must still meet predicate rule validation duties, and any rule that says to document dates, times or sequence of events, or that bars changes from obscuring earlier entries. For device makers, 21 CFR 820.70(i) was removed when the Quality Management System Regulation took effect on 2 February 2026. The validation duty now sits in ISO 13485 clauses 4.1.6, 7.5.6 and 7.6. See ISO 13485 software validation.
- The guidance still recommends risk-based controls. Base validation and audit trail decisions on a documented risk assessment, even where no predicate rule demands them.
- Legacy status is narrow. It needs all four conditions: operational before 20 August 1997, met predicate rules then, meets them now, and documented evidence that it is fit for intended use. A change that stops it meeting predicate rules brings Part 11 back.
Treat discretion as permission to scale effort by risk, not to skip. Without validation or an audit trail, you still have to show the records meet the predicate rule.
Where the 21 CFR Part 11 requirements meet EU and FDA guidance
Part 11 is one of several sources a computerized system answers to. The EU counterpart, Annex 11, is in force in its January 2011 text, and a July 2025 consultation draft is not adopted; see EU GMP Annex 11. FDA’s February 2026 Computer Software Assurance guidance covers medical device production and quality system software; see CSV vs CSA. The EU’s separate draft Annex 22 for AI models is in Annex 22.
No software is “Part 11 compliant” by itself. Compliance depends on how you configure, validate and use it.
A practical order of work for the 21 CFR Part 11 requirements
- List the records your predicate rules require and decide, per record, whether you rely on paper or electronic form.
- Inventory the systems that hold them and classify each as closed or open.
- Assess each system against 11.10 and the signature sections, and record gaps.
- Validate by risk, with traceable requirements and tests.
- Write the policies, training and signature certification the controls depend on.
If you want those steps as ready documents, the 21 CFR Part 11 Toolkit includes the Part 11 Applicability and Predicate Rule Determination Procedure, the Predicate Rule Record Inventory and the 21 CFR Part 11 Compliance Assessment Checklist. It has 105 templates (68 Word and 37 Excel) for $99.
21 CFR Part 11 requirements FAQ
Do the 21 CFR Part 11 requirements apply if we print records and sign on paper?
Generally not, if the paper meets the predicate rule and you rely on the paper to do the regulated work. If you keep working from the electronic record, FDA may treat that as the record. Decide in advance and document it.
Is validation still required given the 2003 enforcement discretion?
Discretion covers the Part 11 validation requirement in 11.10(a). Predicate rule validation duties and your own risk assessment still apply.
Is there a Part 11 certification for software?
No. The certification in 11.100(c) is your letter to FDA about your own electronic signatures. Compliance depends on configuration, validation and use.
Does Part 11 apply to a software vendor?
The rule is written for the companies that use the systems. The regulated company stays responsible for any system it relies on, including vendor-supplied parts.


