How to Track Contract Renewals and Notice Periods

A contract gets the most attention on the days it is least dangerous. Two rounds of redlines, a call to settle the liability cap, somebody senior reading the indemnity, then signature, then a PDF into a folder called Contracts. From that moment the agreement runs by itself, and it keeps running whether or not anyone at your company still remembers what it says.

In most of the files I read the clause is clear and was negotiated properly by somebody who understood it. The failure is downstream of the drafting: nobody converted the clause into a date, and nobody gave the date to a person.

What an auto-renewal clause actually says

An automatic renewal clause, sometimes called an evergreen clause, continues an agreement for a further term unless a party gives notice by a stated deadline. Doing nothing is a choice, and the clause decides which way it goes.

The standard wording runs close to this:

1. This Agreement shall remain in force for an initial term of 12 months and shall renew automatically for successive periods of 12 months unless either party gives written notice of non-renewal not less than 90 days prior to the expiry of the then-current term.

Why the notice date is the only date you can act on

Here is how the failure actually plays out, and it is almost always the same story.

The agreement is signed in March 2026. Signing day is about the discount, so nobody diaries anything. In the last week of March 2027 somebody in finance queries an invoice for a new term nobody remembers approving, opens the contract for the first time since signature, and finds that the window closed on 31 December. The decision was taken by silence, 3 months before anyone looked.

Nothing then rescues you. The company pays for another 12 months of something it had decided to leave, or negotiates an exit from a position of no leverage at all, having already demonstrated that it was not watching.

The fix is arithmetic, not law. Expiry date minus notice period, recorded as its own field, with its own owner. That single subtraction, applied across a portfolio of agreements, recovers more money than most redlining exercises, and it takes an afternoon rather than a negotiation.

Does Indian law give you any relief?

Short answer: no, and it is worth being clear about why.

A commercial agreement between 2 businesses in India is governed by what the parties agreed. Freedom of contract is the starting position under the Indian Contract Act 1872, and there is no general statute that overrides a renewal or notice mechanism 2 companies negotiated at arm’s length. A court asked to relieve a company of a clause it accepted with its eyes open will want to know what was unfair about the bargain, not merely that the deadline was inconvenient to remember.

That is different from the consumer position in several jurisdictions abroad, where automatic renewal in consumer subscriptions is regulated by statute. Business-to-business agreements in India carry no equivalent general protection. The clause is the rule.

There is one practical point that is worth more than any argument about enforceability: check how the clause requires notice to be given. Most notice clauses specify writing, a named recipient, a registered address, and a delivery method, often courier or registered post, sometimes email to a designated address. An email to your account manager is friendly, and it is frequently not valid notice under the contract. Companies do occasionally give notice in time and still renew, because they gave it to the wrong person in the wrong form.

When the notice date arrives, follow the notice clause exactly, and keep proof of delivery.

The six dates in a contract that need tracking

Once you look for dates that require action rather than dates that merely occur, most commercial agreements hold 5 or 6.

The notice date. Expiry minus the notice window. The most valuable date in the document and the one least likely to be recorded anywhere.

The date a right becomes available. Termination for convenience is often drafted so it cannot be used during an initial commitment: no exit in the first 12 months, then 60 days’ notice at any time. Month 13 is when your position changes. Nobody diaries the beginning of a right, only the end of one. The same shape appears in leases with a lock-in.

The date a right expires. Audit rights, inspection rights, price-match and most-favoured-customer protections, options to extend, rights of first refusal. Negotiated hard, then quietly lapsed. An audit right never exercised across a 3-year term was a concession the vendor gave you for nothing.

Escalation and review dates. Fees rise on an anniversary, or on an index, or on notice from the supplier, and the clause usually caps the increase and requires it to be notified within a window. An escalation invoiced outside that window, or above the permitted percentage, is a straightforward overcharge, visible only to somebody holding the clause and the invoice at the same time.

Recurring obligation dates. What your side promised to do on a schedule: certificates of insurance, compliance confirmations, quarterly reports, security questionnaires, usage statements. These get performed in year 1 and forgotten by year 3, and they are the first thing a counterparty’s lawyer lists when a relationship turns adversarial.

The expiry date. Worth recording, mainly so the notice date can be calculated from it, and so somebody knows when the service actually stops.

Read any live agreement against those 6 headings. Most companies find between 4 and 9 real dates in a contract they had recorded as having one.

The obligations that have no date until something happens

There is a harder category, and it is why a register built purely from dates will still miss things.

Some obligations are triggered by events rather than by the calendar. Notify the counterparty within 30 days of a change of control. Inform the licensor if user numbers cross a threshold. Report a security incident within 72 hours of becoming aware of it. Maintain a stated level of insurance throughout the term. Give notice if a key person leaves the account.

None of these has a date until something happens, and by then the clock is already running, usually short. The company that raises a round in March and discovers in November that 4 agreements required notice of a change in shareholding is not in breach because it was careless. It is in breach because the obligation lived in a document nobody read at the moment it became relevant.

You cannot diary these. You can extract them once per contract into a short list phrased as triggers: if X happens, we owe Y within Z days. Keep that list where the people who cause the triggers will see it, which usually means finance, HR and whoever runs security, not the legal folder. It is one page, and it is worth more than the register.

What a contract register should contain

A register earns its place when every row answers one question: what happens if we do nothing?

That phrasing does more work than it looks like it should. It turns an inventory into a decision list. “Renews for 12 months at ₹18 lakh unless we write by 31 December” is a row somebody acts on. “Expiry 31 March 2027” is a row nobody has ever acted on, because it does not say anything is required.

Six fields are enough:

1. The counterparty, and one line on what the contract is for

2. The annual value, so the list sorts by what is at stake

3. The expiry date and the notice period in days

4. The notice date, calculated, in its own column

5. What happens if nobody acts, in one sentence

6. A named person, not a department

Everything else is decoration. I have seen 30-column registers with a status field, a risk rating, a colour code and a governance owner, in companies that could not tell me which agreement renewed next. Six fields, honestly filled in for the 20 agreements that matter, beat a complete register nobody maintains.

Who owns the date, and why it should not be a department

The most common failure in an otherwise good register is an owner column reading “Procurement” or “Legal” or “Ops”.

Whoever negotiated a 3-year agreement has roughly an even chance of not being in the role when the notice date arrives. That is not a criticism of anyone, it is what 3 years does to an org chart. When the diary entry sits in the calendar of the person who signed, it leaves when they do, and the memory of why the clause mattered leaves with it.

Two habits fix it, both free. Put the notice date in a shared company calendar rather than an individual one, with the contract name in the title, and set the reminder 30 days before the notice date rather than on it, because leaving a vendor is not a decision anyone makes on the morning of a deadline. And review the owner column whenever people change roles, in the same conversation as every other handover.

A reminder that fires 30 days early, in a calendar the whole team can see, prevents most of what contract management systems are sold to prevent.

Do you need contract management software?

Not at first, and it is worth being honest about where the line falls.

A spreadsheet is genuinely enough while 2 things hold: the person maintaining it is the person reading the contracts, and every new signature triggers a recalculation. Under about 20 live agreements, with one owner who cares, a spreadsheet outperforms most software, because the maintenance is small and the person doing it understands what the rows mean.

It stops being enough when those 2 things separate. And the failure mode is unpleasant, because the register does not go wrong all at once. It goes stale in one corner, invisibly, since a missing row looks exactly like a contract with nothing due. Nobody discovers a stale register. They discover an invoice.

That is the problem the firm’s client portal was built to remove, and it is why we launched it this month. Every agreement we hold for a client carries its expiry and its notice period; the portal computes the notice date rather than asking anyone to remember to; and it marks a notice window once it has closed, which is the state most worth surfacing and the one a spreadsheet will never volunteer. Clients see it beside their documents, their compliance register and their open requests, at app.standinglawyers.com.

The software is not the insight, and it would be dishonest to write this note as though it were. Everything above works in a spreadsheet, and a company that does the afternoon’s work properly is in a better position than one that has bought a system and filled it with expiry dates. A tool only removes the maintenance.

How to build the register this afternoon

Do not start with a tool, and do not start with all of your contracts.

Pull the 20 agreements with the largest annual value. In most companies under 200 people those 20 carry well over 80 per cent of committed spend, and the tail is small subscriptions where a missed renewal costs a month’s fee rather than a year’s.

For each one, find 4 things: the end of the term, the notice period, whether renewal is automatic or needs positive agreement, and any escalation clause. They sit in the clauses headed Term, Renewal, Termination and Fees, usually in the first 3 pages and the schedule. Then do the subtraction, write the one-sentence consequence, and put a name against it.

That is 6 columns and 20 rows, finishable between lunch and the end of the day. The output is not a document. It is a short list of dates in the next 12 months on which somebody has to decide something, which most companies have never seen written down.

Expect 2 discoveries on the first pass, because almost everyone has them. At least one agreement will have a notice window that has already closed for the coming renewal, which is better known now than in the week the invoice lands. And at least one will have renewed without a decision ever being taken, which tells you what the register is worth before you have finished building it.

Questions people ask

What is the difference between the expiry date and the notice date? The expiry date is when the term ends. The notice date is the last day you can prevent it renewing, and it falls earlier by the length of the notice period. A contract expiring on 31 March with a 90-day notice period has a notice date of 31 December.

Are auto-renewal clauses enforceable in India? Between businesses, yes, as a matter of ordinary contract. Indian law gives commercial parties freedom to agree renewal and notice mechanics, and there is no general statute overriding a term 2 companies negotiated at arm’s length.

How do I give notice of non-renewal correctly? Follow the notice clause exactly: the form it requires, the named recipient, the registered address, and the delivery method. Keep proof of delivery. Notice given in time but in the wrong form has failed.

What if the notice window has already closed? The renewal is likely binding, so the useful question moves on: what does the contract allow next. Look for a termination-for-convenience right in the renewed term, an exit payment that tapers, or a commercial conversation opened early rather than at the following renewal. Diary the next notice date the same day.

How many contracts before a spreadsheet stops working? Less about the count than about ownership. It stops working when the person maintaining the register is no longer the person reading the contracts, or when new signatures stop triggering an update. That commonly happens somewhere past 20 live agreements.