E-Signatures: When Does a Document Actually Count as Signed?

First, the disclaimer that actually matters

I am not a lawyer, and nothing in this post is legal advice. It is a working translation of public statutes into plain English, written by someone who signs client contracts electronically every month and once did it badly. For anything with real stakes, a specific jurisdiction, or an unusual document type, spend the money on a real attorney; it is the cheapest insurance in this entire subject.

With that said, the core question deserves a plain answer, because most people signing a PDF have no idea what makes it count. The answer in both the US and UK is surprisingly generous: the law mostly stopped caring about ink a generation ago. What it cares about instead is intent, consent, and evidence, and those three words are the skeleton of everything below.

ESIGN and UETA in one breath each

Two American laws do the heavy lifting. The federal ESIGN Act, passed in 2000, says that a signature, contract, or record may not be denied legal effect solely because it is in electronic form. That word solely is the engine: a court can still find a contract invalid for the ordinary reasons, fraud, incapacity, missing terms, but not merely because nobody touched paper. UETA, the Uniform Electronic Transactions Act, is the state-level counterpart adopted by nearly every state, with the holdouts running equivalent laws of their own; it says much the same thing for transactions inside state law.

ESIGN defines an electronic signature broadly: 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. Read that definition twice, because it is wider than most people expect. A typed name at the bottom of an agreement, a clicked I Accept button, a drawn squiggle on a touchscreen, even a recorded verbal confirmation can qualify. The form is almost irrelevant. The intent to sign, and the ability to prove it later, is the whole game.

The four things that make an e-signature stick

Boiled down from the statutes and the way disputes actually get argued, four elements recur. I treat them as a checklist every time I send or sign anything that matters.

• Intent: the signer meant to sign, shown by an unambiguous act like drawing, typing a name, or clicking an explicit accept button
• Consent: the parties agreed to do business electronically, which consumer-facing flows usually capture with a disclosure and checkbox
• Association: the signature is attached to or logically linked with the exact document signed, not floating loose
• Retention: a complete copy is kept and reproducible by everyone entitled to one, because a signature you cannot produce might as well not exist

The UK, briefly

The UK reached the same destination by its own road. English law has long been flexible about the form a signature takes, the Electronic Communications Act 2000 and the UK's retained eIDAS rules provide the statutory framework, and in 2019 the Law Commission of England and Wales confirmed in a formal report that electronic signatures are valid for the great majority of documents, without needing new legislation. For ordinary commercial contracts between a US freelancer and a London client, or the reverse, an e-signed PDF is standard practice on both ends.

The UK wrinkle worth knowing is the deed, a special class of document, certain property transfers and powers of attorney among them, which carries extra formalities such as a witness physically present at signing. That is exactly the kind of edge where my opening disclaimer stops being boilerplate: if anyone in a transaction utters the words deed, notary, or land registry, that is a call to a solicitor, not a blog post.

Drawn squiggle vs digital certificate

Here is the distinction the industry constantly blurs. An electronic signature is the broad legal category: typed, drawn, clicked, whatever carries intent. A digital signature is a specific technology, a cryptographic seal made with a certificate, which mathematically binds a signer's verified identity to an exact version of a file and breaks visibly if a single byte changes afterward. Both can be legally valid. What differs is the strength of the evidence when someone later says I never signed that, or that is not the version I signed.

For most everyday agreements, freelance contracts, NDAs, engagement letters, the drawn or typed kind plus a decent audit trail is what the entire market runs on, and it holds up because context corroborates it: the email thread, the invoice, the months of performance under the contract. Certificate-based signatures earn their complexity at higher stakes, regulated industries, large sums, cross-border filings, where identity itself may be attacked. My rule of thumb: match the signature ceremony to the size of the fight you can imagine having about it.

The evidence I keep, and the time I kept none

My admission for this post is painfully on-theme. Early in my freelancing years I e-signed a client contract, felt very modern about it, and saved nothing: no final countersigned copy, no confirmation email, nothing but a vague memory of a green checkmark. Eleven months later a polite dispute arose about revision limits, and I discovered I could not produce the document I was standing on. I had to ask the client for a copy of my own contract, which is roughly as strong a negotiating position as it sounds. The clause was in my favor, as it turned out; the embarrassment was permanent anyway.

Since then, every signed agreement generates a small evidence bundle, filed the same day: the final executed PDF itself, the signing platform's completion certificate or audit trail with its timestamps and email identities, and the email thread around the signature. When a project's paperwork sprawls, I merge the PDFs into one file per client per engagement so nothing orphans. The retention element from the checklist above is where ordinary people actually lose; the law was on my side that day, but the filing cabinet nearly was not.

Where wet ink still rules

The ESIGN Act itself carves out document families where electronic form does not suffice or special rules apply, and the list is worth knowing cold: wills, codicils, and testamentary trusts; family-law documents like adoption and divorce papers; court orders and official court documents; notices of utility shutoff, eviction, foreclosure, and insurance benefit cancellation; product recalls affecting health or safety; and documents accompanying hazardous materials transport. The pattern is visible: where the consequences of a missed or spoofed document are severe and personal, the law keeps the older formalities.

For everything outside those carve-outs, my ordinary workflow is unglamorous and fast: I create a clean signature once with a signature maker, apply it with a sign PDF tool, and send the agreement alongside the corresponding paperwork from an invoice generator so the commercial trail is coherent from day one. Signed, evidenced, filed, usually inside ten minutes. The law made this easy in 2000; the only remaining failure mode is us, forgetting to keep what we clicked.