Three dates a contract record keeps confusing, and what each one governs
In short
The effective date is when the terms begin to bind, the execution date is when the last party signed, and the commencement date is when performance starts. They frequently differ, and each drives a different calculation: term and renewal run from the effective date, evidentiary questions from execution, and service levels and billing from commencement.
Key takeaways
- Effective, execution and commencement are 3 separate facts and belong in 3 separate fields.
- Term and renewal maths run from the effective date, so a record storing the signature date renews on the wrong day.
- Counterparts mean signatures carry different dates; execution is normally the date of the last one unless stated otherwise.
- An effective date stated as an event has no value until the event happens, and the record must hold both.
The effective date is the date from which the agreement's terms bind the parties. The execution date is the date the last party signed. The commencement date is the date performance starts. They can all be different, and on any agreement with a mobilisation period or a condition precedent they usually are.
A repository holding one date field has already decided which of those 3 questions it can answer, generally without anyone noticing the choice was made.
Signed in February, effective from January, live in April
Take a services agreement where the second signature lands on 12 February, the parties state it is effective from 1 January, and the first statement of work says services begin on 1 April. A 24-month term produces 3 different end dates depending which one the system anchored to.
| Date | What it governs | Where it comes from |
|---|---|---|
| Effective | Term length, renewal and notice arithmetic, when obligations attach | Stated in the preamble or a defined term, not from a signature block |
| Execution | Evidentiary questions: who signed, when, with what authority | The signature blocks and the signing platform's completion record |
| Commencement | Service levels, billing periods, delivery milestones, go-live | The schedule or the statement of work, often not the master agreement |
Row 1 is where money leaks quietly. Compute renewal and notice windows from the signature date and every downstream date is wrong by the gap between execution and effectiveness — the same error, in the same direction, across the portfolio, with the mechanics in the renewal alert that fired after the window closed.
The awkward cases that break a single date field
- Counterparts signed on different days. Each signature carries its own date, and execution is normally the date of the last. Store the individual signature dates too: a dispute about authority is about a particular signature.
- An effective date expressed as an event. Effective on the date regulatory approval is obtained, or on completion of a share purchase. Until the event occurs there is no date, so the field holds a condition and a resolved value, and something has to notice when it resolves.
- Provisions with their own start. Confidentiality applying to disclosures made before signature, a non-solicit running from the end of the term, insurance biting at commencement. A single agreement-level date expresses none of them.
- Commencement inside a child document. The master is effective in January; work starts under a statement of work signed in April — which is why a record must know which document a date belongs to, the structure in the parent, the child and the amendment.
- Amendments with their own 3 dates. An amendment signed in June and expressed to take effect from March changes the operative terms retrospectively without touching the original's dates.
What an 'as of' date is, and what it is not
An agreement expressed to be made 'as of' an earlier date records the parties' agreement that the terms apply from that moment. It does not change when the document was signed, and it is not evidence that anything happened earlier. Whether an earlier operative date is appropriate is a legal question; the data-modelling question is simpler.
The fields that keep the 3 apart
- Effective date, plus a flag for whether it was stated as a date or as an event, and the event's description where it was.
- Execution date, plus the per-signatory dates and the name and capacity in which each person signed.
- Commencement date, with the document it came from, since it frequently lives in a schedule rather than in the agreement that governs it.
- Provision-level overrides for any clause with its own start or survival period, held against the clause rather than the contract.
- The definition source for each date. On the counterparty's template the defined term may sit in a schedule and mean something unexpected, one of the reconstructions needed when reviewing on the other side's paper.
There is a retrieval consequence too. A filter for everything effective in a given year returns a different set from a filter on signature date, and neither is wrong — but a user who does not know which the field holds concludes the agreement is missing, one cause in everyone knows the agreement exists and search will not return it.
One date field is a decision about which question the repository can answer. Three fields cost almost nothing and keep all three answerable.
Splitting one field into 3, backfilling what can be backfilled and flagging what cannot is small, cheap, unexciting internal tools and ops work, and it gets more expensive every month it waits. This page sits in contract lifecycle and obligations, part of legal technology software.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is the effective date of a contract?
It is the date from which the agreement's terms begin to bind the parties. It is stated in the document — usually in the preamble or as a defined term — and is not automatically the date of signature. Term length, renewal cycles and notice windows are calculated from it, so a system substituting the signature date produces a wrong renewal date wherever the two differ.
What is the difference between the effective date and the execution date?
The execution date is when the last party signed; the effective date is when the terms start to operate. They coincide only when the agreement says so. Execution answers evidentiary questions — who signed, when, with what authority — while effectiveness answers when obligations attached, so both belong in the record.
Which date should a renewal calculation use?
The effective date, unless the agreement expressly ties the term to something else. The term runs from when the agreement began to operate, so the renewal date, and the notice deadline behind it, both derive from it. Anchoring to the signature date shifts every downstream deadline by the gap between the two.
Can a contract be given an effective date earlier than the day it was signed?
Agreements are sometimes expressed to be made 'as of' an earlier date, recording that the parties intend the terms to apply from then. Whether that is appropriate is a legal question that depends on the circumstances. What is not optional is the record: keep the signature date alongside the stated effective date, because overwriting it destroys evidence of when execution happened.
- contract dates
- effective date
- data model
- abstraction
The work behind this page
Builds from our portfolio that this page draws on.
Brief Forge
Contract review AI for solo lawyers and small firms — extract, score, and redline contracts in minutes.
Legal TechAI Lease Management
AI-powered commercial real estate lease management for multi-brand operators — automates lease data extraction, obligation tracking, and portfolio intelligence.
Real EstateAskVault
An AI internal knowledge-search platform that answers employee questions from your own docs — grounded in citations, with knowledge gaps surfaced and deflection tracked.
Productivity AIRead next
- Auto-renewal: alert on the notice deadline, not the renewal dateThe date printed in the contract is the last date anything can be done about it. The date worth diarising sits 3 subtractions earlier.definition
- The obligation register: 5 attributes an entry cannot work withoutMost registers are lists of clause summaries. A summary tells you what the contract says, not what to do, by when, or how you would prove it was done.definition
- Contract families: the parent, the child, and the amendment on bothA parent field expresses one relationship of one kind at one moment. Real contract families need directed edges carrying a type, a date and a scope.definition
- Everyone knows the agreement exists and search will not return itA known agreement that will not surface has one of four causes, and re-indexing the estate fixes exactly one of them. Four probes, in order, tell you which.diagnostic
- One counterparty, nine records, and never the whole relationshipAsk what you have with a supplier group and the repository answers with half of it. Some near-duplicate records are typing errors; some are different legal persons.diagnostic
- The renewal alert fired on time and the notice window had already closedThe alert was accurate, timely and useless. It counted back from the wrong date, and it treated a decision that takes six weeks as something a person does on the morning they are told.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation