
What Is an Evergreen Contract? Definition, Risks, and How to Exit One
What is an evergreen contract?
An evergreen contract is an agreement that renews automatically at the end of each term, or simply keeps running, until one party gives advance notice to end it. It has no final end date: either it runs for an indefinite period from the start, or it rolls into a new period each time the current one expires, with no limit on how many times that can happen. The clause that creates this effect is usually called an evergreen clause, and in everyday use it overlaps heavily with an "automatic renewal" or "rollover" clause.
The defining feature is that doing nothing keeps the contract alive. A fixed-term contract ends unless the parties act to extend it. An evergreen contract continues unless a party acts to end it. That flip in the default is what makes evergreen terms convenient for stable relationships and expensive for forgotten ones.
Evergreen structures are common in software subscriptions, facilities and maintenance services, equipment leases, property leases that roll into month-to-month terms, staffing and outsourcing agreements, distribution arrangements, and supply contracts. If you have ever found a vendor invoice for a service nobody remembers approving this year, it was probably an evergreen contract doing exactly what it was drafted to do.
This guide explains how evergreen contracts differ from other term structures, the trade-offs for each side, how to get out of one cleanly, and how to find the evergreen contracts already sitting in your portfolio. For the clause-level negotiation positions (notice windows, price caps, reminder duties), see our companion guide to auto-renewal clauses.
Evergreen vs auto-renewal vs fixed-term
Three structures cover almost every commercial contract. The practical difference is what happens at the end of a period if nobody does anything.
| Structure | How it works | What happens if nobody acts | Where you usually see it |
|---|---|---|---|
| Fixed-term | Runs for a defined period, such as 24 months, then ends | The contract expires. Any continuation needs a new agreement or a signed extension | Projects, one-off services, many enterprise licences |
| Fixed term with auto-renewal | Runs for a defined period, then renews for one further defined term unless notice is given before a deadline | It renews for another term, then the same question comes up again at the next boundary | SaaS, support and maintenance, leases |
| Evergreen | No end date, or rolls over indefinitely period by period until terminated | It keeps running, indefinitely | Monthly subscriptions, supply and distribution, staffing, facilities |
The line between the second and third rows is thin. A contract that renews for "successive one-year terms" with no cap on the number of renewals will, in practice, run forever if nobody serves notice. That is why many practitioners describe any uncapped rolling renewal as evergreen. The distinction that actually matters is whether you get a natural decision point: a clear date by which you must choose to continue or exit. Fixed renewal terms give you one every period. Some evergreen contracts, especially those with no fixed term at all, never force the question.
Under English law, courts distinguish between a contract of indefinite duration (no fixed end date, but one the parties expected could be ended someday) and a genuinely perpetual one. In Zaha Hadid Ltd v The Zaha Hadid Foundation [2026] EWCA Civ 192, the Court of Appeal reaffirmed the two-stage test from Winter Garden Theatre: first decide whether the contract is terminable at all, then what notice is reasonable. An indefinite contract with no termination clause will usually be terminable on reasonable notice, assessed at the time notice is given (see the summary by
Mayer Brown
).
Pros and cons for each side
Evergreen terms are not inherently one-sided. They shift effort from renewal to monitoring, and who benefits depends on who is paying attention.
| Supplier or vendor | Customer or buyer | |
|---|---|---|
| Benefits | Predictable revenue, lower churn | No service gap, no yearly re-signing |
| Risks | Disputes; unenforceable without reminders | Paying for unused services; drifting prices |
| What protects you | Clear renewal language, send reminders | Short notice period, price cap, reminders |
Leaving an evergreen contract takes an active step, which is why suppliers see less churn and less re-papering, and why customers risk losing leverage when a notice deadline passes unnoticed. Where a reminder statute applies, a missed reminder can make the renewal unenforceable.
The pattern behind most evergreen disputes is the same: the terms were fine when signed, but nobody diarised the notice deadline. When the customer finally notices the contract, the window has closed and another full period is locked in.
How to exit an evergreen contract
Getting out of an evergreen contract is usually straightforward if you follow the contract's own mechanics precisely, and surprisingly hard if you do not. Courts tend to hold parties to the notice requirements they agreed.
- Find the termination and notice clauses
- Work out the notice deadline
- Check form, channel and addressee
- Serve notice and keep proof
- Diarise the end date and exit tasks
1. Find the termination and notice clauses. Look for the term or duration clause, any renewal clause, the termination clause, and the general notices clause (often near the end). Also check any amendments, order forms, or master agreements that may override them. Our guide to termination clauses covers what these usually contain.
2. Work out the notice deadline. Evergreen contracts normally allow termination either at any time on a set period of notice (for example, "either party may terminate on 90 days' written notice") or only at the end of a renewal period, with notice given a set number of days before. The second form is the one that catches people: miss the window by a day and you are committed for another full period.
Serve notice the way the contract requires
3. Check the form, channel and addressee. Many contracts require notice in writing, sent to a named address or person, sometimes by a specified method such as recorded delivery. Some exclude email. Notice sent the wrong way can be treated as no notice at all.
4. Serve notice and keep proof. State clearly that you are terminating (or not renewing), identify the contract, and state the effective date you believe applies. Keep evidence of delivery.
5. Diarise the end date and the exit tasks. Termination often triggers obligations of its own: data return or deletion, return of equipment, final invoices, transition assistance, and confidentiality duties that survive. Put them on the calendar alongside the end date.
If an evergreen contract has no termination clause at all, you may still be able to end it. Under English law, a contract of indefinite duration is generally terminable on reasonable notice unless it is construed as perpetual, and what counts as reasonable depends on the circumstances when notice is given (see
Goodwin's analysis
). Other legal systems take different approaches. This is general information, not legal advice: take advice on your governing law before relying on an implied right.
The laws that can limit evergreen renewals
For business-to-business contracts, the starting point in most jurisdictions is freedom of contract: if you agreed to an evergreen term, it binds you. A few statutes carve out exceptions, and consumer contracts are regulated much more heavily. Two US examples are frequently relevant in B2B deals.
| Law | Covers | Requires | If ignored |
|---|---|---|---|
| New York General Obligations Law 5-903 | Service, maintenance and repair contracts | Written reminder 15 to 30 days before the notice deadline | Renewal unenforceable against the customer |
| Wisconsin Statute 134.49 | Business services and equipment leases | Disclosure at signing, reminder for renewals over one year | Renewal provision unenforceable |
The New York rule applies to contracts that auto-renew for more than one month and the reminder must call attention to the renewal clause. The Wisconsin reminder is due 15 to 60 days before the customer's deadline to decline.
Outside these statutes, the protections are mostly contractual, which is why the clause itself matters. If your contracts are governed by English law, the implied-notice rule above is the main background protection for contracts with no end date. For negotiating reminder obligations and renewal price caps into the contract, see our guide on auto-renewal clauses.
The portfolio problem: finding the evergreen contracts you already have
Negotiating good evergreen terms on new deals is the easy part. The harder problem is the contracts already signed. Most organizations cannot quickly answer a simple question: which of our contracts roll over automatically, and when is the next notice deadline for each?
The reasons are familiar. Contracts are spread across inboxes, shared drives and departmental folders. Renewal terms are buried in the body of the agreement or in an order form, not in any system field. And evergreen contracts are, by design, the ones nobody has had to touch recently, so they are the least likely to be in anyone's head.
A practical approach:
- Centralize first. Pull every signed agreement into one contract repository. An inventory with gaps gives false comfort.
- Classify the term type. For each contract, record whether it is fixed-term, fixed with auto-renewal, or evergreen.
- Capture the dates that drive decisions. Next renewal date, notice period, and the notice deadline that results. The deadline, not the renewal date, is the date that matters.
- Add the commercial context. Annual value, owner, and counterparty, so you can prioritize the reviews that matter most.
- Review on a schedule. Look at everything with a notice deadline in the next 90 to 120 days, decide keep, renegotiate or exit, and act while you still have leverage.
Our guide to contract renewal management covers the ownership and review process in more depth, and if the inventory is currently a spreadsheet, see our guide to bulk importing legacy contracts.
Worked example: one clause, three outcomes
Consider this clause in a facilities maintenance agreement:
This Agreement shall commence on 1 January 2025 and continue for an initial period of twelve (12) months, and thereafter shall automatically continue for successive periods of twelve (12) months unless either party gives the other not less than ninety (90) days' written notice of termination expiring at the end of the initial period or any subsequent period.
This is an evergreen clause: the renewals are uncapped, so it runs indefinitely. The customer wants out at the end of 2026.
- Notice sent 15 September 2026: on time. Ninety days before 31 December is 2 October, so notice had to arrive by then. It did, so the contract ends on 31 December 2026, provided the notice was in writing and delivered as the notices clause requires.
- Notice sent 20 October 2026: too late for this period. Notice must expire at the end of a period, so the earliest end date is now 31 December 2027. The customer pays for another year.
- Notice sent by email when the notices clause requires post to the registered office: arguably not valid notice at all, depending on the wording. The customer may find itself with another year even though it acted on time.
If the facilities provider were covered by New York GOL 5-903, it would also have had to send its own written reminder 15 to 30 days before the customer's deadline, or it could not enforce the renewal.
The clause and scenarios above are illustrative, to show how evergreen mechanics work in practice. They are not legal advice, and Bind is not a law firm. Notice rules and statutory protections vary by jurisdiction and contract type; have counsel review your specific agreement.
How to do this in Bind
Bind is built for the portfolio problem above: knowing which contracts roll over, and being told in time to decide. Here is how an in-house team would set it up.
- Open Automations in the space
- New automation: what, which documents, when
- On a date: 120 days before End date
- Bind will set Renewal to Review now
Step by step, with the names you will see in Bind:
- Upload your existing contracts. Create a space, for example Customer contracts, click Upload and select all the files. Up to 5,000 files go in one upload: PDF (including scans), Word (.docx), Excel and PowerPoint. Evergreen contracts are usually the oldest ones in the drawer, so include the back catalogue.
- Add the fields that matter. Click Add field and choose AI autofill: for example a Yes/No field "Auto-renews?", a Date field "End date" with the instruction "If it renews automatically, the end of the current term. Leave empty if it runs until terminated.", and a Number field for the notice period in days. Bind reads every contract and fills the values in, with a note quoting the contract.
- Build your evergreen register. Add a table view filtered on Auto-renews? is Yes, and a separate filter for an empty End date to find contracts that run until terminated.
- See what is coming. Add a calendar view Dated by your End date field. Contracts without a date are counted under No date, which is exactly where true evergreen contracts show up.
- Get reminded before the notice deadline. In the space, choose Automations → New automation. Cover the contracts that auto-renew, run it On a date a set number of days before the End date (longer than the notice period), and choose Notify to email the contract's owner through a people field such as Assigned to, or Set a field such as Renewal to Review now and keep a view filtered on it as the team's worklist. Automations are currently in beta.
- Ask when you need a quick answer. In the chat, ask which contracts in the space renew automatically and what their notice clauses say, then open the source contract to confirm before you serve notice.
Query the register from Claude, ChatGPT or a script
The same register answers from outside Bind. With Bind MCP, included on every plan, you can ask Claude or ChatGPT "What is our notice period with Northwind, and by what date must we give notice?" and it reads the contract in Bind and quotes the clause, within your own access. Once procurement decides, a short script can write "Terminate" or "Renew" into a Manual field through the Bind API, a REST API with public documentation, so the register shows what was decided.
Bind's in-house legal users include teams at Atria, listed on Nasdaq Helsinki, and Outdoor Holding, listed on Nasdaq in the US.
Trusted by fast-moving legal teams around the world
See how Bind would work for your team.
Book a demo
