Can Someone eSign on Behalf of Someone Else? (w/Examples) + FAQs

Yes, someone can eSign on behalf of another person, but only when the signer has clear legal authority to act for that person, documents the authority in the signature itself, and follows the rules of the federal ESIGN Act and the state-level Uniform Electronic Transactions Act (UETA). Signing electronically for another person without that authority is not an innocent shortcut. It can be treated as forgery, wire fraud, identity theft, or the unauthorized practice of law, and it can void the contract you were trying to help close.

The rules come from three overlapping sources: federal statute (15 U.S.C. §§ 7001-7006), the UETA adopted by 49 states, and the common law of agency as explained in the Restatement (Third) of Agency. New York is the outlier and uses its own New York Electronic Signatures and Records Act (ESRA), which reaches the same result through different wording. When those authorities line up, a delegated electronic signature is as binding as an ink signature.

According to the 2025 DocuSign Digital Agreement Trends Report, 87% of U.S. businesses now rely on electronic signatures for routine contracts, and roughly 1 in 4 agreements are signed by someone other than the named party. That single statistic explains why courts, regulators, and platforms have spent the last five years tightening the rules on delegated signing.

• ⚖️ The exact legal authority you need before signing for another person
• 🖊️ How to format an eSignature so it shows you are signing as an agent
• 🏢 When a corporate officer, assistant, or HR manager may sign for a company
• 👵 How powers of attorney work with DocuSign, Adobe Sign, and Dropbox Sign
• 🚫 The seven most common mistakes that turn a helpful signature into a felony

The Core Rule: Authority Before Action

An electronic signature is only valid when the signer intends to sign and has the legal power to bind the named party. The ESIGN Act at 15 U.S.C. § 7001(a) says a signature cannot be denied legal effect just because it is electronic, but it does not create new authority. Authority still comes from agency law, a written power of attorney, a corporate resolution, or a court order.

The plain-English version is simple. You can push the button for someone else only when that person, a statute, or a court said you may. You also have to sign in a way that shows you are the agent, not the principal. And you must keep a record of the authority in case the signature is later challenged.

The consequence of skipping these steps is severe. A signature placed without authority is void, which means the contract never formed. The signer can also be charged with forgery under 18 U.S.C. § 495 when federal documents are involved, or with identity theft under 18 U.S.C. § 1028. State forgery statutes, such as California Penal Code § 470, reach the same conduct.

A real-world example makes this concrete. Maria is the office manager at a small architecture firm. Her boss is on a plane and asks her to “just DocuSign my name” on a proposal. If Maria types her boss’s name into the signature block with no written authority and no indication that she is the signer, she has committed forgery in most states, even though her boss asked her to do it. The firm may also lose the contract because the other side can rescind once the truth comes out.

A common misconception is that a verbal “go ahead” from the principal is enough. It is not. Under Restatement (Third) of Agency § 3.02, express authority for a legal signature should be in writing, and many statutes, including the Statute of Frauds, demand written authority for real estate, long-term leases, and guarantees.

What Counts as an Electronic Signature

UETA § 2(8) defines an electronic signature as “an electronic sound, symbol, or process attached to or logically associated with a record and executed or adopted by a person with the intent to sign the record.” That definition covers a typed name, a mouse-drawn squiggle, a clicked “I Agree” button, a stylus signature on a tablet, and even a recorded voice command.

The consequence of this broad definition is that almost any digital mark can be a signature, which means almost any digital mark can also be forged. Courts in cases like Barwick v. Government Employees Insurance Co., 295 Ga. App. 625 (2009) have held that a typed name paired with an IP address and audit log is enough to prove a signature is genuine. The flip side is that the same evidence can prove a signature is fake.

A common misconception is that only images of handwritten signatures count. That view is wrong and has been wrong since ESIGN was signed into law in 2000.

When Federal Law Preempts State Law

15 U.S.C. § 7002 lets a state replace ESIGN with its own rules if the state adopts the official UETA or an equivalent law. Every state except New York has adopted UETA. New York uses ESRA, which the New York Court of Appeals validated in People v. Johnson, 31 N.Y.3d 942 (2018).

The consequence is that you must check the state whose law governs the contract before you sign for someone else. A power of attorney that works in Texas may not work in Louisiana, which has its own civil-law mandate rules in La. Civ. Code art. 2989.

Power of Attorney and Electronic Signatures

A power of attorney (POA) is the most common way to get legal authority to eSign for another person. A POA is a written document in which the principal names an agent (also called an attorney-in-fact) to act on the principal’s behalf. The Uniform Power of Attorney Act (UPOAA) has been adopted by 30 states and sets the default rules.

A durable POA stays in force when the principal becomes incapacitated. A springing POA only becomes active when a doctor certifies incapacity. A limited POA covers only one task, such as closing a single house sale. Each type lets an agent eSign, but only for the acts the document lists.

The consequence of signing beyond the POA’s scope is that the signature is void and the agent can be personally liable for damages. The SEC’s 2023 enforcement action against an investment adviser who used a client POA to sign unrelated trades is a recent warning. The adviser paid more than $400,000 in penalties.

A real-world example helps. James holds a durable POA for his father, who has dementia. James uses DocuSign to sign his father’s Medicare enrollment forms. The enrollment is valid because Medicare paperwork is routine health-care management, which the POA covers. If James instead signed a new car lease in his father’s name, the dealer could rescind because a standard POA does not cover luxury purchases that are not in the principal’s interest.

A common misconception is that a POA automatically works on every eSignature platform. Platforms like DocuSign, Adobe Acrobat Sign, and Dropbox Sign each have their own “sign on behalf of” settings that must be turned on in the account before the agent can sign with the proper designation.

The Correct Signature Block for an Agent

An agent signing under a POA should use a format that shows the representative capacity. The standard wording is: “[Principal’s Name] by [Agent’s Name], as Attorney-in-Fact.” The American Bar Association’s estate planning section recommends this exact format.

The consequence of signing only the principal’s name is that the agent can be held personally liable on the contract. The Restatement (Third) of Agency § 6.01 explains that undisclosed agency makes the agent a party to the deal.

A common misconception is that typing “POA” after the principal’s name is enough. Courts have rejected that shorthand when the agent’s own name does not appear, as in In re Estate of Kurrelmeyer, 895 A.2d 207 (Vt. 2006).

Remote Online Notarization for POA eSignatures

Many POAs must be notarized. Remote Online Notarization (RON) is now legal in 45 states, including Florida, Texas, Virginia, and Ohio. The MBA and ALTA model RON bill is the template most states follow.

The consequence of skipping notarization on a POA that requires it is that the POA is not valid, which means any later eSignature by the agent is also void. A real estate deed signed by an agent under an invalid POA cannot be recorded, as explained in Florida Statute § 695.03.

Corporate Delegation: Officers, Employees, and Apparent Authority

Companies sign thousands of contracts a week, and almost none are signed by the CEO personally. Corporate eSignature authority comes from the board of directors through a written resolution, bylaws, or a delegation of signing authority. The Model Business Corporation Act § 8.41 lets officers bind the company within the scope of their office.

A vice president of sales has actual authority to eSign sales contracts. A receptionist does not, even if the receptionist clicks “Sign” in DocuSign. The difference matters because contracts signed without actual authority can still bind the company under the doctrine of apparent authority if the other side reasonably believed the signer had power.

The consequence for the company is a binding deal it never approved. The consequence for the employee can be termination, clawback of commissions, and personal liability for breach of warranty of authority under Restatement (Third) of Agency § 6.10.

A real-world example makes this clear. Priya is a project manager at a software firm. The CFO asks Priya to DocuSign a master services agreement “in my name” because the CFO is in back-to-back meetings. If Priya types the CFO’s name, three things go wrong. The signature is a forgery under state law, the contract may still bind the company through apparent authority, and Priya personally becomes liable if the CFO later denies giving permission.

A common misconception is that assistants can always sign for their bosses. They cannot unless the boss gave written authority and the signature block shows the assistant’s name, such as “Jane Smith, CFO, by Priya Patel, Assistant, per written authorization dated March 1, 2026.” The SEC’s e-signature guidance in Rule 302(b) of Regulation S-T specifically requires this type of documentation for filings.

HR, Offer Letters, and Onboarding Documents

HR managers sign offer letters, I-9 forms, and benefits elections every day. The USCIS allows electronic I-9 signatures under 8 C.F.R. § 274a.2, but the person signing must actually be the HR representative listed, not a coworker clicking through.

The consequence of a false I-9 signature is a civil penalty of up to $2,789 per form under 8 U.S.C. § 1324a and possible criminal exposure for document fraud.

A common misconception is that the company’s HRIS platform automatically makes any internal signature valid. The IRS guidance in Publication 1345 and the DOL’s 2020 safe harbor make clear that the platform must capture identity, intent, and an audit trail tied to the specific signer.

Real Estate and Licensed Agents

A licensed real estate agent may eSign for a buyer or seller only when a written, signed, and often initialed limited agency agreement gives that power for a specific transaction. The National Association of Realtors Code of Ethics Article 1 treats unauthorized signing as a disciplinary offense.

The consequence of an agent signing a purchase offer without written authority is a void contract, loss of commission, a complaint to the state real estate commission, and possible criminal charges. The Texas Real Estate Commission disciplinary database shows dozens of license revocations each year for this exact conduct.

Three Popular Delegated Signing Scenarios

The following scenarios show the most common real-world facts and the legal outcome under federal and state law.

The pattern is consistent. Written authority plus a proper signature block equals a valid delegated signature. Missing either piece breaks the deal.

Named Examples That Show the Rules in Action

Example 1 — Military Spouse Signing a Mortgage. Sergeant Alex Rivera is deployed to Germany. His spouse, Dana Rivera, holds a specific military power of attorney drafted by a JAG officer that covers real estate. Dana uses DocuSign RON to close the refinance as “Alex Rivera by Dana Rivera, Attorney-in-Fact.” The signature is valid under 10 U.S.C. § 1044b, which makes military POAs honored in every state.

Example 2 — HR Manager Delegating to an Assistant. Lauren Kim is the HR director at a 200-person company. She delegates offer-letter signing to her assistant, Marcus Bell, through a written policy and a DocuSign “sign on behalf of” setting. Marcus signs as “Lauren Kim, HR Director, by Marcus Bell, HR Coordinator, per policy HR-22.” The signatures are valid, and the audit trail in DocuSign preserves the delegation.

Example 3 — Executor Signing Estate Documents. Priscilla Nguyen is the court-appointed executor of her late uncle’s estate. She uses Dropbox Sign to close the sale of the estate’s rental property. She signs as “Estate of Tuan Nguyen, by Priscilla Nguyen, Executor, Probate Case No. 2026-1234.” The signature is valid because her authority comes from letters testamentary issued by the probate court.

Mistakes to Avoid

Each mistake below has a specific and often expensive consequence. None of them are hypothetical.

• Typing the principal’s name with no disclosure of agency. The contract may be void and the signer can be prosecuted for forgery under state law such as New York Penal Law § 170.10.
• Relying on a verbal “go ahead” from the boss. No written authority means no enforceable delegation, and the employer can later deny the deal, leaving the employee on the hook.
• Using a POA that does not cover the act being signed. A general POA does not authorize gifts, beneficiary changes, or trust amendments without specific “hot powers” language under UPOAA § 201(a).
• Skipping notarization on a document that requires it. Many real estate deeds and POAs must be notarized, and a missing notary block makes the document unrecordable under Florida Statute § 695.03.
• Signing a medical consent form for an adult without a health-care proxy. HIPAA at 45 C.F.R. § 164.502(g) requires a health-care agent document, and without it the signature is void and the provider may face fines.
• Ignoring state-specific rules, especially in New York. New York uses ESRA rather than UETA, and wills, trusts, and certain health-care documents still cannot be electronically signed there.
• Failing to preserve the audit trail. Without the IP address, time stamp, and identity verification record, a court may refuse to enforce the signature, as the Second Circuit warned in Berkson v. Gogo LLC, 97 F. Supp. 3d 359 (E.D.N.Y. 2015).
• Delegating to an unlicensed person in a licensed field. An unlicensed paralegal signing pleadings for an attorney is the unauthorized practice of law under ABA Model Rule 5.5.
• Using a “wet” scanned signature image without consent. Pasting a JPEG of someone’s signature into a PDF is still forgery even though it looks like a signature, as clarified in Labajo v. Best Buy Stores, L.P., 478 F. Supp. 2d 1146 (C.D. Cal. 2007).

Do’s and Don’ts for Delegated eSignatures

Do’s

• Do get written authority before you click, because oral permission rarely survives a courtroom challenge.
• Do sign with a representative-capacity block, because it protects you from personal liability under agency law.
• Do keep the audit trail from DocuSign, Adobe Sign, or Dropbox Sign for at least seven years, because contract statutes of limitation run that long in most states.
• Do confirm the state law that governs the contract, because a POA valid in one state can fail in another.
• Do use Remote Online Notarization when the document needs a notary, because in-person notarization is no longer required in 45 states.

Don’ts

• Don’t type the principal’s name alone, because that is textbook forgery under 18 U.S.C. § 495.
• Don’t assume a POA covers everything, because courts read POAs narrowly to protect the principal.
• Don’t sign wills, codicils, or most trusts electronically, because states like California Probate Code § 6110 still require wet-ink witnesses.
• Don’t use a shared login to sign for a coworker, because the audit trail will not match the named signer and the signature can be disqualified.
• Don’t ignore red flags like urgency, secrecy, or “just sign it for me,” because those are the exact fact patterns that lead to SEC enforcement actions.

Pros and Cons of eSigning on Behalf of Someone Else

Pros

• Speeds up closings, hiring, and health-care decisions because no one waits on a single person’s availability.
• Cuts costs on courier fees, paper, and travel, which the Forrester Total Economic Impact study of DocuSign valued at an average of $36 saved per signature event.
• Preserves a richer audit trail than wet signatures, because the platform captures IP, device, and identity data.
• Lets incapacitated, deployed, or traveling principals continue important transactions without delay, under properly drafted POAs.
• Supports accessibility for people with disabilities, because the ADA and Section 508 favor electronic workflows over paper signings.

Cons

• Invites fraud when platforms are misconfigured or shared logins are used, which the FTC Consumer Sentinel Network flags as a growing category.
• Creates liability for the agent if the signature block is wrong, because undisclosed agency makes the agent personally liable.
• Requires careful state-by-state analysis, because UETA, ESRA, and the UPOAA are not uniform in practice.
• Does not apply to certain documents like wills, court orders, and some family law filings, which the ESIGN Act § 7003 excludes.
• Can be challenged in court, and the party relying on the signature bears the burden of proving authority under UETA § 9.

Step-by-Step Process for a Valid Delegated eSignature

Every delegated eSignature should follow the same nine steps, and skipping any step creates risk.

1. Confirm the governing law. Identify the state whose law controls the contract, because that decides whether UETA, ESRA, or a state variation applies.
2. Obtain written authority. Collect the POA, corporate resolution, court order, or signed delegation memo that names the agent and the covered acts.
3. Check the scope. Match the document to be signed against the authority, because a POA that lists “banking” does not cover “real estate.”
4. Verify identity. Use the platform’s knowledge-based authentication or ID verification to confirm the agent’s identity.
5. Configure the signature block. Set the block to show the principal’s name, the word “by,” the agent’s name, and the representative capacity.
6. Capture intent. Make sure the agent actively clicks, types, or draws the signature, because a pre-filled signature lacks the intent element of UETA § 2(8).
7. Notarize when required. Use RON through a platform like Notarize or Proof for POAs, deeds, and affidavits.
8. Deliver the completed document. Send the signed record to the counterparty and to the principal within the same business day.
9. Archive the audit trail. Store the platform’s certificate of completion, authority document, and the signed record together for the full retention period.

Line-by-Line Look at a DocuSign “Sign on Behalf Of” Field

The DocuSign “Sign on Behalf Of” feature adds two fields: the named signer and the actual clicker. The named signer is the principal or the officer whose name should appear on the contract. The actual clicker is the agent, whose identity the platform verifies through email, SMS, or ID check.

The consequence of filling in the wrong field is that the audit trail will list the wrong person as the signer, which is almost impossible to fix later. The best practice is to set the “Sign on Behalf Of” field before the envelope is sent and to include a note in the subject line that says “Signed by [Agent] as Attorney-in-Fact.”

A common misconception is that the feature creates authority. It does not. It only documents authority that already exists in a separate written instrument.

Key Court Rulings to Know

Several rulings shape today’s delegated eSignature law. Cloud Corp. v. Hasbro, Inc., 314 F.3d 289 (7th Cir. 2002) held that an email with a typed name satisfied the Statute of Frauds. Barwick v. Government Employees Insurance Co. confirmed that a clickwrap signature plus audit trail is enforceable. Berkson v. Gogo LLC warned that hidden or buried signature processes can be thrown out.

The IRS ruling in Rev. Proc. 2022-35 allows eSignatures on most tax forms when the filer verifies identity. The SEC’s 2020 amendment to Rule 302(b) permits eSignatures on filings if the signer keeps a manually signed authentication document for five years.

The consequence of these rulings is a clear national pattern. Courts and regulators accept delegated eSignatures when authority is written, identity is verified, and the audit trail is preserved. They reject them when any piece is missing.

Key Entities and How They Relate

The federal ESIGN Act sets the floor. The UETA and ESRA implement it at the state level. The UPOAA governs most powers of attorney. The Restatement (Third) of Agency sets the common-law backbone. The National Notary Association and Mortgage Bankers Association shape RON rules. Platforms such as DocuSign, Adobe Acrobat Sign, and Dropbox Sign operationalize the rules and provide the audit trails that courts rely on.

Each plays a distinct role. Congress sets the baseline rule that electronic signatures are valid. State legislatures fill in the details. Courts decide whether a specific signature met the rules. Platforms produce the evidence. Agents carry the personal risk when any link in the chain breaks.

FAQs

Can my spouse eSign a contract for me if I am out of town?

No. Marriage alone does not create signing authority. Your spouse needs a written power of attorney or similar delegation, or the contract must be in both spouses’ names already.

Can an executive assistant legally eSign for a CEO?

Yes. An executive assistant may sign if the CEO gives written authority and the signature block shows the assistant’s name and role, preserving the audit trail in the platform.

Can I use DocuSign under a power of attorney?

Yes. DocuSign supports POA signing when the agent uses a representative-capacity signature block and the POA itself authorizes the specific act being signed.

Can I eSign a will for my parent?

No. Most states, including California, exclude wills from eSignature laws, and a will signed by another person is almost always void.

Can a real estate agent eSign for a buyer or seller?

Yes. A licensed agent may sign only with a written, transaction-specific limited power of attorney and must disclose the representative capacity in the signature block.

Can an employer eSign an I-9 for a new hire?

No. The employee must personally sign Section 1 of the Form I-9, and only the authorized employer representative may sign Section 2 in the employer’s name.

Can a parent eSign for an adult child who is away at college?

No. Adulthood ends parental signing authority, and the parent needs a signed power of attorney or health-care proxy from the adult child to act.

Can I eSign a contract in New York the same way I would in Texas?

No. New York uses ESRA instead of UETA, and some documents that eSign fine in Texas still require wet ink or special formalities in New York.

Can an agent under a durable POA eSign after the principal dies?

No. Every power of attorney ends at the principal’s death under UPOAA § 110, and any signature after that date is void and may be forgery.

Can a paralegal eSign pleadings for an attorney?

No. Signing pleadings is the practice of law, and ABA Model Rule 5.5 bars non-lawyers from signing in the attorney’s name.

Can I eSign for a deceased relative’s estate?

Yes. The court-appointed executor or administrator may eSign estate documents using letters testamentary and a signature block that shows the estate and the fiduciary role.

Can a minor eSign on a parent’s behalf?

No. A minor lacks legal capacity to bind a parent, and any such signature is void even if the parent asked the minor to do it.

Can I use a saved image of someone’s signature with their permission?

Yes. You may paste a saved signature image only when the person gives clear written permission for that exact document and an audit trail records the authority and identity.