21 CFR Part 11 Requirements: A Guide for Medical Device Manufacturers

November 20, 2026

On February 2, 2026, FDA's Quality Management System Regulation (QMSR) took effect, and the inspection that comes with it looks different. Investigators now work from Compliance Program 7382.850 instead of the Quality System Inspection Technique, and records that were once off-limits are open to review: management reviews, internal quality audits, and supplier audit reports.

Illustration of 21 CFR Part 11 controls: section 11.10 electronic record controls for closed systems beside Subpart C electronic signature requirements

Most of those records are electronic. Procedures live in a document system, approvals happen in a software workflow, inspection results sit in a database, and supplier evidence arrives as files. Whether FDA can trust any of it is the question 21 CFR Part 11 answered in 1997, and its core requirements have not changed since.

Here is what Part 11 requires, how it fits with QMSR, where electronic records programs break down, and how the work splits between you and your software.


What 21 CFR Part 11 Covers


Part 11 sets the criteria under which FDA considers electronic records and electronic signatures trustworthy, reliable, and generally equivalent to paper records and handwritten signatures. It applies to electronic records created, modified, maintained, archived, retrieved, or transmitted under any records requirement in FDA regulations. FDA calls those underlying requirements predicate rules, and for a device manufacturer the central one is Part 820 itself.

Two scoping points shape how Part 11 applies in practice.

The scope is interpreted narrowly. FDA's 2003 guidance, Part 11, Electronic Records; Electronic Signatures: Scope and Application, applies Part 11 when you keep a required record electronically in place of paper, or keep both and rely on the electronic version to perform regulated activities. If a system only produces a printout and the signed paper is the record you rely on, FDA generally does not treat that system as a Part 11 system. Decide which version is the record, and document that decision in your procedures.

Closed and open systems carry different controls. In a closed system, access is controlled by the people responsible for the records' content; open systems add controls such as encryption. A cloud system is usually operated as closed when your company controls who has access, but external users such as suppliers are part of that assessment. Record the determination in your validation documentation.


How Part 11 Fits With QMSR


QMSR replaced the Quality System Regulation with a rule that incorporates ISO 13485:2016 by reference. It did not rewrite Part 11, which still governs the electronic form of the records QMSR requires. What changed is how much of your record set an investigator can reach.

  • Wider record access. QMSR drops the old §820.180(c) exception, so FDA can now inspect management reviews, quality audits, and supplier audit reports. FDA's QMSR FAQ also notes that investigators can review QMS records created before February 2, 2026.
  • A new inspection model. CP 7382.850 replaced QSIT and organizes inspections around six QMS areas, including Outsourcing and Purchasing and Measurement, Analysis, and Improvement.
  • Risk-based software validation. ISO 13485:2016 clause 4.1.6 requires documented procedures for validating QMS software. FDA's Computer Software Assurance for Production and Quality Management System Software guidance, issued February 3, 2026 to align with QMSR, sets a risk-based approach for production and quality management system software and supersedes Section 6 of the General Principles of Software Validation.

The result: more of your electronic records are in reach, so the controls on the systems holding them carry more weight.


Electronic Records Requirements: §11.10 Controls


For closed systems, §11.10 lists the controls that keep electronic records authentic, intact, and, where appropriate, confidential. Some are technical controls; others are procedural ones your quality system owns.

ControlWhat it requiresPrimary owner
(a) ValidationAccuracy, reliability, consistent intended performance, and the ability to discern invalid or altered recordsManufacturer, with vendor documentation
(b) Accurate copiesComplete copies in human-readable and electronic form for FDA inspectionSystem
(c) Record protectionAccurate and ready retrieval throughout the retention periodSystem and manufacturer retention policy
(d) Access limitsSystem access limited to authorized individualsSystem and manufacturer user administration
(e) Audit trailsSecure, computer-generated, time-stamped record of entries and actionsSystem
(f) Operational checksSteps and events performed in the permitted sequenceSystem
(g) Authority checksOnly authorized individuals can sign, alter a record, or perform the operationSystem and manufacturer role design
(h) Device checksValidity of data input sources, as appropriateSystem
(i) TrainingEducation, training, and experience for the people who build, maintain, or use the systemManufacturer
(j) Written policiesIndividuals held accountable for actions under their electronic signaturesManufacturer
(k) Documentation controlsControl over distribution, access, and revision of system documentationManufacturer

The audit trail requirement is the one reviewers read most closely. Section 11.10(e) calls for "secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records," adds that "record changes shall not obscure previously recorded information," and requires the audit trail to be kept at least as long as the records it covers.

The 2003 guidance applies enforcement discretion to the specific Part 11 requirements for validation, audit trails, record copies, and record retention, while FDA continues to enforce access limits, operational, authority, and device checks, and the signature provisions. That is not an exemption: the predicate rules still apply, and the guidance recommends basing validation and audit trail decisions on a justified, documented risk assessment.


Electronic Signature Requirements: Subpart C


Under Part 11, an electronic signature is the legally binding equivalent of a handwritten signature. Where a predicate rule requires a signature and you execute it electronically, it has to meet these requirements:

  • Signature manifestation (§11.50): the signer's printed name, the date and time of signing, and the meaning of the signature, such as review, approval, responsibility, or authorship
  • Signature and record linking (§11.70): a link that keeps the signature from being excised, copied, or transferred to falsify another record by ordinary means
  • Uniqueness and identity (§11.100): one signature per person, never reused or reassigned, issued after identity verification, with a certification to FDA that your electronic signatures are the legally binding equivalent of handwritten ones
  • Signature components (§11.200): at least two components, such as an ID code and a password, with all components required at the first signing in a session and at every signing outside a continuous session
  • ID code and password controls (§11.300): unique combinations, periodic checks, procedures for lost or compromised credentials, and safeguards against unauthorized use

Part 11 signatures include those used to document that an action required by a predicate rule happened, such as a record being reviewed, approved, or verified. ISO 13485 requires documented approval in many places, starting with documents before issue, so a device QMS has more signature candidates than most teams expect. Inventory them, decide which you will execute electronically, and document the decision.


Where Electronic Records Programs Break Down


The rule text is settled. The gaps show up in daily practice. One login at the inspection bench. Five operators on it across three shifts. No way to say who entered what.

  • Shared logins make every entry unattributable, and the uniqueness requirements in §11.100 and §11.300 fail together.
  • Records that change without a trace, such as an overwritten spreadsheet cell or a replaced file on a shared drive, leave the current value as the only value, with nothing to show under §11.10(e).
  • Approvals by email carry no authority check, no link to the revision being approved, and no signature meaning.
  • Hybrid records nobody defined leave a signed paper copy and a stored PDF, with no procedure saying which one is the record.
  • Supplier evidence that arrives as attachments sits outside any controlled system, right when QMSR made supplier audit reports reviewable.

Each of these is a records problem before it is a software problem. The fix starts with procedures and ends with a system that enforces them.


Part 11 Compliance Is a Shared Responsibility


No software is Part 11 compliant on its own. A vendor can design technical controls: access limits, audit trails, record retention, authority checks. Compliance comes from how those controls are configured, validated, and governed inside your quality system.

Your side of the line: an inventory of which records and signatures fall under Part 11, risk-based validation of each system, procedures for user administration and audit trail review, training records, and the §11.100(c) certification if you use Part 11 electronic signatures. The vendor's side: build the controls, document how they behave, and give you the evidence your validation needs. Treat any "Part 11 certified" software claim with caution, because FDA does not certify electronic systems.

When you evaluate a system, look past the audit trail and access controls to two questions that are easy to skip. For records you designate as requiring a Part 11 electronic signature, does the system capture signature meaning and require re-authentication at signing? And can your suppliers submit evidence into the same controlled system, rather than by email?


Where Net-Inspect Fits in a Part 11 Program


Net-Inspect®'s controls map to the electronic-records side of that line, built into the platform that already holds inspection, nonconformance, corrective action, and controlled document records. It was built to make audit-ready records the everyday state of the system, not a project before an inspection.

Mapped to the controls above:

  • Released revisions that are never lost in Document Management, each with its path through approval, its periodic reviews, and its views and downloads in the activity history (§11.10(c), (e))
  • Approval records with the approver's identity, decision, comment, and time, plus a record of any release made without an approval workflow and who made it (§11.10(e), (g))
  • Corrections that require a written reason, with every correction recorded (§11.10(e))
  • Access set by folder, role, division, and program, including restricted folders and temporary access that requires a written reason (§11.10(d), (g))
  • Accounts that stay attached to the records they created: they cannot be renamed or reassigned, and disabling one ends its active sessions immediately (§11.10(d), (e))
  • Multi-factor authentication, which a customer can require of suppliers before they reach its technical data (§11.10(d))
  • Quality records retained in perpetuity by default (§11.10(c))
  • Audit trails on first article buy-off, nonconformance eTags, and corrective actions, recording each change and who made it (§11.10(e))

When an investigator asks who approved a revision and when, the answer is on the record, not in an inbox.

One boundary is worth stating plainly. Net-Inspect approval records capture who approved, what they decided, their comment, and when. Today they stop short of the signature-meaning step and the re-authentication at signing (such as ID code and password re-entry) that Part 11 electronic signatures require, so Net-Inspect does not support Part 11 electronic signatures. Rather than bolt on a generic signature step, we are gathering feedback from medical device customers and evaluating the deeper support that best fits how they work. If Part 11 electronic signatures are on your requirements list, we want to hear how you use them. Until then, build any Part 11 signature requirement into your evaluation and validation planning from the start.

The supply chain side matters more under QMSR. Net-Inspect connects manufacturers and suppliers in one environment: supplier first article reports are submitted and bought off in the platform, and supplier audits link non-passing answers to corrective actions in the same system. Supplier audit reports become records you can retrieve. (More on that in Mastering Quality Auditing.)


Start With the Records Your Predicate Rules Require


Part 11's requirements have not changed since 1997, but QMSR changed how much of your electronic record set an investigator can open. Start with the inventory: which records your predicate rules require, which of them you keep electronically, and which carry a signature requirement. Then hold each system that stores them to §11.10, and validate it for the way you use it.

If your team is mapping Part 11 controls across the systems that hold your quality records, we are happy to compare notes and show how Net-Inspect handles controlled documents, approvals, and audit trails.


Frequently Asked Questions


Does 21 CFR Part 11 apply to medical device manufacturers?


Yes, whenever you keep records required by FDA regulations, such as Part 820, in electronic form in place of paper, or keep both and rely on the electronic version to perform regulated activities.


Did QMSR replace Part 11?


No. QMSR amended Part 820 and incorporated ISO 13485:2016 by reference, effective February 2, 2026. Part 11 still governs the electronic records and signatures used to meet those requirements.


Is there such a thing as Part 11 certified software?


No. FDA does not certify electronic systems for Part 11. A system can be designed with the technical controls Part 11 calls for, but compliance depends on how the manufacturer validates, configures, and governs it.