What an evergreen clause is, and how its notice window works

An evergreen clause is wording that makes an agreement continue, usually for another term of the same or a stated length, unless a party gives notice or takes some other required step. It is also called an auto-renewal or automatic renewal clause. The agreement does not end on its term end date by default; it rolls over.

That makes the term end a less useful date than it looks. What matters is the notice window: the period before each renewal in which a party can still stop it. This guide explains how that window works, what to review before trusting a date, and how the fictional sample workspace records it.

Evergreen wording varies a great deal, but most versions answer the same few questions. Reading a clause against this list is a good way to see what it actually says and what it leaves out.

The notice period counts back from the end of the current term. The last day inside the window is the latest notice date. After that date passes, under most evergreen wording, the agreement renews and the next window opens before the next term end.

Here is the arithmetic on the fictional Alder Works retainer. The term ends on 30 September 2027. The original source requires notice at least 60 calendar days before the end of the term, so the latest notice date is 1 August 2027. Amendment A1 later changes the notice period to 90 calendar days, which moves the latest notice date to 2 July 2027. The term end does not change.

1 August 2027 is a Sunday. The sample uses plain calendar-day subtraction with no weekend or holiday adjustment. A real clause that mentions business days, receipt or a specific delivery method must be reviewed, not quietly shifted to the nearest convenient weekday.

The number of days is the easy part. The mistakes come from the words around it.

An evergreen clause does not produce one notice date. It produces one per term. Once a renewal happens, the term end moves forward by the renewal length and the latest notice date moves with it. A spreadsheet that holds last year's notice date is quietly wrong from the day the agreement renews.

The renewal term can also differ from the initial term. An agreement with a three-year initial term might renew for one year at a time, or move to a rolling monthly arrangement with a different notice period. Record the renewal length separately from the initial term, and recalculate the next latest notice date as soon as a renewal is confirmed, not when the next window is nearly closed.

In the sample, the auto-renewal field on the Alder Works record reads 'Not stated' and its state is missing source, because no renewal clause was found in SOW-S1 or Amendment A1. That is a useful result. It prevents the record from inventing a renewal rule the documents do not contain.

What happens to an agreement with no evergreen wording at the end of its term depends on the agreement, the parties' conduct and sometimes the law that applies. That is a question for qualified advice, not for a date field.

The risk with an evergreen clause is not the clause. It is that nobody owns the next window. Each renewal needs a named person, a confirmed rule and an internal reminder far enough ahead of the latest notice date to gather inputs and decide.

In the sample, Northline's internal reminders fall 60, 30, 14, 7 and 1 days before the 2 July 2027 latest notice date. Those reminders go to Maya Okafor, who owns the record. They are internal. They do not notify Alder Works, and marking one done does not mean notice was given.

For a handful of evergreen agreements, a spreadsheet column for the latest notice date and another for the owner may be enough, as long as someone recalculates after every renewal and amendment. Agreedio keeps the clause excerpt, the confirmed rule, who confirmed it and the internal reminders together, and supersedes the reminders when an amendment changes the rule.