Many supplier and software contracts end the same way: nobody decides anything. The term runs out, the contract renews for another year, and the invoice arrives. The notice period, often one to three months, ended long before anyone looked at it.
A renewal calendar prevents this. It is one list, one owner per contract and one routine, and it needs no special software.
Why renewals slip
Three things go wrong again and again:
- The signer has moved on. The person who negotiated the contract is on another project or has left, and the dates went with them.
- The date that matters is hidden. Everyone remembers the renewal date. Few remember that the notice must be given 60 or 90 days earlier.
- Nobody owns the decision. Finance sees the invoice, the user sees the tool, and neither feels responsible for asking whether it is still needed.
Step one: list every contract with a term
Start with contracts that renew or expire: software subscriptions and licences, hosting, maintenance and support agreements, service contracts, leases, insurance and framework agreements with key suppliers. Collect them from three places: the contracts folder, the accounting system (recurring payments) and the company card statements.
Do not worry about completeness on the first day. A list of the twenty largest contracts is already useful.
Step two: record a few fixed fields
One row per contract, the same columns every time:
- Counterparty and what it covers.
- Annual cost and billing period.
- Start date and current term end.
- Renewal type: automatic, manual or open-ended.
- Notice period and the notice deadline, calculated as term end minus notice period.
- Owner: the person who uses the service or manages the supplier.
- Decision maker: who may approve a renewal or a cancellation.
- Link to the signed document.
The notice deadline is the column that matters. Calculate it once when you add the row, and check the wording in the contract: some count calendar days, some count from receipt, some require a registered letter.
Step three: set the reminder 90 days before the notice deadline
If the notice period is 60 days, a reminder at 90 days before the term end leaves you almost no time. Set the reminder 90 days before the notice deadline. That gives the owner time to review, ask the team, request a quote from another supplier and still negotiate.
For small contracts, 30 days before the deadline is enough. For anything that is expensive, hard to replace or tied to a core process, use 90 or even 120 days. A shared calendar with an entry for each deadline works well; a spreadsheet column with a filter works too.
Step four: the owner prepares a short recommendation
When the reminder fires, the owner writes three to five lines for the decision maker:
- What we use it for and whether that is still true.
- What it costs and whether the price changed.
- Who actually uses it. For subscriptions, our article on a monthly review of software subscriptions shows how to find unused seats.
- Recommendation: renew as it is, renegotiate, replace or end.
- Risks of ending, such as data export, dependent processes or a replacement that takes months. If a system is being replaced, see retiring an old system safely.
The decision maker answers within two weeks, and the answer is written in the calendar: renewed, renegotiated, ended or postponed with a new date.
Step five: use the renewal to renegotiate
A renewal is the moment when you have the most leverage, because the supplier would like to keep you. Before it, check:
- whether the price increase is allowed by the contract and by how much;
- whether you can reduce the scope, number of users or service level;
- whether a multi-year term would give a real discount, and what it would cost to leave;
- whether the terms you agreed when you started, listed in your supplier onboarding checklist, are still being delivered.
Ask for changes in writing and before the notice deadline, not after it.
Step six: keep the calendar alive
- Add a row the day a contract is signed. If the calendar is updated only once a year, it will always be out of date.
- Review it every quarter. Fifteen minutes: which deadlines fall in the next 120 days, and does each one have an owner?
- Name a deputy for every owner who goes on a long leave.
- When someone leaves, reassign their contracts as part of the handover.
Common mistakes
- Tracking the renewal date but not the notice deadline.
- Keeping the contracts in several places, such as one folder per person.
- Listing the contract but not the person who decides.
- Cancelling by e-mail when the contract requires a registered letter or a portal request.
- Starting the review a month before the deadline, when there is no time left to compare alternatives.
- Auto-renewing "just in case" without a recorded decision.
Notes on legal terms
Notice periods, automatic renewal rules and the form of cancellation depend on the contract and on the law of your country. This article describes a working practice, not legal advice. For large or unusual contracts, have the notice terms checked by a lawyer.
Summary
A contract renewal calendar is one list with the term end, the notice deadline, an owner and a decision maker for every contract, a reminder 90 days before the deadline and a short recommendation at each renewal. It takes an afternoon to start, and after the first year it shows how much you paid for things that nobody decided to keep.
Sources
- Our related articles linked above.
- The fields, reminder lead time and review routine are a working practice for small companies, not a legal or industry standard; adjust them to your size, sector and local rules. No client results or market figures are claimed in this article.
