Three moments people collapse into one

"Is it signed?" is the wrong question, or at least an incomplete one. A contract has three distinct milestones that everyday language smears together: the moment you signed, the moment it became fully executed, and the moment it became effective. They can all be the same day — or three different days — and the gap between them is where real confusion lives. A team that treats "I signed it" as "the deal is live" starts performing obligations, or counting a clock, from the wrong moment. This is a plain tour of what each term means and how your signing record pins down each one.

Signed: one party has put their mark down

Signed is the narrowest of the three: a specific person has applied their signature to the document with intent to sign. It's about one party's act. When you sign an agreement that the other side hasn't signed yet, the document is signed — by you — but it is not yet a binding contract between both parties. As we note in what happens after you sign, your signature advances the document; it doesn't necessarily complete it.

This is why "I signed it, so we're good" is a trap on any two-party agreement. Your signature is a commitment offered, not a deal closed — until the other side signs too.

Executed: everyone who must sign has signed

Fully executed is the moment the last required signature lands — every party has signed, so the document is now a binding contract. This is the milestone most people actually mean when they say "the contract is signed." On a multi-party deal it depends on the routing: in a sequential flow the document executes when the final signer in the chain finishes; in a parallel flow it executes when the slowest of the independent signers completes. Either way, execution is a property of the whole envelope, not any one signature — which is precisely why countersigning matters: a contract that needs the other party to countersign isn't executed, and isn't binding, until that final signature is placed.

A good signing platform makes this moment unambiguous. When the envelope status flips to completed, that's your executed timestamp — recorded in the audit trail to the second, for every party, so there's no argument later about when the deal became a deal.

Effective: when the obligations actually start

Here's the twist that catches people: a contract can be fully executed and still not be in force yet. The effective date is when the parties' obligations actually begin — and it's set by the contract's own terms, not by when the ink dried. A contract might say it's effective:

  • On the execution date — the default when nothing says otherwise; live the moment it's fully signed.
  • On a stated calendar date — "effective January 1," signed in December. The obligations wait for the named day even though the document is already executed.
  • On a triggering event — effective on close of a transaction, on receipt of a deposit, on delivery of the first shipment.

So the sequence can genuinely be: you sign the 10th, the counterparty countersigns the 12th (executed), and the term begins the 15th (effective). Three dates, three meanings. Confuse the effective date with the execution date and you might start billing, start a notice period, or begin counting a term from the wrong day — a small error that compounds into a real dispute.

Why the distinction matters in practice

These aren't law-school hairs to split. They drive real actions:

  • Performance. You shouldn't start delivering — or paying — before the effective date, and you're on the hook once it arrives.
  • Clocks. Renewal windows, notice periods, and term lengths usually run from the effective date. Get it wrong and you auto-renew or lapse on the wrong calendar.
  • Recognition. Finance often keys revenue or expense recognition to execution or effectiveness, not to whoever signed first.
  • Disputes. "When did this contract take effect?" is a question a disagreement will eventually ask, and your answer needs to match the document.

How your signing record captures all three

A well-run electronic signing flow pins down each milestone without any extra effort. Every individual signature is timestamped in the audit trail, so each signed moment is on the record. The envelope's completed status marks the executed moment precisely. And the effective date — the one the platform can't know because it lives in the contract's language — is exactly the field you should capture into your contract lifecycle records when the agreement completes, right alongside the counterparty and the renewal window. Do that, and all three dates are documented and findable instead of reconstructed from memory during an argument.

The takeaway

Signed means one party made their mark. Executed means everyone who had to sign has, so the contract is now binding — the moment your envelope status flips to completed. Effective means the obligations actually start, on whatever date the contract's own terms specify, which may be later than execution. They're often the same day and sometimes three different ones. Let your signing platform stamp the signed and executed moments automatically, capture the effective date into your contract records deliberately, and you'll never again start a clock — or a performance obligation — from the wrong day.

This article is general guidance, not legal advice. How execution and effectiveness are determined can depend on the contract's terms and applicable law — consult qualified counsel for a specific agreement.