Renewal mechanics · 7 min read

Contract notice period vs expiry date: which date actually binds you

By Alex Renner · 13 October 2026

Most contract owners track a single number: the expiry date. It is the date printed in the summary, the date that drives the renewal reminder, and the date that feels safe because it is furthest away. It is also, usually, not the date that decides anything. By the time the expiry date arrives, the choice about what happens next has already been made, or lost, somewhere earlier in the calendar.

The two dates in every term

A renewable term carries an end date and a notice requirement. The end date fixes the length of the current term. The notice requirement says how much advance warning one party must give to stop the term from rolling over. The notice deadline is the end date minus the notice period: the last day on which a valid notice can still be served.

Those two dates are usually weeks or months apart, and the gap between them is where the risk sits. A twelve-month term with a ninety-day notice period has a notice deadline in month nine. For the final quarter of the term the contract is effectively already committed, unless notice was served in time.

Which date actually binds you

The notice deadline binds you, because it is the last moment at which the organisation can still change the outcome. After that date the only options are to accept the renewal or to negotiate a variation the supplier has no obligation to grant. The expiry date, by contrast, is mostly informational: it tells you when the next term begins.

Treat the notice deadline as the operational deadline and the expiry date as background context. To test the arithmetic for a specific contract, enter the term end and the notice period into the free notice-period calculator, which returns both dates together with the rule it applied.

A worked example

Take a contract that ends on 30 June 2027 with a notice period of ninety days. Counting back ninety calendar days from 30 June gives 1 April 2027. Notice served on 3 April is late, even though it is nearly three months before the term ends. Notice served on 31 March is valid, assuming the contract counts calendar days and says nothing about business days or receipt.

Now change the unit. The same contract with a notice period of three months instead of ninety days produces a different result. Three months before 30 June is 30 March, not 1 April, because calendar months count backwards by month name rather than by a fixed number of days. The difference of two days is invisible in a summary and decisive in practice.

There is one more reason the expiry date misleads. It is the date a supplier will quote back to you, because a renewal letter sent close to the term end looks reasonable to anyone who has not read the notice clause. A team that tracks the notice deadline can answer that letter with the clause and the date it produces.

What to check in the clause

Four details change the answer, and all four live in the wording rather than in the summary:

• The unit. Calendar days and calendar months are not interchangeable, and a figure such as 90 days is not the same as 3 months.
• The counting rule. Some clauses exclude the day of service, some exclude the end date, and some count business days instead of calendar days.
• The form of notice. Email, registered post and courier each carry their own receipt risk, and a clause that requires receipt by a date is stricter than one that requires sending by a date.
• The direction. Notice obligations are often mutual but not always symmetrical; check whether the notice period applies to both parties or only to you.

If any of those four is unclear, the date you compute is provisional. NoticeAhead is a tracking tool rather than legal advice, so a contract with ambiguous wording should be read by someone qualified to interpret it. The How it works page sets out what happens to a contract once the dates are agreed.