21 CFR Part 11
Electronic signatures and audit trails for maintenance and calibration records
21 CFR Part 11 is the US FDA regulation that sets the conditions under which electronic records and electronic signatures are treated as trustworthy and equivalent to paper records and handwritten signatures. This guide helps quality, validation and maintenance leads in pharmaceutical, medical device and food plants work out which maintenance and calibration records fall in scope and what a system has to show.
Scope
What 21 CFR Part 11 covers
Part 11 sets out the criteria under which FDA considers electronic records, electronic signatures, and handwritten signatures executed to electronic records to be trustworthy, reliable and generally equivalent to paper. It applies to records in electronic form that are created, modified, maintained, archived, retrieved or transmitted under any records requirement in FDA regulations.
That last phrase is the key. Part 11 does not create new records for you to keep. The duty to keep a maintenance log or a calibration record comes from another regulation, which FDA calls a predicate rule. Part 11 governs how that record must be controlled once you keep it electronically.
The regulation has two working parts. Subpart B covers electronic records: controls for closed systems (section 11.10), controls for open systems (11.30), signature manifestations (11.50) and signature to record linking (11.70). Subpart C covers electronic signatures themselves: uniqueness and identity (11.100), and the components and controls of a signature (11.200 and 11.300).
How FDA reads the scope today
In its 2003 guidance on scope and application, FDA said it would interpret the scope of Part 11 narrowly while it re-examined the rule, and that Part 11 remains in effect. In short, Part 11 applies when records required by a predicate rule are kept in electronic format in place of paper, or when you rely on the electronic record to perform regulated activities. If you print a record, rely on the signed paper and the paper meets the predicate rule, Part 11 generally does not apply to the electronic draft behind it.
The guidance also announced enforcement discretion for some Part 11 controls, including validation, audit trails, legacy systems, record copies and record retention. Discretion is not exemption. FDA says records must still be kept or submitted in line with the predicate rules, and it expects decisions on validation and audit trails to rest on a justified and documented risk assessment. For systems that hold GMP records, it is usually simpler to keep audit trails and validation in place than to justify leaving them out.
In scope for maintenance
Which maintenance and calibration records are affected
Whether a maintenance record is in scope depends on the predicate rule for your product. These are the rules most maintenance teams in FDA-regulated plants meet.
| Plant type | Predicate rule | What it asks of maintenance | Part 11 position |
|---|---|---|---|
| Finished drugs | 21 CFR 211.67 | Written procedures for cleaning and maintenance of equipment, including assigned responsibility and schedules. Records of maintenance, cleaning, sanitizing and inspection. | Electronic versions of these records are in scope. |
| Finished drugs | 21 CFR 211.68 | Automatic, mechanical and electronic equipment routinely calibrated, inspected or checked to a written program, with written records of those checks. Controls so only authorized people change records in computer systems. | In scope when kept electronically. |
| Finished drugs | 21 CFR 211.182 | Equipment cleaning and use logs for major maintenance, in chronological order. The people performing and double-checking the work date and sign or initial the log. | An electronic log needs Part 11 signatures for those sign-offs. |
| Medical devices | 21 CFR Part 820 (QMSR) | A documented quality management system that complies with ISO 13485, which Part 820 incorporates by reference, plus FDA's added requirements. Equipment maintenance and measuring equipment calibration sit inside that system. | Electronic quality records are in scope. |
| Human food | 21 CFR 117.305 | Records must be accurate, indelible, legible, created at the time of the activity, and include the date, and the signature or initials of the person. | Records kept only to satisfy Part 117 are exempt from Part 11. Records also required by another rule stay subject to it. |
The food exemption surprises many teams. A sanitation or maintenance record kept only for the preventive controls rule is outside Part 11, but the same record may still fall in scope if another regulation requires it.
Signatures
What an electronic signature must show
Section 11.50 is short and specific. A signed electronic record must clearly show three things: the printed name of the signer, the date and time the signature was executed, and the meaning of the signature, such as review, approval, responsibility or authorship. Those three items must be controlled like the record itself and must appear in any human readable form of the record, on screen and on a printout.
Meaning is the element teams most often leave out. A name and a time say who touched the record. Only the meaning says what they were vouching for. 'Performed by' and 'Verified by' on a calibration record are two different signatures with two different responsibilities, and 211.182 expects both on major equipment work.
Section 11.70 then requires that signatures are linked to their records so they cannot be excised, copied or otherwise transferred to falsify a record by ordinary means. A scanned signature image pasted into a PDF is easy to copy onto another document, which is exactly what 11.70 is meant to prevent. A signature stored as part of the record it signs, and rendered from it, is much harder to transfer.
Rules for the signature itself
Subpart C adds controls on who can sign and how:
- One person, one signature. Each electronic signature is unique to one individual and is never reused by or reassigned to anyone else (11.100(a)). Shared logins on a maintenance tablet break this rule at once.
- Verified identity. Your organization verifies a person's identity before establishing their electronic signature (11.100(b)).
- A letter to FDA. Organizations certify to FDA that the electronic signatures in their system are intended to be the legally binding equivalent of handwritten signatures (11.100(c)). That letter is yours to send, not your software vendor's.
- Two components. A signature not based on biometrics uses at least two distinct components, such as an identification code and a password. In one continuous session the first signing uses all components and later signings use at least one. Signings outside a continuous session use all components each time (11.200(a)).
Audit trails
What an audit trail has to capture
Section 11.10(e) asks for secure, computer-generated, time-stamped audit trails that independently record the date and time of operator entries and actions that create, modify or delete electronic records. Record changes must not obscure previously recorded information. The audit trail must be kept at least as long as the record itself and be available for FDA review and copying.
Read it closely and four tests fall out. The trail is generated by the system, not typed by a user. It is independent, so the person editing a record cannot edit its history. It is time-stamped. And the old value survives the change. A field that simply overwrites, with a 'last modified by' stamp, does not pass.
The other closed system controls in 11.10
Audit trails are one of eleven controls in section 11.10 for closed systems, meaning systems where access is controlled by the people responsible for the records. A maintenance team should recognize each of them.
| Paragraph | Control | What it looks like for maintenance |
|---|---|---|
| (a) | Validation of systems | Evidence that the system does what you use it for and can detect invalid or altered records |
| (b) | Accurate and complete copies | Records can be produced in readable and electronic form for an inspector |
| (c) | Protection of records | Records stay retrievable for the whole retention period |
| (d) | Limited system access | Only authorized people can log in |
| (e) | Audit trails | As described above |
| (f) | Operational system checks | Steps happen in the permitted order, for example no closure before the checklist is complete |
| (g) | Authority checks | Only authorized people can sign, alter a record or perform an action |
| (h) | Device checks | Where appropriate, the source of data input is checked |
| (i) | Training and experience | People who build, maintain and use the system are competent for it |
| (j) | Written accountability policies | People are held responsible for actions taken under their signatures |
| (k) | Control of system documentation | Manuals and change records for the system are controlled |
One calibration record, start to finish
Worked example (illustrative)
CAL-04 is a pressure gauge (an illustrative instrument) on a granulator line in a drug plant. Its calibration is due. The technician records the as-found reading, adjusts, records the as-left reading and attaches the certificate. A QA reviewer checks and signs. Later the technician spots a typo in the as-left value and corrects it.
Here is what the record and its audit trail show. Names are placeholders.
| Time | Who | Action | What the trail keeps |
|---|---|---|---|
| 09:12 | Technician A. Rao | Creates calibration record | All initial values, with user and timestamp |
| 09:40 | Technician A. Rao | Signs, meaning 'Performed by' | Printed name, date and time, meaning, linked to this version of the record |
| 11:05 | QA reviewer S. Iyer | Signs, meaning 'Reviewed and approved' | Second signature with its own meaning |
| 14:30 | Technician A. Rao | Corrects as-left value | Old value, new value, user, timestamp, and the reason entered |
| 14:45 | QA reviewer S. Iyer | Re-reviews and signs the corrected version | New signature linked to the corrected version; the earlier approval stays in the history |
An inspector can see who did the work, who approved it, what changed after approval, and that the approval was repeated for the changed record. Nothing has been overwritten.
Software and you
What software can do, and what stays with you
No product makes a plant meet Part 11 on its own. Part 11 is met by a combination of system features, your procedures and your people. It helps to be clear about the split before you evaluate any system.
| A system can provide | Your organization provides |
|---|---|
| Computer-generated, time-stamped audit trails that keep old values | Validation of the system for your intended use, based on a documented risk assessment |
| Signature manifestation: printed name, date and time, meaning | Identity verification before a signature is issued, and the certification letter to FDA |
| Signatures linked to the record they sign | Written policies holding people accountable for their signatures |
| Role-based access and authority checks | Account administration: no shared logins, prompt removal of leavers |
| Readable and electronic copies of records | Procedures, training records and periodic review of audit trails |
| Record protection and retrieval over the retention period | A decision on which records are in scope, by predicate rule |
A short checklist for your maintenance records
- List the maintenance and calibration records your predicate rules require, and mark which ones you keep electronically and rely on.
- For each, name the signatures needed and the meaning of each one.
- Check that every signature shows printed name, date and time, and meaning, on screen and on printouts.
- Check that edits keep the old value, the user and the time, and that users cannot edit the trail.
- Remove shared logins from tablets and shop-floor terminals.
- Document your validation approach and the risk assessment behind it.
- Decide who reviews audit trails, how often, and where that review is recorded.
Where MaintenanceIQ fits
Where MaintenanceIQ fits
MaintenanceIQ keeps an audit log on every write, so changes to work orders, PM and calibration records carry who and when. Access is role-based and enforced on the backend for every action, including reads. Compliance evidence packs are frozen as records in private storage and downloaded through signed URLs.
An evidence pack can be electronically signed when it is generated. The signature records a named signer bound to their account, a timestamp and an intent statement, and is rendered as a signature block on the PDF. Those are the signer, time and meaning elements Part 11 describes. Signing is optional, and it applies to the evidence pack as a whole rather than to each individual entry. Validation for your intended use, your procedures and your FDA certification letter remain your responsibility. See compliance evidence packs.
Sources
- 21 CFR Part 11, Electronic records; electronic signatures (opens in a new tab), eCFR, US National Archives
- Part 11, Electronic Records; Electronic Signatures: Scope and Application (guidance, September 2003) (opens in a new tab), US Food and Drug Administration
- 21 CFR Part 211, Current good manufacturing practice for finished pharmaceuticals (opens in a new tab), eCFR, US National Archives
- 21 CFR 117.305, General requirements applying to records (opens in a new tab), eCFR, US National Archives
- 21 CFR Part 820, Quality management system regulation (opens in a new tab), eCFR, US National Archives
Frequently asked questions
Does 21 CFR Part 11 apply to maintenance records?
It applies when a predicate rule requires the maintenance record and you keep it electronically in place of paper or rely on the electronic version. For drug makers, 21 CFR 211.67, 211.68 and 211.182 require maintenance, calibration and equipment log records, so electronic versions of those are typically in scope.
What are the required elements of an electronic signature under 21 CFR Part 11?
Section 11.50 requires the printed name of the signer, the date and time of signing, and the meaning of the signature, such as review or approval. These must appear wherever the record is displayed or printed, and section 11.70 requires the signature to be linked to the record so it cannot be copied to another.
Is an audit trail required if FDA uses enforcement discretion?
FDA's 2003 guidance said it would use discretion on some audit trail requirements, but predicate rules still require accurate records, and FDA expects audit trail decisions to rest on a documented risk assessment. An audit trail is also the simplest way to show an inspector that a record was not changed silently.
Are food plant records subject to Part 11?
Records kept only to satisfy the preventive controls rule in 21 CFR Part 117 are exempt from Part 11 under 117.305(g). If the same record is also required by another regulation, that requirement can bring it back into scope.
Can our software vendor do the Part 11 validation for us?
A vendor can supply documentation that supports your validation, but validation is about your intended use in your environment, so it is your organization's responsibility. FDA's guidance asks for a justified and documented risk-based approach.
Keep reading
Compliance evidence packs
Frozen evidence packs with optional e-signature, built from your maintenance records.
ReadCalibration management software
Calibration schedules, certificates and history for each instrument.
ReadISO 55001 asset management evidence
What an asset management audit asks maintenance for, and how to assemble it.
Read