Electronic signatures: six beliefs about what binds you

Plenty of business contracts never touch paper. They go out through an e-signature platform, and the change orders that follow get approved by email.

The federal footing for all of this is the Electronic Signatures in Global and National Commerce Act, commonly shortened to E-SIGN and codified beginning at 15 U.S.C. § 7001. What it says about electronic signatures is narrower than the folklore, in both directions. It makes some things binding that owners assume are casual, and it leaves exposed some things owners assume are settled.

Here are six beliefs we hear from owners of closely held companies, each checked against the statute's text.

"It isn't signed unless there's ink, or at least a signing platform"

The general rule sits in § 7001(a). For any transaction in or affecting interstate or foreign commerce, a signature, contract, or other record "may not be denied legal effect, validity, or enforceability solely because it is in electronic form."

What counts as an electronic signature is broader than most people expect. Section 7006 defines it as "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."

That definition names no software and requires no drawn signature. A typed name or a clicked button can qualify if the person adopted it with the intent to sign.

The word doing the work in § 7001(a) is "solely." Think of the statute as pulling one card out of the other side's hand: the argument that the document doesn't count because it's electronic. Every other card stays in play.

Section 7001(b)(1) says so directly. The Act doesn't alter any legal requirement "other than a requirement that contracts or other records be written, signed, or in nonelectronic form." Whether there was an offer and an acceptance, and whether the person who clicked had authority to bind the company, remain questions of state contract law.

An electronic signature gets a party past the form objection and no further. We've written separately about what enforcing a contract in Oklahoma takes.

"An email thread can't amend our contract"

It can. Section 7006 defines an electronic record as a contract or other record "created, generated, sent, communicated, received, or stored by electronic means," and an email fits comfortably.

So the dispute moves away from the medium and onto harder ground. One question is whether the person who typed "agreed, go ahead" meant that reply as a signature and had authority to change the price. The other is what the contract itself says about how it can be amended.

What the amendment clause can and can't do

Many commercial contracts say they can be modified only by a signed writing. For sales of goods, the uniform text of § 2-209 of the Uniform Commercial Code (UCC), the model commercial statute that states enact in their own versions, backs that clause up. A signed agreement that excludes modification except by a signed writing "cannot be otherwise modified or rescinded."

If an email with a typed name can be a signed writing, then a clause demanding a "signed writing" may not keep email amendments out at all. And the same uniform section adds that an attempted modification that fails the clause "can operate as a waiver."

That's the uniform text as Cornell's Legal Information Institute publishes it. States enact their own versions, and for a contract under Oklahoma or Texas law the enacted wording is what governs.

Where this surfaces in practice

Here's the pattern we see. The signed master agreement is rarely what the fight is about. It's about the long tail of emails after it, written by project managers and sales staff who never thought of themselves as signing anything.

In a dispute, that thread is among the first things each side goes looking for, and it gets read against a definition that turns on intent, not formality. An automatic signature block under a one-line reply becomes an argument.

The contract-hygiene tools here are drafting choices, offered as general observations and not as conclusions about any particular agreement. An amendment clause can define what counts as a signed writing, for instance by requiring a separate document executed by a named officer and stating that email exchanges don't qualify.

A notice clause can specify how formal notices travel. Limits on who can bind the company do the most good when they've been communicated to the other side, since questions of authority often turn on what the counterparty was led to believe.

That same dynamic explains how a casual exchange can form a contract, a problem we covered in our piece on how binding a letter of intent is.

"Everything can be signed electronically"

Not under the federal Act. Section 7003 lists what § 7001 doesn't reach, and the list is specific.

What the statute carves out

Of the nine entries below, the first three are bodies of law, and § 7001 doesn't apply to a contract or record to the extent one of them governs it. The other six are specific documents and notices that § 7001 doesn't cover at all.

• law on the creation and execution of wills, codicils, or testamentary trusts;
• state law on adoption, divorce, or other matters of family law;
• the Uniform Commercial Code as in effect in any state, other than sections 1-107 and 1-206 and Articles 2 and 2A;
• court orders or notices, and official court documents such as briefs and pleadings;
• notices of the cancellation or termination of utility services;
• notices of default, acceleration, repossession, foreclosure, or eviction, or of the right to cure, under a credit agreement secured by, or a rental agreement for, an individual's primary residence;
• notices of the cancellation or termination of health insurance or benefits or life insurance benefits, excluding annuities;
• notices of the recall of a product, or of a material failure of a product, that risks endangering health or safety; and
• documents required to accompany the transportation or handling of hazardous materials, pesticides, or other toxic or dangerous materials.

The UCC exclusion has its own exception: Article 2, which covers sales of goods, and its companion Article 2A stay inside the federal rule. And § 7003 as a whole says only that § 7001 "shall not apply." Whether the listed documents can be electronic is left to some other body of law.

Nothing on the list mentions ordinary commercial agreements or guaranties. Under the general rule, in a transaction the Act reaches, a personal guaranty signed on a phone can't be denied effect solely because of the medium.

Nobody has to say yes

Section 7001(b)(2) says the Act doesn't "require any person to agree to use or accept electronic records or electronic signatures," with an exception that concerns governmental agencies. A lender or a title company can insist on ink, and so can you.

Notaries and filing offices

Where a law requires a signature or record to be notarized or acknowledged, § 7001(g) says the requirement is satisfied if the electronic signature "of the person authorized to perform those acts," together with the other information the law requires, is attached to or logically associated with the record. The federal text doesn't say who that authorized person is. State notary law governs who may notarize electronically and how.

Filing is separate. Section 7004(a) preserves any requirement by a federal or state regulatory agency that records be filed "in accordance with specified standards or formats." Whether a particular office accepts an electronically signed instrument is something we'd confirm before a closing, not after.

"The platform's certificate proves who signed"

Nothing we found in § 7001 mentions an audit trail or any vendor's product, and nothing in it makes a platform's records conclusive.

The federal scheme leans the other way. When § 7002 describes the alternative rules a state may adopt, it rules out procedures that "require, or accord greater legal status or effect to" a specific technology or technical specification.

So who actually clicked? The definition requires that the signature be "executed or adopted by a person," and attribution is a matter of proof.

Where an electronic agent is involved (the Act's term for a program that acts without an individual reviewing each step), § 7001(h) protects the contract only "so long as the action of any such electronic agent is legally attributable to the person to be bound."

A platform's log is usually good evidence. It typically shows the address a signing request went to and when the document was opened and completed. What it can't show unaided is whose hands were on the keyboard, and the recurring weak spots are the shared inbox and the assistant who signs in as the owner.

What a company typically keeps

Two provisions frame the answer. Under § 7001(d)(1), a legal requirement to retain a contract is met by an electronic record that "accurately reflects the information" and stays accessible, in reproducible form, to everyone entitled to it for the period the law requires.

Section 7001(e) is the sharper edge. If a law requires a contract to be in writing, the electronic record's effect "may be denied" if it isn't "in a form that is capable of being retained and accurately reproduced for later reference by all parties or persons who are entitled to retain the contract or other record." Terms shown on a screen that the other side had no way to save or print invite that argument.

Companies that handle this well typically keep the final executed document itself and not just a link to it, the platform's signing record, the emails that transmitted it, and whatever shows the signer's authority.

"Our customers clicked 'Accept,' so our disclosures are delivered"

This belief runs together a valid signature and a valid delivery of legally required information. Section 7001(c) treats them separately, and it applies when the other side is a consumer.

A consumer, under § 7006, is "an individual who obtains, through a transaction, products or services which are used primarily for personal, family, or household purposes." A company buying from another company isn't one.

When some other law requires that information be given to a consumer in writing, § 7001(c)(1) lets an electronic record satisfy that requirement if several conditions are met. The consumer must have "affirmatively consented" and not withdrawn the consent.

Before consenting, the consumer must receive a "clear and conspicuous statement" covering:

• any right or option to have the record on paper, and the right to withdraw consent;
• whether the consent covers only the particular transaction or identified categories of records;
• the procedures for withdrawing consent and for updating the consumer's contact information; and
• how to obtain a paper copy after consenting, and whether a fee is charged for it.

The consumer must also be given, before consenting, a statement of the hardware and software requirements for access to and retention of the electronic records.

Then comes the condition a bare "Accept" button doesn't obviously satisfy. The consumer must consent electronically, or confirm consent electronically, "in a manner that reasonably demonstrates that the consumer can access information in the electronic form that will be used to provide the information that is the subject of the consent." A click on a web page says little about whether the customer can open the file format the disclosures later arrive in.

What a consent failure does and doesn't do

The statute cuts both ways here. Section 7001(c)(3) says a consumer's contract can't be denied effect "solely because of the failure to obtain electronic consent or confirmation of consent" under that demonstration requirement.

Delivery of the disclosure is another matter. If the consent conditions weren't met, the electronic record may not satisfy the law that required a writing, and the consequences come from that underlying law.

"Federal law settles electronic signatures, so state law doesn't matter"

The federal Act invites state law in. Under § 7002(a), a state statute may "modify, limit, or supersede" § 7001 with respect to state law only if it "constitutes an enactment or adoption of the Uniform Electronic Transactions Act as approved and recommended for enactment in all the States by the National Conference of Commissioners on Uniform State Laws in 1999." A state can also specify alternative procedures, provided they're consistent with the federal Act and don't favor a specific technology.

Oklahoma has a statute by that name. State agencies cite Oklahoma's Uniform Electronic Transactions Act as beginning at Section 15-101 of Title 12A of the Oklahoma Statutes, and the State of Oklahoma's Electronic Signature Standard describes itself as subject to that act.

We haven't quoted the Oklahoma act here, and we wouldn't assume its wording matches the federal text line for line. For a contract governed by Oklahoma law, the state statute's current text is what we'd read first. A Texas contract calls for the same exercise under Texas law.

The UCC shows how the layers interact. Its uniform § 1-108 declares that the article "modifies, limits, and supersedes" the federal Act, with two stated exceptions: it leaves the consumer consent rules of § 7001(c) alone, and it doesn't authorize electronic delivery of the notices listed in § 7003(b).

Underneath both layers sits ordinary contract law. Formation and authority are state-law subjects, which is why the same emailed approval can be analyzed differently depending on whose law the contract selects.

What the convenience buys, and what it costs

None of this is an argument for going back to paper. Electronic signing usually leaves a better record than ink does: a time-stamped document and a delivery trail that a paper file rarely has.

The cost is that commitment gets easy. When binding the company takes one click or one reply, more people in the organization can do it, and with less reflection. The statute's low threshold is what makes the convenience possible, and the accidental commitment too.

Companies that get the benefit without the surprise tend to treat signing authority as a governance question, not a software setting. They know who can bind the company, and they know what their contracts say about amendments.

If an emailed approval or a clicked acceptance has become the center of a dispute, or you're reworking your contract forms before that happens, that's a sensible point to bring in counsel. You can reach us through the contact page or at our Oklahoma City office. An early conversation is nearly always less expensive than untangling an agreement nobody meant to sign.

This article is general information about Oklahoma, Texas, and federal law, not legal advice, and it does not create an attorney-client relationship. Facts matter; talk to a lawyer about yours.