How to Reclaim Inactive ITSM Seats

Reclaiming inactive ITSM seats means finding the licensed accounts that have gone dormant, recovering them through a process that will not break anyone's work, and turning the recovered count into a smaller renewal. The saving is real but the timing is contractual: most agreements hold your committed quantity for the term, so reclaimed seats usually translate to a lower number at the next cycle rather than a refund this quarter. That does not make early reclamation pointless. The earlier you find the dormant accounts, the stronger your evidence at renewal and the less room there is for fresh requests to quietly refill the seats you just freed. This method is part of our complete guide to ITSM license optimization.

Define dormancy before you hunt for it

Inactivity is only useful if it is defined the same way every time, so set the rule first: a seat is dormant when its account has performed no meaningful action within a stated window, usually 60 to 90 days. Decide what a meaningful action is, because a login with no follow-on work is not the same as resolving a ticket, and the vendor will exploit any vagueness. Writing the definition down before measuring is what separates a defensible list from an arguable one, and the broader discipline of doing that is covered in how to build ITSM utilization evidence.

Find the accounts the platform already knows about

Most ITSM platforms record last login and last action per user, so the raw signal usually exists; the work is pulling it into one view and reading it honestly. Export the user list with last-activity timestamps, apply your dormancy window, and you have a first candidate list in an afternoon. Be alert to the accounts that look active but are not really yours to count: service accounts, integration users, and shared logins all skew the picture and need flagging rather than reclaiming. The point of this pass is a clean, categorized list, not a snap judgment on each name.

Separate truly dormant from periodic and seasonal

Some accounts go quiet for good reasons. A user who runs a quarterly close, handles a seasonal peak, or covers an occasional on-call rotation will read as dormant in a short window and active in a longer one. Before you move to reclaim, widen the window for the borderline cases and check for a pattern, because reclaiming a seat someone needs twice a year creates a re-provisioning scramble that undoes the goodwill. This is the same care you would apply when distinguishing genuine shelfware from periodic use in how to find ITSM shelfware before your renewal.

Recover the seats without breaking work

Reclamation goes wrong when it surprises people. The safe sequence is to notify the account owner or their manager, allow a short window to object with a reason, deactivate rather than delete first so recovery is reversible, and only then release the seat back to the pool. Keep a record of every step, because the audit trail both protects you internally and becomes evidence externally. Tie the whole flow to your joiner-mover-leaver process so that reclamation stops being a periodic cleanup and becomes the default behavior whenever someone leaves or changes role; the governance side of that is in how to govern ITSM license allocation.

Convert the reclaimed count into a renewal position

A pool of freed seats is leverage only if it reaches the negotiation intact. Hold the reclaimed seats rather than letting them refill, document the count and the dormancy evidence, and bring both to the renewal as the basis for a lower commitment. On platforms with a True Forward mechanic, reclamation also matters for what it prevents: seats you free no longer feed the growth that gets re-billed, a dynamic our ServiceNow pricing 2026 guide works through against ServiceNow's specific terms. Carrying that evidence to the table is core to our buyer-side license optimization work.

Frequently asked questions