How to Request an eSignature in Adobe Acrobat? (w/Examples) + FAQs

Yes, you can request a legally binding eSignature in Adobe Acrobat in under five minutes by opening your PDF, clicking All tools → Request e-signatures, adding recipient emails, placing signature fields, and hitting Send. The feature is powered by Adobe Acrobat Sign, which routes the document, captures signatures, and returns a sealed PDF with an audit trail. Every signature created this way is enforceable under the federal Electronic Signatures in Global and National Commerce Act (ESIGN Act, 15 U.S.C. §§ 7001-7006) and the Uniform Electronic Transactions Act (UETA), which 49 states have adopted.

The problem most senders run into is not the clicking — it is the legal plumbing underneath. A signature that looks fine on screen can still be tossed out if the sender skipped the ESIGN Act’s consumer consent disclosure, failed to keep a tamper-evident record under FINRA Rule 4511, or tried to sign a document that sits inside a statutory carve-out like a will, a codicil, or a notice of foreclosure. The consequence is real: a bounced contract, a voided closing, a malpractice claim, or a refused court filing.

According to Adobe’s 2024 Digital Trends report, organizations using Acrobat Sign close agreements 21 times faster than paper workflows, and Adobe processed more than 8 billion electronic and digital signatures across its cloud in the last reported year. That speed only pays off when the sender gets the setup right.

Here is what you will learn in this guide:

• 📝 How to send a PDF for signature using every Acrobat tier, including Reader, Standard, Pro, and Acrobat Sign Solutions.
• ⚖️ Which federal and state laws control whether your eSignature holds up in court.
• 🧭 How to route signers in order, in parallel, or in bulk using Mega Sign.
• 🛡️ How to lock down authentication with passwords, KBA, phone, and government ID checks.
• 🚫 The seven most common mistakes that void an otherwise valid eSignature request.

What an eSignature Request Actually Is in Adobe Acrobat

An eSignature request in Adobe Acrobat is a workflow that uploads a PDF to Adobe’s cloud, places signer fields on the page, emails a secure link to each recipient, and returns a sealed PDF plus a Certificate of Completion that logs every action. The workflow runs on Acrobat Sign, which is Adobe’s dedicated eSignature engine and the successor to EchoSign.

The request is legally distinct from a digital signature. A digital signature uses a cryptographic certificate issued by a Certificate Authority and binds the signer’s identity to a private key. An eSignature request in Acrobat captures intent through a typed, drawn, or image-based mark plus metadata like IP address, timestamp, and email verification. Both forms satisfy the ESIGN Act, but regulated industries like securities, aviation, and federal contracting sometimes require the stronger digital signature under 21 CFR Part 11 or FedRAMP rules.

The plain-English rule is simple: if a statute says “writing” or “signature,” an eSignature works. If the statute says “notarized,” “witnessed,” or “original,” you need extra steps like remote online notarization or a wet-ink original. The consequence of missing that distinction is a contract that courts refuse to enforce, which is exactly what happened in Bank of New York Mellon v. Roberts, where a sloppy electronic assignment delayed foreclosure for years.

A common misconception is that clicking “I agree” on a web form equals an Acrobat eSignature. It does not. Acrobat’s workflow captures a persistent, reproducible signature block with an audit trail, while a clickwrap often lacks the tamper-evident seal that courts look for under the Uniform Electronic Transactions Act § 12.

The Legal Backbone: ESIGN, UETA, and State Law

The ESIGN Act became federal law in 2000 and says electronic signatures cannot be denied legal effect solely because they are electronic. It preempts state law unless the state has adopted UETA or a “substantially similar” statute. The consequence of ignoring ESIGN’s Section 101(c) consumer consent rule is that a consumer contract — think gym memberships, loan documents, or insurance applications — can be unwound by the consumer at any time.

UETA, drafted by the Uniform Law Commission, has been adopted in every state except New York, which instead passed its own Electronic Signatures and Records Act. Illinois uses the Uniform Electronic Transactions Act as enacted in 2021, replacing the older Electronic Commerce Security Act. The consequence of picking the wrong controlling statute is the same as picking the wrong venue: your e-signature clause may not do what you think.

A real-world example: Maria, a Manhattan estate planner, sends a client retainer through Acrobat. Because New York follows ESRA rather than UETA, her retainer is enforceable, but if she tried to send a will the same way, New York EPTL § 3-2.1 would void it — wills still require wet ink and two witnesses.

A common misconception is that UETA covers everything. It does not. UETA § 3(b) carves out wills, testamentary trusts, and some UCC Article 3 negotiable instruments. Those carve-outs are mirrored in ESIGN § 103.

Before You Click Send: Preparing the PDF

Preparation decides whether the signing experience feels seamless or frustrating. Start with a clean, flattened PDF under 25 MB — the hard ceiling for a single Acrobat Sign transaction is 10 MB per file or 25 MB per transaction on the web tier. The consequence of an oversized file is a silent upload failure that wastes a transaction credit on paid plans.

Flatten form fields you do not want signers to edit by choosing Print → Adobe PDF or File → Save As Other → Flattened PDF. If you skip flattening, Acrobat may auto-detect form fields using its Sensei AI engine and place signer blocks in the wrong spots. The consequence is a signer who signs the wrong line, which can be grounds for rescission under Restatement (Second) of Contracts § 155.

A concrete example: David, a commercial real estate broker in Austin, forgot to flatten a lease amendment. Acrobat Sensei auto-tagged the landlord’s initial box as the tenant’s signature field, and the tenant signed in the landlord’s spot. The landlord had to reissue the entire package, delaying rent commencement by 11 days.

A common misconception is that Acrobat’s auto-detect is perfect. It is good, not flawless. Always preview placement before hitting Send.

Choosing the Right Acrobat Tier

The consequence of picking the wrong tier is either paying for seats you do not need or hitting a ceiling mid-project. A solo practitioner rarely needs Acrobat Sign Solutions, but a 50-person HR team absolutely does.

Step-by-Step: Requesting an eSignature in Acrobat Pro (Desktop)

The desktop workflow is the most feature-rich. Open the PDF in Acrobat Pro, then follow these nine steps.

1. Click All tools in the left rail, then select Request e-signatures.
2. In the recipient panel, enter each signer’s email and choose their role — Signer, Approver, Form Filler, Certified Recipient, or Delegator.
3. Toggle Complete in Order to route sequentially, or leave it off for parallel routing.
4. Add an optional message and a due date; Acrobat lets you set auto-reminders at 1, 3, or 7-day intervals.
5. Click Specify Where to Sign, and Acrobat will either auto-detect fields or open the drag-and-drop field editor.
6. Drag Signature, Initials, Date Signed, Name, Email, Company, Title, Text Field, Checkbox, Dropdown, Radio Button, or Attachment fields onto the page.
7. Assign each field to the correct recipient using the dropdown at the top of the field properties panel.
8. Add authentication under More Options: password, Knowledge-Based Authentication (KBA), phone, or government ID verification.
9. Click Send. Acrobat emails each signer a secure link and tracks status in the Agreements dashboard.

The consequence of skipping the role assignment in step 7 is a shared field that either signer can complete, which breaks the audit trail and opens a dispute window under UETA § 9.

Field Types and When to Use Each

Every field type carries a different evidentiary weight. A Signature field captures the handwritten-style mark and the signer’s typed name, IP, and timestamp. An Initials field is shorter but carries the same legal weight under ESIGN § 106(5). A Date Signed field auto-fills and cannot be back-dated by the signer, which matters for statute-of-limitations calculations.

Use a Text Field for free-form data like a driver’s license number, but pair it with input validation (regex, numeric, or date) to prevent garbage entries. The consequence of an unvalidated text field is dirty data that downstream systems like Salesforce or Workday reject on import.

A named example: Priya, an HR manager at a Chicago logistics firm, uses a regex-validated Text Field for Social Security numbers on I-9 forms. The validation catches a typo before submission, saving her from an IRS Form W-2 correction later.

A common misconception is that checkboxes are interchangeable with radio buttons. They are not. Radio buttons enforce single-selection groups, which matters for compliance attestations like HIPAA authorization forms.

Routing Options: Sequential, Parallel, Hybrid, and Mega Sign

Sequential routing sends the document to Signer 1, then Signer 2, then Signer 3, in order. Parallel routing sends to everyone at once. Hybrid routing lets you group signers — for example, both co-founders must sign before the investor sees it. Mega Sign sends the same document to up to 300 recipients at once, each getting a personalized copy.

The consequence of choosing the wrong routing is either a bottleneck or a compliance gap. Sequential routing is mandatory for documents that require counterparty acceptance before a guarantor signs, like an SBA 7(a) loan.

A named example: James, a franchise attorney in Atlanta, uses hybrid routing so the franchisee and spouse sign first, then the franchisor counter-signs. Without hybrid routing, the franchisor would receive a half-executed agreement, which violates the FTC Franchise Rule disclosure timing requirement.

Requesting an eSignature on the Web (Acrobat Online)

The web flow at acrobat.adobe.com mirrors the desktop flow but adds drag-and-drop uploads and native Microsoft 365 integration. Log in, click E-sign → Request e-signatures, and upload the PDF. From there, the field placement and recipient workflow are identical.

The web tier is the best choice for chromebooks, locked-down enterprise laptops, and anyone working outside the Adobe Creative Cloud desktop app. The consequence of using the web tier without a paid Acrobat plan is a monthly cap of two free requests per user under the free Acrobat Reader tier.

Mobile: iOS and Android

The Acrobat Reader mobile app supports sending for signature on both iOS 15+ and Android 9+. Tap Tools → Request Signatures, add recipients, and place fields by tapping the page. Mobile field placement is less precise than desktop, so review on a larger screen before sending high-stakes documents.

A named example: Elena, a traveling sales rep in Phoenix, closes a software deal from her iPhone at the airport. She uses the mobile Request Signatures flow to send a two-signer MSA to the buyer and the buyer’s CFO before boarding.

The consequence of relying solely on mobile for complex multi-party agreements is a mispaced field that delays closing. Mobile works best for short, standardized documents.

Authentication: Locking Down Who Actually Signs

Authentication is the single biggest factor in whether your eSignature survives a challenge. Acrobat Sign offers five tiers, each with a different evidentiary weight under the Federal Rules of Evidence 901.

• Email verification — default, lowest weight, but sufficient for most B2B contracts.
• Password — sender sets a shared password, delivered out-of-band.
• Knowledge-Based Authentication — signer answers four questions pulled from public records; required for IRS Form 8879 e-filing.
• Phone authentication — one-time code sent via SMS or voice call to a pre-specified number.
• Government ID verification — signer uploads a driver’s license or passport, and Adobe’s AI matches it to a live selfie.

The consequence of defaulting to email-only authentication on high-value contracts is a weak evidentiary record. In IO Moonwalkers, Inc. v. Banc of America Merchant Services, a North Carolina court analyzed whether an electronic acceptance was properly authenticated — the stronger the authentication, the harder the challenge.

A named example: Robert, a CPA in Tampa, uses KBA for every IRS Form 8879 authorization because the IRS e-signature guidance in Publication 1345 specifically requires it for remote transactions.

A common misconception is that KBA is bulletproof. It is not. The FTC warned in 2022 that KBA’s reliance on credit-header data is weakening as more data breaches expose the underlying answers.

Three Real-World Scenarios

Below are the three most common eSignature request scenarios and the practical consequence of each.

Scenario 1: Real Estate Purchase Agreement

Scenario 2: Employee Onboarding Package

Scenario 3: Attorney-Client Engagement Letter

Mistakes to Avoid When Requesting an eSignature

These errors surface again and again in disputed contracts. Each one has a specific, avoidable consequence.

• Skipping the ESIGN consumer consent disclosure. The consequence is an unenforceable consumer contract under 15 U.S.C. § 7001(c), which a consumer can unwind at any time.
• Sending a statutorily excluded document. Wills, codicils, adoption papers, and divorce decrees are carved out of UETA § 3(b); the consequence is a void document.
• Using the wrong signer role. A Form Filler cannot sign — only a Signer or Certified Recipient can; the consequence is a missing signature that blocks execution.
• Forgetting to flatten form fields. Acrobat Sensei auto-tags the wrong spots; the consequence is a signer who signs the wrong line, which courts may treat as a material mistake.
• Defaulting to email-only authentication on high-stakes contracts. The consequence is a weak evidentiary record that fails FRE 901 scrutiny.
• Setting no expiration date on the agreement. The consequence is a document that stays signable for years, which can be signed after a material term has changed.
• Ignoring state carve-outs. Louisiana, Puerto Rico, and some tribal jurisdictions follow different rules; the consequence is unenforceability in the specific forum.
• Storing the signed PDF only in Acrobat’s cloud. The consequence is a records-retention violation under SEC Rule 17a-4 for broker-dealers, who must preserve records in WORM format.
• Emailing the signed PDF without encryption. The consequence is a potential HIPAA breach under 45 CFR § 164.312 for covered entities.

Do’s and Don’ts

Follow these rules to keep every request clean, compliant, and enforceable.

Do’s

• Do capture the ESIGN consent disclosure on the first screen for any consumer transaction, because Section 101(c) requires it before any electronic record is delivered.
• Do use sequential routing for any multi-party agreement where one party’s signature is a condition precedent to another’s, because parallel routing breaks the contractual order.
• Do enable KBA or government ID verification for any document where identity fraud would cause material harm, because stronger authentication creates a stronger evidentiary record.
• Do export the signed PDF and Certificate of Completion to your firm’s document management system within 24 hours, because Acrobat’s cloud is not a system of record under most records-retention policies.
• Do set an expiration date of 14 to 30 days for most transactions, because stale signatures are harder to defend when market or legal conditions have changed.
• Do test the workflow on yourself first by adding your own email as Signer 1, because you will catch field misplacement before the client does.

Don’ts

• Don’t send wills, codicils, or testamentary trusts through Acrobat Sign, because UETA § 3(b) and state probate codes still require wet ink.
• Don’t re-use a shared password across multiple signers, because the audit trail cannot distinguish one signer from another.
• Don’t skip the delegation role when a signer may route to an assistant, because an unauthorized delegate signature is voidable under agency law.
• Don’t rely on mobile for complex multi-page, multi-signer agreements, because field placement precision suffers on small screens.
• Don’t store only the Acrobat audit trail without the signed PDF, because a standalone audit trail without the signed document is evidentiarily weak.
• Don’t forget to disable auto-save of draft agreements on shared workstations, because a draft with confidential terms can leak to the next user.

Pros and Cons of Acrobat’s eSignature Request Feature

Acrobat Sign is powerful but not perfect. Here are the tradeoffs.

Pros

• Native PDF integration — Acrobat is the reference PDF app, so fidelity is better than any competitor when documents contain complex forms or headers.
• Federally compliant — Acrobat Sign is FedRAMP Tailored authorized, SOC 2 Type II, ISO 27001, and HIPAA-ready.
• Strong authentication stack — five tiers of signer verification, including government ID matching through Adobe’s Sensei AI.
• Bulk send via Mega Sign — up to 300 recipients per transaction with per-signer personalization.
• Deep Microsoft 365 and Salesforce integrations — native Teams, Outlook, and Word add-ins mean senders rarely leave their primary workflow.

Cons

• Transaction caps on lower tiers — Acrobat Standard caps at 2 signers; power users need Acrobat Sign Solutions.
• Pricing complexity — Acrobat Sign pricing differs across individual, team, and enterprise SKUs, and transaction credits vary.
• UI learning curve — the shift from classic “Fill & Sign” to “Request e-signatures” confuses long-time users.
• Limited offline signing — the signer must be online; paper fallback is manual.
• No built-in remote online notarization — for notarized documents you need a partner like Notarize.com or Proof.

Industry-Specific Rules You Cannot Ignore

Some industries layer extra rules on top of ESIGN and UETA. Miss one, and the signature is technically valid but regulatorily defective.

Financial Services

Broker-dealers must preserve signed records in WORM (Write-Once-Read-Many) format under SEC Rule 17a-4 for at least six years. FINRA Rule 4511 requires that records be accurate, accessible, and immediately producible. Acrobat Sign’s cloud alone does not satisfy this; firms need a compliant archive like Smarsh or Global Relay.

The consequence of ignoring 17a-4 is a FINRA enforcement action; in 2022, the SEC fined 16 firms a combined $1.1 billion for recordkeeping failures per the SEC press release.

Healthcare

HIPAA-covered entities must use Acrobat Sign’s HIPAA-ready configuration, sign a Business Associate Agreement with Adobe, and encrypt PHI both in transit and at rest per 45 CFR § 164.312. The consequence of sending PHI through a non-HIPAA Acrobat account is a reportable breach under the HHS Breach Notification Rule.

Life Sciences and FDA-Regulated Industries

Clinical trial and pharmaceutical records require compliance with 21 CFR Part 11, which demands closed-system controls, validated audit trails, and unique identifiers. Acrobat Sign offers a Part 11-compliant configuration, but the customer must validate it. The consequence of an unvalidated system is a Form 483 observation from the FDA.

Tax and IRS e-Filing

The IRS requires KBA for remote signatures on Forms 8878 and 8879, per Publication 1345. The consequence of a missing KBA step is a rejected e-file authorization and a malpractice risk for the preparer.

Acrobat Sign vs. Competitors

Buyers often ask how Acrobat Sign stacks up against alternatives. The honest answer depends on volume, integrations, and PDF fidelity needs.

The consequence of picking purely on price is a feature gap that costs more later. A healthcare client that chose a non-HIPAA platform later paid for a migration to Acrobat Sign after a breach-notification scare.

Recapping Key Court Rulings

Courts continue to reinforce that properly executed eSignatures are enforceable. A short recap helps senders understand the evidentiary bar.

• In Barwick v. GEICO, the Arkansas Supreme Court upheld an electronically signed arbitration clause because the insurer produced a clear audit trail.
• In IO Moonwalkers, Inc. v. Banc of America Merchant Services, the North Carolina Court of Appeals examined whether click-through acceptance was properly attributable to the signer — authentication was decisive.
• In Newton v. American Debt Services, the Ninth Circuit refused to enforce an electronic arbitration clause because the provider could not show the consumer actually assented.

The through-line: an eSignature is only as strong as the audit trail and authentication behind it. Acrobat Sign’s Certificate of Completion is designed to meet that bar, but the sender must use the right settings.

Managing Sent Agreements and the Audit Trail

Every sent agreement lives in the Manage tab of Acrobat or on the Acrobat Sign dashboard. From there, senders can remind, cancel, modify, delegate, or download the signed PDF and audit trail. The audit trail captures signer email, IP address, timestamps for view and sign, authentication method, and any delegation events.

The consequence of not regularly downloading completed agreements to an internal system is a records-retention gap. Adobe retains agreements according to your account’s retention policy, but a corporate records schedule may demand longer or shorter retention.

A named example: Sophia, a compliance officer at a Boston biotech, exports every signed agreement nightly to her firm’s Veeva Vault because FDA inspectors expect documents produced from a validated system, not from an Acrobat browser tab.

A common misconception is that canceled agreements disappear. They do not. A canceled agreement remains in the audit log, and that log is discoverable in litigation.

Frequently Asked Questions

Is an Adobe Acrobat eSignature legally binding in the United States?

Yes. Acrobat eSignatures satisfy the federal ESIGN Act and UETA in 49 states, plus New York’s ESRA, making them enforceable in courts and regulatory proceedings across the country.

Can I request an eSignature using the free Adobe Acrobat Reader?

No. The free Reader lets you sign documents sent to you, but sending for signature requires Acrobat Standard, Pro, or an Acrobat Sign Solutions subscription.

Do I need Acrobat Pro to use the full Request eSignature feature?

Yes. Acrobat Pro unlocks advanced routing, Mega Sign, KBA, government ID verification, and unlimited fields, while Standard is capped at two-signer transactions.

Can I send wills or trusts through Acrobat Sign?

No. UETA § 3(b), ESIGN § 103, and state probate codes exclude wills, codicils, and most testamentary trusts; those still require wet ink and witnesses.

Does Acrobat Sign support bulk sending to hundreds of recipients?

Yes. The Mega Sign feature sends the same document to up to 300 recipients at once, each signing a personalized copy with its own audit trail.

Can I require government ID verification on my signers?

Yes. Acrobat Sign’s Government ID authentication uses AI to match an uploaded ID to a live selfie, satisfying higher-assurance use cases.

Is Acrobat Sign HIPAA compliant?

Yes. Adobe offers a HIPAA-ready configuration, signs a Business Associate Agreement, and encrypts PHI at rest and in transit under 45 CFR § 164.312.

Can I cancel an agreement after I send it?

Yes. You can cancel from the Manage tab at any time before all signers complete, and the cancellation is logged in the audit trail for later reference.

Does Acrobat Sign meet SEC Rule 17a-4 recordkeeping requirements?

No. Acrobat Sign alone does not provide WORM storage; broker-dealers must export signed agreements to a compliant archive like Smarsh or Global Relay.

Can signers use mobile devices to sign?

Yes. Signers receive a link that works on any modern browser and on Acrobat Reader mobile apps for iOS 15+ and Android 9+.

Is Knowledge-Based Authentication required for IRS Form 8879?

Yes. IRS Publication 1345 requires KBA for remote electronic signatures on Forms 8878 and 8879 before an Electronic Return Originator can e-file.

Can I set an expiration date on an eSignature request?

Yes. Under More Options, you can set an expiration between 1 and 365 days, after which the agreement auto-cancels and is logged as expired.

Does Acrobat Sign integrate with Microsoft 365 and Salesforce?

Yes. Adobe ships native add-ins for Word, Outlook, Teams, and Salesforce, plus a REST API for custom integrations in both Sandbox and Production environments.

Can I add multiple signers with different roles?

Yes. Acrobat supports Signer, Approver, Form Filler, Certified Recipient, and Delegator roles, each with distinct permissions and audit-trail entries.

Is remote online notarization available inside Acrobat Sign?

No. Acrobat Sign does not include native RON; customers must use a partner like Notarize.com or Proof to meet state notary requirements.