IT systems · Practical guide

Adobe Acrobat Sign for GxP: validating electronic signatures

A visible signature in a PDF does not establish a controlled approval process. For Adobe Acrobat Sign Solutions, check identity, authentication, signature meaning, record linkage and retrieval together. Verify the licensed plan and the effective settings of the sending group. Use the BioPharma functions in scope to connect Adobe's documentation to your business requirements.

Table of contents

At a glance

What does Acrobat Sign need for a signature workflow subject to Part 11?

A Part 11 signature process needs verified identities, appropriate signature components, effective authentication, a clear signature meaning and a permanent link to the signed record. Demonstrate these controls for the configured Acrobat Sign workflow. BioPharma settings can support part of the process, but the plan, group, form and recipient authentication method must fit. Enabling a menu or downloading a validation package is insufficient.

  • Acrobat Sign Solutions and specific functions such as simple form filling or signing a PDF document differ.
  • The current functional documentation restricts Enforce identity authentication to Enterprise.
  • Demonstrate separate verification of identity, registration, and professional authorization for signature.
  • Retain signed document, audit report, and required original records.

Which Adobe solution and which plan are intended?

Adobe provides multiple methods for filling out and signing documents. Fill & Sign in Acrobat, for example, allows the insertion of a custom signature. The scope considered here, however, is a configured signature process using Acrobat Sign Solutions along with the required administrative controls. Ownership of Acrobat Pro does not automatically confirm this functionality.

In the BioPharma functions, a careful review is warranted: the older overview page lists Business and Enterprise. The more specific documentation for Enforce identity authentication, dated 1 September 2026, restricts this function to Enterprise. Signing Reasons has its own availability specification. Therefore, verify the tariff, release, and actually available settings for your account.

The receiving method may also have additional requirements. Phone-based authentication is currently listed as a paid feature of Acrobat Sign Solutions; required transactions must be obtained directly from Adobe Sales prior to usage. Review such quotas and contractual terms early to ensure your release logic does not depend on an unavailable pathway.

Sources: [1] [2] [3] [4] [5]

Part 11, Annex 11, and eIDAS address various questions

Part 11 should be evaluated in relation to the affected electronic records, signatures, and underlying FDA requirements. For the considered GMP application in human medicinal product manufacturing, Annex 11 is also relevant. Therefore, a general contractual signature and a quality-related release may have different requirements.

eIDAS establishes the European legal framework for electronic signatures. A qualified electronic signature, according to EU classification, has the same legal effect as a handwritten signature. However, this statement neither replaces the assessment of FDA applicability nor the validation of your release process. Similarly, a QES is not automatically required for every activity solely due to Part 11.

The following work matrix separates requirements that are frequently conflated in projects. It serves as a guide for requirement capture, not a complete regulatory checklist.

Workflow matrix for a regulatory relevant signature process
QuestionClarifying requirementSuitable evidence
Who is the person? Verify identity prior to assignment of the electronic signature. Documented procedure and personnel assignment.
Can she decide? Define professional responsibility and representation. Authorization and approved responsibility.
How is it signed? Components, session context, and required authentication determine. Configuration and appropriate positive/negative tests.
What does the signature mean? Clearly express examination, approval or other meaning. Visible, technically appropriate signature text.
Which version is intended? Sign the signature firmly and directly to the relevant record. Version, document reference and retrievable proof.
What is retained? Record, sign-off attribution, and required metadata to be retained. Verified complete and legible retrieval.

Sources: [9] [10] [12] [13]

Identity first to be clarified, targeted authentication to be enforced

A repeated correctly entered password does not confirm how the original identity was verified. Part 11 requires an individual assignment and identity verification prior to the establishment or recognition of an electronic signature. Control internal and external personnel, as well as the revocation of their authorizations.

Identity authentication enforcement includes separate triggers upon opening, at the signature field, and upon completion. Supported methods include Adobe Sign authentication, telephone/SMS, and one-time code via email. When a different assigned method is specified, the process proceeds as per Adobe's default behavior without enforcing the additional mandatory authentication. Your configuration must account for this.

Adobe describes E-Mail-OTP as a single-factor authentication method; furthermore, limitations apply to telephone and E-Mail-OTP when an embedded iframe signature is used with an active authentication requirement. Select the full signature pathway appropriate to the need. For non-biometric electronic signatures, the two identification components under 21 CFR 11.200 and its session rules must be specifically evaluated; this does not imply a blanket requirement to disable all three Adobe triggers.

Sources: [9] [3]

Further reading:

Make the signature on the form binding.

21 CFR 11.50 requires, for signed records, among other things, name, date, and time, as well as the meaning of the signature. Therefore, it is essential to clearly define what is affirmed by signing. "Reviewed" and "Approved" represent distinct decisions. A form that allows the same individual to perform both actions must align with the intended role model.

Signing Reasons can be provided from a predefined list or as free-text input. The function can be optionally enabled or required, depending on configuration. Verify the configured setting and actual display in the result. Fields with initial values are excluded from this functionality; a stamp used as a signature, as indicated in the BioPharma Overview, does not include Signing Reasons.

Use clear and unambiguous justifications for a controlled process. Verify whether an inappropriate selection is technically precluded or identified during the process. A signed statement should also remain understandable outside the original browser window. This applies in particular to exported documents that are later used for review or retention.

Sources: [9] [4] [2] [12]

Control account, group, and shipping route together

BioPharma settings may apply at both account and group levels; group values can override account values. The manufacturer's guide outlines the significance of the sending group in the signature workflow. Therefore, document not only a central setting but also the groups and pathways through which relevant documents are actually sent.

Review forms, recipient assignments, and, if applicable, integrations with the intended user. An unregulated contract process may follow different rules; however, a GMP-related activity must reliably proceed through the designated workflow. Also test changes that a sender may make prior to transmission. The allowable options remain part of your requirements.

If delegation or substitution of a signer is authorized, the individual designated must have the requisite technical competence. The handbook describes delegation as a configurable process; mere technical access alone does not establish release authority. Maintain consolidated records of standing authorization rules, training, and individual accountability. Shared access is not an appropriate substitute for a personal signature.

Sources: [2] [7] [9]

Combine audit report with signed PDF containing the correct documentation.

Acrobat Sign provides an Audit Report for agreements. This report describes events occurring during the signing process; it is not automatically equivalent to the complete change history of the system in which the technical data were generated. Adobe associates the signed document with the Audit Report through the transaction ID and retrieval as separate PDF files.

Define which components must be stored together and how a reviewer can identify the association. Verify during export the actual document status, signer, significance, time stamps, and associated report. A failed import into your document management system shall not be considered a successful document archiving. Also test re-pickup, duplicate detection, and assignment to your internal document number.

The signed PDF does not necessarily replace the original GMP dataset. For dynamic laboratory records, necessary data and metadata may extend beyond a static report. The FDA explicitly distinguishes between original records, faithful copies, and static and dynamic formats. Therefore, determine whether the PDF itself constitutes the authoritative record or merely a derived representation. A signature does not rectify a previously incomplete data selection.

Sources: [6] [7] [9] [11]

Further reading:

Example: electronically approving a validation report

This example does not describe a completed Adobe test. A small and medium-sized enterprise wishes to electronically sign off an approved validation report by an internal reviewer and an authorized approver. The approved template specifies the intended use of each signature. The report is sent to the designated group and subsequently stored in the designated audit reporting system.

For this example process, the desired authentication triggers are intentionally defined. Other processes may require a different justified configuration. The following test concepts evaluate normal operation and key failure paths; acceptance criteria are pre-negotiated with Quality and IT.

Example: Test ideas for report, identity, and signature verification
Test approachExpected effectSuitable evidence
Perform the intended normal scenario The correct individuals sign the correct version with appropriate meaning. Document, active settings, and result files.
Attempt to use an incorrect or revoked permission No unauthorized personal authorization. Identity/Role status and observed workflow.
Select another permitted shipping method The required rules remain in effect or the pathway is excluded. Group, recipient method and authentication events.
Assign an unsuitable receiving method The configuration prevents an undetected loss of required control. Negative testing and, if necessary, required correction.
Exclude signature origin or use incorrect field The required significance cannot be implicitly waived. System behaviour for mandatory fields and final visible signature block.
Interrupt storage connection An incomplete transfer remains detectable and is monitored and subsequently retrieved. Failure state, repetition, and unambiguous assignment.
Recall Archived Process The report and signature confirmation are complete and legibly linked. Deletion by the intended role within the target system.

Sources: [3] [4] [7] [9] [12]

What the Adobe Validation Package delivers and what remains with you

Adobe describes a package featuring customizable validation templates, such as for requirements, configuration, testing, and result reporting. The public description assumes the execution of a configured enterprise service with SAML settings for internal users. The templates are to be tailored by the customer to its specific strategy and executed accordingly; download of the templates does not imply a successful test.

Review whether the considered cases align with your internal and external signatories, integrations, and document types. Add missing requirements and document any deviations. The specific version and configuration mapping of the evidence should be clearly visible. A manufacturer package can reduce duplicate efforts without replacing your technical acceptance decision.

Name the process owner, quality assurance, account administration, and identity service or repository owner. Within the scope of Part 11, organizational prerequisites also apply, including the declaration to the FDA as required under 11.100(c). This declaration and the assignment of individual accountability do not arise merely by enabling the BioPharma functions.

Sources: [8] [9] [12]

Plan operational and maintenance efforts based on your signature workflows

Determine the effort primarily based on the number and diversity of processes: internal or external personnel, different identity services, multiple user groups, signature types, templates, and connected archives. Clarify these variations prior to estimation. A seemingly simple process involving external identification and manual document placement may require more coordination than a standardized internal workflow.

Plan time for technical requirements, account configuration, testing, training, and deviation handling. Also clarify cost-bearing authentication transactions and required manufacturer documentation. Flat fees or project weeks cannot be derived from the product name alone. Start with a clearly defined process where roles and records are already established.

In operation, changes to groups, templates, identity service, and integration require evaluation. Determine which controls need to be re-verified and how ongoing activities are managed. Define retention, authorized deletion, and access procedures during employee turnover or contract termination. A persistently accessible cloud-based interface must not become the sole unarticulated assumption in your documentation strategy.

Sources: [5] [8] [12] [9]

Release checklist for the signature process

This workflow guide links technical settings to operational procedures. Capture open items as specific requirements. A robust project status demonstrates not only screenshots of activated options, but also their actual impact on the end-users, documents, and shipping routes.

  • Document types, recordkeeping obligations, and signature requirements are determined.
  • Confirm Acrobat Sign Tariff, Enterprise Features, and Transaction Quotas.
  • Identity verification, individual assignment, and professional authorization definition.
  • Supported recipient methods and selected authentication triggers are verified.
  • Control sender-defined group rules and potential modifications.
  • Define the significance of signatures and specify appropriate signature fields as binding.
  • Consider delegations, rejections, and revoked authorizations.
  • Link transaction ID, document version, and audit report for traceability.
  • Original records, export, storage, and retrievability clarify.
  • Evaluate results and deviations; assign operation, changes, and responsibility.

Sources: [9] [12]

Project experience and collaboration

Trace the signature process from sending the document through to retention

Who signs which declaration, and in which version of the document? We use that question to examine your Acrobat Sign process, including identity, permissions, signing and subsequent storage of the necessary evidence. Focused checks may improve an existing workflow. For a new implementation, we first clarify its business purpose and the applicable framework. Your designated owners decide how the process will operate.

Frequently asked questions about Adobe Acrobat Sign

Does Acrobat Pro or Fill & Sign suffice for a Part 11 process?

The product name or a visible signature is insufficient as evidence. Verify that the functions required by your intended process are available. Enterprise-specific help currently limits "enforce identity authentication"; telephone-based authentication also has its own licensing requirements. Therefore, an existing Acrobat Pro license does not confirm the availability of these features.

Sources: [1] [3] [5]

Are BioPharma settings also available in the Business plan?

Supplier declarations vary by function and document version. The older overview distinguishes between Business and Enterprise; the more recent version, related to Enforce Identity Authentication as of September 2026, lists only Enterprise. Signing Reasons has a separate designation. Confirm the required functions for your agreement and verify their impact within the account.

Sources: [2] [3] [4]

Does each person have to enter their password several times?

Not a one-size-fits-all approach for every process. Adobe provides triggers upon opening, at the signature field, and at completion. The triggers required depend on your specific requirements and the signature concept. For non-biometric signatures, 21 CFR 11.200 distinguishes between controlled continuous sessions and other scenarios. Derive a justified configuration and appropriate testing strategies accordingly.

Sources: [3] [9]

Is an email containing a one-time code considered a secure method of identity verification?

The mere use of a single-factor authentication method does not constitute a prior verification of the real person. Adobe classifies email-based one-time passwords (OTP) as a single-factor authentication method because both the notification and the code are delivered to the same email address. Therefore, identity verification, access control, and signature components must be evaluated independently. The overall workflow should be selected in accordance with the required level of reliability and regulatory requirements.

Sources: [3] [9]

What happens when an authentication method is unsupported?

According to the current Adobe help documentation, the process can proceed normally, without enforcing identity authentication for this recipient. Therefore, verify the allowed methods and sender options. Specifically test such a scenario when re-authentication is part of your requirement; in that case, activation of a group option alone is not sufficient validation evidence.

Sources: [3]

Is a qualified electronic signature automatically compliant with Part 11?

No. QES and Part 11 relate to distinct regulatory frameworks. The specific legal effect of a QES under eIDAS does not address all questions regarding system validation, records, responsibilities, or your release process. Therefore, both requirements should be evaluated separately. Conversely, Part 11 does not establish a general obligation for QES with every electronic signature.

Sources: [13] [9]

Are initials or a stamp an alternative to Signing Reasons?

The documented function of Signing Reasons applies to electronic and digital signature fields, not to initial fields. The BioPharma overview also excludes a stamp used solely as a signature. Therefore, verify your actual form. If a meaning is required, it must be unambiguously and subsequently traceable within the intended signature workflow.

Sources: [4] [2] [9]

Does the signed PDF suffice without an Audit Report?

Not automatically. Events occurring during the signing workflow are documented separately by Adobe in the corresponding Audit Report; the transaction ID links it to the signed PDF. Retain both records together if your audit evidence must include these events. Verify export and assignment at the conclusion of a completed transaction, rather than relying solely on the visible signature image.

Sources: [7] [6] [11] [9]

Does the Adobe validation package render its own tests obsolete?

No. Adobe describes templates that are to be customized and executed for customer deployment. The specified Enterprise-/SAML framework must align with your setup. Enhance your forms, groups, external recipients, and integrations. Release is based on evaluated results and deviations, not on the existence of a template repository.

Sources: [8] [12]

What due diligence should a small and medium-sized enterprise perform prior to purchasing?

Describe a specific release process including document type, signatories, roles, identity pathway, and storage location. Then clarify required tariffs, transactions, and technical integrations with Adobe or the partner. Quality assurance and IT should jointly evaluate the requirements. This ensures visibility into the required functionalities and the specific contributions your organization must provide.

Sources: [5] [8] [9] [12]

Sources and review date

As of October 6, 2026. Technical statements refer to the officially designated Adobe documentation and their respective functional limitations. For Enforce identity authentication, the specific documentation from September 2026 is referenced. Regulatory reference basis: Human medicinal product GMP and relevant FDA records; eIDAS is treated separately. Tables, checklist, and test example are standalone planning aids.

  1. Adobe: Fill and sign documents in Acrobat on the web
  2. Adobe: Configure bio-pharma settings
  3. Adobe: Enforce identity authentication
  4. Adobe: Signing reasons
  5. Adobe: Configure phone authentication
  6. Adobe: Configure the content of your Audit Reports
  7. Adobe: Acrobat Sign Handbook for FDA-regulated organizations
  8. Adobe: 21 CFR Part 11 Validation Package
  9. eCFR: 21 CFR Part 11 – Electronic Records; Electronic Signatures
  10. FDA: Part 11 – Scope and Application
  11. FDA: Data Integrity and Compliance With Drug CGMP, December 2018
  12. European Commission: EU GMP Annex 11, January 2011 revision
  13. European Commission: Explanation on eSignature and eIDAS

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Define the signing process prior to configuration in a clear and structured manner.

We support you in establishing identities, release significance, and records within a traceable audit framework. Daniel Herrmann Consulting aligns its approach with your specific process and the actual Adobe functionalities available.

  • 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.

Send a project enquiry Customer testimonials →