Seven questions to ask before signing another IT renewal
IT renewals have a habit of arriving with less scrutiny than new purchases. The service is already running, the incumbent knows the estate, and the procurement team is busy. The result is often a rolled-over contract with a modest discount and an unchanged set of risks. For UK mid-market and public-sector buyers, renewal season is precisely the moment to test whether the contract still serves the organisation.
The questions below are not a substitute for legal or commercial advice. They are a practical checklist for leaders who need to challenge the renewal before signature. Each question includes a common red flag and a negotiation prompt.
1. What exactly are we buying now, and what has changed since signature?
Contracts age. Volumes fall, departments merge, cloud consumption replaces fixed licences, and new services are added through change requests. A renewal should begin with a current service and consumption baseline, not last year's contract schedule.
Red flag: the supplier presents a like-for-like renewal without a usage review, or the schedule includes modules that are no longer used.
Negotiation prompt: ask for a line-by-line schedule mapped to current business owners, volumes and service levels. Remove dormant services or convert them to a lower-cost tier before discussing price.
2. Which costs are fixed, variable and index-linked?
A headline percentage increase can hide a great deal. The important question is which elements are fixed, which are consumption-based and which are subject to an index. In the UK, CPI-linked or RPI-linked clauses can compound significantly over a multi-year term.
Red flag: an open-ended indexation clause with no cap, or a consumption model that makes forecasting impossible.
Negotiation prompt: seek a capped indexation mechanism, a fixed price for the first renewal term, and clear thresholds for any consumption uplift. Ask for a worked example of the cost at expected and high usage.
3. Do service credits actually bite?
Service credits are often presented as a protection. In practice, they may be capped at a small percentage of monthly charges, excluded for dependencies, or triggered only after repeated failures. A credit that never triggers is not a risk control.
Red flag: credits that require the buyer to prove causation, or exclusions that cover most of the service chain.
Negotiation prompt: ask for the last twelve months of service reporting and credit calculations. Seek clearer triggers, a meaningful cap and a right to escalate or terminate after repeated failures.
4. What happens at exit?
Exit is usually the least discussed part of a renewal and the most expensive to discover late. The contract should set out termination assistance, transition services, data extraction, deletion and knowledge transfer.
Red flag: exit assistance is priced at the supplier's discretion, or there is no committed timeframe for data return.
Negotiation prompt: require a priced exit schedule with defined deliverables and timescales. Ask for confirmation that exit assistance will be provided at agreed rates for a defined period after termination.
5. Who owns and can access our data?
Data portability is not only a legal issue. It is an operational one. The buyer should be able to extract data in a usable format, through an API or bulk export, without disproportionate cost. For public-sector bodies, records management and retention obligations add another layer.
Red flag: data is available only in a proprietary format, or export is treated as a professional service with no service level.
Negotiation prompt: specify export formats, frequency, completeness and cost. Ask for a test export before renewal and confirm deletion obligations at exit.
6. How will performance be measured and verified?
A renewal should include a service reporting regime that the buyer can verify. That means agreed metrics, regular reporting, a right to audit or benchmark, and a route to remedy underperformance.
Red flag: reporting is supplier-controlled with no independent verification, or service levels are measured only at the infrastructure layer rather than the business service.
Negotiation prompt: add business-facing measures, a quarterly service review and a right to require improvement plans. For critical services, consider independent assurance.
7. What is the benchmark and the walk-away position?
Before renewing, the organisation should know what the market would charge for a comparable service and what it would do if the supplier refused reasonable terms. That does not require a full competitive tender, but it does require commercial preparation.
Red flag: no market comparison, no internal alternative and a renewal timetable that leaves no time to test the market.
Negotiation prompt: obtain a benchmark or indicative pricing from a comparable framework. Set a walk-away position in advance and make sure the renewal timetable allows for it.
A discipline, not a formality
Renewal season is a commercial checkpoint. The organisations that handle it well do not treat it as an administrative rollover. They use it to confirm scope, test value, reduce lock-in and preserve future options. Seven questions will not resolve every contractual risk, but they will expose the ones that matter before another signature commits the organisation for years.