How to Request an eSignature in DocuSign (w/Examples) + FAQs

You request an eSignature in DocuSign by uploading your document, adding recipients with their email addresses, placing signature and other fields on the document with the drag-and-drop tagger, and then clicking Send. The recipient receives an email, reviews the file, adopts a signature, and completes the signing ceremony inside a browser or the mobile app, producing a legally binding record under federal law.

Federal enforceability comes from the ESIGN Act of 2000, which gives electronic signatures the same legal weight as wet-ink signatures across interstate commerce. At the state level, 49 states follow the Uniform Electronic Transactions Act (UETA), while New York applies its own Electronic Signatures and Records Act (ESRA). Missing a required field, skipping authentication, or sending to the wrong email address can void your agreement, delay closings, or trigger evidentiary problems in court.

According to the DocuSign Momentum 2024 report, over 1.6 million customers and more than a billion users have signed agreements through the platform, and the average completion time for an eSignature envelope is under one hour.

Here is what you will learn in this guide:

• 📩 Exactly how to build and send an envelope, from upload to final Send click
• 🖊️ How to place signature, initial, date, and data fields so signers cannot skip anything
• 🔐 How to add Knowledge-Based Authentication, SMS, and access codes to satisfy FINRA Rule 4511 and 21 CFR Part 11
• 📑 How to use templates, bulk send, PowerForms, and conditional routing for high-volume work
• ⚖️ How to avoid the seven most common mistakes that make an eSigned contract unenforceable

The Legal Foundation for Requesting an eSignature

Before you click Send, you need to understand why a DocuSign signature carries legal weight. The request workflow is not just a software feature. It is a compliance process built on three layers of law: federal statute, state statute, and industry-specific regulation. Each layer creates rules about consent, identity, intent, and recordkeeping that DocuSign automates for you, but only if you configure the envelope correctly.

The ESIGN Act Sets the Federal Floor

The federal Electronic Signatures in Global and National Commerce Act (ESIGN) took effect on October 1, 2000. It says no contract, signature, or record can be denied legal effect solely because it is electronic. The rule applies to any transaction in or affecting interstate commerce, which covers most business contracts.

The consequence of ignoring ESIGN is severe. A signature created without proper consent disclosures can be thrown out by a judge. In Forcelli v. Gelco Corp., a New York appellate court enforced an email-based settlement because the record showed clear intent. Courts look for the same signals inside your DocuSign envelope.

A real-world example helps. Maria, a commercial real estate broker in Dallas, sends a lease addendum through DocuSign. Because she enables the Electronic Record and Signature Disclosure, the tenant sees and affirms consent before signing. If Maria skipped that step, the tenant could later argue he never agreed to do business electronically.

A common misconception is that ESIGN covers every document. It does not. Wills, codicils, testamentary trusts, court orders, adoption papers, and some utility shutoff notices are excluded and still need wet ink.

UETA Fills in the State Gaps

The Uniform Electronic Transactions Act has been adopted by 49 states, the District of Columbia, Puerto Rico, and the U.S. Virgin Islands. New York is the sole holdout and uses ESRA instead. UETA requires that both parties agree to transact electronically, that the signature is attributable to the signer, and that the record is retainable.

The consequence of a UETA mismatch is a voidable contract. If your signer later proves she never intended to use electronics, a court can unwind the deal. DocuSign captures IP address, timestamp, and authentication events in its Certificate of Completion to defeat that argument.

Imagine David, an HR director in Chicago, sending an offer letter. He uses DocuSign’s audit trail to show the candidate opened the email, adopted a signature, and clicked Finish at 3:42 p.m. Central. That audit trail satisfies UETA’s attribution requirement.

A common misconception is that UETA forces people to sign electronically. It does not. Consent must be voluntary, and any party can insist on paper.

Industry Rules Add Extra Steps

Some industries layer extra requirements on top of ESIGN and UETA. The FDA’s 21 CFR Part 11 governs life-sciences records. FINRA Rule 4511 requires broker-dealers to preserve books and records. HIPAA governs protected health information. The IRS allows electronic signatures on most forms, including Form 8879, as long as identity verification meets the agency’s standards.

Ignoring these rules can trigger fines, license suspension, or criminal charges. A life-sciences company that skips Part 11’s audit-trail controls can lose FDA approval for a drug trial.

Picture Priya, a clinical operations manager at a biotech in Boston. She uses DocuSign Part 11 Module, enables biometric signing, and locks the audit log. If she used the standard product instead, the FDA could reject her entire batch record on inspection.

A common misconception is that DocuSign is automatically compliant with every rule. It is not. You must choose the right product tier and configuration.

Step-by-Step: How to Request an eSignature in DocuSign

The request workflow has five stages: upload, add recipients, add fields, set options, and send. Each stage has choices that change the legal and operational outcome. Skipping one can break the envelope.

Step 1: Log In and Start a New Envelope

Sign in at the DocuSign login page using your email, single sign-on credentials, or a federated identity provider. From the Home screen, click the blue Start button and choose Send an Envelope. DocuSign uses the term envelope to describe the container that holds your documents, recipients, fields, and metadata.

The consequence of choosing the wrong start path is wasted time. Sign a Document is only for self-signing, while Send an Envelope is the full request workflow. If you pick the wrong one, you cannot add other recipients later without restarting.

A real example: Jamal, a freelance designer in Atlanta, once clicked Sign instead of Send on a client contract. He signed the blank template himself, had to void it, and restarted the envelope, which embarrassed him in front of the client.

A common misconception is that you must upgrade to send envelopes. You do not. Even the free Personal plan lets you send a limited number of envelopes per month.

Step 2: Upload Your Document

Click Upload and pull files from your desktop, Google Drive, OneDrive, Dropbox, Box, or Salesforce. DocuSign accepts PDF, DOCX, DOC, XLSX, PPT, JPG, PNG, TIF, and several other formats, converting everything to PDF automatically. The per-envelope size limit is 25 MB per document and 5 MB per image, with up to 100 documents per envelope on most plans, per the DocuSign supported file types page.

The consequence of uploading an unsupported or oversized file is a failed envelope and a frustrated signer. Signers cannot complete a document that never renders properly.

For example, Elena, a nonprofit grants manager in Seattle, tried to upload a 40 MB scanned application. The upload failed, delaying her submission by a day. She fixed it by using DocuSign’s built-in compression tool.

A common misconception is that DocuSign stores editable originals. It does not. Once uploaded, the document is flattened to PDF, so you should keep the source file in your own system.

Step 3: Add Recipients and Set Routing

Enter each recipient’s name and email address in the Recipients panel. Assign a role from the drop-down: Needs to Sign, In Person Signer, Receives a Copy, Needs to View, Allow to Edit, Update Recipients, Specify Recipients, or Certified Delivery. Toggle Set signing order to enable sequential routing, then drag recipients into position.

The consequence of wrong routing is a broken deal. If you put the wrong email or the wrong order, a junior staffer can bind a company before the CEO reviews the terms.

Take Marcus, a venture partner in Menlo Park. He once set signing order as founder first, then investor, but typed the founder’s personal Gmail instead of her corporate email. The term sheet closed, but the company’s general counsel flagged it as a governance issue.

A common misconception is that signing order is optional. For many regulated industries, including mortgage closings under TRID rules, ordered routing is required to preserve audit integrity.

Step 4: Drag Signature and Data Fields onto the Document

Click Next to enter the tagger. On the left panel you will see standard fields: Signature, Initial, Date Signed, Name, Email, Company, Title, Text, Checkbox, Dropdown, Radio, Attachment, Formula, Note, and Approve/Decline. Drag each field to the right spot, then assign it to the correct recipient using the color-coded drop-down at the top of the field.

The consequence of a missing field is an incomplete contract. If you forget the signature block on page 12, your envelope completes without a binding mark in that spot.

For example, Naomi, a contracts manager at a SaaS startup in Austin, forgot to add an Initial field on the arbitration clause. Two years later, a customer argued the clause was not enforceable because they never initialed it, costing her company leverage in mediation.

A common misconception is that DocuSign auto-places fields. Auto-tagging with anchor text works only when the document contains matching keywords like \s1\ or \date\, and many templates do not include them.

Step 5: Set Envelope Options and Send

Before sending, click Edit next to Advanced Options. Set reminders (for example, every three days), expiration (typically 30, 60, or 120 days), signer authentication (Access Code, SMS, Phone, KBA, ID Verification), and language. Add a clear email subject and message, then click Send.

The consequence of skipping authentication is weaker evidence. Courts weigh identity verification heavily, and a missing KBA step can be the difference between winning and losing a motion to enforce.

Picture Rachel, a wealth advisor in Miami subject to FINRA oversight. She always enables KBA on account-opening documents. When a client later claimed he never signed, the KBA log showed he answered four out-of-wallet questions correctly, closing the dispute.

A common misconception is that the default 120-day expiration is fine for everything. For time-sensitive deals like purchase agreements with financing contingencies, you want a shorter window so stale offers do not linger.

Three Common Scenarios When Requesting an eSignature

Real business moves faster than a manual. Below are the three most common real-world scenarios and the outcome of each signer action inside DocuSign.

Scenario 1: Sending an NDA to a New Vendor

Scenario 2: Sending a Residential Lease with Co-Signer

Scenario 3: Sending an IRS Form 8879 to a Tax Client

Named Examples of the Request Workflow in Action

Example 1: Maria the Realtor in Dallas

Maria represents a buyer on a $425,000 single-family home. She uploads the Texas Association of Realtors One-to-Four Family Residential Contract into DocuSign, adds her buyer and the seller’s agent as recipients, and enables sequential signing. She drags Initial fields onto every page and Signature fields on the final page. Because Texas follows UETA Chapter 322, her eSigned contract is fully enforceable. Maria also turns on SMS authentication because her broker requires it.

The consequence for Maria is a faster close and a defensible audit trail. If she had skipped SMS, her broker’s compliance officer would have rejected the file during the post-close audit.

Example 2: David the HR Director in Chicago

David onboards 15 engineers a month. He builds a DocuSign template that includes the offer letter, Form I-9, Form W-4, the employee handbook acknowledgment, and a PIIA. Each template uses anchor tags so the signature fields auto-place when he swaps in a new candidate’s name. David uses Bulk Send for handbook updates across his 800-person workforce.

The consequence for David is dramatic time savings and uniform compliance. Before templates, he spent three hours per new hire on paperwork. Now he spends under 20 minutes, and his audit logs are consistent across every file.

Example 3: Priya the Clinical Ops Manager in Boston

Priya runs Phase II trials for a biotech. She uses DocuSign’s Part 11 Module so every signature includes the signer’s printed name, date, time, and meaning of the signature, as required by 21 CFR § 11.50. She restricts administrator actions and enables tamper-evident sealing. When an FDA inspector arrived, the audit log was printed and accepted without objection.

The consequence for Priya is continued FDA approval. If she had used the standard plan, the inspector could have issued a Form 483 observation, delaying her trial by months.

Mistakes to Avoid When Requesting an eSignature

Every mistake below creates a real negative outcome. You want to prevent all of them.

• Typing the wrong signer email. The envelope goes to a stranger, who may read confidential terms or sign maliciously.
• Forgetting a required signature field. The contract is incomplete, which can void the clause or the entire deal.
• Skipping the Electronic Record Disclosure. ESIGN consent fails, and the signature can be challenged in court.
• Assigning fields to the wrong recipient. The CFO ends up signing where the CEO should, creating authority problems.
• Using default 120-day expiration on urgent deals. Offers sit open, creating legal exposure on stale terms.
• Not turning on authentication for high-value deals. You lose the identity proof courts look for in IO Moonwalker v. Banc of America-style disputes.
• Failing to lock the template. Another employee edits the template, breaking every downstream envelope.
• Ignoring supplemental documents. Exhibits attached outside the envelope are not sealed by the Certificate of Completion.
• Sending to a shared inbox. Attribution fails under UETA because you cannot tell who signed.
• Not retaining the signed PDF. You violate recordkeeping rules under FINRA 4511, HIPAA, or IRS Pub 1345.

Advanced Features That Power Larger Send Workflows

Templates

Templates save a reusable envelope structure. You build the document once, place fields, set routing, and save. Next time, you load the template, swap in new recipient names, and send. The consequence of not using templates is manual rework and inconsistent field placement across hundreds of envelopes. DocuSign’s template guide walks through every setting.

Bulk Send

Bulk Send pushes one template to dozens or thousands of recipients at once by importing a CSV. Each recipient gets a unique envelope, not a shared one. The consequence of misusing Bulk Send is a privacy breach, because a misaligned CSV can send Alice’s W-9 to Bob.

PowerForms

PowerForms turn a template into a public URL that anyone can open and sign. They are perfect for job applications, event waivers, and membership forms. The consequence of forgetting to add authentication to a PowerForm is spam or fake signatures flooding your system.

Conditional Routing and Conditional Fields

Conditional routing sends the envelope to different people based on data entered earlier, such as a dollar threshold triggering VP approval. Conditional fields show or hide based on a checkbox or dropdown. The consequence of skipping conditional logic is over-approval workflow fatigue and missed escalations on high-dollar deals.

Signer Attachments

Signer Attachments let you ask the signer to upload supporting files, such as a driver’s license or void check. The consequence of not using this field is chasing documents over email outside the audit trail, which weakens your evidentiary posture.

Do’s and Don’ts When Requesting an eSignature

Do’s

• Do verify every email address before clicking Send, because a typo can send confidential terms to a stranger.
• Do enable authentication on any envelope worth more than a few thousand dollars, because identity proof wins court fights.
• Do use sequential routing when order matters, because parallel routing can let a junior signer bind the company prematurely.
• Do save every final template with version numbers, because undocumented template edits cause contract drift.
• Do download the Certificate of Completion and store it with the signed PDF, because the certificate is the evidentiary backbone under UETA.

Don’ts

• Don’t reuse old envelopes by Correct on completed documents, because correction resets authentication.
• Don’t send sensitive documents to shared inboxes, because attribution fails under UETA Section 9.
• Don’t rely on the default message, because a clear subject and message reduce signer drop-off.
• Don’t leave reminders off, because 30% of envelopes go stale without nudges.
• Don’t forget to void abandoned envelopes, because open envelopes create orphan legal records.

Pros and Cons of Requesting Signatures Through DocuSign

Pros

• Legally binding in all 50 states under ESIGN, UETA, and ESRA, reducing contract risk.
• Integrates with Salesforce, Workday, NetSuite, Microsoft 365, and Google Workspace, cutting manual data entry.
• Provides a tamper-evident Certificate of Completion, which judges accept as evidence.
• Supports multi-factor authentication including KBA, SMS, phone, and ID Verification, improving identity assurance.
• Offers industry modules (Part 11, Real Estate, Notary), so regulated industries can stay compliant.

Cons

• Paid plans are more expensive than Dropbox Sign or PandaDoc, which can strain small budgets.
• Advanced authentication like KBA costs per transaction, adding variable cost.
• The interface overwhelms first-time users who only need a simple signature, leading to abandoned envelopes.
• Some document types (wills, codicils, court orders) are excluded under ESIGN Section 103, so not every use case is supported.
• International use requires attention to eIDAS rules in Europe, which DocuSign supports but not automatically.

DocuSign vs. the Alternatives

Here is how DocuSign compares with its top rivals for a U.S. buyer evaluating eSignature tools.

Key Entities in the eSignature Ecosystem

Several organizations and concepts shape every DocuSign request. The National Conference of Commissioners on Uniform State Laws drafted UETA. Congress passed the ESIGN Act. The Federal Trade Commission enforces consumer protection around electronic records. The Consumer Financial Protection Bureau oversees electronic disclosures in mortgages. The Internal Revenue Service sets identity standards for electronically signed tax returns. The Food and Drug Administration enforces Part 11 in life sciences. FINRA regulates broker-dealer recordkeeping. HIPAA covered entities must protect PHI inside signed records. DocuSign’s own Trust Center publishes audits and certifications.

Each entity has a specific role. Congress sets the federal floor, states fill in gaps through UETA or ESRA, and industry regulators (FDA, FINRA, IRS) layer technical controls. Understanding the hierarchy lets you configure the right DocuSign plan and features for your use case.

Recap of Key Rulings That Validate eSignatures

Courts have repeatedly upheld eSignatures. In Forcelli v. Gelco Corp., a New York appellate panel enforced an email settlement under ESRA. In IO Moonwalker, Inc. v. Banc of America Merchant Services, a South Carolina federal court enforced a DocuSigned merchant agreement. In Barwick v. Government Employees Insurance Co., the court relied on a clickwrap and eSignature to bind an insurance dispute to arbitration. Each ruling highlights the importance of authentication, consent, and a clean audit trail.

The consequence of these rulings is simple. Properly configured DocuSign envelopes win in court. Sloppy ones create openings for the other side. Reading the DocuSign Court Admissibility Guide before a high-stakes send is time well spent.

FAQs

Is a DocuSign signature legally binding in the United States?

Yes. Under the ESIGN Act and UETA, DocuSign signatures are enforceable in all 50 states for most business, consumer, and commercial contracts, subject to limited exclusions like wills and court orders.

Do I need a paid DocuSign plan to request signatures?

No. The free Personal plan allows a limited number of envelopes per month, but paid plans unlock templates, bulk send, authentication, and integrations needed for regulated or high-volume use.

Can I request signatures on tax forms like Form 8879?

Yes. The IRS allows eSignatures on Form 8879 and many other forms when identity verification meets IRS Publication 1345 standards, which DocuSign’s KBA feature satisfies.

Does DocuSign support 21 CFR Part 11 compliance for life sciences?

Yes. The DocuSign Part 11 Module adds required controls like signature meaning, printed name, tamper-evident sealing, and restricted administrator actions to meet FDA requirements.

Can I send one document to hundreds of recipients at once?

Yes. Bulk Send lets you import a CSV and generate a unique envelope for each recipient, preserving individual audit trails and authentication settings.

Is Knowledge-Based Authentication required for every envelope?

No. KBA is optional and typically used for high-value or regulated deals, but courts weigh it favorably when identity is contested.

Can I revoke or void a sent envelope?

Yes. You can void any envelope before all signers complete, which locks the file and notifies recipients that the request is withdrawn.

Does DocuSign comply with HIPAA for medical records?

Yes. DocuSign signs Business Associate Agreements with covered entities, and its platform meets HIPAA Security Rule controls on transmission and storage of PHI.

Can international recipients sign a DocuSign envelope?

Yes. DocuSign supports over 40 languages and complies with eIDAS in the European Union, though you should confirm local law for cross-border enforceability.

Do I need a witness or notary for a DocuSign envelope?

No. Most contracts do not require a witness, but DocuSign Notary supports remote online notarization where state law allows it, such as in Florida, Texas, and Virginia.

What happens if a signer refuses to adopt an electronic signature?

No. You cannot force electronic signing under UETA Section 5, and you must offer a paper alternative if the recipient insists.

How long should I retain a signed DocuSign envelope?

Yes. You should keep signed envelopes for the full statute-of-limitations window for that contract type, which is typically 3 to 10 years and sometimes longer under FINRA or IRS rules.