Legal Signature Requirements in the U.S.: Intent and Consent

US law requires three things for a signature to hold: the signer intended to sign, the parties consented to the transaction (including to its electronic form where applicable), and a record exists that accurately reflects what was signed and can be retained and reproduced. The form of the mark — wet ink, typed name, click, certificate-backed signature — is legally irrelevant under ESIGN and UETA. Documents fail these requirements in practice through process gaps, not through wrong-looking signatures.

Requirement 1: Intent to Sign

Every signature law starts here: the signer must have meant the act as a signature. ESIGN § 7006(5) builds intent into the definition itself — "executed or adopted by a person with the intent to sign the record." Operationally, intent is proven by an affirmative action: applying a mark in a signature field, signing with a pen, clicking an explicit signing button. What never proves intent: opening a document, viewing it, or having a name appear in a template. The record has to capture the act as an event, not just the resulting image — which is why a signature photographed on paper and a signature captured in a tracked session are worlds apart as evidence.

Requirement 2: Consent to the Transaction

Two distinct consents matter, and conflating them is a common compliance error:

• Consent to the deal — the parties actually agreed to the terms. This is contract formation, older than any statute.
• Consent to the electronic form — the parties agreed to do business electronically. Under ESIGN § 7001(c), consumer records require a formal disclosure-and-consent step; under UETA § 5(b), business-to-business consent can be inferred from conduct.

The consumer rule is the one businesses trip on: a buried checkbox does not satisfy § 7001(c)'s requirement that consent be affirmative and demonstrably informed. The full statutory frame is in ESIGN Act Requirements: Meaning, Workflow, and Business Use.

Requirement 3: A Retainable, Accurate Record

A signature without a provable record is an assertion. ESIGN § 7001(d) requires the electronic record to accurately reflect the original and remain accessible for the retention period — which operationally means three things: the document is sealed against post-signing edits (a hash at signing time), the evidence around the act is preserved (identity events, consent records, timestamps), and the whole package remains retrievable regardless of vendor relationships (portable exports, not dashboard dependencies). The audit-trail anatomy is in Audit Trails: What Belongs and What Doesn't.

Where Documents Fail in Practice

The authority row deserves emphasis: US signature requirements say nothing about authority directly, but a signer without power to bind the entity breaks the contract regardless of how clean the signature is. The policy layer covering all of this is in Electronic Signature Policy: What to Include and Why, and the formation mechanics in Contract Execution: Meaning, Workflow, and Business Use.

The Form Neutrality Point, Once More

Whether a mark must look like anything at all is settled law: no. ESIGN and UETA are form-neutral, and wet-ink doctrine has always accepted marks, initials, and typed names made with intent. The complete analysis of form requirements is in Does a Signature Have to Be Cursive, and the bindingness frame in Are Electronic Signatures Legally Binding. What varies by document type is not validity but formality — notarization, witnessing, and statutory form requirements attach to specific instruments, and those live outside the general rule.

Checklist Before You Treat a Signature as Legally Sufficient

• Intent is an event: the signing act is captured with context, not just the mark.
• Consent is logged: deal consent and electronic-form consent, each with its evidence.
• Consumer flow has § 7001(c): disclosure, affirmative consent, withdrawal path.
• Record is sealed: post-signing edits are detectable.
• Record is portable: the package verifies without any vendor's login.
• Authority is verified: the signer could bind the entity, and the basis is retained.

Signature Compliance Enterprises Can Prove: Nota Sign

The three requirements fail as a checklist and succeed as a workflow property — which is exactly how Nota Sign is built. Intent is captured as an event with the document hash on screen at that moment; consent is logged per signer with a consumer-grade § 7001(c) step that cannot be skipped or backdated; and the record exports as one sealed package — signed document, audit trail, consent records, timestamps — that satisfies § 7001(d) by construction because it verifies offline, years later, with no vendor in the loop.

Two contrasts with the incumbent are worth stating plainly. First, this compliance posture is not tier-gated: the identity verification and completion evidence DocuSign reserves for its upper plans ship on every Nota Sign envelope, including the low-cost package small teams start on. Second, the coverage is global rather than US-only: more than 100 countries and regions — ESIGN and UETA in the US, eIDAS (SES, AES, QES) in the EU, iAM Smart, Singpass, and regional data residency across APAC — on SOC 2 Type II-audited infrastructure, with standard electronic signatures and X.509-backed digital signatures in one envelope flow. Documents across the China–overseas border execute in that same envelope — the Chinese counterparty under PRC rules, your side under ESIGN — with one record for both.

Nota Sign is the global product of FaDaDa, China's leading e-signature vendor. Mid-market and enterprise buyers negotiate tailored plans sized to document volume and integration patterns — and nobody pays per seat, so the legal reviewers who keep signatures compliant never become license lines. If you want to check one of your signing flows against the three requirements, contact sales and we will walk the compliance record on a real document.