Is Docusign Part 11 compliant?

The Docusign Part 11 module is a pre-set eSignature account configuration that adds signature-level authentication, a signing reason and a signature manifestation with printed name, time stamp and reason. Docusign pairs it with the Validator for Life Sciences, which runs monthly QA tests on Part 11 functions and posts the reports in the account. Here is what that adds up to when one SOP approver signs, and which line of the rule each step answers.

1. 01

   The account runs the Part 11 module

   The module is a pre-set configuration of a Docusign eSignature account. The controls below come with it; a signing flow outside a Part 11 account is not the one this page reads.

   § 11.10
2. 02

   The signer authenticates at the signature

   Authentication happens at the point of signing, not only at log-in. Part 11 asks for at least two distinct components, such as an identification code and a password, for every non-biometric signature.

   § 11.200(a)
3. 03

   The signer gives a reason

   Each signature carries a signing reason. That reason is the meaning the rule asks for, such as review, approval, responsibility or authorship.

   § 11.50(a)(3)
4. 04

   The manifestation is stamped on the record

   Printed name, the date and time the signature was executed, and the reason appear with the signature. The rule wants all three in any human-readable form of the record, on screen and on paper.

   § 11.50
5. 05

   The signature is bound to the document

   Docusign's help pages describe how the signature is linked to the signed record. The rule's test: the signature cannot be excised, copied or moved to falsify a record by ordinary means.

   § 11.70
6. 06

   The history records it

   The signing events go into a computer-generated, time-stamped history that Docusign's own pages describe for Part 11 accounts.

   § 11.10(e)

Every one of these steps is a signature control, and that matters. FDA's 2003 guidance relaxed enforcement on four Part 11 areas (validation, audit trail, copies and retention) but said it intends to enforce “requirements related to electronic signatures (e.g., §§ 11.50, 11.70, 11.100, 11.200, and 11.300)” in full. The Part 11 requirements, section by section walk through each one.

We read Docusign's product page, its Part 11 help pages and its Part 11 white paper against the same 10 rows we use for every e-signature tool. Of those, 6 are verified on Docusign's own documentation, 4 are stated without the control being described, and 0 have nothing published. The right-hand column is the work that stays on your side of each row.

The same rows, read for Adobe, are on is Adobe Acrobat Sign Part 11 compliant; the two side by side are in Docusign vs Adobe Sign for regulated teams; and every signing tool we read is in the Part 11 e-signature software comparison.

The module tightens signing, and a few everyday features go with it. Docusign's own pages list them; this is the part a sales call tends to skip, and the part that breaks a workflow in week one.

Fewer ways to collect a signature

Docusign: Signers re-enter their Docusign username and password, or the last four digits of their phone and an SMS code, at each signature field (Original mode) or when opening and completing the envelope (Rapid mode); in-person, delegated and mobile-app signing are not available on Part 11 accounts.

Plan for it: Map every signing flow before go-live. A QA approver on leave cannot hand the signature to a deputy, so name a backup approver in the SOP and route the document to that person. A signature collected face to face on someone else's device needs another route: each signer signs under their own credentials.

Some settings are not yours to change

Docusign: Some Part 11 account settings can only be changed through Docusign Support.

Plan for it: Treat a change made through Docusign Support like any other configuration change: a change record, an impact assessment and the re-test it calls for. Ask how Support confirms a change, and file that confirmation with the change record.

The reasons list depends on the plan

Docusign: Signing reasons can be edited by accounts on the Enterprise Pro plan.

Plan for it: Check the plan before you buy. If your SOPs name meanings the preset reasons do not, you either need a plan that lets you edit them or a line in the SOP mapping each preset reason to the meaning you intend.

Part 11 binds the people who use a system, not the people who sell it. So the honest answer to “is Docusign Part 11 compliant” is that the module can be part of a compliant set-up, and the rest of the set-up is yours. These are the duties that never move to a vendor, with the piece of evidence an inspector asks to see for each.

1. § 11.1(b)

   Decide which documents go through Part 11 signing

   A written scope: which records a predicate rule requires and which signatures stand in for handwritten ones. FDA's 2003 guidance recommends you “document this decision (e.g., in a Standard Operating Procedure (SOP), or specification document)”. The Part 11 applicability checker sorts one record type at a time.

2. § 11.10(a)

   Validate the system for your intended use

   Requirements, a risk assessment, executed tests and a signed summary report. See the next section.

3. § 11.100(b)

   Verify each signer's identity before they sign

   One record per signer: who checked the identity, against what, and on which date.

4. § 11.10(j)

   Hold signers accountable in writing

   A policy, acknowledged by each signer, that actions under their e-signature are their own.

5. § 11.10(i)

   Train the people who send, sign and administer

   Training records against the signing SOP and its version, for senders, signers and account administrators.

6. § 11.100(c)

   Send FDA the certification letter

   The letter saying your e-signatures are “intended to be the legally binding equivalent of traditional handwritten signatures”, signed by hand. FDA calls it a Letter of Non-Repudiation; it can cover named people or the whole company, and FDA's page says a mailed paper copy is now optional.

7. § 11.10(c)

   Keep records retrievable for the whole retention period

   A retention schedule per record type. Part 11 sets no period of its own; the predicate rule does, such as “at least 1 year after the expiration date of the batch” for drug CGMP records under § 211.180.

8. § 11.30

   Call the system open or closed, and act on it

   A short assessment against the definitions in § 11.3(b)(4) and (9). An open system adds measures “such as document encryption and use of appropriate digital signature standards”. Run it through the open vs closed system check.

Validation under § 11.10(a) means showing the system does what you need, as you have set it up. Docusign covers part of the testing with its Validator for Life Sciences, which runs monthly QA tests on the Part 11 functions and posts the reports in the account. Docusign's product page calls the Validator for Life Sciences an additional module. Your share is everything specific to your account.

Size the work by risk. GAMP 5 sorts software by how much it is configured or custom-built; an account you set up yourself sits with the configured components, so the testing goes where your settings carry risk. If you make medical devices, FDA's Computer Software Assurance guidance (current version issued February 3, 2026) recommends more rigor, such as scripted testing, where process risk is high, and allows unscripted testing where it is not. FDA wrote it for device makers; drug and GLP labs often borrow its risk ideas. The CSA validation scope planner sets that out feature by feature, and the CSV guide for small labs covers the whole pack.

Vendor statements read on Docusign's own pages; regulation text quoted from the eCFR; guidance quoted from FDA and the European Commission. General information, not regulatory advice.

1. Life Sciences modules (product page), Docusignread 2026-10-22
2. Part 11 Envelope Access and Signatures, Docusign Supportread 2026-10-22
3. Authentication Methods for Part 11 Signers, Docusign Supportread 2026-10-22
4. Part 11 Information in Completed Documents, Docusign Supportread 2026-10-22
5. Validator for Life Sciences, Docusign Supportread 2026-10-22
6. How the Part 11 Module Helps Enable Compliance, Docusign Supportread 2026-10-22
7. Using Docusign to facilitate compliance with 21 CFR Part 11 (white paper), Docusignread 2026-10-22
8. 21 CFR Part 11, Electronic Records; Electronic Signatures, eCFRread 2026-10-22
9. Part 11, Electronic Records; Electronic Signatures: Scope and Application (2003), FDAread 2026-10-22
10. Letters of Non-Repudiation Agreement, FDAread 2026-10-22
11. Computer Software Assurance for Production and Quality Management System Software, FDAread 2026-10-22
12. EudraLex Volume 4, Annex 11: Computerised Systems (PDF), European Commissionread 2026-10-22