The Universal ITSM Renewal Checklist

A renewal goes well when the work is done before the vendor opens the conversation, and a checklist is how you make sure none of that work is skipped. This is the platform-agnostic list we run on every ITSM renewal, whether the contract sits on ServiceNow, ManageEngine, TOPdesk or anything else: the same disciplines, in the same order, that turn a renewal from a price you are quoted into a number you set.

It pairs with our guide to mid-market and other ITSM platform pricing for the per-vendor detail, and with our complete guide to ITSM renewal negotiation for the reasoning behind each step. Use this as the operational companion to both.

12 to 6 months out: build the runway

Leverage is mostly a function of time. The single biggest predictor of a good renewal is how early you started, because early is what makes a credible alternative believable and a walk-away real. In the year before the date:

• Confirm the exact renewal and notice dates, and diary the auto-renewal cut-off so it cannot pass quietly.
• Pull the current contract: seats or agents, editions or tiers, add-ons, the uplift clause and any True Forward or co-term mechanics.
• Start a usage baseline now, so that at renewal you have months of login and consumption data, not a snapshot.
• Name an internal owner and the stakeholders who must approve the outcome, so the decision does not stall later.

Map: know exactly what you are paying for

You cannot negotiate what you have not measured. Mapping is the reconciliation of contract against reality, and it is where most of the recoverable spend is found before a single rate is discussed:

• List every licensed seat, agent or technician and match it to a person who actually logs in.
• Identify the edition or tier and the specific capability that justifies it; flag any whole-base tier bought for one team.
• Inventory add-ons and modules, and mark anything licensed but never configured. Our cross-platform shelfware reclamation guide covers how to surface this cleanly.
• Confirm the data, integrations and migration cost of leaving, so the switching cost is a known number rather than a vendor talking point.

Benchmark: price the deal against the market

A discount off the vendor's list is not a benchmark. A benchmark is what an organisation of your size and shape actually pays for the same scope:

• Normalise the quote to a per-unit, fully loaded figure so it can be compared like for like.
• Set the per-seat rate, the uplift and the term against comparable deals, the method in how to benchmark a mid-market ITSM contract.
• Decide your target price and your walk-away number before the first call, and write them down.

Leverage and Close: set the terms

With the runway, the map and the benchmark in hand, leverage is simply making the alternative and the timing real, then closing terms that protect you into the next cycle:

• Make at least one alternative credible enough that the incumbent has to compete, not merely renew.
• Negotiate a reconciled baseline, a capped annual uplift, and protection against mid-term increases.
• Align co-terms and the term length to your advantage, not the vendor's fiscal calendar.
• Get the close in writing with the levers locked, then diary the next renewal the day you sign.

When you want the whole sequence run for you, our contract negotiation service works on fixed fee or gainshare, with no fee unless we save you money.

What changes by platform, and what never does

The unit of licensing is the part that changes between platforms, and it is worth naming because it is where the reconciliation actually happens. ServiceNow counts fulfillers and applications; ManageEngine counts technicians across editions; SolarWinds and most mid-market tools count agents; TOPdesk counts operators with free end users. The checklist adapts to whichever applies: in every case you are matching what you license to who genuinely uses it. What never changes is the sequence. Map before you benchmark, benchmark before you leverage, and leverage before you close, because each step supplies the evidence the next one needs.

The mistakes this checklist is designed to prevent

Most renewals that go badly fail in predictable ways, and the checklist exists to catch them. The first is starting late, which collapses leverage because no alternative is credible on a short clock. The second is negotiating on the vendor's number, accepting a discount off list as though it were a benchmark. The third is letting the auto-renewal date pass unnoticed, which surrenders the one moment when the vendor has to compete. The fourth is approaching the table without internal alignment, so that a good outcome stalls in approvals while the deadline closes. Run the list in order and each of these is headed off before it can cost you.

Treat the checklist as a living document on each contract rather than a one-off. The day you sign a renewal is the day you diary the next one and reopen the usage baseline, so that twelve months later you are starting from evidence rather than scrambling for it.

One final discipline ties the checklist together: write everything down. The renewal and notice dates, the reconciled seat list, the benchmark figure, the target and walk-away prices, and the terms you intend to close all belong in a single document that the internal stakeholders have seen before the first vendor call. A renewal that lives in one person's head stalls the moment that person is unavailable or overruled; a renewal that lives on paper survives contact with the vendor and with your own approval chain. The checklist is only as strong as the record you keep of running it.

Frequently asked questions

When should an ITSM renewal start?

Twelve months out for a major contract, six at the latest for a smaller one. The runway is what makes a credible alternative believable and a walk-away real, and leverage is largely a function of how early you began.

What is the most overlooked step in a renewal?

The usage baseline. Starting consumption and login tracking months ahead means that at renewal you negotiate from data rather than a snapshot, and you can prove which seats and modules are genuinely used.

Does this checklist work for any ITSM platform?

Yes. The disciplines are platform-agnostic. The per-unit names change, seats, agents, technicians, operators, but Map, Benchmark, Leverage and Close apply identically across every ITSM vendor.