Evergreen and rolling software contracts: how they work and how to get out
Most software contracts do not end. They continue, on terms agreed once and rarely revisited, until somebody takes a deliberate action to stop them. The contract language for this is evergreen, and in practice people call the same thing a rolling contract, a periodic contract, or just "it auto-renews".
The word is not the problem. The problem is that two contracts can both be described as rolling and carry completely different exposure: one commits you to another month, the other to another year. Nobody tells you which you signed, because the distinction lives in a single clause most people read once, at the point where they had already decided to buy.
What an evergreen contract actually is
An evergreen contract renews itself for a further term, automatically, at the end of each term, and keeps doing so indefinitely. There is no final end date written anywhere in it. It stops only when one party gives notice in the way the contract requires, or when both agree to end it.
That is the whole mechanism, and on its own it is neutral. For a tool the business genuinely depends on, an evergreen structure is convenient: nobody has to re-sign a contract every year for software everyone agrees to keep. The cost appears in the long tail, where the same mechanism keeps charging for tools whose champion left eighteen months ago. Our renewal terminology glossary defines the term alongside the rest of the vocabulary; this guide is about what to do with it.
The two structures people both call rolling
Almost every evergreen software agreement is one of two shapes, and the difference between them is the single most useful thing to establish about any contract you hold.
Fixed term, then successive terms of the same length
A twelve-month initial term that renews into another twelve months, then another. This is the common enterprise shape and the expensive one. Every rollover recommits you for a full year, so a deadline missed by a week costs roughly fifty-one weeks of software you had decided to stop paying for.
Fixed term, then month to month
The same twelve-month initial term, but on expiry it continues on a monthly basis rather than recommitting for a year. The consequence of missing the deadline here is one month, not twelve. Some vendors also start month-to-month from day one with no initial term at all, which is the lowest-commitment version of the structure.
Why the rollover period decides your exposure
Your real exposure on an evergreen contract is not the annual cost. It is the cost of one renewal term, because that is what a single missed deadline buys. A tool at £400 a month that rolls monthly puts £400 at risk. The same tool rolling into successive annual terms puts £4,800 at risk, from the same oversight on the same day.
This is also why the notice period matters more on some contracts than others. Notice and rollover interact: a ninety-day notice period on an annually rolling contract means the decision window opens nine months into a twelve-month term, and closes three months before you next see an invoice. Read them as a pair rather than as two separate fields.
Occasionally the pair is drafted incoherently, and it is worth spotting when it is. A monthly rolling contract carrying a ninety-day notice period is not really monthly: you are never less than three months committed, whatever the billing cycle says. If you hold one of those, the billing frequency is telling you one story and the termination clause another, and the termination clause is the one that governs.
How to read the clause in your own contract
The relevant wording is usually in a clause headed Term, Term and Termination, or Duration, and it is typically one sentence built from the same parts every time. Something close to: this agreement shall continue for an initial term of twelve months and shall automatically renew for successive periods of twelve months unless either party gives not less than ninety days written notice prior to the end of the then-current term.
Pull five things out of it and you have everything you need:
- The initial term, and the date it started - usually the effective date or the service commencement date, which is not always the date you signed
- The renewal term: the length of each successive period, which is what you are actually exposed to
- The notice period, and whether it is counted from the end of the current term or from some other anchor
- The method of notice: email to a named address, a portal request, or written notice to a registered office, and whether email is expressly excluded
- When termination takes effect - almost always the end of the current term, not the date you serve notice
That last point catches people out regularly. Serving valid notice does not stop the service or the billing immediately. It stops the next rollover. You keep the software, and keep paying for it, until the current term runs out.
How to get out of one
The mechanics are the same every time, and the hard part is arithmetic rather than negotiation.
First establish when the current term actually ends. On an evergreen contract this is rarely written down anywhere, because the only date on the document is the original start date. You work it forward: the start date plus however many whole terms have elapsed since. A contract that began on 1 March 2023 on annual renewal is in a term ending 1 March 2027, not 2024. This is the calculated renewal date, and getting it wrong by one cycle is the most common way an otherwise careful exit fails.
Then count the notice period back from that date to get the cancellation deadline. That deadline, not the renewal, is the date that belongs in a calendar and in a reminder. Serve notice in the contractual method before it, keep evidence that you sent it, and ask the vendor to acknowledge receipt in writing. Our guide on serving notice of non-renewal covers the wording and the delivery in detail.
If the deadline has already passed, the position is worse but not always hopeless, and it is worth checking whether the vendor met its own obligations before accepting another term. What to do after a contract has auto-renewed sets out the arguments that are actually available.
Changing the structure at renewal
A renewal conversation is usually treated as a conversation about price. The structure is frequently the more valuable thing to move, and vendors defend it less hard because it does not show up in the number they are measured on.
Three asks are worth more than a small discount on most contracts:
- Convert successive annual terms into monthly rolling after the initial term. This cuts the cost of a future mistake from a year to a month and costs the vendor nothing today.
- Shorten the notice period, or move it to a length that matches the rollover. Ninety days on an annual term is long; thirty is common and reasonable to ask for.
- Require the vendor to notify you a set number of days before each automatic renewal. Many agreements already impose this and it is an easy addition when they do not, because a vendor confident in its product has no reason to object to reminding you.
Get any of it into the order form or a signed amendment. A concession agreed in an email thread, by an account manager who has since moved on, is not a concession you hold.
How to record one so it cannot surprise you
An evergreen contract is only dangerous while it is invisible. Recorded properly it is one of the easier things to manage, because the dates are entirely predictable once you know the structure. For each one, capture the original start or renewal date, the renewal cycle, the notice period, and the fact that it auto-renews. Those four facts produce the cancellation deadline for every future term without anybody maintaining anything.
The reason this is worth doing in a system rather than a spreadsheet is the rollover itself. A stored renewal date goes stale the moment a term rolls, so a spreadsheet quietly starts showing dates in the past while the contract keeps renewing. StackTrackr rolls the date forward automatically, derives the cancellation deadline from the notice period, flags a contract in red once it has entered its notice window, and emails the named owner before the window closes rather than after the invoice arrives. The auto-renew flag is what marks the contracts that need this treatment, and notice periods and the cancellation deadline goes deeper into the arithmetic.
Start with the contracts that roll into long terms, because those carry almost all of the risk. The free Starter plan covers up to ten tools, which is usually enough to protect every annually rolling contract a smaller company holds. Create an account and record the structure of your largest one first.