How to Map ITSM Entitlements to Actual Usage

Mapping entitlements to usage means placing what you pay for beside what you actually use, line by line, until the gap between the two is visible and counted. The entitlement side comes from the contract: every seat type, module, tier and quantity. The usage side comes from the platform's own telemetry: who logged in, who did meaningful work, which modules were touched. The map is the join between them, and it is the single artifact that turns a vague sense of waste into a defensible number. Everything downstream, from reclamation to the renewal ask, depends on this map being built honestly. It is one of the core methods under our complete guide to ITSM license optimization.

Build the entitlement baseline from the contract

Start on the contract side, because it is the side you control and the side that anchors the money. Translate the order form into a plain list of every charged item: seat types and their quantities, modules, tiers, add-ons and any consumption commitments. Order forms are written to be hard to read in aggregate, so this step is genuine work, not a copy exercise, and it is the same baseline you would assemble in how to run an ITSM license audit. The output is a clean entitlement register where each line names exactly one thing you pay for, ready to receive its usage figure.

Pull the usage side from platform telemetry

The usage data almost always exists; the work is extracting it cleanly and at the right grain. For seats you want last login and last meaningful action per user; for modules, invocation and activity counts; for tiers, evidence that the specific premium feature was actually used. Some of this sits behind admin roles or reporting modules, so confirm access before you promise a timeline. Where a data point genuinely cannot be pulled, record the gap and the proxy you used in its place, because a documented proxy survives scrutiny and a silent assumption does not. The wider standard for sourcing this telemetry defensibly is set out in how to build ITSM utilization evidence.

Join the two on a common key

This is the step teams underestimate. Entitlement and telemetry rarely share a clean identifier out of the box: the contract counts license types while the platform counts users, modules are named differently in the order form than in the console, and tiers may not map one-to-one to a measurable feature. Decide the key deliberately, usually the user or the entitlement line, and resolve the naming mismatches explicitly so every paid item ends up carrying its real usage. A messy join produces a map nobody trusts, while a careful one produces a register where each line reads "you pay for this, here is what was done with it."

Read the gap honestly

With the map built, the gaps fall into clear categories: entitlements provisioned but never used, premium tiers covering features nobody touched, modules billed but dormant, quantities committed well above the active count. Resist the urge to read every gap as pure savings, because some reflect genuine periodic use that a short window hides; widen the window on the borderline cases before you commit to a conclusion. The clean version of the gap is the input to how to quantify ITSM shelfware in dollars, where the unused lines get priced into a number the renewal can act on.

Carry the map into the renewal

A map is leverage only if it reaches the table intact and reproducible. Bring the entitlement register, the usage figures, the window and the method, and let the vendor reproduce the gap from their own system. On platforms with a True Forward mechanic, the map does double duty: it sizes the reduction and shows precisely which growth should and should not be re-billed, a dynamic our ServiceNow pricing 2026 guide works through against ServiceNow's specific terms. Building and defending that map is at the center of our buyer-side license optimization engagements.

Frequently asked questions