Evergreen contract: managing agreements that renew themselves

An evergreen contract is an agreement that renews automatically at the end of each term unless one party gives notice within a set window. Software subscriptions, maintenance agreements, leases for equipment and many service contracts work this way. The clause itself is ordinary; the cost comes from missed notice dates — contracts renewed for another year at a price nobody reviewed, for a service nobody still uses.

How an evergreen contract clause works

• An initial term — commonly one to three years.
• Automatic renewal for successive terms, often of the same length.
• A notice window before the end of each term, such as 60 or 90 days, within which either party may give notice not to renew.
• Sometimes a price adjustment on renewal, tied to an index or the supplier's current list price.
• The required form of notice — in writing, to a named address, sometimes by a specific method.

The date that matters is not the renewal date but the last day to give notice. Track that date, with a reminder well before it, or the contract renews by default.

Contract extension vs automatic renewal

A contract extension is an active decision: both parties agree to continue, often on revised terms, and usually document it in writing. An evergreen renewal is passive: nothing is signed, and the contract simply continues. Extensions give you a natural review point; evergreen clauses remove it, which is exactly why they need a register that creates the review point artificially.

Build a renewal register

1. List every contract with an automatic renewal clause, starting with the largest by annual value.
2. Record the current term end date, the notice period and the calculated last notice date.
3. Record the notice method required by the contract and the address it must go to.
4. Name an owner who decides whether to renew, renegotiate or terminate.
5. Set a reminder at least 30 days before the last notice date — longer for contracts that need a replacement lined up.
6. Record the decision each cycle, including "renew unchanged", so the next review has context.

Ettex Records holds this register with dates, owners and the contract document attached to each row, and date fields make "last notice date in the next 90 days" a filter rather than a calendar search. The notice letter itself can be drafted and sent for signature so the proof of service sits with the contract.

Where evergreen contracts cost money

• Subscriptions renewed for seats or modules no longer used.
• Price uplifts accepted by default because the review point passed unnoticed.
• Services duplicated after a replacement supplier was brought in but the old contract kept renewing.
• Notice given by email when the contract required post, and rejected as invalid.
• Supplier performance problems left unaddressed because the renewal never prompted a supplier scorecard review.

For organisations with many agreements, a renewal register is the first practical step before investing in contract management software; it also exposes which contracts need the stronger service level agreement or exit terms at the next negotiation.