- Unassigned licenses are seats allocated to nobody: the purest waste, invisible to activity-based usage reports.
- They come from bulk purchases sized to projections, departures without reclamation, headcount-based renewals, and duplicate purchasing paths.
- Find them by reconciling three lists: contract entitlements vs console assignments vs actual sign-in activity.
- Prevent them by checking the idle pool before purchases and reclaiming at offboarding, not at renewal.
Unassigned licenses are seats you bought that were never given to a user. Not underused, not shared: assigned to nobody, doing nothing, and billed anyway.
They’re the purest form of software waste, and they’re surprisingly common at every company size, because the moment of purchase and the moment of assignment are handled by different people in different systems. The problem hides well: license counts live in vendor admin consoles nobody audits between renewals, and finance sees an invoice total, not a seat-by-seat assignment report. In License Logic’s interviews with 80 mid-market executives, 50% reported wasting 20% or more of their license spend on unused seats. This article covers how unassigned seats accumulate, how to find them, and how to keep them from coming back.
How do unassigned licenses accumulate?
Four mechanisms produce almost all of them:
- Bulk purchases sized for projectionsA rollout buys seats for the whole department plus growth headroom. The rollout reaches 70% adoption, projections slip, and the headroom seats never get assigned. Enterprise IT teams describe thousands of unassigned seats of a single AI add-on, bought ahead of a rollout that moved slower than the purchase order.
- Departures without reclamationAn employee leaves, their account is disabled in the identity provider, but the license in the vendor’s console stays assigned or floats into an unassigned pool nobody rechecks before buying more.
- True-ups and renewals negotiated on headcount, not usageThe vendor proposes seat counts from your employee number; nobody checks how many current seats are even assigned before agreeing.
- Duplicate purchasing pathsTwo teams buy the same tool separately, each with their own spare capacity. After a merger or fast growth this multiplies: one operations leader described tripled headcount producing overlapping purchases and unmanaged renewals within a year.
Why don’t these show up in usage reports?
Because most usage monitoring starts from activity, and an unassigned seat generates none. A dashboard of “least active users” won’t show a seat with no user at all. SSO sign-in logs, the usual data source, only record people who exist and log in.
That entitlement-versus-usage comparison is where contract data earns its keep: the contract’s line items say what you’re paying per seat, so an unassigned-seat count converts directly into a dollar figure for the renewal conversation.
What does the waste actually cost?
Take a deliberately conservative shape: a 500-person company with 30 SaaS products averaging 5% unassigned seats at a blended $30 per seat per month is paying for 750 ghost seat-months a year before anyone underuses anything. The point isn’t the specific number, it’s that unassigned waste scales with purchasing volume, not with employee behavior, so no amount of user training fixes it. And specialty tools make single seats expensive: buyers in design and engineering tooling describe seats in the hundreds of dollars each, bought one at a time on cards, where even a few orphaned seats are real money.
How do you find unassigned licenses?
Reconcile three lists per vendor, in this order:
Entitlements from the contract
What did you buy? Your contract repository (or the order form, if you’re starting from scratch) gives seat counts and per-seat cost by line item.
Assignments from the vendor console
How many of those seats are allocated to a named user? The gap between steps 1 and 2 is your unassigned pool: immediate, arguable-with-the-vendor waste.
Activity from identity and usage data
Of the assigned seats, who has actually signed in during the last 90 days? The gap between steps 2 and 3 is your inactive pool, the second wave of reclaimable spend. Inactive-user detection across your identity providers automates this pass.
Do this manually once and you’ll find money; the harder part is that the answer decays immediately as people join, leave, and change roles. Keeping the three lists reconciled continuously is a systems problem, the kind a license management platform exists to solve: contracts, assignments, and sign-in activity in one view, per vendor, with the deltas visible.
How do you keep them from coming back?
- Check the unassigned pool before every purchaseMake “do we already own idle seats?” a required step in the intake form for new software requests.
- Reclaim at offboarding, not at renewalTie license reclamation to the departure checklist, when the account is disabled, rather than discovering the pile eleven months later.
- Right-size at renewal with data in handA renewal alert 90 days out gives you time to pull the entitlement-assignment-activity comparison and negotiate the seat count down from evidence. Surprise renewals kill this: half the executives we interviewed reported them, and an auto-renewal that fires unnoticed locks in the ghost seats for another year.
- Watch the growth-mode failureFast-growing teams overbuy on purpose (“we’ll grow into it”). Fine, but date-stamp the assumption and revisit it at 90 days, or the headroom quietly becomes the baseline.
The pattern across all four: unassigned licenses are a coordination failure between purchasing, IT, and the vendor console. Fix the coordination, one system that sees contracts, renewals, and usage together, and the ghost seats stop regenerating. For the broader playbook, see our guide to reducing SaaS costs.
License Logic puts contract entitlements, console assignments, and real sign-in activity in one view per vendor, so unassigned and inactive seats surface as reclaimable spend, with the renewal alert timed to act on it.
Frequently asked questions
What’s the difference between an unassigned license and an unused license?
An unassigned license has no user attached at all; it sits in the vendor’s admin console as purchased-but-unallocated. An unused (inactive) license is assigned to someone who doesn’t sign in. Both waste money, but unassigned seats never show up in usage reports because there’s no activity to measure.
Why doesn’t our usage dashboard show unassigned seats?
Usage dashboards start from activity data (sign-ins, sessions), and an unassigned seat produces none. You find unassigned seats by comparing what the contract says you bought against what the admin console says is allocated. That’s an entitlement comparison, not a usage report.
How often should we audit license assignments?
Continuously for your top ten vendors by spend, and at minimum 90 days before each renewal so the findings arrive while you can still change the seat count. A one-time audit finds money once; the pool regenerates with every departure and bulk purchase.
Can we get money back for unassigned seats mid-contract?
Usually not mid-term; most SaaS agreements bill committed seats regardless of assignment. The leverage moment is renewal: bring the entitlement-versus-assignment gap to the negotiation and right-size the count. That’s why renewal alerts and the audit need to be connected.
Who should own license reclamation?
IT executes it (they control the consoles and the offboarding checklist), finance audits it (they see the invoices). It works when reclamation is a standing step in offboarding and procurement intake, not a quarterly cleanup project.