21 CFR Part 11 · Electronic records & signatures
21 CFR Part 11 software: audit trails, e-signatures and controlled records.
V5 provides the technical controls Part 11 asks about — audit trail, e-signatures, access control — while your validation and procedures decide how they are used.
ALCOA+ from the Data Model Up
Every field, every state change, every signature — captured in a tamper-evident, append-only audit trail.
E-signatures that are fast enough to use
Biometric or PIN-based, sub-2-second at the kiosk.
Witness signatures where the SOP demands
Two-person verification on critical steps — dispense, line clearance, batch release — gated by skills matrix and trained-on-current-SOP checks.
What goes wrong today4 common problems
Retrofitted systems can't pass Part 11
Bolting an 'audit log' onto a legacy ERP doesn't make it compliant. If the underlying data can be edited without leaving a trail, you have a 483 waiting to happen.
Validation Packs Cost More than the Software
Validation effort for computerised systems is often underestimated when buying software.
Operators Bypass Clunky e-Signatures
If signing takes 30 seconds at the kiosk, operators batch them at end-of-shift. That's not contemporaneous — that's a finding.
Auditors Test the Audit Trail
The first thing a Part 11 auditor does is edit a record and watch what the system captures. If the trail doesn't show who, what, when, and the prior value — game over.
Everything V5 does here5 capabilities
ALCOA+ from the Data Model Up
Every field, every state change, every signature — captured in a tamper-evident, append-only audit trail. There is no admin override.
E-signatures that are fast enough to use
Biometric or PIN-based, sub-2-second at the kiosk. Operators sign in the moment of the action — contemporaneous by design.
Witness signatures where the SOP demands
Two-person verification on critical steps — dispense, line clearance, batch release — gated by skills matrix and trained-on-current-SOP checks.
IQ/OQ and Validation Support with Enterprise
Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable.
Role-based access with named accountability
Every action is attributable to a named, trained, currently-employed individual. No shared logins. No 'admin' that can rewrite history.
How it works, step by step6 steps
What 'Part 11 by architecture' looks like in practice — the moments an inspector tests and what V5 produces.
- Edit a record and watch what happens. Inspector edits a numeric field. V5 captures the user, timestamp, prior value, new value, and prompts for a reason. The change appears inline on the record; the audit trail is the record, not a separate log.
- Try to Log in as Another User. Inspector asks an operator to log in as a colleague. The system refuses — biometric or PIN are individual. There is no shared account to attempt.
- Ask for a signed PDF. Inspector requests a signed batch record. V5 generates a PDF carrying printed name, date/time, and meaning of every signature, plus the audit trail summary. Byte-identical to the source.
- Try to edit a signed record. Inspector attempts to edit a previously signed record. The binding breaks, the system requires re-signature, and the prior signature is preserved with its 'invalidated by subsequent edit' annotation.
- Ask for the validation pack. Inspector asks for validation documentation. Your team presents its own validation package, PQ and approvals; with Enterprise, IQ/OQ material supplied under your quote is kept with it.
- Test access removal. Inspector asks what happened when a named employee left. V5 shows the termination event, the time-stamped access removal, and the assertion that subsequent records cannot be attributed to that user.
What to look for when choosing
Part 11 compliance is not a feature you can switch on — it's an architecture. These criteria separate systems with Part 11 controls built in from systems that bolt an audit log onto a non-compliant base.
ALCOA+ at the Data Model
Are records Attributable, Legible, Contemporaneous, Original, Accurate — plus Complete, Consistent, Enduring, Available — at the field level? ALCOA+ is the schema. Every field carries attribution, timestamp, prior value, and reason for change — built in, not appended.
Tamper-Evident, Append-Only Audit Trail
Can any user — including 'admin' — edit a record without leaving a trail? Append-only architecture. No admin override exists. The platform owner is subject to the same trail as the line operator.
E-Signature Speed at the Point of Use
How long does it take an operator to sign at the kiosk — sub-2 seconds, or 20-30 seconds? Biometric or PIN, sub-2-second at the kiosk. Operators sign at the moment, not at end of shift.
§11.50 manifestations
Does every signed record display printed name, date/time, and meaning of signature? Printed name, time-stamp, and explicit meaning are part of every signature record. PDF exports include them.
§11.70 signature/record linking
Are signatures cryptographically bound to the record they sign — and is the binding broken by any subsequent edit? Signatures are bound to the record state at time of signing. Any subsequent change requires re-signature; the chain is visible.
Validation Pack Ownership
What validation support does the vendor provide, and what stays with your team? Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable.
Named Accountability, No Shared Logins
Does the system enforce individual authentication — no shared logins, no generic 'operator1' account? Every action requires individual authentication (biometric or PIN). Roles are assigned to named, trained, currently-employed individuals.
Annex 11 + GAMP 5 in One Architecture
Does the same compliance footprint cover EU GMP Annex 11 and GAMP 5 — or do you maintain Part 11 separately? Same architecture passes Part 11, Annex 11, GAMP 5, PIC/S PI 011 and ICH Q9 simultaneously.
V5 Compared with Other Approaches
How Part 11 technical controls compare across the three options most regulated manufacturers consider.
| capability | spreadsheet | legacy Qms | v5 |
|---|---|---|---|
| Audit trail architecture | None — Excel cannot meet §11.10(e) | Separate log file, can be cleared | Append-only, inline on the record, no clear function |
| Admin override | Anyone with edit rights | Common — DBA can edit silently | Does not exist; platform owner is on the trail |
| Signature speed | N/A — handwritten on print-out | 20-30 seconds (password + reason) | Sub-2 seconds (biometric or PIN) |
| §11.50 meaning of signature | Manual | Often absent in default config | Default-on, explicit per signature |
| §11.70 record binding | None | Inconsistent across modules | Cryptographic binding, broken by any edit |
| Validation cost per release | N/A | Varies by vendor and scope | Enterprise IQ/OQ and validation support, scoped in your quote |
| Shared logins possible? | Yes | Yes (often disabled by SOP only) | No — enforced by the system |
| Annex 11 coverage | Fails | Separate config | Same architecture |
Regulations this supportsYour quality team stays responsible for compliance
21 CFR Part 11 verbatim — and how V5's architecture answers each subsection inspectors actually test.
21 CFR Part 11 §11.10(a)
Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable. The append-only audit trail discerns invalid or altered records by design.
21 CFR Part 11 §11.10(d)
Role-based access tied to named, trained, currently-employed individuals. Termination removes access automatically. No shared logins exist at the system level.
21 CFR Part 11 §11.10(e)
Append-only trail with prior-value preservation. Deletion is logical, not physical — the original record remains visible with its deletion event attributed and timestamped.
21 CFR Part 11 §11.50(a)
Every V5 signature carries printed name, date/time, and explicit meaning. These manifestations appear in the on-screen record, in the PDF export, and in the electronic export.
21 CFR Part 11 §11.70
Signatures are cryptographically bound to the record state at time of signing. Any change to the record breaks the binding and requires re-signature; the chain is visible to the auditor.
21 CFR Part 11 §11.200(a)(1)
Non-biometric V5 signatures require both identification code and password. The first signing of a session uses both; continuous signing within the session uses the password component, per §11.200(a)(1)(i)-(ii).
EU GMP Annex 11 §4.4
Your team writes and approves the URS for its intended use. Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable.
GAMP 5 (2nd ed.) software categories
Your team assesses the GAMP category and validation effort for its configured use. Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable.
Standards Referenced
- 21 CFR Part 11 §11.10 (controls for closed systems)
- 21 CFR Part 11 §11.50 (signature manifestations)
- 21 CFR Part 11 §11.70 (signature/record linking)
- 21 CFR Part 11 §11.200 (e-signature components & controls)
- EU GMP Annex 11 (computerised systems)
- GAMP 5 (validation lifecycle)
Common questions5 answers
- What does 21 CFR Part 11 require?
- Part 11 (Electronic Records; Electronic Signatures) requires that electronic records used to meet FDA predicate rules are trustworthy, reliable, and equivalent to paper. Practically: validated systems, tamper-evident audit trails, secure access controls, attributable e-signatures, and the ability to generate accurate copies for inspection.
- Does V5 Ultimate make us 21 CFR Part 11 compliant?
- V5 provides the technical controls — ALCOA+ data model, append-only audit trails, electronic signatures and role-based access — and Enterprise adds IQ/OQ and validation support. Your team remains responsible for intended-use validation, procedures, roles, training and periodic review; software alone does not make a site compliant.
- Do I need to re-validate when V5 releases an update?
- Your change control decides. You assess each update against your intended use and decide what testing, including any PQ, is needed. Enterprise includes IQ/OQ and validation support; exact deliverables are set in your accepted quote/SoW. Your team plans, runs and approves intended-use validation and PQ as applicable.
- What's the difference between Part 11 and EU GMP Annex 11?
- Both govern computerised systems in regulated manufacturing, but Annex 11 is broader in scope (covers risk management explicitly) while Part 11 is more prescriptive on e-signatures. V5 provides technical controls relevant to both; your team decides how each applies to your intended use.
- How does V5 prevent shared logins?
- Every action requires individual authentication (biometric or PIN). 'Admin' accounts cannot edit historical records — even the platform owner sees the audit trail. Roles are assigned to named, trained individuals; when employment ends, access ends automatically.