Does a contract signature need a date to be valid in the US?

Usually not for formation — but the date fixes timing for deadlines, notice periods, and statute-of-limitations questions. Undated signatures invite avoidable disputes; timestamped ones settle them.

Is a typed name in the signature block legally a signature?

Yes, when adopted with intent to sign — the same rule that governs typed and conformed signatures generally, covered in What Does /s/ Mean in a Signature .

What happens if the signer's title is wrong or missing?

The company can argue the signer lacked authority to bind it. Correct capacity lines — and platforms that refuse to complete envelopes with blank title fields — are the fix.

Do both parties sign the same signature block?

No — each party signs its own block, one per entity or individual. Multi-party contracts simply stack blocks, and e-signing platforms route each block to its signer automatically.

Contract Signature Examples: US Blocks, Roles, Dates

A complete US contract signature block contains four elements: the signature itself, the signer's printed name, their title or capacity when signing for a company, and the date. Each element answers a different legal question — identity, authority, and timing — and a missing one is the kind of defect that surfaces at enforcement, not at signing.

Example 1: the individual signer

/s/ Jordan Lee

Jordan Lee

Date: March 4, 2026

Three elements, three proofs: the mark shows a deliberate act, the printed name removes ambiguity about identity, and the date fixes the moment of execution. Individual blocks appear on NDAs, offer letters, and personal guarantees. No title line is needed — the signer acts for themselves.

Example 2: the company signer

ACME INDUSTRIES, INC.

By: /s/ Maria Ortiz

Name: Maria Ortiz

Title: Chief Operating Officer

Date: March 4, 2026

Company blocks add the two elements that decide enforceability against the entity:

The entity name on top — the company, not the person, is the contracting party
By/Name/Title — identifies the human and asserts their capacity to bind the company

The capacity question is where signature blocks fail in practice: a signature without a title invites the argument that the signer lacked authority. The authority mechanics are covered in Contract Signature Lines: Names, Titles, Authority.

Example 3: the multi-party block with witnesses or initials

Some documents add witness lines (certain notarized or state-specific instruments) or per-page initials (common in lengthy agreements to prevent page substitution):

/s/ Jordan Lee (Party) /s/ Dana Kim (Witness)

Initials: JL on pages 1–14

Witness requirements are document- and state-specific — the workflow for them is covered in Witnessing of Signatures: Meaning and Workflow, and initials as evidence in Initials as a Signature: Uses, Risks, E-Workflows.

What each element proves — and what e-signing adds

Element	Proves	What e-signing adds
Signature mark	Deliberate act	The signing event, with session data
Printed name	Identity clarity	Identity verification behind the name
Title/capacity	Authority to bind	Template-enforced completion — no blank titles
Date	Timing	Trusted timestamp, not a typed claim

The last column is where electronic execution improves on ink: every element arrives with evidence attached. The signature event carries identity verification, the date is a third-party timestamp rather than a typed assertion, and the completed block exports with the audit trail. What the full record contains is covered in What a Signed Contract Proves on Receipt.

Where signature blocks go wrong

The blank capacity. The deal closes with an unsigned title line, and the authority argument begins years later. Template-driven signing prevents this by construction: the envelope cannot complete with an assigned field empty.

The personal-versus-company blur. The signer writes their name where the entity name belongs — now it is ambiguous who the contract binds. Pre-placed, labeled fields remove the ambiguity at the source.

The undated or self-dated signature. A typed date is an assertion; a system timestamp is evidence. On paper the distinction is philosophical; in a deadline dispute it decides the case.

Contract Signing Built for Cross-Border Deals: Nota Sign

Ask where US incumbents are weakest and the answer is a map: DocuSign's APAC story offers no iAM Smart or Singpass authentication and no regional data residency. Nota Sign was built by the region's leader — FaDaDa, China's leading e-signature vendor — so the cross-border signature page this article describes is home turf. A US company block and a Chinese counterparty's chop-and-name convention execute in one envelope, PRC rules on their side and ESIGN on yours, with one audit trail documenting the whole page.

The second advantage is completeness enforced by construction. Template roles require every element above — signature, name, title, date — so no contract leaves with a blank capacity; dates stamp from the signing session rather than the signer's keyboard; and the executed page exports with its evidence — identity events, consent records, timestamps, the document hash binding page to terms — verifiable offline without a login. Standard electronic signatures and X.509-backed digital signatures share the envelope flow, with coverage across more than 100 countries and regions: ESIGN and UETA in the US, eIDAS (SES, AES, QES) in the EU, SOC 2 Type II-audited infrastructure throughout.

The third advantage is the commercial model: no per-seat fees, so the legal reviewers and approvers who guard signature-page quality never become license lines — a low-cost package for small teams, tailored plans for mid-market and enterprise buyers, priced against document volume and integration patterns.

If you want to see how one of your own contracts executes — signature page, evidence package, and all — send us a live agreement and we will route it through the platform and hand back the export.