What to Check in a Contract Before It Auto-Renews

Auto-renewal clauses exist because they favour the vendor. Unless you take deliberate action before a notice deadline, the contract rolls over on its current terms — the price, the scope, the liability caps, and the data processing obligations you agreed to when the business looked different.

A renewal review does not need to be a full legal audit. There are five things that matter most, and most teams can assess all five in under an hour if the contract is easy to find.

Find the exact clause that defines how notice must be given to prevent auto-renewal. Notice requirements vary significantly: some require written notice to a specific email address or legal contact, some require registered mail, and some have very specific timing windows that are easy to miss.

Confirm that your intended method of giving notice actually satisfies the contractual requirement. Sending an email to your account manager may not constitute valid notice if the clause requires written notice to the vendor's legal department. This distinction has cost companies their right to exit.

Many contracts include an automatic price escalation at renewal — a CPI adjustment, a fixed percentage increase, or a move to current list pricing. These are often buried in the payment terms rather than the renewal clause.

Check whether the price you will pay in the next period is the same as the current period. If there is an escalation, calculate the annual impact before your negotiation conversation. A five percent increase on a £60,000 contract is £3,000 per year — worth knowing before you decide whether to renegotiate.

Contracts often define the permitted scope of use: number of users, volume of transactions, geographic limitations, or specific use cases. Check whether your current usage still falls within those limits.

Usage above the contracted scope can create liability or result in true-up invoices at renewal time. If you have grown significantly since signing, a renewal is the right moment to renegotiate scope to reflect actual usage rather than continuing on terms that no longer fit.

If the vendor processes personal data on your behalf, the contract should contain a data processing agreement or equivalent clauses. Check that these still reflect your current obligations — particularly if your business has entered new markets or customer segments since the contract was signed.

Also check whether the vendor's security certifications and sub-processor list are still current. Many vendors update their sub-processor lists without proactively notifying customers. If you have obligations to maintain an accurate processor register, this check is not optional.

Before renewing, confirm what exit looks like. How long does the vendor retain your data after termination? What format is data exported in, and is export self-service or does it require a support request with a lead time? Is there a minimum commitment in the renewal period or can you exit on shorter notice?

Understanding exit terms before you renew is not pessimistic — it is sound commercial practice. A vendor whose exit terms are onerous deserves a harder negotiation at renewal than one who makes offboarding straightforward.

At the 90-day mark, the right conversation with your vendor is not about cancellation — it is about the next period. Ask for a usage review, ask whether there are new pricing structures, and ask what they would offer to retain you for another year. Vendors who know you are informed and engaged consistently offer better renewal terms than vendors who expect passive rollover.

Document the outcome of this conversation in your contract management system regardless of what you decide. A renewal decision that is logged with a rationale is evidence of governance. One that happens by default is a risk that will eventually cost you.