Checklist · Technology

Building an Enforceable Online Agreement and E-Signature Process: A Practical Checklist

15 U.S.C. § 7003

Type: Checklist
Jurisdiction: National
Date: 2024-03-26
Topic: Technology

This checklist builds an online agreement and e-signature process that will actually be enforced, and preserves the records to prove it years later, in nine phases. Phase 1 is scoping: which documents may be executed electronically at all, given the statutory exclusions that trap careless practitioners. Phase 2 is the assent screen, specified element by element against the case law from Specht through Meyer. Phase 3 is the consumer consent procedure required whenever an electronic record substitutes for a statutory writing, and Phase 4 is the records architecture: terms versioning, interface archiving, and the event log field that most systems omit. Phase 5 covers the confirmation email and Phase 6 covers modification, which fails more often than practitioners expect. Phase 7 covers the regulatory overlay including dark patterns, negative option billing, and cancellation symmetry. Phase 8 covers signature platforms, identity verification, signing authority, and remote notarization, and Phase 9 is a litigation-readiness audit run annually against three real accounts. Five model documents, a design specification table, and a ranked failure-mode list are included.

Building an Enforceable Online Agreement and E-Signature Process: A Practical Checklist

Technology > E-Commerce | Published 26 March 2024 - Updated 14 March 2026 | UpLaw - uplaw.us

Three engineering tasks determine whether an entire consumer contract portfolio is provable. Phase 4 is those three tasks.

Keywords: assent screen, terms versioning, event log, consumer consent, modification, cancellation symmetry, audit trail

How to use this checklist

Nine phases. Each has - [ ] items and a Why it matters, and the traps note. A fictional dispute — a meal delivery service, a Start My Plan button, and $340 in contested charges — runs throughout.

Doctrine is in Electronic Signatures and Online Contract Formation: A Comprehensive Guide to ESIGN, UETA, and Clickwrap. The narrative is I Agree: How a Click Became a Contract. The materials are in The Electronic Contracting and E-Signature Toolkit.

Phase 1 — Scope: what may be signed electronically

[ ] Inventory every document type the business executes.
[ ] Check each against the exclusions at 15 U.S.C. § 7003.
[ ] Flag wills, codicils, and testamentary trusts.
[ ] Flag adoption, divorce, and family law documents.
[ ] Flag court documents.
[ ] Flag notices of default, acceleration, repossession, foreclosure, eviction, or right to cure on a primary residence.
[ ] Flag health and life insurance cancellation notices, utility cancellations, and product recall notices.
[ ] Flag documents requiring acknowledgment or notarization.
[ ] Flag documents requiring attesting witnesses.
[ ] Confirm your state's enactment of the uniform act — 15 U.S.C. § 7002.
[ ] Confirm the parties have agreed to conduct business electronically, from context and conduct.
[ ] Write the policy down, so it is not researched under time pressure.

Why it matters, and the traps. 15 U.S.C. § 7003 is the most-ignored provision in the statute. Several states now authorize electronic wills under specific schemes, but the default assumption must be that an excluded document requires a separate statutory basis.

Notarization is a separate regime, not a subset of electronic signature law, and a document requiring an acknowledgment is not cured by a click. Witness "presence" requirements have been amended, allowed to lapse, and re-amended in many states — check the current statute rather than a memory of it.

Phase 2 — The assent screen

[ ] Layout, in order: form fields → assent sentence → button.
[ ] Put the notice above the button, never below.
[ ] Use body text size and color — not gray, not eight-point.
[ ] Name the button in the sentence: "By clicking Create Account, you agree to…"
[ ] Hyperlink both the terms and the privacy policy, styled unmistakably as links.
[ ] Ensure the entire flow is visible without scrolling on the target device.
[ ] Keep the screen uncluttered — no promotional content competing with the notice.
[ ] Ensure nothing on the page contradicts the notice about what the button does.
[ ] For arbitration, class waivers, limitations of liability, or assignments: add a separate unchecked checkbox naming those terms.
[ ] Never pre-check a consent box.
[ ] Test every mobile breakpoint and confirm the notice stays above the fold.
[ ] Avoid browsewrap entirely.

Why it matters, and the traps. Specht v. Netscape Communications Corp., 306 F.3d 17 (2d Cir. 2002) refused enforcement where terms sat below the download button. Nguyen v. Barnes & Noble Inc., 763 F.3d 1171 (9th Cir. 2014) held that a conspicuous footer link near the checkout button, with no affirmative act, is not constructive notice. Sgouros v. TransUnion Corp., 817 F.3d 1029 (7th Cir. 2016) refused where page text said the button did something else. Meyer v. Uber Technologies, Inc., 868 F.3d 66 (2d Cir. 2017) enforced an uncluttered screen with the notice above the button.

Notice below the button is the single most common real-world defect, and it is free to fix. A user fills the fields top to bottom and clicks; everything below the button is past the end of the interaction.

Worked example. The meal service put its notice below the button in gray eight-point type. Everything else about the screen was fine. That one choice turned a routine motion into contested litigation.

Phase 3 — Consumer consent for statutory writings

[ ] Identify every disclosure another law requires in writing.
[ ] Provide a clear and conspicuous statement of the right to a paper copy and any fee.
[ ] State whether consent covers this transaction only or categories of records.
[ ] State how to withdraw consent, the consequences, and any fee.
[ ] State how to update contact information.
[ ] Provide the hardware and software requirements for access and retention.
[ ] Obtain consent electronically, in a manner that reasonably demonstrates the consumer can access the format that will be used.
[ ] Re-obtain consent if the technical requirements change materially.
[ ] Log the consent event separately from the contract assent event.

Why it matters, and the traps. This is 15 U.S.C. § 7001's consumer consent procedure, and it is skipped constantly.

The contract can be perfectly enforceable and the disclosure still defective, and the consequences are entirely different — statutory damages and extended rescission rights rather than a formation dispute. Companies that get the assent screen right frequently assume they are finished, then route credit disclosures required by 15 U.S.C. § 1638 and 12 C.F.R. part 1026 through the same generic email pipeline as marketing.

Phase 4 — Records: the three tasks

[ ] Version the terms, each with an effective date and an immutable identifier.
[ ] Archive a rendering of every deployed assent screen, at every major breakpoint.
[ ] Log the terms version identifier in the assent event.
[ ] Log timestamp, account identifier, address, user agent, and the specific action taken.
[ ] Retain the deployment history of the interface.
[ ] Ensure records remain accessible and capable of accurate reproduction.
[ ] Confirm records survive vendor migration and contract termination.
[ ] Define retention periods matched to the longest applicable limitations period.
[ ] Assign an owner for the archive who is not the product team.
[ ] Test retrieval annually with a live sample.

Why it matters, and the traps. This is where enforceable agreements die.

Companies redesign flows constantly and rarely archive them. Two years later counsel produces the current screen and the current terms, neither of which proves anything about the transaction at issue. A perfectly enforceable agreement becomes unprovable through ordinary product iteration.

The three tasks — version identifier in the log, archived rendering, terms in the confirmation email — are each smaller than a sprint and together convert nine months of contested litigation into a two-page declaration. A record you cannot render is not a retained record, which is why vendor migrations destroy evidence routinely.

Phase 5 — The confirmation email

[ ] Send it immediately on assent.
[ ] Attach or link the operative version of the terms — not "our terms."
[ ] State the date and time of acceptance.
[ ] Identify the account and the transaction.
[ ] Keep it transactional, separate from marketing.
[ ] Retain the message content and evidence of delivery.
[ ] Comply with 15 U.S.C. § 7701 where any message is commercial: accurate headers, working opt-out, physical postal address.

Why it matters, and the traps. The confirmation email is the cheapest corroboration available and it is routinely wasted by linking to a page that later changes.

Keeping transactional messages separate from marketing matters for both deliverability and the commercial-email rules.

Phase 6 — Modification

[ ] Give direct notice — email or a dismissable in-product notice.
[ ] State a future effective date.
[ ] Summarize what changed, not just that something did.
[ ] Provide a meaningful opportunity to reject, generally by terminating.
[ ] Require an affirmative click for material changes.
[ ] Apply changes prospectively only.
[ ] Log the modification assent exactly as the original.
[ ] Never add an arbitration clause or class waiver by silent posting.
[ ] Retain the prior version and the notice sent.

Why it matters, and the traps. A promise performable however one side later chooses is illusory, and modification requires assent, which requires notice. Posting to a page nobody visits is not notice, and "continued use constitutes acceptance" fails where the user did not know there was anything to accept.

Retroactive application to an existing dispute draws the hardest scrutiny of all. Treat a material amendment as a new agreement requiring new assent.

Phase 7 — The regulatory overlay

[ ] Audit the interface for dark patterns — 15 U.S.C. § 45 and every state act.
[ ] Remove asymmetric choice architecture, confirmshaming, pre-selection, false urgency, and misdirection.
[ ] For subscriptions: disclose all material terms before obtaining billing information — 15 U.S.C. § 8403.
[ ] Obtain express informed consent to the recurring charge.
[ ] Provide a simple mechanism to stop recurring charges.
[ ] Make cancellation no harder than sign-up.
[ ] For telephone transactions, check 16 C.F.R. part 310.
[ ] For bank debits rather than cards, comply with 15 U.S.C. § 1693c and honor stop-payment rights.
[ ] If minors may use the service, address 15 U.S.C. § 6501 and verifiable parental consent.
[ ] Check state auto-renewal statutes, many of which add private remedies.

Why it matters, and the traps. Cancellation symmetry is the operative principle. A subscription started in two clicks and cancellable only by telephone during business hours is the paradigm enforcement case.

These claims frequently survive an order compelling arbitration, and state unfair practices acts often carry statutory damages and fee-shifting that make a small claim viable when the contract claim is not.

Phase 8 — Platforms, identity, and notarization

[ ] Choose a platform producing a tamper-evident record and a certificate of completion.
[ ] Store the certificate with the executed document, not only in the platform.
[ ] For high-value agreements and guarantees, add identity verification.
[ ] Require signature from a device previously associated with the signer where feasible.
[ ] Deliver the executed copy to an independently confirmed address.
[ ] For entities, verify the signer's authority to bind, and configure the platform so only designated signers can complete high-value envelopes.
[ ] Record the signer's title and the authority relied on in the signature block.
[ ] For remote notarization, follow the specific state statute: identity proofing, credential analysis, audio-visual recording, journal, and retention.
[ ] Confirm the recording jurisdiction accepts an out-of-state remote notarization.
[ ] Plan for vendor migration without losing certificates.

Why it matters, and the traps. A platform proves a great deal and does not prove that the named person pressed the key. Attribution is a factual question shown in any manner, including the efficacy of the security procedures — and a one-time code sent to a phone proves the code was entered, not who entered it.

Authority is the business-side failure. Electronic execution makes it trivially easy for someone without authority to bind an entity, and the attribution rules answer whether the person signed, not whether they could bind the company.

Phase 9 — Annual litigation-readiness audit

[ ] Pick three real accounts from the past three years at random.
[ ] For each, produce: the terms version in force, the rendering of the screen as deployed, the assent event log with version identifier, the deployment record, and the confirmation email with delivery evidence.
[ ] Time how long it takes.
[ ] Identify who could provide a declaration from personal knowledge of the system.
[ ] Verify the archive survived every deployment and vendor change in the period.
[ ] Verify records are still capable of accurate reproduction.
[ ] Review any interface changes against Phase 2.
[ ] Review any terms changes against Phase 6.
[ ] Re-check Phase 1 exclusions against current state law.
[ ] Document the audit.

Why it matters, and the traps. This audit takes an afternoon and finds the failure before opposing counsel does.

The most common defect it surfaces is a declaration that would have to attach current artifacts — and current terms with a current screenshot prove nothing about a transaction fourteen months old.

Model language

A. The assent sentence

By clicking Create Account, you agree to our [Terms of Service] and [Privacy Policy].

B. Material-terms checkbox

☐ I have read and agree to the [Terms of Service], which include an arbitration provision and a class action waiver that affect how disputes are resolved.

C. Consumer consent to electronic records

"We can provide the disclosures required for this transaction electronically instead of on paper. You have the right to receive them on paper at no charge, and to withdraw your consent to electronic delivery at any time by [method], which will [consequences]. This consent applies to [this transaction only / the categories listed below]. To access and retain these records you will need [hardware and software requirements]. To confirm you can access documents in the format we will use, please open the sample document at [link] and then check the box below. ☐ I can open the sample document and I consent to receive these records electronically."

D. Modification notice

"We are changing our Terms of Service, effective [future date]. What changed: [plain-language summary of each material change]. If you do not agree, you may [terminate / decline] before [date] at [link]. These changes apply only to activity on or after the effective date. To continue, please review and accept the updated terms: [button]."

E. Cancellation disclosure

"Your plan renews automatically every [period] at $[amount], charged to the payment method on file, until you cancel. You can cancel at any time in two clicks at [link] — no phone call required. Cancellation takes effect at the end of the current period."

Design specification, at a glance

Element	Requirement
Position of notice	Above the button
Text size and color	Same as body text; never gray micro-type
Sentence	Names the button and links both documents
Links	Visually unmistakable
Scrolling	Not required to see the notice
Competing content	None
Contradictory text	None anywhere on the page
Material terms	Separate unchecked checkbox
Breakpoints	Every one tested and archived
Event log	Timestamp, account, address, user agent, action, terms version
Confirmation email	Attaches or links the operative version

Failure modes, ranked

Notice below the button.
Gray, undersized notice competing with promotional content.
Browsewrap — a footer link and a hope.
A button label describing something other than agreeing, with no adjacent notice.
Page text contradicting the notice.
Untested mobile breakpoints.
Not logging the terms version identifier.
Not archiving renderings of each deployed screen.
Confirmation emails that link a page which later changes.
Modification by silent posting, applied retroactively.
Skipping the 15 U.S.C. § 7001 consumer consent procedure.
Electronic execution of a 15 U.S.C. § 7003 excluded document.
Treating remote notarization as ordinary electronic signature.
Storing certificates only in the vendor platform.
Cancellation materially harder than sign-up.

The three tasks, restated as a ticket

Phase 4 is the phase everyone skips because it belongs to engineering rather than legal, and no one owns the handoff. Here it is written as something a team can actually pick up.

Ticket 1 — Version the terms and log the version.

Today: the assent event records user_id, timestamp, ip, user_agent, event: account_created.

Required: add terms_version_id and privacy_version_id, populated from whatever the interface actually rendered at that moment — not from a lookup performed later. The distinction matters: a later lookup reconstructs what should have been shown; the rendered value records what was.

Acceptance criteria: given any account identifier, the system returns the exact terms document displayed at sign-up, retrievable as a document rather than a version string.

Ticket 2 — Archive the assent screen.

Today: the sign-up flow is deployed continuously and no rendering is preserved.

Required: on each deployment that touches the assent flow, capture and store a rendering at each supported breakpoint — desktop, tablet, and at least two phone widths — tagged with the deployment identifier and date range.

Acceptance criteria: given any date in the past seven years, the system returns an image of the screen a user would have seen on that date, at a specified viewport width.

Ticket 3 — Carry the terms in the confirmation email.

Today: the confirmation email links to /terms, which resolves to the current version.

Required: attach the operative version as a file, or link to a version-pinned URL that will not change.

Acceptance criteria: the confirmation email, retrieved from the mail archive, resolves to the terms as they existed on the send date.

Why this framing works. Each ticket is smaller than a sprint, each has a testable acceptance criterion, and together they convert nine months of contested litigation into a two-page declaration. The reason they do not get written is not cost — it is that the person who understands why they matter does not write tickets, and the person who writes tickets has never read a motion to compel arbitration.

Reading a screen against the case law

Use this to assess an existing flow — yours or an opponent's. Score each row.

Question	If yes	If no
Is the notice on the same screen as the button, without scrolling?	Good	Specht problem
Is it above the button?	Strong — compare Meyer	Weak; the most common defect
Is it in body text size and color?	Good	Conspicuousness argument available
Does the sentence name the button?	Strong	Ambiguous action problem
Are the links visually unmistakable?	Good	Notice argument weakens
Is the user's action unambiguous?	Strong	"Start My Plan" means start my plan
Does any page text describe the button differently?	Fatal — Sgouros	Good
Is there an affirmative act tied to the terms?	Clickwrap	Browsewrap — Nguyen
Does the notice stay above the fold on a phone?	Good	Untested breakpoints
Is the screen uncluttered?	Good	Competing-attention argument

A flow that fails rows two, three, and nine is not unenforceable — it is contestable, which is worse than it sounds, because the cost is measured in motion practice rather than in outcomes.

What "provable" looks like: the declaration test

The practical test of everything in Phases 4 and 5 is whether a competent declaration can be written without hedging. Draft it now, hypothetically, for an account from two years ago:

"I am [name], [title] at [company]. I have personal knowledge of the systems described. On [date], account [identifier] was created from address [address] using [user agent]. At that time, the sign-up interface deployed in production was the version attached as Exhibit A, captured from our interface archive at deployment [identifier], effective [date range]. The Terms of Service in force and displayed to that user were version [identifier], attached as Exhibit B with an effective date of [date]. Our event log for that account records terms_version_id: [identifier], attached as Exhibit C. A confirmation email attaching those terms was delivered to [address] on [date], attached as Exhibit D with delivery confirmation."

Every sentence in that paragraph corresponds to one item in Phase 4 or 5. If you cannot write it, the audit in Phase 9 has already told you where the gap is — and the gap is almost always Exhibit A, because interface archives are the one artifact nobody thinks to keep.

The version most companies can actually produce reads: "Our current terms are attached. Our sign-up flow has always displayed a notice." That is an inference rather than a record, courts do sometimes accept it, and it converts a routine motion into a fight.

Three sentences worth memorizing

"The statute removed an obstacle; it did not create an agreement."

"Notice above the button, in body text, naming the button."

"Log the terms version, and archive the screen."

Building an Enforceable Online Agreement and E-Signature Process: A Practical Checklist

How to use this checklist

Phase 1 — Scope: what may be signed electronically

Phase 2 — The assent screen

Phase 3 — Consumer consent for statutory writings

Phase 4 — Records: the three tasks

Phase 5 — The confirmation email

Phase 6 — Modification

Phase 7 — The regulatory overlay

Phase 8 — Platforms, identity, and notarization

Phase 9 — Annual litigation-readiness audit

Model language

A. The assent sentence

B. Material-terms checkbox

C. Consumer consent to electronic records

D. Modification notice

E. Cancellation disclosure

Design specification, at a glance

Failure modes, ranked

The three tasks, restated as a ticket

Reading a screen against the case law

What "provable" looks like: the declaration test

Three sentences worth memorizing

Related Documents