Table of contents
At a glance
How do you validate DocuSign for a GxP process?
Define the intended document and signature workflow, account configuration, authentication and complete data path. Test signatory identity, signature meaning, document version, return and retention against defined outcomes. Use Validator reports for the functions they cover and fill the evidence gaps. A Part 11 module or completed envelope does not establish substantive approval or validation of your use.
- Part-11 Account, Life Sciences Module, and Validator Scope to be separately captured.
- Verify authentication, authorization, and signature significance jointly.
- A fully signed incorrect document version remains the incorrect evidence.
- Export, data retention, and feedback into the primary system are part of the inspection process.
1. Define the signing process and its scope of application
This guide addresses DocuSign eSignature with activated Part 11 capabilities for regulated document processes. A typical use case is the review and approval of a GMP SOP. First, describe the lead document, the active version, the involved roles, and the point in time at which the organization begins using the approval for actual batch release.
For computerized processes in the manufacture of human medicinal products, EU GMP Guideline Chapter 4 and Annex 11 are key reference points. The European Commission continues to publish both texts in EudraLex Volume 4 in the January 2011 version. A clinical consent process, a medical device procedure, or a standard supply agreement requires individual assessment.
21 CFR Part 11 is added if the FDA-related electronic records and signatures described there are within the scope of application. The American manufacturer name or an international company is not sufficient for this. Note the result of the classification before calling technical settings a regulatory obligation.
2. Identify the actual account
The current product page distinguishes Part 11-specific eSignature functionalities from the complementary Validator for Life Sciences. The Life Sciences documentation consolidates signature functions, validation support, and SMS authentication as featured components. However, the scope of an individual contract cannot yet be determined from this information.
The developer support requires a Part 11-activated account and references commercial agreements rather than standard web plans. Personnel responsible for shipping both with and without this scope must have separate accounts. Therefore, it is insufficient merely for an employee to have access to a designated account.
Capture the account used in the process, modules, data transfer pathway, and integrations. Also verify the technical origin of the QMS system connection: is it using the approved account or an alternative? Document the actual state of the test and production environments. Configuration inheritance should be verifiable, not based solely on an administrator's memory.
3. Separate identity, authorization, and signature significance
Access to a document, authentication during signing, and authorization for approval address various questions. A person may technically be successfully authenticated yet still lack an approval role for this SOP. Therefore, define who validates identities, who assigns roles, and how delegation or resignation is handled.
The DocuSign support documentation distinguishes between Remote Signing and Embedded Signing. In the context described in Part-11, it refers to SMS for access and signature for Embedded Signing. For Remote Signing, several combinations are documented. By default, authentication is required again during signing; an alternative account setting defers authentication to access and session termination. Carefully verify the selected workflow, including cancellation and re-authentication.
In the FDA scope, § 11.50 and § 11.70 concern visible signature information and the relation to the data set. § 11.100 deals with, among other things, the upstream identity check. A suitable selection of the signature ground should be understandable for the signatory and reflect his actual action. A preset "approved" does not make a mere knowledge for professional examination.
4. Verify the validator's actual scope of coverage
The current Life Sciences document outlines QA testing conducted on a Part 11 example account across demo and production environments. The referenced monthly reports include test screenshots and results, representing valuable supplier information. However, these reports do not automatically indicate which of your templates, external recipients, QMS fields, or folders were reviewed.
Assign the received report to a specific version and your requirements. Document coverage, exclusions, and open points. The following standalone work aid prevents both unnecessary duplicate reviews and unverified acceptance of a general quality seal.
| Item under test | Available supplier certificate | Evidence to produce |
|---|---|---|
| Activated Part-11 Account | Documented account functions and test scope | Actual account in the shipping and integration pathway |
| Signature workflow | Verified Authentication and Signing Functions | Own roles, external recipients, and selected session options |
| Document version | General Processing and Integrity Functions | Correct SOP version prior to shipment and after recall |
| Interface | Evidence for specifically included integration functions | Mapping, error handling and restart for your actual interface |
| Retention | Documented storage and export functions | Required dataset, authorizations and future readability |
5. Test example: Five signatures, but only one appropriate closing endorsement
The example does not constitute a completed product test. For SOP-Q17 Revision 3, internal instructions require two authorized individuals: A performs the review, B provides approval. Only after both actions have been completed may the revision become effective within the QMS. The traceability must assign the document and signature context to the correct data set. This two-step sequence is a procedural example and not a universal requirement.
Three isolated test envelopes are assigned separate identifiers. The intended version is independently archived prior to test initiation. Thus, subsequent evaluation is not dependent on the version that inadvertently ends up in the envelope.
| Test case | Starting point | Expected professional judgment | Supporting record |
|---|---|---|---|
| E1 | Revision 3; A and B sign off appropriately | The process is fulfilled, provided that the feedback and assignment are consistent. | Final version, final dataset, envelope identifier and signature information |
| E2 | Revision 2; A and B fully sign off | Do not accept as approval from Revision 3 | Content/version comparison and documented defect findings |
| E3 | Revision 3; only A signed | Approval by B is missing; no efficacy established | Expected roles versus actually existing signatures |
| Copy of E1 | Content reviewed upon completion is verified and modified only if justified. | An altered copy shall not substitute for the unaltered original. | Source export, separate copy and results of integrity check |
6. Test the feedback into the QMS as a separate transition step
A successful signature process does not guarantee that the correct document has reached the intended location. Define the linkage between QMS document identifier, revision, and envelope identifier. A filename alone is often an insufficient association: the same name may refer to different content.
Proposed test scenarios include a interrupted reflux, a duplicate status message, and an outdated assignment. The expected response must be predefined: for example, a controlled repeat without duplicate activation or a visible error state. The technical implementation depends on the actual integration method employed.
In Embedded Signing, the manufacturer guidance requires consistent recipient data between the document transfer and the requested signature session. Verify this alignment using a deliberately differing test identifier. Log-in to the QMS and subsequent DocuSign authentication must not be considered equivalent control activities without explicit documentation. Retain records for both sides of the transition for the test.
7. Hold audit trail, signature information, and history as read by all users
The visible signature is only part of the evidence. Equally important are the person, timestamp, context, and reference to the signed version. DocuSign provides a Certificate of Completion, audit information, and manipulation detection. Define which of these elements are required for your process and ensure they remain collectively retrievable thereafter.
Do you check an export from the perspective of an employee who does not know the original process. Can he determine the valid version, classify the signatory and recognize the connection between document and signature? Does the planned technical integrity check work even after the transfer to the target store?
Conduct a change test exclusively on a designated copy. The original remains unchanged as a reference. A file comparison may reveal discrepancies; however, it does not automatically substitute the verification of signature information and its context. Furthermore, a printed copy is not a substitute for the complete electronic record.
8. Clarify retention prior to deletion or account change
The general eSignature assistance distinguishes between document deletion, metadata, and certain personal data. A configured retention rule can automatically flag documents for deletion. The guidance also outlines different options for shipped and received envelopes. Verify which of these apply to the specific Part-11 account in question.
Determine where the master dataset is stored: in the service environment, in the QMS, in an archiving solution, or in a defined combination. Identify responsible parties, required components, permitted deletion actions, and evidence of successful transfer. Prior to account closure, independently verify accessibility and readability without relying on the previous user account.
Technical standard retention periods are not regulatory retention periods. Chapter 4 distinguishes document types and their intended purposes; Annex 11 addresses accessibility and integrity of archived data. The presence of an active, visible transfer entry in service does not prove that the document and its required context have been preserved.
9. Evaluate changes based on their impact on the process
In addition to supplier releases, document templates, recipient roles, phone numbers, authentication methods, signing justifications, and retention rules may affect the validity of the evidence. Maintain a documented as-is baseline and assign changes to the relevant requirements. A new company name on the letterhead has different implications than a change to the QMS traceback process.
Use current supplier reports to determine remaining tests. Unchanged functions may also require retesting, for example if a new integration uses data differently. Conversely, full reexecution of all previous tests is not automatically the best approach for every release.
Describe the incident: Who recognizes a hanging envelope, assesses a faulty return and decides on a controlled alternative? Retrieving a signature is not a neutral repair if it changes version, time or approval meaning. The original finding and decision should remain comprehensible to each other.
10. Preparation and Checklist for QA and IT
For a SME, preparation should begin with an actual, representative document flow and a test copy. QA defines the meaning in the process of signatures. The process responsible party determines roles and authority. IT documents accounts, integrations, and operations. Document governance specifies which evidence must be retrievable in which system at a later stage.
Effort arises primarily due to different signature pathways, external signatories, unclear legacy records, and multiple document locations. A single template with defined roles must be managed differently from a combined workflow featuring automated document generation and automatic forwarding to multiple systems. Plan participation based on these transition points, not on the number of visible signature fields.
- Scope and document process with responsible roles demarcated.
- Actual in-use Part-11 account and ordered validator scope confirmed.
- Identity, authorization, and signature workflow applicable for release are traceable.
- Test version, negative cases, and acceptance criteria to be defined prior to testing.
- Recall, integration errors, and duplicate processing reviewed.
- Export with required context readable and properly linked to the correct dataset.
- Retention, exit, changes, and failure decisions in operation are governed.
Project experience and collaboration
Link the correct document version to the signer and the meaning of the signature
With your process team, we trace an intended Docusign workflow from the approved document to the signed version retrieved later. We check the account, authentication, interruption and meaning of the signature. An established workflow may need targeted checks. Unclear recipients or a missing document link call for a process decision first. With QA, we record the evidence expected and its limits. A completed envelope does not automatically constitute operational approval.
Frequently asked questions about DocuSign
Is DocuSign with Part-11 module automatically validated for our GMP process?
No. The activated module provides certain functions. Its evaluation must demonstrate that the account, document templates, roles, data flows, and operations are appropriate for the intended use. Therefore, first assess which requirements are already supported by appropriate supplier documentation. Supplement the remaining customer-specific justifications. Technical release serves as an initial step and is not a final approval report.
Can I send standard envelopes and Part 11 envelopes from the same account?
The current developer guidance specifies separate accounts for these two shipping methods. An activated Part-11 account is not simply an arbitrarily switchable shipping mode per document. Therefore, clearly define which account actually corresponds to the user and integrations in use. A targeted test with the technical sender helps identify whether an integration inadvertently uses the standard account.
Sources: [3]
Must each external signer have their own DocuSign account?
Not applicable to every documented authentication method. The current help text also covers SMS-based procedures without a dedicated signer account; remote and embedded signing offer different capabilities. Decide based on the specifically approved workflow. Additionally, verify identity confirmation, maintenance of contact information, and authorization privileges. Successful delivery of a code alone does not fully address these organizational considerations.
Must the password be re-entered for each individual signature field?
Not mandatory in every field. Docusign requires re-authentication at every signature and stamp in its standard Part 11-compliant accounts. With "Rapid Part 11 signing," as described in the developer guidance, re-authentication occurs only upon accessing the envelope and at the time of envelope completion; the vendor recommends coordination with your Quality Assurance team. Section 11.200(a)(1) mandates that for non-biometric signatures within a continuous period of controlled system access, all components must be verified for the first signature, and for subsequent signatures, at least one component that can be used exclusively by the authorized individual must be verified. Outside of such a continuous period, all components must be verified. Therefore, QA must evaluate the specific signing mode, including interruptions and resumptions.
Does the Validator for Life Sciences replace our own testing?
It can enable verified testing, but cannot unconditionally replace the entire internal process. The specification outlines tests conducted on a sample account. Compare the actual report against your configuration and the intended document workflows. An appropriate coverage may be applied; any missing tests, such as QMS traceability or a dedicated template, must be clearly justified and supplemented.
Is a Certificate of Completion the complete audit trail?
It is an important transactional record, but the completeness required depends on the document process. Verify the linkage to the actually signed content and the required signature information. Then test whether a subsequent reader can reconstruct the complete document. A certificate without the corresponding document or with an incorrectly assigned revision does not satisfy this own traceability requirement.
How can I check a change made to a document after the original review?
Keep the original export unchanged as a reference. Modify only a dedicated test copy and verify the intended manipulation detection as well as the target destination control. The expected outcome must be defined in advance. A modified copy must not be silently treated as the unaltered original for further use. Concurrently document which procedure verifies the signature information and document reference.
Can a completed signature authorize the incorrect SOP version?
Technically, a fully signed procedure may contain content that differs from what is expected based on technical requirements. Precisely for this reason, the required matrix includes the case of an outdated revision. Compare content and version identifier against an independently defined reference procedure. Do not accept the procedure as approval of the new revision solely because all signatures are present or file names match.
How long should signed documents remain in DocuSign?
There is no one-size-fits-all retention period applicable to all documents. First, determine the type of record, applicable requirements, and the relevant retention location. Then, align specific retention and deletion functions with these factors. If the service is used solely for the signature process, the intended data set must demonstrably function prior to any deletion or account closure that terminates access.
What documents should we gather prior to the validation project?
Useful are process descriptions, document examples, role lists, account assignments, module contracts, available validator reports, and a sketch of the filing locations and interfaces. Supplement known error cases and the desired business decision. This enables the team to early identify whether the main issue is the absence of supporting evidence or whether the process itself needs modification. The number of linked pathways typically has a greater impact on effort than a single signature field.
Sources and review date
As of October 6, 2026. Supplier reference: public Docusign product documentation and eSignature developer guidance; specific account, module, and contract coverage to be individually confirmed. Regulatory reference: Human Medicinal Product GMP and, if applicable, 21 CFR Part 11, eCFR as of October 2, 2026. This example is an internal work aid, not a completed product test.
- Docusign Life Sciences Modules for 21 CFR Part 11
- Life Sciences Module – Increase Efficiency and Simplify Compliance
- eSignature REST API: CFR Part 11 accounts
- eSignature REST API: Purging documents
- Docusign Product security
- European Commission: EudraLex Volume 4 – current directory
- EU GMP Annex 11: Computerised Systems, January 2011 revision
- EU GMP Chapter 4: Documentation, January 2011
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic Signatures
Sources checked: .
Ensure their signature process is traceable.
We help you define the actual DocuSign capabilities, evaluate existing supplier invoices, and implement missing evidence jointly with QA and IT.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

