The ESIGN Act and UETA, explained for small business

Almost every e-signature tool's marketing page name-drops the ESIGN Act and UETA, usually in a single line that doesn't actually explain what either one requires of you as the business sending the contract. Here's the plain version, including the part that actually matters: what you need to do, not just what the law says in theory.

What each law says, in plain words

The Electronic Signatures in Global and National Commerce Act, known as the ESIGN Act, is a US federal law passed in 2000. Its core rule, from 15 U.S.C. § 7001, is that a "signature, contract, or other record relating to such transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form." It applies to transactions affecting interstate or foreign commerce, which in practice covers the overwhelming majority of normal business dealings.

The Uniform Electronic Transactions Act, UETA, is a model law written for individual states to adopt, and it's been adopted in some form by 49 states plus Washington DC and the US Virgin Islands. UETA covers the same basic ground as ESIGN but at the state level, for transactions that ESIGN's federal reach doesn't necessarily cover, and it's the law actually governing most state-level contract disputes. A couple of states have their own slightly different statutes rather than adopting UETA's exact text, which is a detail worth checking if you're dealing with an unusual transaction type in a specific state, rather than something I'd generalize about here without you confirming it directly for your situation. A state-by-state quick reference lists the details.

In practice, ESIGN and UETA work together, not against each other. ESIGN sets a federal floor that preempts a state from banning electronic signatures outright; UETA (or each state's own equivalent law) fills in the actual mechanics most contract disputes get decided under.

What a business must actually do

Three things, in practice, cover almost everything:

• Get real consent, especially from consumers. ESIGN specifically requires that when a law mandates a written disclosure to a consumer, you need the consumer's affirmative consent to receive it electronically instead, clear notice of their right to get a paper copy, and confirmation they can actually access the format you're sending. For business-to-business contracts, this is less rigid, simply proceeding to sign electronically is generally treated as consent, but stating it plainly in the contract is cleaner and avoids any argument later. What to tell customers is covered in e-sign consent and disclosure.
• Keep an accessible, accurate record. You need to be able to produce the signed document later, in essentially the form it was in when signed. This is exactly what a proper e-signature tool's audit trail and document storage are built to handle, timestamped, tied to the specific signer, and retrievable on demand.
• Don't quietly change the format on someone. If you change your system in a way that affects a consumer's ability to access records they previously consented to receive electronically, you generally need to notify them and get fresh consent. This one trips up businesses switching e-signature or document platforms more than people expect.

Exceptions, and where it genuinely gets tricky

Both laws carve out specific exclusions rather than covering absolutely everything electronically. Under ESIGN, the clearest exclusions include wills and testamentary trusts, certain family law documents like divorce and adoption papers, court orders and official court documents, notices of eviction, foreclosure, or termination of utility services, and notices of product recalls or health and safety information related to hazardous materials. Requirements around notarization, acknowledgment, verification, or oath-taking can generally still be satisfied electronically, as long as the person doing the notarizing or verifying is properly authorized and the electronic method actually fulfills the legal function, which is exactly the gray area that remote online notarization laws, state by state, have been built to clarify.

Where it gets genuinely tricky for a small business is less about the law itself and more about counterparties and specific industries. A bank, insurer, or government office might still require certain documents on paper due to their own internal policy, independent of what ESIGN or UETA technically allow. Certain regulated industries, healthcare records under HIPAA, specific financial disclosures, layer additional requirements on top of the basic electronic signature framework. None of that makes electronic signing invalid, but it does mean "ESIGN says it's fine" isn't always the complete answer for a specific document in a specific industry.

How the two laws actually interact in a dispute

A detail that confuses even people who've read both laws: ESIGN doesn't disappear once a state adopts UETA. ESIGN includes a specific provision allowing it to be superseded by a state's adoption of UETA, but only if that state adopts UETA in a form consistent with ESIGN's own standards, and even then, certain ESIGN provisions remain in effect regardless. In practice, this means a contract dispute in a UETA state is usually decided primarily under that state's UETA statute, with ESIGN sitting in the background as the federal floor that prevents any state law from denying electronic signatures validity outright. You don't need to litigate this distinction yourself, a lawyer would if it ever actually mattered, but it explains why you'll see both laws cited together so often: they're doing complementary jobs, not competing ones.

A worked example

Say you run a small landscaping business and send a seasonal maintenance contract to a residential client by email, with a link to sign electronically. The client signs, and three months in, disputes a clause about the cancellation fee, claiming they never really "agreed" to the contract, just clicked through it. Here's where ESIGN and UETA actually earn their keep: because your signing tool captured the client's affirmative action to sign, timestamped it, and tied it to their verified email and IP address, you have concrete evidence of exactly what was presented and what intent was shown. That's the practical payoff of these two laws existing, not an abstract legal point, but real evidence you can point to when a disagreement like this comes up, which happens more often in small business than people expect. If the client had printed and signed on paper instead, whether a signed paper copy still wins is a fair question.

A second worked example: switching platforms

Say you've been using one e-signature tool for three years and decide to switch to another, perhaps to save money or get better features. If any of your existing consumers previously consented to receiving disclosures electronically in a specific format tied to your old platform, and the new platform delivers documents in a meaningfully different way, say, a different file type, or a portal that requires a new login rather than a simple email link, ESIGN's requirement to notify and re-confirm consent when a system change affects access can genuinely apply. Most small businesses never think about this when evaluating a platform switch purely on cost and features. It's a small, easily missed step, a short notice to existing customers confirming they can still access documents in the new format, but skipping it is exactly the kind of technical gap that becomes a real problem only if a dispute happens to come up during or after the transition.

A quick reference for which law actually governs a dispute

If you ever need the short version for your own records: a dispute over a contract's enforceability as electronic generally gets decided under your state's own electronic transactions statute, UETA in most states, or the state's own separate law in a handful of others, with the federal ESIGN Act operating as a backstop that prevents any state from categorically rejecting electronic signatures. Neither law requires you to cite it in the contract itself for it to apply; they're a legal framework that exists regardless of whether the document mentions them, similar to how contract law generally applies without needing to be referenced explicitly in every agreement.

How I'd approach this

When I'm setting up contract or document signing for a client, I treat ESIGN and UETA as the baseline, not the finish line. The baseline tells me electronic signing is legally sound for the document in front of me, which is true for the large majority of everyday business contracts. The actual work is confirming consent is genuinely captured, the audit trail is solid enough to hold up if challenged, and the specific document isn't one of the excluded types above. That's a short checklist, but it's the difference between "technically legal" and "actually going to hold up if someone pushes back."

Frequently asked questions