21 CFR Part 11 for Executives Who Aren't Technologists
What the regulation genuinely requires, where the real work sits, and why no software is compliant on its own.
21 CFR Part 11 is the FDA regulation that lets a regulated company use electronic records and electronic signatures in place of paper. It applies only when a predicate rule — an underlying Good Manufacturing Practice or Good Laboratory Practice requirement — already requires you to keep that record, and you choose to keep it electronically. It does not apply to records you keep on paper, and it does not certify products.
The full text is short, public, and worth reading directly at Title 21, Part 11 of the Code of Federal Regulations. FDA's own guidance on scope and application states the scope plainly, and it is narrower than vendor marketing implies.
See how your IT actually stacks up.
Twelve questions, about four minutes, and your score appears on screen immediately — no sales call required.
What is 21 CFR Part 11, in plain terms?
Part 11 is the rule under Title 21 of the Code of Federal Regulations that says when the FDA will treat an electronic record as the equivalent of paper, and when it will accept an electronic signature as binding. It applies to records created, modified, maintained, archived, retrieved, or distributed under any records requirement of the predicate rules — the GxP regulations that govern drug and device manufacturing, laboratories, and distribution. If a predicate rule requires a record and you keep it electronically, Part 11 governs that record. If no predicate rule requires the record, Part 11 does not reach it.
The regulation applies to FDA-regulated entities: drug and device manufacturers, contract laboratories, contract manufacturers, and others subject to GxP. It does not apply to companies outside an FDA predicate rule, or to records no predicate rule requires. Your general ledger, for example, is not a Part 11 record unless a predicate rule requires it — which, for most companies, it does not. Pharmaceutical IT obligations extend beyond Part 11 into the wider GxP environment, but Part 11 is the specific rule for electronic records and signatures.
What does the regulation actually require?
Part 11 sets controls across six areas. Each is a business obligation, not a feature checkbox.
Validation. You must validate the system to confirm it does what it claims, under actual use. In practice this means documented evidence the system was installed correctly, operates as specified, and meets its intended purpose — see the validation section below.
Audit trails. Secure, computer-generated, time-stamped records that capture the creation, modification, and deletion of records. The audit trail must be retained as long as the record itself, and an operator must not be able to alter or silence it (§ 11.10(e)).
Access controls. The system must limit access to authorized individuals (§ 11.10(d)) and enforce authority checks so only the right people can take a given action (§ 11.10(g)). For life-science companies, audit-ready access controls and monitoring are where this obligation lives operationally.
Electronic signatures. Each signature must include the printed name, the date and time, and the meaning — review, approval, responsibility (§ 11.50). The signature must be linked to its electronic record so that falsification is detectable and the signature cannot be excised, copied, or transferred (§ 11.70).
Record retention and retrieval. Records must be protected and retrievable for the retention period the predicate rule sets, and the system must produce accurate and complete copies in both human-readable and electronic form (§ 11.10(c)).
Open systems. When records pass across an open system — one not fully controlled by the people responsible for the records' content — additional controls such as encryption and digital signatures are required (§ 11.30).
Why "Part 11 compliant software" is a misleading phrase
A product cannot be "Part 11 compliant" on its own. Compliance is a property of a configured, validated, and operated system, not of the software you bought. The regulation speaks to controls and procedures the regulated entity must put in place; a vendor can build features that support those controls, but it cannot validate your configuration, govern your users, or write your procedures for you.
A vendor can legitimately say a product is designed to support Part 11 controls — that it generates audit trails, enforces role-based access, and binds signatures to records. Those features are real and worth paying for. What a vendor cannot truthfully say is that buying the product makes you compliant. A system with audit trails that nobody validated, shared admin credentials, and a change pushed after go-live without revalidation is non-compliant regardless of what the brochure promised.
The distinction matters because the work that fails in audits is rarely the software's fault. It is the validation that was skipped, the audit trail turned on but never reviewed, the offboarded user whose access lingered. Buying compliant-capable software and then under-operating it is the most common path to a finding.
| What a vendor can legitimately claim | What you are still responsible for |
|---|---|
| The system generates an audit trail | Enabling it, reviewing it, and retaining it with the record |
| The system supports role-based access | Defining roles, assigning them, and revoking access on departure |
| The system can bind signatures to records | Validating that the binding holds in your configuration |
| The system offers electronic signatures | Defining what each signature means and who is authorized |
| The system is designed to support Part 11 controls | Validating the system for your intended use |
| The vendor provides a validation kit or IQ/OQ templates | Executing validation, writing the PQ, and signing the report |
| The infrastructure provider publishes attestations such as SOC 2 | Owning configuration, user management, and your procedures |
| The platform retains data for a configurable period | Setting that period to meet your predicate-rule retention |
What does validation actually involve?
Validation is documented evidence that a system does what it claims under actual use. In pharma it is conventionally broken into three stages — installation qualification, operational qualification, and performance qualification — none of which require a software engineering degree to understand.
Installation qualification (IQ) confirms the system is installed correctly: the right version, on the right infrastructure, with the right configuration, by a documented procedure. The output is an IQ report and a configuration baseline.
Operational qualification (OQ) tests that the system behaves as specified: that access controls enforce the roles you defined, that the audit trail captures changes and who made them, that signatures are bound to records. The output is a set of executed, signed test scripts with evidence.
Performance qualification (PQ) confirms the system works for its intended use in the real environment, with real users and real data. The output is a PQ report and a statement of fitness for purpose.
The documentation is the deliverable: protocols, executed test cases with evidence, deviation logs, and a validation summary report. For a single, moderately complex application, expect weeks of elapsed time and meaningful internal effort, not an afternoon. The work scales with the complexity of the system and the criticality of the records it holds.
Where do companies most often get caught?
We have sat in these audits and read the Form 483s. The findings cluster in a small number of places.
Audit trail gaps. The most common Part 11 weakness we see. The system logs changes but not who viewed the record, or the audit trail was enabled after go-live and the early history is gone, or the trail exports to Excel where it can be edited. The regulation requires the trail to capture creation, modification, and deletion, and to be retained with the record (§ 11.10(e)).
Shared logins. When five people share one account, the audit trail names the account, not the person. Part 11 requires that actions be attributable to a specific individual (§ 11.200). Shared credentials break that link entirely.
Unvalidated changes after go-live. A configuration change is pushed to production and nobody revalidates. The validation report now describes a system that no longer exists. Even a small change can call for a risk-based assessment and partial revalidation.
Spreadsheets used as records. An Excel sheet tracking deviations or training is a regulated record if a predicate rule requires the record. A spreadsheet with no access control, no audit trail, and no validation is a Part 11 failure waiting to be found. We have seen this gap more often than any other single one.
Offboarded users retaining access. An employee left six months ago and the account is still active. Authority checks are a stated Part 11 control (§ 11.10(g)), and a departed user's continued access is the clearest possible evidence that the check is not working.
What should you ask a vendor before buying?
These questions separate a product that can support compliance from one that will quietly fail you. Ask in writing, and ask for the answer in writing.
- 1.Does the system generate a tamper-evident audit trail by default, and can it be disabled? A good answer: the audit trail is always on for regulated records and cannot be turned off by an administrator.
- 2.Does the audit trail capture who viewed a record, or only who changed it? A good answer: both — read events are part of the trail.
- 3.How are signatures bound to the record, and can a signature be copied to another record? A good answer: signatures are linked such that they cannot be excised, copied, or transferred (§ 11.70).
- 4.Does each signature record the printed name, date and time, and meaning? A good answer: yes, all three, automatically (§ 11.50).
- 5.How does the system enforce role-based access, and how do you prove access was revoked promptly when someone left? A good answer: roles are centrally managed, changes are logged, and there is a report for departed users.
- 6.What validation documentation do you provide, and what remains ours to do? A good answer: the vendor provides IQ/OQ templates or a validation kit; the customer owns execution, the PQ, and the report.
- 7.Is the system validated for our intended use, or do you only claim it is capable? A good answer: the vendor is explicit that it provides capability and the customer validates for intended use. A vendor claiming its validation covers your intended use is overclaiming.
- 8.Where is data stored, for how long, and how do we retrieve it on demand? A good answer: documented retention, documented retrieval, and human-readable plus electronic export (§ 11.10(c)).
The pattern in a good answer is specificity. A vendor that answers "of course, we're fully Part 11 compliant" has not understood the question.
Part 11 and the cloud
Running a system in the cloud does not outsource the obligation. Part 11 responsibility splits three ways, and the regulated entity — you — holds the obligation that matters most.
The software vendor is responsible for the application: the features, the audit trail logic, the signature binding, the validation kit. The infrastructure provider is responsible for the platform: availability, physical security, and the controls described in its own attestations. You are responsible for everything that touches the regulated record: configuration, user provisioning and deprovisioning, validation for your intended use, the standard operating procedures, and the ongoing evidence that the controls are operating.
A SaaS provider may offer a qualification package and a SOC 2 report. Both are useful inputs. Neither is your validation. You still validate the system as configured for your use, you still own user access, and you still answer to the auditor. The question to put to any cloud provider is which controls they operate, which they document, and which they expect you to operate — and to get that in a documented matrix.
The real work in Part 11 is not buying the right software. It is running the controls you bought, validating the configuration you chose, and keeping the evidence current as people come and go and systems change. A product can make that work easier. It cannot do it for you.
Hero photo: "Stacks of paper documents and file folders" by Wesley Tingey on Unsplash.
Frequently asked questions
Don't see your question? Email info@isectra.com and we'll answer it directly.
Santiago Aristizabal is President & COO at iSectra. He works with pharmaceutical and life-science companies on the IT systems that have to hold up under FDA scrutiny.
Related reading
Get the next post in your inbox.
Signal, once or twice a month. No spam — just the posts worth reading.
Let's see what your IT could feel like.
A senior engineer will review your environment and respond within 24 hours. No sales script, no obligation.
