Contract Signed: What It Means on Receipt

A contract is "signed" in the US when both parties have taken an affirmative action that demonstrates intent to be bound, on a document version both have agreed to. The word "signed" is doing real work in that sentence: it is not the same as "sent," "received," "viewed," or "effective." A contract can be signed before it is effective; it can be effective before it is fully signed; and the moment of signing is what most disputes end up litigating.

What Has to Happen for a Contract to Be Signed

Three things have to be true at the moment a contract is signed:

1. Both parties have shown intent. Not viewed, not opened, not received. Each party has taken an action that the law reads as assent: a wet signature on a paper document, an electronic signature on a tracked envelope, an oral "yes" on a recorded call where the parties have agreed oral assent counts.
2. Both parties have agreed to the same document version. Not the version one party sent; not the version the other party edited in redline. The same revision. A signature on a different version is not a signature on the contract.
3. The contract does not require an additional formality to be binding. Notarized documents, witnessed signatures, and certain regulated filings have to clear their own formality step before the signature counts. A signature alone does not satisfy those steps.

What the law does not require is simultaneity. Most US contracts are signed sequentially. The counterparty signs second, on the same document version, and that second signature is the moment the contract is formed.

Signed Versus Effective: The Two Timestamps

A contract's signing date and its effective date are not always the same. The two most common reasons they diverge:

1. Effective date clause. A contract can be signed on Monday and become effective on the following Monday, or on receipt of a down payment, or on the closing of a financing. The signing date is when intent was shown; the effective date is when obligations begin.
2. Conditions precedent. A contract can be signed but not effective until a condition is satisfied: a regulatory approval, a board vote, an insurance policy being issued. The signing creates the obligation to perform; the effective date is when performance is due.

The distinction matters for two operational reasons. First, the statute of limitations for a contract dispute usually starts on the effective date, not the signing date. Second, internal records (revenue recognition, contract management systems, audit trails) often key off the effective date rather than the signing date.

How Counterparts and Electronic Execution Change the Picture

US contract law has long accepted the practice of executing a document in counterparts. Each party signs its own copy, and the two copies together constitute one agreement. The convention predates electronic signatures; what electronic execution added is the ability to produce a single document hash that ties both parties' signatures to the same revision.

For an electronically executed contract, the practical effect is that the two parties do not have to sign the same file at the same time. Each party signs the version they received, and the platform's audit trail proves both signatures were applied to the same byte sequence. The hash is what makes the counterparts enforceable; without it, the second signer could have signed a different document than the first.

This is the reason counterpart clauses appear in nearly every US commercial agreement drafted in the last decade. They are not boilerplate; they are the mechanism that makes sequential electronic execution work.

How platforms structure the execution path is in Signature Solutions: Features, Cost & Migration Guide 2026.

What a Signing Platform Has to Capture

For a contract to be defensibly "signed," the platform that produced the signatures has to capture, at a minimum:

• The document hash at the moment each party signed. This is what proves both parties agreed to the same revision.
• The identity proofing at the moment of signing. Who, how, and when.
• The consent record. What each signer was shown about the agreement and what action they took.
• The completion timestamp. When the second signature was applied and the platform marked the envelope complete.
• The export package. A self-contained file that a third party can verify offline.

The platform's job is to make all five exportable as a single package. A screenshot of a "completed" status is not evidence; the package is.

For regulated industries, the bar is set higher; CFR Part 11 Compliance Guide reads the regulated-record expectations.

Why "Signed" Is the Word That Gets Litigated

The disputes that end up in a lawyer's hands are almost never about whether a mark appeared on a page. They are about whether the mark carries the intent the contract requires. The four intent arguments that recur:

1. The signer did not read the document. A signature on a contract the signer did not read is still a signature, in most US jurisdictions. The argument is about whether the platform's consent capture defeats the "I didn't see it" defense.
2. The signer signed the wrong version. A signature on a version the counterparty later edited is not a signature on the contract. The platform's document hash is what defeats this argument.
3. The signer lacked authority. A signature on behalf of an entity by someone without authority is not the entity's signature. The platform's identity and role capture is what defeats this argument.
4. The contract was induced by fraud. A signature on a contract procured by fraud is voidable. The platform cannot defeat this argument; only the underlying facts can. The platform's job is to make the signature itself provable, not to prevent fraud.

The platform that captures all five elements above produces a signature that survives the first three arguments automatically. The fourth argument is the case the platform cannot help with.

What the audit trail has to capture for that package to be portable is in DocuSign Advanced Audit Trail Compliance.

What "Signed" Means in Common Business Settings

Five workflows where the question comes up most often:

• Sales contracts. Signed at the moment the buyer accepts the seller's standard form, with the seller's signature applied automatically on receipt. The buyer's signature is the moment of formation.
• HR onboarding documents. Each document is a separate contract. The signing of the offer letter is one moment; the signing of the IP assignment is another; the signing of the non-compete is a third. Each is its own signed agreement.
• Vendor agreements. Signed when the vendor's authorized signatory applies the mark. The customer's signature on the PO is acceptance of an offer, not the formation of the contract in most cases.
• NDAs. Signed at the moment of the second party's signature, on the same version the first party produced.
• Board resolutions. Signed when all directors have signed, or when the chair signs a conformed resolution on behalf of the board under the bylaws. The authority source matters.

In each case, what changes is who signs, in what order, on what document version. The platform's job is the same: capture the five elements, export them, and make the package portable.

How US teams in particular handle the audit-trail evidence is covered in Electronic Signature Audit Trails for US and APAC Teams.

Checklist Before You Treat a Contract as Signed

Use this before you act on a contract as if it were binding:

• Both signatures: confirm both parties' marks are present on the same document version.
• Identity proofing: confirm each signer was verified at signing time.
• Consent capture: confirm the platform recorded what each signer was shown.
• Effective date: confirm whether the effective date is the signing date or another date set by the contract.
• Conditions precedent: confirm whether the contract has conditions that must be cleared before it becomes effective.
• Export package: confirm the signed document and the audit trail are stored together and can be retrieved as one unit.

What the audit trail has to capture for that package to be portable is in DocuSign Advanced Audit Trail Compliance.

What "Signed" Looks Like at the Export

The dispute over a contract usually ends with one question: what document version did each party agree to, and on what was each signature applied. The FaDaDa platform answers that question by tying each envelope to a single document hash from the moment it is uploaded to the moment the second signature is applied, and bundling the two signatures, the consent records, and the completion timestamp into a single export.

The export is what the lawyer or the auditor will read, not the screen the signer saw. The platform's design is that "signed" means the export is complete, not that a status indicator showed a check mark. If the export does not show both signatures on the same hash, the contract is not signed, regardless of what either side's UI said.

If you want to see what the export looks like for a contract that is about to be signed, send us one of your live agreements and we will route it through the platform and show you the export.

Disclaimer

This article describes the technical and legal mechanics of electronic and digital signatures in general terms. It is not legal advice and does not certify compliance with any statute, regulation, or industry rule. Specific obligations vary by document class, jurisdiction, and counterparty policy, and your counsel and records-management team should approve any signature workflow before it is adopted.