How to Request an eSignature for a Document (w/Examples) + FAQs

Requesting an eSignature means sending a document through a secure electronic platform that captures a legally binding signature, a verified identity, and a tamper-evident audit trail. The fastest path is to upload your file to a trusted eSignature service like DocuSign, Adobe Acrobat Sign, or Dropbox Sign, add the signer’s email, place signature and date fields, and click send.

The federal Electronic Signatures in Global and National Commerce Act (ESIGN) and the Uniform Electronic Transactions Act (UETA) give electronic signatures the same legal weight as wet ink in nearly every U.S. transaction. Failing to follow the consent, attribution, and record retention rules baked into those statutes can void your contract, expose you to fraud claims, and trigger evidentiary challenges in court.

According to the 2024 DocuSign State of Contracts report, 82% of agreements are now signed electronically, and businesses save an average of $36 per agreement compared to paper workflows.

• 🖊️ How to send a legally compliant eSignature request in five steps
• ⚖️ Which laws govern eSignatures at the federal and state level
• 📂 What document types still require wet ink or notarization
• 🛡️ How to protect your contract with audit trails and identity verification
• 🚫 The seven most common eSignature mistakes and how to avoid each one

What an eSignature Actually Is Under U.S. Law

An electronic signature is any “electronic sound, symbol, or process attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record,” according to 15 U.S.C. § 7006. That definition is intentionally broad. It covers a typed name at the bottom of an email, a finger-drawn signature on a tablet, a checkbox click that says “I agree,” and a cryptographic digital signature backed by a public key infrastructure.

The federal ESIGN Act, signed in 2000, preempts state law where state law would deny legal effect to a signature solely because it is electronic. UETA, adopted in 49 states (every state except New York, which uses its own Electronic Signatures and Records Act), supplies the day-to-day operational rules: consent, attribution, retention, and admissibility. Together these two frameworks form the backbone of every legitimate eSignature request in the United States.

The consequence of skipping these rules is severe. A contract signed without proper consumer consent under 15 U.S.C. § 7001(c) can be ruled unenforceable, and a court may treat the signature as a forgery if the audit trail does not link the signer to the document. In Naldi v. Grunberg, 80 A.D.3d 1 (N.Y. App. Div. 2010), the court confirmed that emails can satisfy the Statute of Frauds, but only when the signer’s intent is unmistakable.

A common misconception is that any image of a signature pasted onto a PDF qualifies as an eSignature. It does not. Without intent, attribution, and a record of the signing process, that image is just a picture, and a judge can throw it out.

The Three Legal Pillars

Every compliant eSignature rests on three pillars. The first is intent to sign, which the platform must capture through an affirmative action like clicking a “Sign” button. The second is consent to do business electronically, which under ESIGN section 101(c) requires consumers to receive a clear disclosure and demonstrate they can access the electronic record. The third is association of the signature with the record, meaning the signature must be logically linked to the exact document version that was signed.

If any pillar collapses, the signature collapses with it. A signer who never saw the consent disclosure can later claim they never agreed to electronic delivery, and the contract reverts to an unsigned state. A real-world example is a gym membership lawsuit where the gym lost because it could not show the customer ever clicked through the electronic consent screen before signing.

The misconception here is that consent can be implied from continued use of a service. Under federal law, consent must be affirmative, informed, and capable of being withdrawn.

Step-by-Step: How to Request an eSignature

The process is the same across most platforms, though the buttons and menus differ. Following each step in order is the difference between a contract that holds up in court and one that gets challenged.

Step 1: Choose a Compliant Platform

Pick a vendor that complies with ESIGN, UETA, and, if you handle health data, the HIPAA Security Rule. The leading options include DocuSign, Adobe Acrobat Sign, Dropbox Sign, PandaDoc, and SignNow. Each generates a Certificate of Completion, the audit trail document that proves who signed, when, from which IP address, and with which authentication method.

The consequence of using a non-compliant tool, like a free PDF editor that only flattens an image, is that you lose the audit trail. Without the audit trail, you cannot prove the signer was who they claimed to be. A small example: Maria, a freelance graphic designer, used a free PDF tool to “sign” a client agreement, then sued for nonpayment. The client successfully argued the signature was unverifiable, and Maria lost a $12,000 invoice.

The misconception is that all eSignature tools are interchangeable. They are not. Free tools rarely capture the metadata required for litigation.

Step 2: Upload the Document

Upload the final version of the contract as a PDF or Word file. Lock the document so no one can edit it after upload, because under UETA section 12, an electronic record must be capable of being retained and accurately reproduced. Edits after signing break that chain.

If you upload the wrong version, the signed contract will reflect terms you never intended. The classic example is Jamal, a real estate broker, who uploaded a draft purchase agreement instead of the final version with the agreed-upon $500,000 price. The buyer signed the draft showing $475,000, and Jamal’s brokerage absorbed the difference.

A common misconception is that you can swap the file after sending. You cannot. Most platforms void the envelope if the document changes mid-flight.

Step 3: Add Recipients and Set Signing Order

Enter each signer’s full legal name and email address. If multiple parties must sign, set a signing order so the document routes correctly. Use the platform’s role tags, such as Signer, Approver, CC, or In-Person Signer, to assign permissions.

Skipping the signing order can cause a junior employee to receive a contract before their supervisor approves it, or a co-signer to sign before the primary obligor. The consequence is a contract that may be voidable for lack of authority. Aisha, an HR director, sent an offer letter to a candidate before the CFO approved the salary, and the company had to rescind the offer, exposing it to a promissory estoppel claim.

The misconception is that signing order does not matter as long as everyone signs eventually. Order matters when authority, dependency, or sequencing terms are involved.

Step 4: Place Signature, Date, and Initial Fields

Drag fields onto the document where each signer must act. At minimum, every contract needs a signature field and a date field. Add initials fields next to material terms, name fields, title fields, and any required checkboxes for consent disclosures. Mark each field as required so the platform blocks completion until every field is filled.

If you forget a required date field, the contract may lack the effective date needed to start the clock on performance, termination, or Statute of Limitations periods. Carlos, a contractor, forgot a date field on a construction agreement, and a payment dispute later turned on whether the contract was signed before or after a key code change.

A common misconception is that the platform’s default timestamp replaces the date field. The system timestamp lives in the audit trail, but the visible date on the document carries weight in court because it is what humans read.

Step 5: Send, Monitor, and Store

Click send. The platform emails each signer a secure link, captures their consent, records every action in the audit trail, and returns a Certificate of Completion when finished. Download the signed PDF and the certificate, and store both in a system that meets your record retention rules under UETA section 12.

If you delete the audit trail or store only the PDF, you lose your evidentiary backbone. The consequence in litigation is that the opposing party can challenge authenticity, and you may have to authenticate the signature through expensive forensic testimony.

The misconception is that the signed PDF is the contract. The contract is the PDF plus the audit trail. Treat them as a single record.

Three Common eSignature Scenarios

Each scenario below shows a typical action and the legal or business consequence that follows. These scenarios reflect the most frequent fact patterns reported by the American Bar Association’s eSignature task force.

Real-World Examples With Named People

Concrete examples make the rules stick. Each of the three personas below illustrates a different industry and a different legal nuance.

Example 1: Priya, a SaaS founder. Priya sends a Master Services Agreement to a Fortune 500 client through Adobe Acrobat Sign. She enables knowledge-based authentication (KBA) because the contract value exceeds $250,000. KBA asks the signer four questions drawn from public records to confirm identity, satisfying the heightened attribution standard many enterprise clients require. The agreement closes in two days instead of two weeks, and the audit trail later defeats a frivolous “I never signed that” challenge from a departing executive.

Example 2: Marcus, a real estate broker in Texas. Marcus uses DocuSign for a residential purchase agreement and pairs it with remote online notarization for the deed. Texas adopted RON in 2018 under Texas Government Code Chapter 406, so Marcus’s transaction closes without anyone leaving home. The seller’s identity is verified by credential analysis and KBA, and a Texas-commissioned online notary witnesses the deed signing on video.

Example 3: Linh, an HR manager at a 200-person tech company. Linh sends offer letters, employee handbooks, and Form I-9 supporting documents through Dropbox Sign. She is careful to use a separate, USCIS-compliant tool for the I-9 itself, because 8 CFR § 274a.2 imposes specific electronic storage and indexing rules. Linh’s audit trail saved the company in a Department of Labor audit when an investigator questioned whether a former employee had received the company’s arbitration agreement.

Mistakes to Avoid When Requesting an eSignature

Each mistake below has tripped up real businesses and led to real losses. Avoiding them protects your contracts and your bottom line.

1. Skipping the electronic consent disclosure. Federal law requires consumers to receive a clear notice about electronic delivery. Skipping it lets a signer back out of the contract.
2. Using a free PDF editor that flattens a signature image. Without an audit trail, you cannot prove who signed or when, and the signature can be challenged as a forgery.
3. Sending a draft instead of the final version. Once a signer clicks, the draft becomes the binding contract, and you absorb the difference.
4. Forgetting the date field. The visible date drives effective date, performance deadlines, and statute of limitations calculations.
5. Mismatching signer names. A contract signed by “Bob Smith” when the entity is “Robert J. Smith, Trustee” can fail attribution.
6. Storing only the PDF. The audit trail is half of your evidence package, and losing it weakens your case in litigation.
7. Using eSignature for excluded documents. ESIGN section 103 carves out wills, codicils, testamentary trusts, family law matters, court orders, and certain UCC instruments.
8. Failing to verify identity for high-value contracts. Without KBA or multi-factor authentication, a stolen email account can sign on someone’s behalf.
9. Ignoring state-specific carve-outs. New York’s ESRA differs from UETA, and a few states exclude certain notices from eSignature.
10. Not training staff. A junior employee who reuses a signed envelope template without updating the document terms can bind the company to outdated obligations.

Federal Law: ESIGN in Detail

The ESIGN Act, codified at 15 U.S.C. §§ 7001-7031, applies to any transaction in or affecting interstate or foreign commerce. It does four things. First, it gives electronic signatures the same legal effect as handwritten signatures. Second, it sets consumer consent rules. Third, it preserves state law that mirrors UETA. Fourth, it lists exceptions where electronic signatures do not apply.

The consequence of ignoring ESIGN is that a court can refuse to enforce the contract against a consumer who never received the disclosure. A real-world example is a payday loan case where the lender could not produce the consumer’s electronic consent to receive the Truth in Lending Act disclosures electronically, and the court rescinded the loan and ordered all interest refunded.

A misconception about ESIGN is that it covers all transactions. It does not. The carve-outs in section 103 are narrow but important, and many family law and probate matters still require wet ink.

Consumer Consent Disclosure Requirements

For consumer transactions, ESIGN section 101(c) requires you to disclose seven items before obtaining consent. These include the right to receive paper records, the right to withdraw consent, any fees for paper copies, the hardware and software requirements to access the electronic records, and the procedure for updating contact information. The signer must then “reasonably demonstrate” the ability to access the format used.

If the disclosure is missing or buried, the consumer can withdraw consent retroactively and demand paper records. A real example is Tanya, a borrower who signed a mortgage modification electronically but was never shown the consent disclosure. Her lawyer used the missing disclosure to force the lender into mediation.

The misconception is that “click to accept” replaces the disclosure. It does not. The disclosure must come before the click and must be specific.

State Law: UETA and Its Variations

UETA was drafted by the Uniform Law Commission in 1999 and has been adopted by 49 states, the District of Columbia, Puerto Rico, and the U.S. Virgin Islands. Only New York stands apart with its own ESRA, though ESRA reaches the same outcome through different language.

UETA applies only to transactions where each party has agreed to conduct business electronically, which can be shown by the parties’ conduct. UETA section 7 confirms that a record or signature cannot be denied legal effect solely because it is electronic. UETA section 9 provides that an electronic record is attributable to a person if it was the act of the person, which can be proven by any evidence, including the security procedures used.

If you operate across multiple states, you must check each state’s adoption. California, for instance, modified UETA to exclude certain real estate documents and judicial filings under California Civil Code § 1633.3. Illinois replaced its earlier statute with the Uniform Electronic Transactions Act in 2021, aligning the state with the rest of the country.

The misconception is that UETA is identical in every state. It is not, and the variations matter most for real estate, notarization, and government filings.

Remote Online Notarization Across States

Remote online notarization, or RON, lets a notary witness a signature over live video. As of 2026, more than 45 states have permanent RON laws, including Florida, Texas, Virginia, and Nevada. Each RON state requires the notary to use an approved technology vendor, perform credential analysis, and retain an audio-video recording for a set number of years, typically five to ten.

If you use a notary commissioned in the wrong state or skip the recording, the notarization can be invalidated. A common example is a deed recorded in California that was notarized via RON by a Florida notary; the county recorder rejected it because California did not yet recognize that notary’s commission for that transaction.

The misconception is that any online notary can notarize for any state. The notary must be commissioned in a state whose RON law applies to the transaction.

Industry-Specific eSignature Rules

Some industries layer extra rules on top of ESIGN and UETA. Knowing your industry’s overlay is the difference between compliance and a costly enforcement action.

Healthcare and HIPAA

Healthcare providers must use eSignature platforms that sign a Business Associate Agreement and meet the HIPAA Security Rule’s encryption, access control, and audit log requirements. Sending a patient consent form through a non-BAA tool exposes the provider to a HIPAA breach, with civil penalties up to $1.5 million per violation category per year.

A real example is a small dental practice that used a generic eSignature tool for patient intake forms. After a phishing incident, the Office for Civil Rights fined the practice $50,000 because the vendor had not signed a BAA.

The misconception is that any encrypted tool meets HIPAA. Encryption is necessary but not sufficient.

Financial Services and the Truth in Lending Act

Lenders must deliver TILA disclosures in a form the consumer can keep. Regulation Z and ESIGN work together: the consumer must consent to electronic delivery, and the lender must provide a downloadable, printable record. A lender who emails a PDF without a consent disclosure can face rescission claims for up to three years on a closed-end mortgage.

A misconception is that emailing the disclosure is the same as ESIGN-compliant delivery. It is not, and the difference shows up at the closing table.

Government and Court Filings

Federal courts accept electronic signatures through PACER and CM/ECF, but state courts vary widely. Some require wet-ink signatures on certain pleadings, and most require the attorney’s S/-style signature block plus a registered ECF account. Filing with the wrong format can lead to a stricken pleading and a missed deadline.

The misconception is that an attorney’s typed name in CM/ECF is the same as a personal eSignature. The CM/ECF login itself is the signature for federal filings.

Do’s and Don’ts of Requesting an eSignature

Following these practical rules keeps your contracts enforceable and your audit trail clean.

Do’s:
– Do confirm the signer’s identity through KBA or MFA for high-value contracts, because attribution is the most common challenge.
– Do present a clear electronic consent disclosure before the first signature, because ESIGN demands it for consumers.
– Do lock the document after upload, because edits after sending void the audit trail.
– Do download the Certificate of Completion alongside the signed PDF, because the certificate is your evidence package.
– Do keep records for the longer of seven years or your industry’s retention rule, because shorter retention can leave you defenseless in late-arising disputes.
– Do test your envelope on yourself first, because a misplaced field is easier to fix before the signer sees it.

Don’ts:
– Don’t reuse old envelopes without updating the document, because outdated terms can bind you to old prices, old indemnities, or old jurisdictions.
– Don’t email a signed PDF as the only record, because the email is not a substitute for the audit trail.
– Don’t use eSignature for wills, codicils, or family law unless your state explicitly allows it, because ESIGN excludes these documents.
– Don’t rely on a typed name without an affirmative click, because intent must be demonstrable.
– Don’t forget to add date fields, because the visible date controls performance and limitations periods.
– Don’t store records in personal email, because business records belong in a system you control.

Pros and Cons of Electronic Signatures

Weighing both sides helps you decide when eSignature fits and when it does not.

Pros:
– Speed: contracts close in hours instead of weeks, because routing is instant.
– Cost: average savings of $36 per agreement, because paper, printing, and shipping disappear.
– Audit trail: every action is timestamped, because the platform captures metadata automatically.
– Accessibility: signers can complete documents on any device, because modern platforms are mobile-friendly.
– Compliance: leading platforms maintain SOC 2, ISO 27001, and HIPAA-ready environments, because enterprise customers demand them.
– Storage: cloud retention keeps records searchable and disaster-resilient, because cloud beats a filing cabinet for retrieval.

Cons:
– Identity risk: a hacked email account can sign on a person’s behalf, because email is the weakest link.
– Excluded documents: wills, family law, and some real estate filings still need wet ink, because state law has not caught up.
– Subscription cost: enterprise plans run thousands per year, because per-envelope pricing adds up.
– Technical literacy: some signers struggle with mobile signing, because not every user is comfortable with apps.
– State variation: cross-border transactions require state-by-state analysis, because UETA is not perfectly uniform.
– Vendor lock-in: switching platforms requires data migration, because each vendor stores audit trails in proprietary formats.

Recap of Key Court Rulings

Courts have repeatedly upheld eSignatures when the audit trail is solid. In Forcelli v. Gelco Corp., 109 A.D.3d 244 (N.Y. App. Div. 2013), the New York Appellate Division enforced a settlement agreement where the attorney’s email signature satisfied the writing requirement. In Naldi v. Grunberg, the same court confirmed that emails meet the Statute of Frauds when the signer’s intent is clear. In Berkson v. Gogo LLC, 97 F. Supp. 3d 359 (E.D.N.Y. 2015), the federal court refused to enforce an agreement because the user never had reasonable notice of the terms, reminding senders that presentation matters as much as the signature.

Each ruling rests on the same theme: intent, attribution, and a clean record. Where any element is missing, courts will not save a sloppy process.

The misconception is that one favorable ruling means all eSignatures are bulletproof. They are not. Courts examine each transaction on its facts.

FAQs

Is an electronic signature legally the same as a wet-ink signature?

Yes. Under the federal ESIGN Act and UETA in 49 states, an eSignature has the same legal effect as a handwritten one for almost every transaction, with narrow exceptions for wills and certain family law documents.

Can I use a free tool like a PDF editor to capture an eSignature?

No. Free tools rarely capture the audit trail, identity verification, and tamper-evident sealing that courts expect, leaving your contract vulnerable to challenges of authenticity and attribution.

Do I need the signer’s consent before sending an electronic agreement?

Yes. ESIGN section 101(c) requires consumers to receive a specific disclosure and affirmatively consent to electronic records before the platform can capture a binding signature.

Can I send a will or codicil through DocuSign?

No. ESIGN section 103 excludes wills, codicils, and testamentary trusts in most states, though Nevada, Florida, Indiana, Arizona, and a few others now permit electronic wills under specific statutes.

Is remote online notarization legal in every state?

No. RON is permanent in more than 45 states as of 2026, but a handful still require in-person notarization or limit RON to specific document types like real estate or business filings.

Can two parties in different states sign the same eSignature envelope?

Yes. ESIGN preempts state law that would deny effect to interstate electronic signatures, so cross-border deals are routinely closed by parties in different states using the same envelope.

Do I need identity verification for every eSignature?

No. Email-based authentication is sufficient for most low-risk contracts, but high-value or regulated transactions should add KBA, MFA, or government-ID verification to strengthen attribution.

Can a typed name in an email count as an eSignature?

Yes. Courts have repeatedly held that a typed name at the bottom of an email can satisfy the Statute of Frauds when the sender’s intent to sign is clear from the surrounding context.

Is the Certificate of Completion required to enforce a contract?

Yes. While not technically required, the certificate is the practical backbone of enforcement because it documents who signed, when, from where, and with which authentication method.

Can a minor sign a contract electronically?

No. Minors generally lack capacity to sign binding contracts regardless of medium, and an eSignature does not cure that defect, though some states allow minors to enter limited categories like employment or necessities.

Do I need a separate eSignature tool for HIPAA-protected forms?

Yes. You must use a platform that signs a Business Associate Agreement and meets the HIPAA Security Rule, because generic tools without a BAA can trigger six-figure penalties from the Office for Civil Rights.

Can I cancel an eSignature request after sending?

Yes. Most platforms let the sender void or recall an envelope before all parties sign, though once every signer has completed, the contract is generally binding and must be amended through a new agreement.