TL;DR
An auto-renewal is not automatically bad; an unmanaged renewal is.
The control problem is usually missing dates, unclear ownership, fragmented spend data or a decision that starts after the notice window has closed.
Build one renewal record, assign one accountable owner and make the decision before negotiation becomes urgent.
Measure your own portfolio rather than relying on generic leakage benchmarks.
What is a contract auto-renewal?
An auto-renewal clause allows an agreement to continue for another term unless one party gives notice in the way and within the period specified by the contract. The clause can preserve continuity, but it also creates a control point: somebody must know the notice requirement, review the supplier and make a deliberate decision before the option disappears.
The procurement risk is therefore not simply that a contract renews. It is that the organisation renews by accident, without checking demand, performance, price, risk, alternatives or contractual leverage.
Why renewals become uncontrolled
The contract is hard to find. The signed agreement, amendments and commercial schedules sit in different systems or inboxes.
The notice date is not recorded. Teams track the end date but miss the earlier date by which notice must be served.
Ownership is ambiguous. Procurement, legal, finance and the business each assume somebody else is leading the decision.
Spend and usage are disconnected. The owner cannot see invoices, licences, consumption or related agreements in one place.
The review starts too late. The team discovers the renewal when its negotiating options are already constrained.
The minimum renewal record
Each renewable agreement should have one maintained record containing:
supplier and contract name;
business owner and procurement owner;
current term, expiry date and notice requirement;
renewal mechanism and the next decision point;
current commercial commitment and the source used to verify it;
usage, performance and open-risk information;
linked amendments, statements of work and related agreements;
decision status, required approvers and evidence supporting the decision.
The record is only useful when a named person is responsible for keeping it current. A repository without ownership becomes another place to store stale information.
A practical renewal-control workflow
1. Establish the record
Confirm that the signed contract and every amendment are present. Extract the renewal and termination language from the executed documents, not from a spreadsheet copied from an earlier version.
2. Assign accountability
Name the person accountable for the commercial decision. Procurement may run the process, but the business owner should confirm whether the requirement still exists and whether the supplier is delivering the intended outcome.
3. Review the evidence
Bring together contractual terms, spend, usage, supplier performance, incidents, risk, stakeholder feedback and viable alternatives. Record where each piece of evidence came from.
4. Choose an explicit route
The decision should be one of four things: renew as agreed, renegotiate, replace or exit. “Do nothing” should not be treated as a fifth option when doing nothing causes a renewal.
5. Execute and document
Serve any notice using the method required by the agreement. Record approvals, negotiation decisions and the final signed change. Then create the next control point immediately.
Questions to answer before renewing
Do we still need the product or service?
Which agreement and amendments govern the renewal?
What must happen, and by when, to preserve our options?
Who uses the service, and what evidence shows that it is delivering value?
Has the supplier met its obligations and resolved material issues?
Has the requirement, risk profile or market changed?
What is our realistic alternative if the negotiation fails?
Which technology can help?
A controlled spreadsheet can work for a small, stable portfolio if access, ownership and review are disciplined. As volume and complexity increase, teams may need a contract repository, CLM platform, SaaS-management tool, procurement intake workflow or an integration with finance and identity systems.
Technology should improve the control model rather than replace it. Ask how a product captures notice language, handles amendments, assigns owners, connects spend and usage, records evidence, escalates exceptions and proves that alerts were acted on.
For potential technology routes, use the AI contract management vendor landscape, then apply the WOP procurement-software evaluation guide. A vendor's presence in a landscape is not a recommendation; validate fit against your own process and evidence.
Metrics worth building from your own data
share of active contracts with a verified notice requirement;
share with an accountable business owner;
renewal decisions completed before the contractual notice point;
renewals supported by usage, performance and spend evidence;
unplanned renewals and the reason each control failed;
time from review start to signed decision.
These are measurement definitions, not external benchmarks. Establish a baseline from your own portfolio and improve it over time.
FAQ
Are auto-renewal clauses always bad?
No. They can preserve service continuity. The risk appears when the organisation cannot see the clause, assign ownership or make a timely decision.
Who should own a renewal?
The business owner should be accountable for the continuing requirement and outcome. Procurement can coordinate commercial review and negotiation; legal should advise on interpretation and notice where needed.
Is an expiry-date alert enough?
No. The important control point is usually the contractual notice requirement, which may occur before expiry. The alert must also reach a named owner and trigger a defined workflow.
Should AI extract renewal dates?
AI can assist with extraction and review, but material dates and notice requirements should be verified against the executed contract. The system should preserve the source clause and an audit trail.
Evidence note
This guide deliberately avoids generic claims about average renewal loss, sector miss rates or software ROI. The previous version contained precise figures without direct source links or adequate methodology, so those figures were removed.