What makes an e-signature legally binding

1. What the law counts as a signature

Both statutes define a signature functionally rather than visually. The definition has two halves: a sound, symbol or process that is attached to or logically associated with the record, and a person who executed or adopted it with the intent to sign. Nothing in either definition requires the mark to look like handwriting.

That is why a typed name, a finger-drawn scrawl, and a click on a button labelled to indicate assent can all be signatures: each is a symbol or process, each can be logically associated with the record, and each can be adopted with intent. The legal weight sits in the intent, not in the pixels. What the different forms change is not validity but evidence: how hard it will be, later, to show whose act it was.

2. The rule that keeps it from being thrown out

The operative provision in both statutes is a non-discrimination rule, and reading it precisely matters. It does not say an electronic signature is valid. It says a signature, record or contract may not be denied legal effect solely because it is electronic. The word doing the work is "solely".

So the statutes remove one objection and leave every other one standing. Offer, acceptance, consideration, capacity, authority to sign, whether the parties agreed to the same terms — all of it survives untouched. An electronic signature on a contract that fails for some other reason still fails. Conversely, the change is real: a party cannot walk away from an otherwise good agreement by pointing at the medium.

UETA adds two provisions that come up in practice more than the headline one: it states that an electronic signature satisfies a law requiring a signature, and separately that a record cannot be excluded from evidence in a proceeding merely for being electronic.

3. Two statutes, and which one governs you

There is a federal statute and there is your state's statute, and the federal one contains the rule for how they interact. E-SIGN sets a floor for transactions in or affecting interstate commerce. A state may modify or supersede that floor, but only through one of two doors: by adopting the Uniform Electronic Transactions Act as approved in 1999, or by specifying alternative procedures that are consistent with E-SIGN, that do not privilege any particular technology, and that make specific reference to E-SIGN if enacted after June 30, 2000.

What that constrains is how far the ground can shift when you cross a state line. Whether your own state went through the first door or the second is a question about your state, and this page does not answer it — the count of adoptions in circulation traces back to secondary sources and moves, so no number for it appears here.

The differences that bite in practice are usually not in the electronic-transactions statute at all. They are in the real estate rules layered on top of it: what your commission requires in a transaction file, what has to be notarized, what a county will accept for recording, and how long a broker has to keep records.

Two lookups get you your own answer: your state's electronic transactions statute, on your legislature's website, and your state real estate commission's rules and guidance for transaction documents. Where those two disagree with anything on this page, they govern and this page does not.

4. Under UETA, both sides have to have agreed to do it electronically

This is the condition most often missed, because it is satisfied silently almost every time. UETA applies only to transactions between parties each of which has agreed to conduct transactions by electronic means — and whether they agreed is determined from the context and surrounding circumstances, including their conduct. Nobody has to sign an agreement to agree; emailing a document back and forth is conduct.

Two consequences follow that are less obvious. First, the statutes do not force anyone onto electronic means: neither one requires a record or signature to be created or used electronically. Second, agreeing once does not agree forever. UETA gives a party who has agreed to conduct a transaction electronically the right to refuse for other transactions, and says that right cannot be waived by agreement.

Note the exact scope of that second point: §5(c) is about OTHER TRANSACTIONS, not about picking and choosing documents inside the one you are already doing electronically. What it settles is that agreeing to close one deal by e-signature does not enrol somebody in doing the next one that way.

5. When a consumer is on the other end, a checklist appears

E-SIGN adds a separate set of conditions that apply in one specific situation: where some other law requires that information be given to a consumer in writing, and you want to satisfy that requirement electronically. Note how narrow the trigger is — it is not "every consumer signature", it is a writing requirement in some other law. Which disclosures in a residential transaction carry one is a question about that other law, whichever law that turns out to be.

When it applies, the statute is unusually specific. The consumer has to affirmatively consent and not have withdrawn consent. Before consenting they have to get a clear and conspicuous statement covering their right to a paper copy, their right to withdraw and what withdrawal costs, and whether the consent covers just this transaction or a category of records. They have to be told the hardware and software they will need. And the consent itself has to be given or confirmed electronically in a manner that reasonably demonstrates the consumer can actually access records in the form that will be used.

The demonstration in that last clause is part of the requirement, not a nicety around it: consent collected in a channel the consumer can open, for records delivered in a format they cannot, has not shown what the paragraph asks to be shown.

The statute also limits its own consequence, and this is the part most summaries omit. Failing to obtain electronic consent under (1)(C)(ii) does not, by itself, make the consumer's contract unenforceable. What is at stake is whether the electronic record satisfies the other law's writing requirement — not the validity of the deal.

6. Proving later that this person signed

When a signature is challenged, the question is almost never whether electronic signatures are valid. It is whether this signature was the act of this person. UETA answers that with a rule of proof rather than a rule of technology: a record or signature is attributable to a person if it was the act of the person, and that act may be shown in any manner — including by showing the efficacy of a security procedure used to determine who signed.

"In any manner" is deliberately open, and it cuts both ways. No particular technology is required, which is why the statutes work for a click as well as for a cryptographic certificate. But the provision confers no presumption either: it says how attribution may be shown, not that it is assumed. Whatever the showing turns out to require — and who has to make it is a question of your state's evidence law, not of these two statutes — the material available to make it is whatever the signing system recorded at the time.

UETA defines a security procedure as one employed to verify that a signature, record or performance is that of a specific person, or to detect changes or errors in an electronic record — and names algorithms, codes, identifying words or numbers, encryption, and callback or acknowledgement procedures as examples. A link sent to an address only that person controls, a passcode, a recorded IP address and timestamp, and a hash that proves the document has not changed since signing are all evidence of that kind. A signing record that can answer the four questions below is producing exactly the material §9(a) contemplates; one that can answer none of them leaves the question to two people's recollection.

7. Keeping the record so that it still counts

Retention is where an electronic file most often fails quietly, and both statutes set the same two tests. Where a law requires a record to be retained, keeping an electronic one satisfies that requirement if it accurately reflects the information in the record, and if it remains accessible — under E-SIGN, accessible to everyone entitled to it, for the period the law requires, in a form capable of being accurately reproduced for later reference.

E-SIGN also states the negative case directly, and it is worth reading twice: where a law requires a writing, an electronic record of it may be denied legal effect if the record is not in a form capable of being retained and accurately reproduced by all parties entitled to it. A document the other side could view but never save is exposed on this point in a way that has nothing to do with how it was signed.

Two things follow for a transaction file. The executed copy sitting in a sent-mail folder is not obviously accessible for the retention period to everyone entitled to it. And the retention period itself is not in either statute: both provisions defer to "the period required by" whatever other law required the record to be kept. So the length of time is set somewhere else entirely, and for a brokerage transaction file that is a question for your broker, not one this page can answer.

8. What these statutes deliberately leave out

Both statutes carve out categories, and the carve-outs are not obscure. E-SIGN does not apply to records governed by the law of wills, codicils or testamentary trusts; to state law governing adoption, divorce or other family law; or to most of the Uniform Commercial Code. It also does not apply to court orders and official court documents, to documents accompanying hazardous materials, or to a specific list of notices — including notices of default, acceleration, repossession, foreclosure or eviction under a credit agreement secured by, or a rental agreement for, a primary residence. That last one is worth noticing if any part of your practice touches distressed property.

UETA has its own scope section, and it is not identical. It carves out wills, codicils and testamentary trusts — the same first item — plus the Uniform Commercial Code other than the named provisions, the Uniform Computer Information Transactions Act, and whatever else the enacting state chose to add. It does not carve out family law.

What is on neither list is the thing agents most often assume is: an ordinary purchase agreement, listing agreement, addendum or amendment between private parties. Those are inside both statutes as written.

One qualification, and it is the reason section 3 matters. UETA §3(b)(4) leaves a slot for other laws identified by the enacting state, so a state's own version can carry exclusions the uniform text does not. E-SIGN addresses that directly in the passage quoted in section 3: an exception a state enacts under §3(b)(4) is preempted to the extent it is inconsistent with E-SIGN. Your state's enactment is still the document to check.

9. Notarization, and why recording is a separate question

Notarization is not carved out, but it is only half-answered. UETA says a notarization requirement is satisfied if the electronic signature of the person authorized to perform the act is attached to or logically associated with the record — together with all other information required to be included by other applicable law. Read that trailing clause carefully. UETA supplies the electronic-form half and then defers, expressly, to whatever the other applicable law requires; it says nothing about who may notarize, how, or whether it can be done over video.

So the question "can this be notarized electronically" is not answered by UETA §11 alone. §11 tells you the electronic form is not the obstacle, and then defers everything else to "other applicable law". Which body of law that is, and what it requires of a notarial act, is not settled by either statute on this page.

Recording is a separate question again, and conflating the two is the most common mistake here. A purchase agreement between two private parties and a deed presented to a county recorder are different problems. The first is what the statutes on this page govern. Whether a recording office will accept a particular electronic document is governed by recording law and by that office's own requirements — neither of which is addressed anywhere in E-SIGN or UETA, so nothing on this page answers it. The recorder is the party to ask, and the title company on the file usually already knows.

What this means in Real Deal Pro

Nothing a software product does can make a particular signature enforceable — that depends on the transaction, the parties and the law of the state the property sits in. What a product can do is make sure the facts the statutes talk about are captured at the moment they happen, and are still there a year later when somebody asks. Those are the claims below, each pointing at the code that makes it true.

It is also worth saying where this is not the answer. If your brokerage already requires a specific signing platform for compliance review, use theirs — a signature you cannot get into the file your broker audits solves nothing. And if what you need is remote online notarization, that is a different category of service with its own state-by-state commissioning rules.

• Intent is captured explicitly at adoption, and the form used — typed or drawn — is stored with the event rather than inferred from the image.
• The six consumer disclosures are presented before a signature can be adopted, and the acceptance is recorded as a consent event with its own audit entry.
• Each signing event that fires — created, consent given, consent withdrawn, each field signed, session completed, declined, withdrawn or resent — is logged with actor, timestamp, IP address and user agent.
• For a document generated in the product, the Certificate of Completion records a SHA-256 hash of the pre-signature PDF and a second of the flattened executed PDF, binding the executed copy to what signers were shown.
• The flattened executed PDF is written back to the document record on the deal, downloadable once the document is fully signed.
• The Certificate of Completion is archived to that same document record, so how it was signed is retained next to what was signed.

Reading the sources yourself

The two primary documents behind this page are linked in full in the Sources section below, and both are free to read. The E-SIGN Act as codified is published by the U.S. Government Publishing Office; the Uniform Electronic Transactions Act (1999) is published by the Uniform Law Commission and is Copyright © 1999 by the National Conference of Commissioners on Uniform State Laws. If you want the underlying text rather than anyone’s description of it — including ours — start there.

Your own state's enactment is the one that actually governs you, and it may differ from the uniform text. It will be on your legislature's website.

Real Deal Pro, Inc. is a software company and is not a real estate brokerage. Every plan is software only — you keep your own brokerage. Nothing on this page is legal advice; for your own transaction, ask your broker or a licensed attorney in the state where the property sits.

Wrapping up

The short version, stated carefully: neither statute declares electronic signatures valid. Both forbid rejecting a signature, record or contract for the sole reason that it is electronic, and everything else about contract law is left exactly where it was. The conditions worth remembering are that intent is what makes a mark a signature, that under UETA both sides must have agreed to transact electronically, that a consumer writing requirement brings its own disclosure checklist, that attribution is shown with whatever the system recorded, and that a retained record has to stay accurate, accessible and reproducible.

The part that varies is not usually the signature law. It is what your state and your commission require around it — record retention periods, notarization, and what a county will record. Those are the questions worth taking to your broker rather than to a search engine, this page included.

Related reading

• What Regulation B says about getting a copy of the appraisal

  A federal rule that permits electronic delivery by pointing at the consent provisions quoted here

• How the Closing Disclosure three-day rule works, and what the creditor needs from you

  The document with its own delivery deadline, and the three changes that restart its three-day wait

• What makes a real estate agent a statutory nonemployee

  A federal tax definition that turns on a written contract, quoted in full

• The federal lead-based paint disclosure rule, in its own words

  A federal rule that names three years, and puts the agent’s own signature on the record

• A dotloop alternative, compared job by job

  How transaction-management tools handle signing, and what a whole stack costs over a year

• How a lease ends under the Servicemembers Civil Relief Act

  A federal notice provision that names electronic delivery, and what it asks of it

• What 47 CFR §64.1200(c), (d) and (e) say about prospecting calls

  A federal calling rule under which a signed, written agreement is what evidences permission

Sources

Every quotation above is taken from the documents below, on the date shown; the explanation around each quote is ours. Statutes are amended and uniform acts are revised — check the current text before relying on any of it.

1. [1] 15 U.S.C. §7006 — Definitions — Office of the Law Revision Counsel, U.S. House of Representatives, uscode.house.gov/view.xhtml, read August 23, 2026
2. [2] Uniform Electronic Transactions Act (1999) — final act text (Sections 1–21) — Uniform Law Commission, www.uniformlaws.org/HigherLogic/System/DownloadDocumentFile.ashx, read August 23, 2026
3. [3] 15 U.S.C. §7001 — General rule of validity — Office of the Law Revision Counsel, U.S. House of Representatives, uscode.house.gov/view.xhtml, read August 23, 2026
4. [4] 15 U.S.C. §7002 — Exemption to preemption — Office of the Law Revision Counsel, U.S. House of Representatives, uscode.house.gov/view.xhtml, read August 23, 2026
5. [5] 15 U.S.C. §7003 — Specific exceptions — Office of the Law Revision Counsel, U.S. House of Representatives, uscode.house.gov/view.xhtml, read August 23, 2026