Auto-renewal: alert on the notice deadline, not the renewal date
In short
The date to alert on is not the renewal date but the last day valid notice can still be given, and that sits at least 3 subtractions earlier: the notice period, the deemed-receipt rule for the delivery method used, and the internal lead time to decide and approve. Store only the renewal date and the window has closed before the reminder fires.
Key takeaways
- An evergreen clause renews the term unless notice is given, so the notice deadline is the only actionable date.
- The alertable date is renewal date minus notice period, minus deemed receipt, minus internal decision lead time.
- Some notice windows have an outer bound, so notice given too early is as invalid as notice given too late.
- Store the inputs and compute the date; a stored date goes stale the moment an amendment moves the period.
An auto-renewal or evergreen clause extends the term automatically unless a party gives notice within a defined window. The renewal date is the least useful date in it: by the time it arrives, the decision has been made by inaction. The date worth holding is the last day valid notice can be given.
That date is at least 3 subtractions away from the one printed in the contract, and only the first subtraction is in the renewal clause at all.
From the printed date to the date worth diarising
| Step | Source | Date |
|---|---|---|
| Term ends and renews automatically | The renewal clause | 31 December |
| Less the notice period: not less than 90 days before term end | The renewal clause | 2 October |
| Less deemed receipt: served 2 business days after posting | The notices clause | 29 September |
| Less internal lead time to decide, approve and sign | Your process, not the contract | 30 August |
4 months separate the date in the contract from the date somebody has to be told. 2 of the 3 subtractions come from a clause most abstracts never read — the notices clause — and the third is not in the document at all.
The fields that make the deadline computable
A repository can compute this date only if it holds the inputs rather than someone's arithmetic. The notice obligation is an obligation like any other, and needs the attribute set in what an extracted obligation has to carry.
- The term basis. Whether the term ends on a fixed date or runs from commencement, which is why the record keeps effective, execution and commencement dates apart rather than collapsed into one field.
- Notice length, unit and counting convention. 90 days, 3 months and 13 weeks are 3 different periods, and calendar days against business days changes the answer again.
- Permitted delivery methods, each with its own deemed-receipt rule. Email deemed received on transmission and post deemed received 2 business days after despatch give 2 different last-safe dates.
- The addressee and address, including any copy-to requirement. A notice to the right company at the wrong address can fail on service alone.
- Non-business-day handling. If the computed date lands on a weekend or holiday, whether it moves forward or back — and against whose calendar — is often unstated.
- Internal lead time and the named decision owner. Not from the contract, and the commonest reason a technically correct alert arrives too late to use.
Where the arithmetic quietly breaks
- Months treated as 30 days. A 3-month period ending on 31 May is not 90 days, and month arithmetic from the 31st has no single obvious answer. Store the unit as written.
- Rolling terms after the first renewal. Once a 12-month term has rolled, the term end has moved and any absolute date captured at signature is wrong for every later cycle.
- Windows with an outer bound. A clause allowing notice no earlier than 180 days and no later than 90 days before term end makes early notice invalid; the model needs 2 edges.
- Amendments that move the period without moving the term. The renewal date looks unchanged, the notice deadline has moved months, and a repository keyed to the renewal date shows nothing.
- The wrong clause read entirely. Termination for convenience and non-renewal are different rights with different periods, and abstracting one into the other gives a confident wrong date.
A renewal date is a fact about the contract. A notice deadline is a fact about your calendar, and only one of them can still be acted on.
The point generalises: a clause captured as one number has usually lost the fields that made it mean something, the failure in storing a liability cap without its basis and its carve-outs that swallow the cap. What happens when an alert is anchored to the wrong date has its own account in the renewal alert that fired after the window closed.
Statutory overlays sit on top of the clause, not instead of it
Several jurisdictions regulate automatic renewal in consumer and small-business contracts, usually by requiring the supplier to give advance notice before a term rolls. Whether such a rule reaches a given agreement is a question for counsel there, and the rules change — confirm the current text against the source. None of it removes the contractual notice obligation; it adds a second one, on the other side.
Computing these dates, watching for amendments that move them and drafting the notice is safely automatable; sending it is not, which is the containment pattern in AI agents in production applied to a deadline. Building that with a human at the send step is AI agents and automation work. 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 notice period in an auto-renewal clause?
It is the minimum time before the end of the term by which a party must say it does not want the contract to renew. Miss it and the term extends automatically. The period sits in the renewal clause, but how notice must be delivered and when it counts as received come from the notices clause, and both decide the last safe day.
How do you calculate a renewal notice deadline?
Start at the renewal date, subtract the notice period as written, subtract the deemed-receipt allowance for the delivery method you intend to use, then subtract your own time to make and approve the decision. On a 90-day period with 2 business days' deemed receipt and a month of internal process, the alertable date is roughly 4 months before the date printed in the contract.
What is an evergreen contract?
One that renews itself indefinitely for successive periods unless a party gives notice to stop it. No positive decision is ever required to continue, so the agreement outlives everyone who chose it. That is why the notice window, not the renewal, is what a repository has to surface.
Can notice to prevent renewal be given too early?
Yes, where the clause sets an outer bound as well as a minimum — notice no earlier than 180 days and no later than 90 days before term end, for example. Notice served outside that window can be ineffective, so the record models the window as 2 edges rather than a single deadline, and the reminder fires inside it.
- auto-renewal
- evergreen clause
- notice periods
- critical dates
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
- 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
- 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
- Three dates a contract record keeps confusing, and what each one governsA repository with one date field has already chosen which of three questions it can answer, usually without noticing that it chose.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
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