How to Run a Continuous ITSM License Review

A continuous ITSM license review is a standing cadence of light checks on seats, modules and tiers against real usage, run on a rhythm rather than as a panicked audit in the weeks before each renewal. The practical shape is three layers: a light monthly check on accounts created and deactivated, a quarterly true-up of tiers and module activity, and a deeper review ninety to a hundred and twenty days before the contract date. Each layer is cheap precisely because the one beneath it has already kept the data clean, so the pre-renewal deep dive becomes a confirmation rather than an excavation. This is how the gains from a one-time clean-up actually survive, and it is the discipline that anchors our complete guide to ITSM license optimization.

Why a one-time audit decays

A single audit, however thorough, captures a moment that is already passing. The day after you finish it, new accounts are provisioned at the default tier, a reorganization orphans a batch of seats, and a project quietly spins up a module that will outlive it. Within a year the estate has drifted back toward the shape you just corrected, and the savings you reported have leaked away unobserved. The fix is not a bigger audit; it is a smaller, repeating one that never lets the gap grow. The full one-time exercise is described in how to run an ITSM license audit, and the continuous review is what keeps its result from decaying.

The monthly layer: catch the deltas

The monthly check is deliberately light. It looks only at what changed: accounts created, accounts deactivated, and any seats that crossed a dormancy threshold. The point is to act while the change is fresh and the context is known, deactivating leavers' seats before they become anonymous line items and questioning new provisioning that defaulted to a premium tier nobody asked for. Because it only handles deltas, the monthly layer takes an hour, not a week, and it is the layer that does most of the real work.

The quarterly layer: true up tiers and modules

Once a quarter, widen the lens to tiers and module usage across the estate. This is where you catch tier drift, the slow tendency for users to accumulate on higher editions than their work justifies, and where dormant modules surface before they harden into permanent line items. A quarter is long enough to smooth out seasonal patterns and short enough that nothing dangerous has had time to compound. This layer also keeps your evidence current, so the standard set out in how to build ITSM utilization evidence is always close to renewal-ready rather than rebuilt from scratch.

The pre-renewal layer: confirm, do not excavate

If the monthly and quarterly layers have done their job, the pre-renewal review is short and confident. You are confirming a clean estate and assembling the evidence pack rather than discovering shelfware you have to scramble to remove before the baseline locks. Starting this layer roughly a quarter ahead of the contract date leaves room to act on anything the quarterly checks flagged but had not yet resolved, and it puts you at the table with current numbers rather than a hurried snapshot.

Give the cadence an owner

The single reason continuous reviews fail is that no one owns them, so they quietly lapse the moment the person who cared about the last renewal moves on. Assign the cadence to a named role with a standing place on the calendar and a simple report that goes somewhere visible. On ServiceNow, where fulfiller licensing and premium add-ons drift faster than most estates, an owned cadence matters even more, a dynamic our ServiceNow pricing 2026 guide reflects. Standing up that cadence, and running it with you until it is self-sustaining, is part of our buyer-side license optimization engagements.

Frequently asked questions