What are the three main requirements of the ESIGN Act?

Intent, consent, and retention. The signer must take an affirmative act demonstrating intent to sign; the parties must agree to transact electronically (with a formal disclosure-and-consent step for consumers under § 7001(c)); and the electronic record must be retained accurately and remain accessible for the required period under § 7001(d).

Does ESIGN require a specific type of electronic signature?

No. The statute is technology-neutral — typed names, drawn marks, clicks, and certificate-backed digital signatures all qualify under the § 7006(5) definition of "electronic sound, symbol, or process" adopted with intent to sign. Compliance is about the record around the act, not the technology of the mark.

What records does ESIGN § 7001(c) apply to?

Records that law requires to be provided to consumers in writing. The consumer must receive a specific disclosure — covering consent scope, hardware and software needs, and withdrawal rights — and affirmatively consent electronically in a way that demonstrates access to the electronic records. Business-to-business records have no equivalent formal step.

What happens if a document falls under a § 7003(a) exclusion?

ESIGN simply does not apply — the document's validity is governed by whatever law would otherwise apply, which usually means traditional execution: wet ink, witnesses, or notarial form as the specific statute requires. The exclusion does not make electronic signing illegal; it removes the federal presumption of validity for that category.

ESIGN Act Requirements: Meaning, Workflow, and Business Use

The ESIGN Act (Electronic Signatures in Global and National Commerce Act, 2000) sets three operational requirements for electronic signatures and records to hold in US commerce: the signer must intend to sign, the parties must consent to transact electronically, and the electronic record must be retained accurately and remain accessible. The statute is deliberately short and technology-neutral — it does not tell you how to sign, only what must be true for the result to count. The compliance work is building the workflow that makes those three things provable.

The Core Rule Before the Requirements

Section 7001(a) is the rule everything else serves: a signature, contract, or record "may not be denied legal effect, validity, or enforceability solely because it is in electronic form." ESIGN does not create signatures — it prevents their disqualification. The requirements below are what keep a specific signature on the right side of that rule in practice.

Requirement 1: Intent to Sign

The definition ESIGN protects — § 7006(5) — is "an 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." The operational requirement: the signer must take an affirmative act that demonstrates intent. Opening, viewing, or receiving a document shows nothing; clicking a signature field, typing a name into it, or applying a drawn mark shows intent — provided the record captures the act as an event, not just the resulting image.

ESIGN requires the parties to have agreed to do business electronically. For business-to-business transactions, consent can be inferred from conduct — no formal step required. For consumer records, § 7001(c) adds a formal structure:

A disclosure telling the consumer what electronic records and signatures mean for them, covering the hardware and software needed and how to withdraw consent.
Affirmative consent, given electronically, in a way that demonstrates the consumer can access the electronic records being consented to.
A logged consent event — the disclosure version, the action, and the timestamp — because the burden of proving consent sits with the party relying on it.

The workflow version of this requirement is a consent step in the signing flow that cannot be skipped and cannot be backdated. The policy layer is covered in Electronic Signature Policy: What to Include and Why.

Requirement 3: Accurate, Accessible Record Retention

§ 7001(d) makes retention part of validity: where a law requires a record to be retained, an electronic record satisfies it only if it "accurately reflects the information" in the original and "remains accessible" for the required period, in a form that can be accurately reproduced. Two operational consequences:

Integrity must be provable — the signed file must be sealed so later edits are detectable; the document hash at signing time is the standard mechanism.
Accessibility must be durable — the record must remain retrievable for the retention period regardless of vendor relationships, which is what portable exports are for. The audit-trail anatomy is in Audit Trails: What Belongs and What Doesn't.

The Exclusions: What ESIGN Does Not Cover

§ 7003(a) removes categories from the statute's reach: wills and testamentary trusts, family law documents, court orders and official court documents, utility termination notices, notices of default or repossession tied to a primary residence, and documents accompanying hazardous materials. State overlays add their own — recorder-bound real estate instruments being the common one. The bindingness analysis is in Are Electronic Signatures Legally Binding.

The Workflow That Satisfies All Three

A compliant signing workflow is just the three requirements made structural:

Presentation — the signer is shown the final document version, with any required disclosures.
Identification — identity verification at the level the document class requires.
Consent capture — the affirmative consent event, logged with its disclosure version.
The act — the affirmative signing action, logged with the document hash on screen at that moment.
Sealing and retention — the document is sealed and the full record exports as a portable package.

The business-use frame for the whole flow is in E-signatures: Meaning, Workflow, and Business Use, and the paperless program it slots into in Going Paperless: Workflow Design, Controls, and ROI.

Checklist Before You Treat a Flow as ESIGN-Compliant

Intent is an event: the signing act is captured, not just the resulting mark.
Consent is logged: affirmative action plus disclosure version, per signer.
Consumer flow has § 7001(c): disclosure, demonstrable access, withdrawal path.
Integrity is sealed: post-signing edits are detectable.
Retention is portable: the record exports and verifies without the vendor.
Exclusions are screened: document type is not on the § 7003(a) list.

ESIGN Compliance Enterprises Can Audit: Nota Sign

ESIGN compliance fails as a document exercise and succeeds as a workflow property, which is the distinction Nota Sign was built on. The five-stage flow above is the platform's default posture: presentation is logged, identity verification is set per document class, the consent step cannot be skipped or backdated, the signing act is captured with the document hash on screen at that moment, and every completed envelope exports one package — signed document, audit trail, consent records, timestamps — that satisfies § 7001(d) by construction because it verifies offline with no vendor in the loop.

ESIGN is where the requirement starts, not where it ends, and that is the difference between a US-only tool and a global one. DocuSign covers § 7001 well; what it does not cover is the rest of your counterparties' map — no native PRC flow for Chinese signers, no iAM Smart or Singpass for APAC ones. Nota Sign runs the same compliant workflow across more than 100 countries and regions: ESIGN and UETA in the US, eIDAS (SES, AES, QES) in the EU, and the full APAC compliance layer, on a SOC 2 Type II-audited environment, with standard electronic signatures and X.509-backed digital signatures in one envelope flow. Compliance across the China–overseas border runs in the same envelope: each party executes under its own jurisdiction's rules, and the record satisfies both sides' retention logic.

The pricing matches the compliance posture: no per-seat fees — unlike the per-seat incumbents, the legal reviewers and approvers who make a flow auditable never become license lines. Nota Sign is built by FaDaDa, China's leading e-signature vendor; small teams start on a low-cost package, and mid-market and enterprise buyers negotiate tailored plans sized to document volume and integration patterns. If you want to check one of your signing flows against the three requirements, contact sales and we will run a document through the platform and walk the compliance record it produces.