Minnesota settled the big question about electronic signatures twenty-six years ago, and most people still get it wrong in both directions. Business owners tell me an email chain “doesn’t count” because nobody signed anything. Families tell me a will typed and e-signed on a laptop “should count” because everything’s electronic now. The statute — chapter 325L, Minnesota’s version of the Uniform Electronic Transactions Act, enacted in 2000 — answers both, and each answer is the opposite of what those people wanted to hear. The email chain can absolutely bind you. The e-signed will is a nullity.
I spend a fair amount of my practice on both ends of this: arguing that a string of emails formed a contract, and arguing that it didn’t. Here’s how the statute actually works, and what I look for before I make either argument.
The definition is broader than you think
Start with what an “electronic signature” is, because the definition does most of the work in these fights. Section 325L.02(h):
“Electronic signature” means an electronic sound, symbol, or process attached to or logically associated with a record and executed or adopted by a person with the intent to sign the record.
Read that list again: sound, symbol, or process. A DocuSign certificate qualifies. So does a typed name at the bottom of an email. So does clicking “I agree.” Nothing in the definition requires cryptography, a stylus squiggle, or a third-party platform. The fight isn’t about the technology. It’s about the bolded phrase. In every disputed case the question is whether the sound, symbol, or process was executed or adopted with the intent to sign. An automatic email footer that tacks your name onto every message you send, including the ones rejecting the deal, is weak evidence of intent to sign anything. A typed “/s/ David Madgett” under the words “we accept your terms” is strong evidence. Same technology, opposite results, because intent is the element.
What legal effect does an electronic signature get?
Full effect. Section 325L.07 stacks four rules on top of each other, and between them they shut every door a signature-denier might try:
(a) A record or signature may not be denied legal effect or enforceability solely because it is in electronic form.
(b) A contract may not be denied legal effect or enforceability solely because an electronic record was used in its formation.
(c) If a law requires a record to be in writing, an electronic record satisfies the law.
(d) If a law requires a signature, an electronic signature satisfies the law.
Paragraphs (c) and (d) are the ones with teeth. Minnesota has dozens of statutes requiring that particular agreements be “in writing” and “signed” — I cover the main ones in my article on the statute of frauds. Section 325L.07 means an email can satisfy those statutes. The defense that “a contract for that has to be in writing, and all we have is email” fails on its own terms if the email is a signed electronic record. And § 325L.13 adds the evidence rule that goes with it: a record or signature may not be excluded from evidence solely because it’s electronic.
The consent requirement — and why it’s easier to satisfy than people hope
Chapter 325L doesn’t force anyone to do business electronically. Section 325L.05(a) says so expressly, and § 325L.05(b) limits the whole chapter to “transactions between parties, each of which has agreed to conduct transactions by electronic means.” Litigants read that sentence and think they’ve found the exit: “I never agreed to contract by email.”
Then they read the second sentence of § 325L.05(b):
Whether the parties agree to conduct transactions by electronic means is determined from the context and surrounding circumstances, including the parties’ conduct.
No signed consent form is required. If two businesses negotiate a deal over forty emails, the conduct is the agreement. In my experience the consent element is a real obstacle in roughly one fact pattern: a party who kept insisting on paper — “send me the hard copy and I’ll sign it” — and never performed under the electronic exchange. Short of that, a court looking at “context and surrounding circumstances” will find consent in how the parties actually behaved. One more wrinkle: under § 325L.05(c), agreeing to do one transaction electronically doesn’t obligate you to do others the same way, and that particular rule can’t be varied by agreement.
The exclusion list — the part everyone skips
Here’s the part of the chapter nobody expects, and the reason the estate-planning half of my practice cares about a commercial statute. Section 325L.03 carves a short list of documents out of the electronic world entirely, and they’re exactly the documents people most want to sign from a hospital bed or a deployment overseas.
1. Wills, codicils, and testamentary trusts. Section 325L.03(e): “This chapter does not apply to the creation and execution of wills, codicils, or trusts other than trusts relating to the conduct of business, commercial, or governmental purposes.” Your e-signed contract is fine. Your e-signed will isn’t a will. Minnesota’s execution requirements for wills live elsewhere and still contemplate ink and witnesses — I walk through them, and through the narrow paths for defectively executed wills, in my article on will execution and the harmless-error doctrine. Note the carve-out inside the carve-out: business trusts are back inside the statute. A trust that runs a company can be papered electronically. A trust that distributes your estate can’t.
2. Health care directives. Section 325L.03(b)(2) excludes transactions governed by “section 145C.03, subdivision 1, relating to requirements for creation of a health care directive.”
3. Instruments affecting real estate offered for recording. The same paragraph excludes transactions governed by “section 507.24, relating to requirements for recording any conveyance, power of attorney, or other instrument affecting real estate.” The purchase agreement for land can be electronic. The recordable deed answers to the recording statutes, not to chapter 325L.
4. Statutory short form powers of attorney. Excluded by reference to “section 523.23, subdivision 3.”
5. Declarations regarding intrusive mental health treatment. Excluded by reference to “section 253B.03, subdivision 6b.”
6. Most of the Uniform Commercial Code — but not the part you use every day. Section 325L.03(b)(1) excludes transactions governed by the UCC “other than section 336.1-306, article 2, and article 2A.” Parse that double negative carefully, because it runs backward from what you’d guess. Sales of goods (Article 2) and leases of goods (Article 2A) are inside chapter 325L — your electronic purchase order for equipment is covered, and it pairs with the warranty rules I cover in my Article 2 warranties article. What stays outside are the other UCC articles, which carry their own formalities: negotiable instruments, secured transactions, and the rest. The promissory note is the classic trap. It lives in a different legal world than the loan agreement stapled to it.
Section 325L.03 has two more wrinkles, and each gets a sentence. Under paragraph (c), a record excluded under paragraph (b) is still covered “to the extent it is governed by a law other than those specified in paragraph (b)” — the exclusions go transaction by transaction, not document-wide. And under paragraph (d), a transaction inside the chapter “is also subject to other applicable substantive law.” Chapter 325L validates the signature. It doesn’t validate the deal. Fraud, capacity, unconscionability, and every other contract defense survive intact — see my article on fraud and misrepresentation claims for what that layer looks like.
Attribution: “somebody else clicked it”
After intent, the next most-litigated question is attribution — proving whose act the electronic signature was. Section 325L.09(a):
An electronic record or electronic signature is attributable to a person if it was the act of the person. The act of the person may be shown in any manner, including a showing of the efficacy of any security procedure applied to determine the person to which the electronic record or electronic signature was attributable.
“In any manner” means what it says. You can prove attribution with the platform’s audit trail — IP address, timestamp, the email account that got the signing link — but you can also prove it the old-fashioned way: the signer performed under the agreement for eight months, mentioned it in later correspondence, and never once disowned it until sued. Under § 325L.09(b), the legal effect of the attributed record is then “determined from the context and surrounding circumstances at the time of its creation, execution, or adoption,” including any agreement of the parties. In practice, the “my assistant clicked it” defense loses to a course of performance nearly every time, and the serious attribution fights involve accounts that really were compromised, not a shared office computer.
Where the federal E-SIGN Act fits
There’s a parallel federal statute, the Electronic Signatures in Global and National Commerce Act. Its general rule, 15 U.S.C. § 7001(a), tracks the same idea for “any transaction in or affecting interstate or foreign commerce”: a signature, contract, or record “may not be denied legal effect, validity, or enforceability solely because it is in electronic form”. For consumer transactions, § 7001(c) adds an affirmative-consent regime — where a law requires that information be provided to a consumer in writing, the electronic version satisfies it only after the consumer affirmatively consents following specified disclosures. And by § 7002(a), Congress let state enactments of the 1999 uniform act modify or supersede § 7001 as to state law. Minnesota enacted UETA in 2000. So for ordinary Minnesota contract disputes, chapter 325L is the statute you work with, and E-SIGN matters mainly at the edges — consumer disclosure regimes and transactions governed by federal law.
What I look for before arguing an email chain formed a contract
When a client brings me an email thread and asks whether there’s a deal, I run five questions in order. Each one lines up with a way these cases actually get lost.
- Are the essential terms all in the writings? Chapter 325L makes the emails count as signed writings. It doesn’t supply a price, a quantity, or a closing date the parties never stated. An agreement to agree fails electronically just like it fails on paper.
- Is there a statement of assent, and who typed it? I want the words of acceptance — “we accept,” “agreed,” “go ahead on those terms” — and the typed name or signature block adopted with them. That pairing is the § 325L.02(h) intent evidence.
- Does the conduct show agreement to transact electronically? Under § 325L.05(b) I’m looking for the negotiation itself to have lived in the electronic channel. Forty emails over three weeks answers the question. A single unanswered email doesn’t.
- Can I attribute every key message? Section 325L.09 lets me prove it “in any manner,” so I collect the audit trail if a platform was used and the performance evidence either way.
- Is the subject matter on the exclusion list? Five minutes with § 325L.03 before I write the demand letter, every time. It’s a short list, but landing on it is fatal.
Run the same five questions from the other side and you’ve got the shape of the opposing argument. And if you’re setting up a business rather than litigating one, build the answer in from day one — a signature protocol belongs in your formation stack next to the items in my startup checklist.
Madgett Law, LLC
Madgett Law, LLC represents Minnesota businesses and individuals in contract formation and enforcement disputes, including cases that turn on whether an email exchange, an e-signature platform record, or a clicked acceptance created a binding agreement — and estate matters where the electronic-execution rules run the other way. If you’re holding an email chain and wondering whether it’s a contract, that question has an answer. Call 612-470-6529 or send us a message.
Sources: Minn. Stat. § 325L.01 (short title, Uniform Electronic Transactions Act; enacted 2000 c 371); Minn. Stat. § 325L.02(h) (definition of “electronic signature”: “an electronic sound, symbol, or process attached to or logically associated with a record and executed or adopted by a person with the intent to sign the record”); Minn. Stat. § 325L.03(a)–(e) (scope; (b)(1) UCC exclusion “other than section 336.1-306, article 2, and article 2A”; (b)(2) exclusions referencing § 145C.03, subd. 1 (health care directives), § 507.24 (recording instruments affecting real estate), § 523.23, subd. 3 (statutory short form power of attorney), and § 253B.03, subd. 6b (declarations regarding intrusive mental health treatment); (c) partial application of excluded records; (d) other substantive law preserved; (e) wills, codicils, and trusts other than business/commercial/governmental trusts excluded); Minn. Stat. § 325L.05(a)–(e) (electronic means not required; chapter applies only between parties who have agreed to conduct transactions electronically, “determined from the context and surrounding circumstances, including the parties’ conduct”; right to refuse other electronic transactions non-waivable; variation by agreement); Minn. Stat. § 325L.07(a)–(d) (legal recognition of electronic records, signatures, and contracts; electronic record satisfies a writing requirement; electronic signature satisfies a signature requirement); Minn. Stat. § 325L.09(a)–(b) (attribution: record or signature attributable to a person “if it was the act of the person,” shown “in any manner”; effect determined from context and surrounding circumstances); Minn. Stat. § 325L.13 (evidence of a record or signature may not be excluded solely because it is in electronic form); 15 U.S.C. § 7001(a) (E-SIGN general rule of validity), § 7001(c) (consumer consent to electronic records); 15 U.S.C. § 7002(a) (state UETA enactments may modify, limit, or supersede § 7001).
This article is general legal information about Minnesota law. It is not legal advice, it does not create an attorney–client relationship, and it does not promise or imply any particular outcome. Statutes, rules, and case law change; verify current authority before relying on any of it.