Guide
What Is the ESIGN Act? A Plain-English Guide
The ESIGN Act is a U.S. federal law, passed in 2000, that says a contract or signature can't be denied legal effect just because it exists in electronic form instead of on paper.
The basics
Full name: the Electronic Signatures in Global and National Commerce Act. Codified at 15 U.S.C. §7001 and following. Passed by Congress and signed into law in June 2000, at a point when e-commerce was growing fast and courts hadn't settled whether an electronic signature actually counted as a signature.
What it actually says, stripped of the statutory language: if a law requires a signature or a written record, an electronic signature or electronic record satisfies that requirement — provided the people involved consented to transact electronically and a few basic safeguards are in place.
What it requires, in practice
- Consumer consent, with a real disclosure. If a consumer is on the other end of the transaction, the law requires they be told, in a specific way, that they have the right to receive paper instead, and that they consent to electronic records. (Business-to-business transactions have a lighter version of this requirement.)
- The record has to be retainable. A consumer has to be able to keep an accurate, reproducible copy — a signature process that only shows a document once, with no way to get a copy later, doesn't meet the bar.
- No favoritism toward any particular technology. ESIGN is deliberately "technology neutral" — it doesn't require a specific type of e-signature software, a digital certificate, or any particular vendor. A typed name with the right process behind it counts the same as a drawn signature.
How it relates to state law
ESIGN operates alongside, not instead of, state law. Most states independently adopted UETA (the Uniform Electronic Transactions Act) to cover the same ground at the state level — see our ESIGN Act vs. UETA comparison for exactly how the two divide the work. The short version: state UETA law generally governs day-to-day transactions, and ESIGN's federal provisions step in as a backstop, including preempting any state law that tries to require a specific technology or discriminate against electronic signatures outright.
What it doesn't do
ESIGN doesn't make any electronic signature automatically valid regardless of how it was collected — it sets the conditions (consent, retainability, non-discrimination), and a signature process still has to actually meet them. It also explicitly carves out several document categories where it doesn't apply at all: wills and testamentary trusts, certain family law matters, court orders, and a handful of consumer notices (things like eviction, foreclosure, and utility or insurance cancellation notices). Those need a different process regardless of what tool you're using.
Where the real depth is
Because ESIGN describes required outcomes — consent, attribution, retention, an audit-worthy record — rather than mandating specific technology, the actual compliance work happens in how a signing tool is built. In DocuAgree, that's: an explicit ESIGN/UETA disclosure every signer has to accept before signing, IP address / device / timestamp captured server-side at the moment of signing (not asserted by the signer), and a SHA-256 hash of the final document computed the instant it's completed, so any later alteration is detectable. Read more on what makes a signature legally binding and what holds up if it's ever challenged.
General information, not legal advice for your specific situation. For a transaction with real legal stakes, get an attorney's opinion on your specific facts.