Electronic Signature Legality (ESIGN Act and UETA)

Why this matters

Trade businesses rely on electronic signatures for proposals, change orders, completion sign-offs, customer authorizations for credit card charges, and employment paperwork. Most owners use DocuSign, Adobe Sign, the signature pad on the technician's tablet, or a generic "I agree" checkbox in the customer portal without knowing whether those captures will hold up if challenged. The legal foundation is well established and dates back to 2000 federal law and state-level uniform acts; understanding what makes an electronic signature enforceable lets the business design its workflows so the signatures actually do the legal work they are supposed to do.

The two governing laws

Two laws govern electronic signatures in the United States:

ESIGN Act (Electronic Signatures in Global and National Commerce Act), 15 USC Chapter 96. Federal law enacted in 2000. Applies to interstate and foreign commerce; preempts state law unless the state has enacted UETA.

Uniform Electronic Transactions Act (UETA). State-level uniform act drafted in 1999. Adopted by 49 states, the District of Columbia, Puerto Rico, and the US Virgin Islands. New York is the lone non-UETA state and has its own equivalent statute (NY Technology Law Article 1).

In practice, the two laws produce substantially the same result: an electronic signature has the same legal effect as a handwritten signature when certain conditions are met.

The four conditions for enforceability

Four conditions must be met under ESIGN and UETA:

1. Intent to sign. Signer intended to sign deliberately (clicking a Sign button, drawing on a pad with knowledge of what is being signed, typing the name in a designated field with a "by typing my name I am signing" disclosure).
2. Consent to transact electronically. Express or implied. Consumer transactions require affirmative consent and disclosure (see below); B2B is often inferred from context.
3. Association with the record. Signature bound to the document (embedded in the PDF, or stored as a database record referencing the document by hash). Captured separately without binding fails.
4. Record retention. Signed record retained in a form that produces an accurate reproduction. Captured-then-lost is unenforceable.

DocuSign, Adobe Sign, PandaDoc, HelloSign are engineered to meet all four. Custom-built signature capture must explicitly meet the four conditions.

Consumer disclosure requirement

ESIGN requires consumer-transaction disclosure before electronic consent: the right to a paper copy; the right to withdraw consent and the procedure; whether consent applies to this transaction or a category; hardware/software requirements; how to update contact info. Consumer affirmatively consents after review (button or checkbox); the platform usually provides a template, but verify it covers all five. B2B does not require this disclosure; mixed contexts (sole-prop owner signing personally) apply it as a conservative practice.

Acceptable signature types and wet-signature carve-outs

ESIGN and UETA are technology-neutral. Acceptable forms: typed name in a designated signature field, drawn signature on a touchscreen or signature pad, clicked "I agree" button with appropriate context, digital signature with cryptographic certificate, emailed "I agree" response, voice signature recorded with consent. The technology does not determine enforceability; the four conditions do.

Documents excluded from ESIGN that require wet signatures: wills and testamentary trusts; adoption, divorce, and family law documents; court orders and official court documents; notices of cancellation of utility, life, or health insurance services; notices of default, foreclosure, or eviction for primary residence; product recall notices affecting health or safety; documents required by transportation of hazardous materials. For trade businesses the practical impact is limited; most business-generated documents (proposals, change orders, completion authorizations, employment agreements) are eligible for electronic signature. State laws sometimes require wet signatures for local-permit applications, certain real-property transactions, and some commercial loan documents.

Workflow design for enforceability

An enforceable workflow: identify the signer (in-person establishes identity; remote uses email or login, MFA or knowledge-based authentication for high-value documents); present the document in full (not summary; the signer can scroll, read, review); capture consent with clear "by signing below, you agree to the terms" disclosure preceding the action; capture the signature (typed, drawn, or clicked); bind the signature to the document (most platforms embed in a PDF with a content hash); provide a copy via email; retain the signed document with audit trail (timestamp, IP, signer email); maintain the platform's audit log as the primary evidence for challenges.

For in-home tablet signatures, the workflow has to display the full document (not just "Sign here"), capture the signature image, bind to the document with timestamp, generate a signed PDF, email the PDF to the customer, and retain in the CRM. Modern FSM platforms handle this end-to-end; verify the audit-log and email-delivery steps are configured.

Common failures, state notes, and retention

Common workflow failures: signature captured before the document is shown (intent and consent fail); signature captured but not bound to document (no association); never emailed back to signer (provide-a-copy requirement); no retention; consumer disclosure skipped; generic "I agree" with no context (intent challengeable).

State variations are minor for trade purposes; the federal ESIGN floor applies in all states. New York: UETA not adopted, NY Technology Law Article 1 applies. Illinois and California: UETA with state variations; California AB 1755 added remote online notarization provisions separate from standard e-signature.

ESIGN and UETA do not set a retention period; the underlying transaction's recordkeeping requirements govern. Customer contracts: warranty period plus contract statute of limitations (typically 4 to 6 years). Employment agreements: throughout employment plus the longest applicable statute (often 4 to 7 years post-termination). Credit card authorizations: per card-network rules plus PCI DSS. Retention must be in a form that produces an accurate reproduction of the original.

References

• ESIGN Act, 15 USC Chapter 96, Sections 7001-7031
• Uniform Electronic Transactions Act (UETA), 1999, adopted by 49 states
• New York Technology Law, Article 1 (Electronic Signatures and Records Act)
• FTC guidance on electronic signatures in consumer transactions
• NIST Special Publication 800-63B, Digital Identity Guidelines, Authentication and Lifecycle Management
• 26 USC 6001 - Notice or regulations requiring records (retention requirements for tax purposes)