Article
Contract expiry reminders: what to track for renewals, terminations and auto-renewal clauses
A contract expiry reminder needs more than an end date. Pull four kinds of dates from each contract: the expiry date, the notice period for renewal or termination, any auto-renewal terms, and obligations due before expiry. Work back from the notice deadline to set reminder dates, and give each reminder an owner. Reminders kept in the contract register, attached to the contract record, are more reliable than ones in a personal calendar.
- By
- Zico Team
- Published
2 min read
The short version
The usual way to track contract expiry is to put the end date in a calendar and get a reminder a few days before. The trouble is that for many contracts the date that matters is not the end date. If a contract renews automatically, you often have to give written notice a set number of days before expiry to stop it; miss that window and the contract renews for another term on the same conditions.
So before setting reminders, find four kinds of dates in the contract, then decide how early to remind and whom.
1. Find four kinds of dates
- Expiry date: the last day of the term. Framework agreements, annual service contracts and leases all have one.
- Notice period: how many days before expiry you must notify the other side to renew, terminate or renegotiate, often written as "thirty days' written notice before expiry". This is the date that tends to get missed.
- Auto-renewal: whether the contract renews automatically, for how long, and whether the price changes on renewal.
- Obligations due before expiry: final payments, deposit refunds, delivery acceptance, return of data. Leaving these until after expiry puts you on the back foot.
Not every contract has all four, but check each one for every contract. Where something does not apply, record "none" rather than leaving it blank.
2. Work back from the notice deadline
Set the reminder from the day action is needed, not from the expiry date. If termination requires thirty days' notice, the first reminder should come around forty-five days before expiry, leaving time to decide internally whether to renew and to get approval.
Two reminders work well: the first asks the owner to decide whether to renew; the second, a few days before the notice deadline, checks that the notice has gone out.
3. Give every reminder an owner
Who receives the reminder matters more than whether one is sent. A common split: the business owner decides whether to renew, legal confirms how notice is given and worded, and finance watches payments and price changes after renewal. When the owner leaves or changes role, their contracts' reminders move with the handover.
4. Keep reminders in the register, attached to the contract
Reminders in a personal calendar or a spreadsheet comment disappear when people change. It is more reliable to record the expiry date, notice period and auto-renewal flag as fields on each contract in the contract register and generate reminders from those fields. For the other fields a register should hold, see contract register template: the fields you need.
E-signature does not cover this stage: tracking obligations and expiry after signing is contract management, as explained in e-signature vs. contract management system.
Summary
Start with four kinds of dates: expiry, notice period, auto-renewal and obligations due before expiry. Work back from the notice deadline to set reminders, give each reminder an owner, and keep reminders in the contract register.
Zico (FIM) is a contract lifecycle management system; after approval and signing, it sends automatic reminders for payment, delivery and expiry milestones, and archives performance milestones with the register.
Related
- E-signature vs. contract management system: what still needs managing after the signatureE-signature handles how a contract gets signed: online signing, signer identity and an audit trail…
- Should your contract management system run on your own servers? Four questions to ask firstRunning a contract management system on your own servers (private deployment) suits companies whose contract data is sensitive, who face regulatory…
- What features does a contract management system need, and how do you test them before go-live?Contract management system features usually fall into six groups: drafting and templates, negotiation and versions, approval and sign-off…
Bring these questions to a demo
Book a dedicated demo and walk one complete path matching your organization, collaboration platform and deployment requirements.