How to Build ITSM Utilization Evidence

Utilization evidence is a documented, sourced record of how every licensed seat, module and tier is actually used, and it is the thing that turns a claim of waste into a number the vendor cannot wave away. You build it by sourcing the right telemetry, defining what meaningful use means in terms you can defend, measuring over a representative window, and assembling it so the vendor could reproduce your figures from their own system. Get that right and the evidence carries the negotiation; get it loose and the vendor picks it apart. This method sits under our complete guide to ITSM license optimization.

Source the telemetry first

Before defining anything, confirm what your platform can actually expose: last login, last meaningful action, and feature-level activity per user and per module. Some of this sits behind admin roles or reporting modules you may not hold, so checking access is the first task, not an afterthought. The detail of getting from raw telemetry to a usable mapping is in how to map ITSM entitlements to actual usage. If a data point genuinely cannot be pulled, document the gap and the proxy you used in its place, because a transparent proxy is defensible and a hidden assumption is not.

Define meaningful use before you measure

The vendor will attack any soft definition, so write yours down first and tie it to their own license terms. Decide what counts as use for each thing you are measuring: for a seat, is it any login, or a resolving action; for a module, a single invocation or sustained activity; for a tier, use of the specific feature that justifies it. The point is not to set the bar low or high but to set it explicitly, so the same rule applies to every record and nobody can claim you moved the line to suit the conclusion.

Choose a representative window

A single month can mislead in either direction, catching a quiet period or a one-off spike. Measure over a window long enough to capture the normal rhythm of the work, usually a full quarter, and note any seasonality that a renewal conversation should account for. State the window in the evidence so the vendor sees you measured the real pattern, not a convenient slice. This is also where you separate the genuinely dormant from the merely periodic, which matters when the same data feeds how to right-size ITSM agent and fulfiller counts.

Assemble the record so it is reproducible

The strongest evidence is the kind the vendor can recreate from their own system and arrive at the same answer. Lay out, per licensed item, the entitlement, the provisioning, the usage figure, the window, and the definition applied. Keep the method visible rather than buried, because a transparent record invites verification and a verified record ends the argument. The moment the vendor reproduces your numbers, the conversation stops being about whether the waste is real and starts being about how it is corrected.

Turn the evidence into a position

Evidence is built to be used. Once assembled, it becomes the spine of the renewal conversation: the priced gaps define the target, and the reproducibility defends it. The discipline of converting the record into a negotiating stance is in how to turn ITSM usage data into renewal leverage. On platforms with a True Forward mechanic the evidence does double duty, both sizing the reduction and showing exactly which growth should and should not be re-billed; our ServiceNow pricing 2026 guide works that through ServiceNow's specific terms.

Keep the evidence current

Utilization evidence has a shelf life. The estate moves, people join and leave, modules switch on and off, so a record built once and filed away is stale by the next renewal. The teams that negotiate well treat evidence as a living artifact, refreshed on a cadence rather than reconstructed in a panic before each cycle. That standing record is also what makes a continuous optimization possible rather than a one-off scramble, and it is the foundation under our buyer-side license optimization work.

Frequently asked questions