The Short Definition Every US Team Should Anchor On
A signature is a mark, name, symbol, or electronic record that a person executes with intent to adopt or authenticate a document, showing agreement to its terms. Under the US ESIGN Act (2000) and UETA, signatures include electronic sounds, symbols, and processes attached to or logically associated with a contract.
That single sentence settles most of the arguments a US operations team will have about whether a given scribble, typed name, or click-to-sign box "counts." The definition has three load-bearing pieces: something is signed, the signer meant to sign it, and the act is tied to a specific document. Everything else — pen on paper, a stylus on a phone, a checkbox on a web form, a certificate-based cryptographic stamp — is a variation on those three pieces, not a replacement.
This article works through each variation in plain English, lays out the six signature types teams run into, and gives you a comparison table plus an execution checklist for standardizing signature policy across contracts, approvals, and cross-border deals.
Where the Word "Signature" Came From and Why It Still Matters
The English word signature comes from the Latin signare — to mark. For most of legal history, that mark was a handwritten flourish on parchment, followed by a wax seal. The mark's job was not to identify the writer's handwriting; a notary or witness could do that. The mark's job was to bind the signer's will to the words on the page.
Modern statutes keep that focus on intent and attribution. The US ESIGN Act, passed in 2000, gives electronic records and electronic signatures the same legal effect as paper and ink for almost every commercial transaction. The Uniform Electronic Transactions Act (UETA), adopted by most US states, sets the same baseline and adds rules about how intent and consent are demonstrated. Both laws judge a signature by what it does — link a person to a record with intent — not by the technology used.
Two practical consequences follow:
- No signature technology is automatically invalid in the US. A typed name, a tap on a phone, a clicked checkbox, or a certificate-based digital stamp can all qualify, provided the four binding elements below are met.
- The same technology can be valid in one deal and weak in another. A simple click-to-sign is enough for a US SaaS order form. It may not satisfy a foreign counterparty whose jurisdiction requires a qualified certificate. The technology choice is a risk choice.
The Six Core Signature Types US Teams Encounter
Most signing work falls into six categories. Some are old; some are twenty years old; one is a product of modern cryptography. They are not interchangeable, and they do not all prove the same things.
- Wet-ink (handwritten) signature. A physical mark applied by hand with a pen, stylus, or finger. Still required for some notarized documents, certain estate instruments, and a shrinking set of regulated filings.
- Printed-name signature. A name typed or printed on a signature line. Common in office memos, internal approvals, and low-risk forms. Valid when intent is clear, though it provides weak identity evidence.
- Conformed signature. A typed representation of a handwritten signature, often placed in a block by administrative staff and paired with "/s/" notation.
- Electronic signature (general). Any electronic sound, symbol, or process attached to or logically associated with a contract and executed with intent. This is the ESIGN/UETA category. It covers click-to-sign, typed names, drawn signatures on tablets, biometric captures, and recorded consent.
- Digital signature (cryptographic). A subset of electronic signature using a public-key infrastructure (PKI) certificate to bind the signer's identity to the document and detect any change after signing. Common in regulated industries, government filings, and long-archive records.
- eIDAS-style assurance levels (SES, AES, QES). The EU's eIDAS regulation sorts electronic signatures into three ascending tiers — Simple Electronic Signature (SES), Advanced Electronic Signature (AES), and Qualified Electronic Signature (QES) — each adding stronger identity verification, tamper-evidence, or certificate requirements. QES carries a legal presumption equivalent to a wet-ink signature in EU member states and is the international benchmark many cross-border teams aim at.
Type, Look, Proof, and Risk: A Comparison Table
The same word — signature — gets used for six very different artifacts. The table below lines them up against what each one looks like in practice, what it actually proves, where it usually shows up, and where the risk sits.
| Type | What it looks like | What it proves | Typical use | Risk profile |
|---|---|---|---|---|
| Wet-ink | Handwritten mark on paper | Intent + physical presence | Notarized deeds, some wills, certain court filings | Loss, forgery, slow to execute, hard to scale |
| Printed-name | Typed name on a signature line | Intent only | Internal memos, low-risk approvals | Weak identity evidence; disputed in fraud cases |
| Conformed ("/s/") | Typed name, often with /s/ notation | Intent + administrative control | Legal filings, court bundles, signed contracts printed for record | Reliance on staff discipline; original electronic record must exist |
| Electronic (general) | Click, tap, typed name, drawn mark with audit trail | Intent + signer association + integrity of record | US commercial contracts, HR documents, sales orders | Depends on audit trail, identity verification, and consent capture |
| Digital (PKI) | Cryptographic stamp bound to a certificate | Intent + verified identity + tamper-evidence | Regulated filings, government forms, long-archive records | Strong if certificate lifecycle is managed; weak if certificates expire or are misissued |
| eIDAS QES | AES-grade signature using a qualified certificate from a trust-service provider | Intent + verified identity + tamper-evidence + EU legal presumption | Cross-border contracts with EU counterparties | Requires qualified certificate provider and identity verification per eIDAS |
Two rows deserve extra attention. The "electronic (general)" row is where most US teams operate; its strength depends entirely on the audit trail, identity checks, and consent capture behind the click. The "eIDAS QES" row is the international gold standard and the one to reach for when a counterparty signs from a country that grades signature assurance.
What Makes a Signature Legally Binding in the US
A signature becomes legally binding when four conditions are present. Drop any one and the signature is at risk — not automatically invalid, but vulnerable to challenge.
1. Intent to sign. The signer must mean to adopt the document as their own agreement. Courts look at context, prior dealings, and the steps taken (a clear "I agree" button beats a buried checkbox).
2. Attribution. The signature must be tied to a specific, identifiable person. In the electronic world, this is where the audit trail, identity verification, and authentication steps earn their keep.
3. Integrity of the record. The document signed must be the document that survives later. Hashing, sealing, and tamper-evident audit trails exist for this reason. A signature on a document that someone can quietly rewrite afterwards is not worth much.
4. Retention and reproducibility. The signature and the document must be retained in a form that can be accurately reproduced later for the parties or for a court. This is why many teams store the signed PDF plus the certificate, audit trail, and identity-verification evidence together.
US courts have repeatedly enforced electronic signatures on these same elements. If you want a deeper look at how digital signatures behave in litigation, see whether digital signatures hold up in court. And if you are weighing wet-ink against an eSignature for a specific document type, the practical comparison of converting a wet signature to an eSignature is a useful starting point.
Electronic vs Digital Signature: Where US Buyers Get Confused
The words "electronic signature" and "digital signature" are often used as if they mean the same thing. They do not.
- Electronic signature is the broad legal category. It includes every method of capturing intent electronically — click, tap, typed name, drawn mark, recorded consent — provided the four binding elements above are met.
- Digital signature is a specific implementation, built on PKI, that ties a cryptographic key pair and a digital certificate to the signer. When someone verifies the digital signature, they confirm who signed and whether the document was altered after signing. The mechanics are explained in how digital signatures work for business and walked through in a digital signature with an example.
The eIDAS-Style Assurance Ladder: An International Benchmark
For US companies signing deals with counterparties abroad, the EU's eIDAS regulation provides the clearest international benchmark. It defines three rungs:
- Simple Electronic Signature (SES). Any electronic data adopted by the signer as their signature. Click-to-sign, typed names, and drawn marks all qualify.
- Advanced Electronic Signature (AES). Uniquely linked to the signer, capable of identifying them, created using means the signer can keep under their sole control, and linked to the data signed so that any later change is detectable.
- Qualified Electronic Signature (QES). An AES-grade signature created with a qualified certificate issued by a qualified trust service provider, using a qualified signature creation device. QES carries a legal presumption equivalent to a handwritten signature in EU member states.
The same ladder appears in modified form in the United Kingdom's trust framework, Singapore's Electronic Transactions Act, and Hong Kong's Electronic Record and Signature Ordinance. A US team that signs across multiple jurisdictions should pick a signing layer that supports all three rungs so the same document can be elevated from SES to QES when a counterparty requires it. See what an eIDAS-compliant electronic signature actually demands for the practical requirements.
Execution Checklist for Teams Standardizing Signature Policy
Use this checklist when you are formalizing signature policy across your contract templates, approval workflows, and cross-border deals. Each row is a decision, not a recommendation — the right answer depends on the document type, the counterparty's jurisdiction, and your retention requirements.
| Checklist item | Decision to make before launch | Why it matters |
|---|---|---|
| Signature type by document class | Which of the six types is acceptable for each contract or approval? | Prevents ad-hoc signature choices that weaken later evidence |
| Identity verification depth | Does the signer need email confirmation, SMS OTP, government-ID check, or video verification? | Sets the floor for attribution strength and dispute defense |
| Audit trail capture | Does the signing record include signer identity, IP, timestamp, document hash, and consent language? | Without it, the "electronic signature" loses most of its legal weight |
| Document integrity controls | Are signed PDFs sealed, hashed, and tamper-evident? | Detects post-signing edits that would otherwise invalidate the signature |
| Retention period | How long must the signed record, certificate, and audit data be kept? | Aligns storage with statute of limitations, regulatory retention, and tax rules |
| Witness or notary requirements | Does the document type require a witness, notary, or in-person verification? | Avoids contracts that look signed but lack a required formality |
| Cross-border escalation rule | When can the team escalate from SES to AES or QES? | Lets a US-only deal become a QES deal if the counterparty requires it |
| Template and block language | Is the signature block standard across all templates, or improvised per document? | Consistent language is easier to defend in litigation and audit |
| Record export and audit access | Who can retrieve the signed record, certificate, and audit trail later? | Evidence is useless if the team cannot produce it when challenged |
| Vendor sign-policy parity | Does your signing vendor support the same signature types and assurance levels your policy demands? | Prevents policy gaps when templates meet platform limits |
A signature policy without these decisions in writing tends to drift. A signed contract looks fine in the moment and turns brittle the first time someone asks who verified the signer's identity or whether the document was sealed. Start with a single high-volume template, then expand.
When a Signature Must Hold Up Abroad: Nota Sign
Cross-border deals expose a gap most US signature policies never close at home: a contract that is rock-solid in New York may be questioned in Frankfurt, Singapore, or Hong Kong because the signature does not match the local assurance ladder. The remediation is rarely a new vendor — it is a signing layer that already recognizes the legal frameworks a counterparty lives by.
The signing layer FaDaDa operates for international business — Nota Sign — was built for that reality. Its workflows are recognized under the electronic-signature laws of more than a hundred countries and regions, so the same envelope does not have to be re-engineered each time a counterparty signs from a different jurisdiction. On top of that geographic coverage, the platform supports the full eIDAS-style assurance ladder — Simple, Advanced, and Qualified — so a US buyer can start a deal at SES and elevate the same document to AES or QES when a European counterparty needs the higher assurance. That combination — broad framework recognition plus a complete assurance ladder — is what turns "the signature will probably hold up" into a policy you can defend.
Underneath the coverage sit the records themselves: every signature event lands in a tamper-evident audit record, so the integrity half of the validity question — not just the legal half — travels with the document. The pricing model keeps a multi-jurisdiction policy within reach of smaller teams, which are not billed per seat, while mid-market and enterprise buyers can shape terms around their real volume and integrations.
For teams that would rather pressure-test this before committing, talk to Nota Sign with a sample cross-border contract, the jurisdictions involved, and the retention requirement driving the deal.









