Table of contents
At a glance
What is 21 CFR Part 11?
Under 21 CFR 11.1(a), FDA sets the conditions under which it considers electronic records and signatures trustworthy, reliable and generally equivalent to paper records and handwritten signatures. Scope includes records required by other FDA regulations and electronic submissions under § 11.1(b). Controls include system validation, access controls, audit trails and electronic signature requirements. FDA’s “Scope and Application” guidance explains its narrower interpretation and enforcement discretion in specified areas. Part 11 and the underlying recordkeeping requirements remain in effect.
- The scope aligns with the relevant records and their underlying FDA requirements.
- An additional exception excludes actually used electronic records from being automatically included in the scope.
- Signature display, identity, and permanent linkage to the record are separate verification attributes.
- Enforcement discretion does not constitute a blanket exemption from validation or data integrity controls.
Determine the scope of applicability with the Predicate Rules
predicate rules are the underlying legal or regulatory FDA requirements outside Part 11. For example, they determine which records must be kept, retained or filed. Part 11 supplements this basis for the affected electronic records and signatures. Therefore, belonging to an industry is not sufficient to classify each application as a Part-11 system at a flat rate.
For the scope assessment, it is recommended to maintain a list of relevant documentation types. For each type, document the purpose, underlying regulatory requirement, generation, usage, and retention. Then determine whether electronic documentation is being used instead of paper, or whether paper retention is retained alongside electronic documentation, and whether the regulated activity is being performed. The FDA recommends documenting these decisions and considering the actual way of work.
Even the exceptions in the regulatory text and requirements regarding electronic submission must be considered. The assessment must not be based solely on a supplier's assertion that its software is "Part 11-compliant." A system may manage different types of recording, each subject to distinct obligations. A common technical platform does not render these differences irrelevant.
Paper, electronic use, and hybrid workflows differ
The following table illustrates the FDA's interpretation of the scope. It does not replace individual case assessments. For hybrid processes, it is particularly important to determine which version is used for regulated activities and what information is required for their reconstruction.
Recommendation: Demonstrate the workflow using a typical example. A SOP may describe a paper-based review, while the team actually uses electronic filters, calculations, or release decisions. Such a discrepancy should be resolved prior to scope determination. Otherwise, evaluate a described process that does not align with actual operational practice.
| Starting point | Major question | Context |
|---|---|---|
| Electronic batch records replace paper records | Which predicate rule requires documentation? | Part-11 Relevance to be assessed based on obligation and usage |
| Electronic recording plus printing | What actually underpins regulated activities? | The term alone does not constitute an exemption. |
| The computer generates the printed record exclusively used. | Does this paper-based record comply with all applicable requirements? | The FDA does not view this as a trigger for Part 11 under the described conditions. |
| Internal file without relevant retention obligations | Is there any other applicable submission or documentation obligation? | The electronic form alone does not constitute record-keeping under Part 11. |
Classify closed and open systems correctly
Part 11 classifies systems based on control over access. In a closed system, individuals who are responsible for the content of electronic records control access. In an open system, this control is absent. Therefore, classification cannot be determined solely from terms such as "cloud," "internet," or "local server."
Section 11.10 describes controls for closed systems. Section 11.30 addresses additional measures for open systems, where applicable, such as encryption or appropriate digital signature standards. This relates to authenticity, integrity, and, if necessary, confidentiality of records from the point of creation to the point of receipt.
Recommendation: Describe access and responsibility along the actual data flow. Capture administrators, service providers, and involved organizations. Document who grants, modifies, or revokes permissions. When a dataset passes through multiple environments, explicitly address the transitions between them. A generic system classification may inadvertently obscure the transfer step, which may require additional controls.
Sources: [1]
Audits of electronic records verification
The regulation addresses reliable system performance, complete copies of records, protected retention, authorised access and traceable changes. To assess your system, read these requirements alongside the applicable predicate rules and FDA guidance on scope. A feature name alone does not demonstrate that the requirements are met.
Recommendation for Audit Trails: Evaluate at representative events whether the actual data recorded is sufficient and whether prior information remains traceable. Consider also access controls, retention, and future retrievability. A generic technical log may be insufficient for the required professional justification. The assessment should explain how relevant changes can be detected and investigated.
When copies and exports are created, future usage must be considered. A PDF may represent a displayed result, but it may not fully preserve the necessary relationships for certain dynamic data. The FDA, in the context of Drug CGMP, highlights the importance of metadata and distinguishes between static and dynamic records. Recommendation: Verify that recipients can understand and trace the required process based on the provided data and relationships; test the export using a meaningful example.
Electronic Signatures: Identity, Significance, and Interconnection
With an electronic signature, several distinct questions must be addressed. Section 11.50 requires clear indications of the name, timestamp, and significance of the signature. Section 11.70 addresses the linkage between the signature and the record. Section 11.100 covers, among other things, unambiguous assignment to a specific individual and prior identity verification. A visible name line alone does not satisfy these requirements.
For non-biometric signatures, § 11.200 specifies at least two distinct identification components, for example, username and password. The regulation distinguishes between signature sequences during a continuous controlled system access from other signature events. This phrasing should not be unverifiedly equated with two independent factors of a modern multi-factor authentication.
For testing, take an entire approval through the workflow using an authorised role and an unauthorised role. Check how the signature is displayed and linked to the version actually approved. Include subsequent changes and later retrieval of the signed record. Define how credentials are issued and disabled, how users are trained and how compromised credentials are handled. Also consider the certification to FDA under § 11.100(c) that electronic signatures are intended to be the legally binding equivalent of handwritten signatures.
What Enforcement Discretion Means
The FDA Guidance "Scope and Application" outlines a limited flexibility in the enforcement of certain Part 11 requirements, including those related to validation, audit trails, retention, and copies. It simultaneously clarifies that Part 11 remains in effect and that applicable predicate rules continue to be enforced. The guidance includes official interpretations and recommendations; it is not a revocation document.
From this, neither a general waiver of validation nor the traceability of changes can be inferred. The FDA recommends a justified, documented risk assessment taking into account product quality, safety, and the integrity of records. In the context of Drug-CGMP, the complementary data integrity guidance further emphasizes the need for appropriate system and process controls.
Recommendation: If you intend to implement a measure differently, first document the applicable obligation and the specific risk involved. Then explain how the selected control addresses that risk and how its effectiveness is verified. A standalone reference to Enforcement Discretion neither establishes the legal basis nor demonstrates the technical justification for the decision.
Example: Electronic laboratory results with additional printout
Example: A laboratory generates electronic measurement data and a printed result report. For the evaluation of the result, additional processing steps and further data are considered in the system. If a relevant FDA record requirement exists, the expression alone cannot take the electronic part out of the Part-11 scope. The decisive factor is what the regulated activity actually relies on.
A potential evaluation approach first identifies the required raw data, calculations, metadata, changes, and release records. Subsequently, it determines which information must be retained and in what form it remains reviewable in the future. A test can assess whether the required history of a sample dataset—including its associated mappings—can be retrieved and understood.
This is an example illustrating the application of scope logic. It contains no statement regarding a specific laboratory product. The actual assessment depends on the employed method and applicable obligations. The practical benefit lies in making the entire traceability chain visible prior to selecting a specific export format or signature function.
A documented evaluation pathway for your system
A cohesive evaluation document with references to existing evidence is recommended for implementation. Begin with record types and predicate rules, document the actual electronic or hybrid usage, and assign responsibility to the relevant systems. Supplement with control requirements and current status. Based on this, gaps can be prioritized.
A pure manufacturer checklist can serve as a source of information. However, it should demonstrate whether a function exists, is activated, correctly configured, and has been validated against the intended process flow. Organizational prerequisites such as training, responsibilities, and change management also need to be evaluated. For open items, specific outcomes and ownership responsibilities must be defined.
The following checklist serves as a guidance document for this inventory review. It does not provide a general compliance confirmation and does not substitute for the evaluation of applicable requirements.
- Are relevant record types and the underlying FDA requirements identified?
- Has the actual use of electronic and paper records been clarified?
- Are system access, responsibilities, and data transfers clearly documented?
- Were relevant controls verified based on specific procedures?
- Are signature identity, significance, linkage, and subsequent presentation assessed?
- Are storage, copies, and retrieval including required metadata defined and addressed?
- Is each essential gap linked to a risk, corrective action, and responsible party?
- Are changes to the process or system reviewed for impacts on the scope?
Project experience and collaboration
Identify the controls needed for each required record
We select an electronic record your team actually needs. Who creates it, who can change it and what later decision relies on it? With IT and process owners, we trace identity, change history, signature and retention through that workflow. A targeted configuration test may answer an open question about a standard function. Custom handovers often need additional evidence. The record's purpose and the applicable FDA regulations determine the detailed Part 11 requirements.
Frequently asked questions about 21 CFR Part 11
Does Part 11 apply to every system of a pharmaceutical company?
No. The scope shall align with the relevant records, the underlying FDA requirements, and actual usage. The mere presence of an electronic file format or the nature of the organization is insufficient. Exceptions specified in the regulatory text must also be considered. The FDA recommends documented scope determinations for relevant records.
What are Predicate Rules?
These are the underlying statutory or regulatory FDA requirements outside Part 11. For example, you determine which records need to be kept, kept or filed. For the Part-11 evaluation, these obligations form the starting point. The currently applicable rule must be determined for the specific activity.
Does a paper printout contain electronic data from the scope?
Not automatically. If regulated activities continue to rely on electronic recordkeeping, Part 11 may still remain relevant despite the presence of a printed copy. The FDA distinguishes such processes from those that are solely based on paper records meeting the applicable requirements. The actual way of working is decisive and should be clearly defined and demonstrable.
Is a cloud system automatically an open system?
No. Part 11 defines open and closed access based on control of access by personnel responsible for the content. The technical operation within a cloud environment does not determine this solely. Recommendation: Describe the actual access and responsibility boundaries, including third-party services and data transfers, and justify the resulting classification accordingly.
What information constitutes an electronic signature?
Under § 11.50, the name, date, and time, as well as the meaning of the signature, must be clearly visible. Additional requirements also apply, such as identity verification, signature validation, and linkage to the record. The mere presentation of these elements does not constitute sufficient evidence that the entire signature process is appropriate.
Do Audit Trails and Validation Be Exempted Through Enforcement Discretion?
This does not result in a flat-rate exemption. The FDA describes limited restraint in certain Part-11 requirements; applicable predicate rules remain. Decisions on validation and appropriate controls should be justified and documented risk-based. The impact on reliable records and product quality remains essential.
Does the software vendor's Part 11 statement suffice?
It can provide information on functionalities and validation evidence. For your intended use, the scope, configuration, processes, and organizational controls must be evaluated. Recommendation: Ask for specific evidence supporting the required functionalities and align them with your requirements. A general product claim neither replaces this alignment nor the actual review of the operational workflow.
Sources and review date
The regulatory text was reviewed in the continuously maintained eCFR on October 6, 2026. The overall amendment date for Title 21 will not be issued as an amendment to Part 11. FDA Guidance outlines the agency's position and contains non-binding recommendations. The Data Integrity Guidance applies to Drug CGMP; its scope is not extended to all FDA-regulated activities.
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic Signatures
- eCFR: § 11.10 – Controls for closed systems
- eCFR: § 11.200 – Electronic signature components and controls
- FDA: Part 11 – Scope and Application (Final Guidance, 2003)
- FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers (2018)
Sources checked: .
Part 11 – Scope and Evaluability of Controls
We support you in identifying relevant records and assessing the technical and organizational controls of your system.
- GAMP 5 consulting →
Understand how GAMP 5, EU GMP Annex 11 and 21 CFR Part 11 apply to your systems. We translate the relevant requirements into proportionate validation work and evidence your team can defend in an audit.

