Software renewal terminology: a plain-English glossary
Software contracts reuse a small set of words, and several of them sound interchangeable while meaning very different things. "Renewal date" and "cancellation deadline" are months apart in practice. "Auto-renew" and "evergreen" describe different structures. "Expiry" and "renewal" are opposites in what they cost you if you do nothing.
This is a reference for the vocabulary, written in the order the terms matter. Each entry says what the term means, and where it makes a practical difference to what you pay.
What is a renewal date?
The renewal date is the day a contract's current term ends and the next one begins. It is the date the vendor bills you again, and the date from which the next term's pricing applies.
It is worth being clear about what the renewal date is not: it is not a deadline. By the time the renewal date arrives, the decision has usually already been made for you, because the window to give notice closed weeks or months earlier. The renewal date tells you when money moves. The cancellation deadline tells you when you had to act.
Renewal date vs expiry date
A renewal date implies continuation - the contract rolls into a new term unless somebody stops it. An expiry date implies the opposite: the contract ends on that day unless somebody actively extends it. The distinction decides what happens when everyone forgets. A missed renewal date costs you another term; a missed expiry date costs you the tool, sometimes mid-project.
What is a renewal cycle?
The renewal cycle - also called the billing cycle or the term length - is how long each term runs before it renews again. Monthly, quarterly and annual are the common ones, and some purchases are one-off, with no cycle at all.
The cycle matters because it sets both the size of the commitment and how often you get a chance to change it. An annual cycle means one decision point a year and twelve months of exposure if you miss it. A monthly cycle means twelve cheap exits. Vendors discount annual terms precisely because the longer commitment is worth more to them than the discount costs.
What is a calculated renewal date?
A calculated renewal date is the NEXT renewal date, worked out from the original renewal date plus however many cycles have passed since. It exists because a stored date goes stale: a tool that renewed on 1 March 2025 on an annual cycle has a real next renewal of 1 March 2026, then 1 March 2027, without anyone editing the record.
StackTrackr rolls the date forward automatically for auto-renewing tools, so a renewal in the past never silently drops off your dashboard. A tool that does not auto-renew keeps its stored date, because a passed renewal there is a genuine problem worth flagging rather than a date to advance. There is a fuller explanation in renewal date vs calculated renewal date in the help centre.
What does auto-renew mean?
Auto-renew (an automatic renewal clause) means the contract continues into a new term by default, without either party signing anything. It needs no action from you to carry on - only action to stop.
That asymmetry is the entire risk. An auto-renewing contract converts your inattention into a purchase. Every other term in this glossary matters mostly because it changes how much warning you get before that happens. Mark which of your tools auto-renew before you do anything else, because that flag decides which records need watching and which merely need remembering.
What is a notice period?
The notice period is how far in advance of the renewal date you must tell the vendor you are leaving. It comes from the termination clause, and in software contracts it is usually somewhere between 30 and 90 days.
Read the clause for two details beyond the number. First, whether notice must be in writing and to a specific address - an email to your account manager sometimes does not count. Second, what the notice is measured against: usually the renewal date, but occasionally the end of a calendar month, which quietly moves your real deadline earlier. SaaS notice periods explained goes through the clause language in more detail.
What is a cancellation deadline?
The cancellation deadline is the last day you can give notice and still stop the contract renewing. It is the renewal date minus the notice period, and it is the only date in this glossary that is genuinely a deadline.
A tool renewing on 1 October with a 90-day notice period has to be cancelled by 3 July. Nothing about July looks like a renewal month, which is why this date is the one teams miss. It is also the reason a register that stores only renewal dates does not protect you: the date you need is one the contract never states directly, and you have to derive it for every tool you own.
What is an evergreen or rolling contract?
An evergreen contract has no fixed end date - it rolls from one term into the next indefinitely until one party cancels. Monthly subscriptions are usually evergreen by nature.
The difference from a straightforward auto-renewal is one of scope rather than mechanics. An auto-renewing fixed-term contract renews into another defined term, and each renewal is a point where price and terms can be revisited. An evergreen arrangement has no such natural boundary, so it can run for years without anyone reviewing what it costs. Evergreen tools are the ones most likely to be quietly overpriced, because nothing ever forces the conversation.
What is an option to renew?
An option to renew is the opposite structure to auto-renewal: the contract expires at the end of its term unless you actively choose to extend it. The default is ending, not continuing.
These are the friendlier contracts to hold, but they carry their own failure mode. Because nothing renews on its own, forgetting the date means losing access rather than overpaying - and losing access to something a team depends on mid-quarter can cost considerably more than a wasted subscription. Option-to-renew tools still need a date in the register; they just need a different kind of reminder.
What is an anniversary date?
The anniversary date is the yearly recurrence of the contract's start date. On a simple annual contract it coincides with the renewal date, which is why the two terms often get used as if they were the same thing.
They come apart as soon as anything is added mid-term. Buy extra seats in month seven and those seats commonly align to the original anniversary rather than starting a term of their own - so you pay a part-year for them, and the whole contract still renews on the original date. When a vendor quotes an anniversary date, check whether they mean the date your money is next due or simply the date the paperwork began.
What is a lifecycle status?
A lifecycle status records where a tool currently sits between first evaluation and final shutdown. It answers a question a renewal date cannot: is this thing being trialled, running normally, awaiting a decision, or already on its way out?
Some statuses are facts only a person knows, so you set them yourself:
- Trial - being evaluated, not yet a paid commitment
- Active - live and in use
- Notice given - cancelled, but still running until the current term ends
- Cancelled - ended and no longer running
- Expired - lapsed without a renewal decision
The more useful states are the ones nobody should have to maintain by hand, because they are simply consequences of today's date. StackTrackr derives these for any tool marked active - Upcoming and Due soon as a renewal approaches, Notice window when a cancellation deadline is close enough to need a decision now, and Overdue when a renewal date has passed on a tool that does not auto-renew. Lifecycle states and badges lists them with the thresholds behind each one.
The reason to separate the two kinds is maintenance. A register where every status is typed in by hand is out of date within a fortnight, and a status nobody trusts is worse than no status at all.
What is annualised cost?
Annualised cost is what a subscription costs over twelve months, restated so tools on different billing cycles can be compared. A £40 monthly tool and a £600 annual one are £480 and £600 a year respectively, and only in that form does the comparison mean anything.
Without it, monthly tools systematically look cheap and get waved through, which is how a stack accumulates small recurring charges that nobody ever adds up. Annualising every line is what turns a list of subscriptions into a budget. The help centre covers how annualised cost is calculated.
What is contract liability or committed spend?
Contract liability is the money you are already committed to paying under contracts you have signed - the remaining value of current terms, plus any term that will auto-renew before you next get a chance to stop it. It is a different figure from annual spend, and usually a larger one than people expect.
The distinction is what makes it worth tracking. Annual spend is what you paid last year and can, in principle, change. Liability is what you cannot change without breaching something. When a budget needs cutting, the liability figure tells you what is genuinely available to cut and what is already spent. How to calculate SaaS contract liability works through the method.
Putting the vocabulary to work
Most of these terms only earn their keep in combination. Auto-renew tells you whether inaction costs money. The notice period tells you how much warning you get. Together they produce the cancellation deadline, which is the date that belongs in the calendar. The renewal cycle sets how often the whole sequence repeats, and the lifecycle status records where each tool has got to.
Three fields per tool - renewal date, notice period, whether it auto-renews - are enough to derive everything else. StackTrackr does that derivation for you and alerts the named owner before each deadline rather than after the invoice. The free Starter plan covers up to ten tools, which is enough for the contracts that carry most of the risk. When it earns its place, create an account and bring the rest across.