Answers · By Hugh Donatello, Atlas Bio · Updated 2026-10-29

Does 21 CFR Part 11 Apply to AI Tools and Agents?

Does 21 CFR Part 11 apply to AI tools used in GxP work? Yes, when the AI tool creates, modifies, maintains, archives, retrieves or transmits an electronic record that an FDA regulation requires, or a record submitted to FDA. Part 11 regulates records and signatures, not technologies, so the test is what the tool touches, not whether it uses AI. Where it applies, the closed-system controls in 11.10 and the electronic signature rules in 11.50 to 11.300 apply to the workflow the AI is part of.

What Part 11 actually covers

Section 11.1(b) says Part 11 applies to records in electronic form that are created, modified, maintained, archived, retrieved or transmitted under any records requirement in FDA regulations. It also applies to electronic records submitted to FDA under the Federal Food, Drug, and Cosmetic Act and the Public Health Service Act, even if those records are not specifically identified in regulations. The underlying requirements, such as the drug CGMP record rules in 21 CFR Part 211, are what FDA calls predicate rules.

Section 11.3(b)(6) defines an electronic record as any combination of text, graphics, data, audio, pictorial or other information in digital form that is created, modified, maintained, archived, retrieved or distributed by a computer system. Nothing in that definition turns on how the content was produced. An entry typed by an analyst, calculated by a script or drafted by a language model is the same kind of record if a predicate rule requires it.

FDA's 2003 guidance Part 11, Electronic Records; Electronic Signatures - Scope and Application says the agency interprets the scope of Part 11 narrowly. Part 11 records are those required under predicate rules and kept in electronic form in place of paper, records kept electronically in addition to paper and relied on to perform regulated activities, records submitted to FDA in electronic form, and electronic signatures intended to be the equivalent of handwritten signatures. The guidance adds that a record used in generating a submission, but not itself submitted, is not a Part 11 record unless a predicate rule otherwise requires it to be kept and it is kept electronically. FDA may also look at actual business practice: if you print a record but rely on the electronic version to do regulated work, the agency may treat the electronic record as the one in use.

Where common AI uses tend to land

The table below applies those tests to typical uses. It describes what the regulation and guidance say; whether a given record is in scope is a decision for your quality and regulatory function, documented in advance.

AI usePart 11 record?What decides it
Brainstorming, literature summaries or exploratory analysis kept outside any required recordUsually notNo predicate rule requires the output and it is not submitted to FDA
Drafting an SOP or report that a person finalises in a document systemDepends on the final recordThe approved, required document is the record; FDA's 2003 guidance gives a word processor used only to generate SOPs as a case where validation would not be important
Drafting text for a submissionNot by itselfA record used in generating a submission, but not itself submitted, is not a Part 11 record unless a predicate rule requires it
An agent that enters, calculates or changes data in a LIMS, batch record or other required recordYesThe agent is creating or modifying a record required by a predicate rule (11.1(b))
AI output submitted to FDA in electronic formYesElectronic records submitted to FDA are in scope (11.1(b))
Applying an approval or review signatureYes, where the signature is intended as the equivalent of a handwritten signature on an in-scope record; the AI cannot be the signerElectronic signatures must be unique to one individual (11.100(a))

Which controls apply once it is in scope

Section 11.10 lists the procedures and controls for closed systems. Each one has a direct reading when an AI tool or agent is part of the system that creates or changes the record. Section 11.30 extends these controls, plus measures such as encryption and digital signature standards as needed, to open systems, which may matter if the electronic record is created or held in a system whose access your organisation does not control. Where the model runs does not by itself decide whether a system is open or closed.

Enforcement discretion and what it does not cover

The 2003 guidance says FDA intends to exercise enforcement discretion over the Part 11 requirements for validation, audit trails, record retention and record copying, as explained in that guidance, and over systems that were operational before 20 August 1997. It does not relax everything. FDA says it will continue to enforce limiting system access, operational system checks, authority checks, device checks, training, written accountability policies, systems documentation controls, the corresponding open-system controls in 11.30, and the electronic signature requirements, including 11.50, 11.70, 11.100, 11.200 and 11.300. Predicate rules are enforced in full, and records must remain secure and reliable under them.

Enforcement discretion is not an exemption for AI. Predicate rules carry their own expectations: FDA's 2018 guidance Data Integrity and Compliance With Drug CGMP says each CGMP workflow on a computer system is an intended use to be checked through validation, with the extent of validation commensurate with the risk. The 2003 guidance recommends basing your approach on a justified and documented risk assessment of the system's potential to affect product quality, safety and record integrity.

Signatures: an AI tool can prepare, a person signs

Section 11.3(b)(7) defines an electronic signature as a computer data compilation of symbols executed, adopted or authorized by an individual to be the legally binding equivalent of that individual's handwritten signature. Section 11.100(a) requires each electronic signature to be unique to one individual and never reused by or reassigned to anyone else. Section 11.50 requires a signed record to show the printed name of the signer, the date and time, and the meaning of the signature, such as review, approval, responsibility or authorship. Section 11.70 requires signatures to be linked to their records so they cannot be excised, copied or transferred to falsify a record.

Read together, these provisions leave no room for an AI agent to sign in its own right or to sign with a person's credentials. The workable pattern is that the tool prepares the record, the audit trail shows what the tool contributed, and a named person signs with a stated meaning after review.

Related guidance: CSA, FDA's AI draft and EU GMP

FDA's Computer Software Assurance for Production and Quality Management System Software is final guidance dated February 2026, issued by CDRH and CBER. It describes a risk-based approach to establishing confidence in software used in medical device production or the quality management system under 21 CFR Part 820, and it supersedes the version issued on 24 September 2025. Its scope is device production and quality systems, not drug CGMP, so treat it as context for risk-based assurance rather than as a requirement for drug or biologic records.

FDA's January 2025 guidance Considerations for the Use of Artificial Intelligence To Support Regulatory Decision-Making for Drug and Biological Products is a draft, not for implementation. It sets out a seven-step, risk-based credibility assessment for an AI model's output within a defined context of use. It does not address AI used in drug discovery or for operational efficiencies, such as drafting a submission, that do not affect patient safety, drug quality or the reliability of study results. It sits alongside Part 11; it does not replace it.

Part 11 is US law: it follows the record into FDA scope wherever the site is, so an EU site keeping records for US-marketed product or for FDA submissions is still in scope through the predicate rules. For EU GMP, EudraLex Volume 4 Annex 11 covers computerised systems used in GMP-regulated activities, and sites supplying both markets have to meet both. Annex 11 requires risk management across the system lifecycle, consideration, based on a risk assessment, of building in an audit trail of GMP-relevant changes and deletions, with the reason for a change or deletion documented, and electronic signatures permanently linked to their records. The European Commission ran a stakeholder consultation from 7 July to 7 October 2025 on a revised Annex 11 and a new draft Annex 22 on artificial intelligence. The draft Annex 22 covers static models with deterministic output in critical GMP applications and says generative AI and large language models should not be used in critical GMP applications; in non-critical uses, qualified people should be responsible for checking the outputs. These are consultation drafts, not adopted text.

Drawing the boundary in practice

Start from the records, not the tools. List the records each predicate rule requires, note where an AI tool or agent creates, changes, calculates or transmits any of them, and decide in advance whether the electronic or paper version is the one relied on. FDA's 2003 guidance recommends documenting that decision, for example in an SOP. For each in-scope use, record how the system is validated for that use, how the agent is identified and limited, what the audit trail captures and who signs. For out-of-scope uses, write down why they are out of scope, so the line is visible when a draft later becomes a required record. This page describes what the regulation and guidance say; it is not legal advice, and the scoping decision belongs to your quality and regulatory function.

The first step is knowing which of your AI uses touch regulated records. Atlas Bio's Secure AI for Life Sciences starts with an AI risk assessment of current AI use and data exposure. Status, October 2026. In use in Atlas Bio's own agent platform today: a separate verification step that checks agent work, and a hold that stops a task until a person decides. Built and tested on synthetic data, not yet used with a client: the AI risk assessment tooling (AI discovery, data-flow and vendor-terms mapping, and a NIST AI RMF gap report) and a record of what data an AI used, what it produced and who reviewed it. In development: a customer-controlled AI environment in your own Azure tenant, an AI gateway, agent permissions, evidence linkage and notifications. Each engagement states which controls are built. Decisions on GxP scope, validation and compliance stay with your quality function.

Can an AI product be Part 11 compliant out of the box?

Not on its own. Section 11.10 calls for procedures and controls, including validation for the intended use, training and written accountability policies, so compliance depends on how the tool is configured and used inside your system, not only on the product.

Does using a general-purpose chatbot to draft an SOP trigger Part 11?

The draft itself usually is not a Part 11 record. The approved SOP, if a predicate rule requires it and it is kept electronically, is. FDA's 2003 guidance gives a word processor used only to generate SOPs as an example where validation would not be important.

Does FDA's January 2025 AI guidance replace Part 11?

No. It is a draft guidance, not for implementation, about establishing the credibility of AI model output used to support regulatory decisions. Part 11 is a regulation about electronic records and signatures and still applies to in-scope records.

Can an AI agent apply an electronic signature?

No. Section 11.3(b)(7) defines an electronic signature as executed by an individual, and 11.100(a) requires each signature to be unique to one individual and not reassigned. The agent can prepare the record; a named person signs.

Does Part 11 apply to AI use in EU manufacturing?

Part 11 is a US FDA regulation. In the EU, EudraLex Volume 4 Annex 11 covers computerised systems in GMP, and a new Annex 22 on AI was published as a draft for consultation in 2025. Work that supports both markets has to satisfy both.

  1. eCFR: 21 CFR Part 11 - Electronic Records; Electronic Signatures
  2. FDA guidance: Part 11, Electronic Records; Electronic Signatures - Scope and Application (September 2003)
  3. FDA guidance: Data Integrity and Compliance With Drug CGMP - Questions and Answers (December 2018)
  4. FDA guidance: Computer Software Assurance for Production and Quality Management System Software (final, February 2026)
  5. FDA draft guidance: Considerations for the Use of Artificial Intelligence To Support Regulatory Decision-Making for Drug and Biological Products (January 2025)
  6. European Commission: EudraLex Volume 4, Annex 11 - Computerised Systems
  7. European Commission: Stakeholders' consultation on EudraLex Volume 4 - Chapter 4, Annex 11 and new Annex 22 (draft, consultation closed 7 October 2025)

Talk to Atlas Bio.

Sponsors, researchers and clinicians: tell us the decision you are trying to make and we will show what the platform can and cannot answer.

Contact Us →