How Many Spare Software Licences Should You Keep?

Unused software licences are not always waste, but an unexplained reserve can become a recurring cost. We explain how to size a licence buffer, test whether it is needed and decide when spare seats should be reassigned or removed.
Treat spare licences as a capacity decision
A software subscription with unassigned seats presents a decision, not an automatic instruction to cut. Those seats might support confirmed starters, a temporary project or a purchasing process that cannot respond quickly. They might also be the remains of an old hiring forecast. The useful question is not simply how many licences are unused, but what each reserve is protecting the business against.
We recommend setting an explicit buffer for each important product rather than applying one spare-seat percentage across all software. A widely used collaboration tool and a specialist design application have different demand patterns and consequences of delay. This article focuses on how much spare capacity to retain after the basic licence inventory is understood, rather than on conducting a complete licence audit.
Separate available capacity from removable cost
Start with three figures for the relevant subscription: purchased seats, assigned seats and seats genuinely available for reassignment. Record the contract term and the next opportunity to reduce the purchased quantity alongside them. An available seat is operational capacity; it is not necessarily an expense you can remove today. Unassigning a user and changing the commercial commitment are separate actions.
Microsoft’s licence-assignment guidance illustrates why this distinction matters. It describes assigning and unassigning Microsoft 365 licences, while noting that some subscriptions have limited cancellation windows. It also explains that the licence view can aggregate seats across subscriptions for the same product. Check the underlying subscriptions before treating a single total as one flexible pool.
Build a small decision record showing the product, subscription, available seats, restrictions on reuse, reduction opportunity and person authorised to approve a change. Do not assume that every licence can be transferred freely between people, entities or locations. Where the entitlement is unclear, verify the applicable terms before counting the seat as usable reserve.
Estimate demand over the actual purchasing lead time
The buffer should cover a defined period of uncertainty. Find out how long it actually takes to provide an additional working licence, including internal approval, supplier processing, assignment and any setup. If seats can be added promptly through an authorised process, a large paid reserve may have little operational value. If procurement takes longer, spare capacity may prevent a genuine interruption.
Ask team managers for confirmed starters, planned contractors and temporary project requirements within that lead time. Separate approved demand from possible hiring. Ask which roles need the product immediately and which can begin with another approved tool. A broad headcount forecast is not enough: a new employee does not necessarily require every application in the catalogue.
Include expected releases from leavers or completed projects, but mark them as uncertain until IT confirms when reassignment is safe and permitted. A departure date alone does not establish availability. Data handling, handover and service dependencies may affect the timing. Match demand and releases by date rather than subtracting one annual total from another.
Compare the cost of readiness with the cost of waiting
For each product, compare a few practical options: retain a small reserve, purchase only when demand is confirmed, or use a permitted short-term arrangement for uncertain demand. Compare them over the same planning period. Include the cost of unused seats, internal purchasing effort, any contractual minimums and the consequences of delayed access. Use your actual terms rather than public headline pricing.
Ask a concrete question: if a confirmed starter cannot access this application on their first day, what work stops, and what approved alternative exists? For a specialist role, the interruption may justify a reserve. For occasional access to a non-essential tool, waiting may be acceptable. Record the consequence in operational terms instead of inventing a financial value for every hour of inconvenience.
The FinOps Foundation’s framework emphasises business value and collaboration between technology, finance and business teams. Applied here, that means neither Finance nor IT should set the buffer alone. Finance checks the commercial exposure, IT validates provisioning and dependencies, and the business owner confirms whether readiness is worth paying for.
Give the buffer a ceiling and an expiry date
Turn the decision into a short rule that people can use. For example, reserve seats only for approved near-term starters and a separately justified contingency, with any increase requiring the application owner’s approval. The exact allowance should follow your demand and lead-time evidence; there is no universal correct quantity.
Name an owner and set a review date linked to the demand window and the next contractual reduction opportunity. Record why each reserve exists and when that reason expires. If a project is cancelled or recruitment pauses, the justification should not survive automatically. Equally, an exhausted buffer should trigger a demand review, not an automatic purchase that permanently raises the baseline.
Keep exceptions visible. A critical application may need a different approach from ordinary office software, but the exception should state the operational reason and approving person. This prevents temporary caution becoming an indefinite commitment that nobody is willing to question.
Use reminders where the review process breaks down
A shared record and a regular review may be sufficient. Automation becomes useful when licence exports, staffing changes and purchasing records repeatedly fall out of step. A narrow workflow could flag when spare capacity exceeds the approved ceiling, a reserve justification expires or a reduction deadline approaches. The useful output is a decision request with supporting evidence, not another dashboard.
Keep purchasing and removal decisions under human approval. An alert should distinguish between purchased, assigned and commercially removable seats, and identify stale or missing data. Do not automatically revoke access because a buffer appears too large. The workflow should also have an owner who handles failed imports and unanswered requests; otherwise it only moves the administrative gap.
Test the policy against the next real change
Start with one product where spare seats are visible and demand can be checked. Record the proposed buffer, evidence, approval and next review date. After the next starter, departure or project change, ask whether access arrived when needed, whether the reserve was used and whether buying additional seats required avoidable effort. Adjust the policy using those observations.
Judge the result on both cost and readiness. A smaller reserve is not an improvement if it causes repeated disruption, and a smooth onboarding process does not prove every unused seat is justified. Where a reduction is approved, check the resulting subscription quantity and invoice separately; a policy change alone does not demonstrate a lower bill.
We can help structure this decision around your contracts, provisioning process and operational needs. Request a free 30-minute IT cost conversation through our form. We will confirm a suitable time with you personally. The introductory conversation is for clarifying the situation and a useful next step, not a complete licence audit.
Frequently asked questions
Are unassigned software licences always waste?
No. They may cover approved demand or a genuine purchasing delay. Each reserve should have a documented purpose, an owner and a review date.
Does unassigning a licence reduce the bill?
Not necessarily. Unassignment may release capacity for reuse without changing the purchased quantity. Check your subscription terms and reduction window.
Should we keep the same buffer for every application?
No. Base each buffer on demand, provisioning lead time, contractual flexibility and the operational effect of delayed access.
Sources and further reading
Related practical guides
- Software Licence Review: Reconcile Use, Rights and Renewals
- Annual or Monthly SaaS Billing? Price the Flexibility
Discuss the next step
Explore the relevant Petatec service. Request a free 30-minute introductory conversation. We will confirm a suitable time with you. This introductory conversation is not a full audit.
Reduce IT spend without making support worse.
Petatec reviews licences, suppliers, infrastructure and support models to cut avoidable spend while keeping business-critical systems stable.
We will confirm a suitable time with you.
Related Articles

Should You Downgrade Premium Software Licences?
A premium licence may be lightly used yet still support an essential control or occasional task. We explain how to test a lower tier for a defined group without confusing low activity with low business value.

Duplicate Software Subscriptions: Merge or Keep Separate?
Two subscriptions for the same software are not necessarily two purchases of the same thing. Before merging them, check billing commitments, licence rights, administrative boundaries and the cost of making the change.

Can You Reuse Software Licences Before Buying More?
An unused software seat is not automatically available to another team. We explain how to check transfer rights, subscription boundaries, operational dependencies and purchase timing before deciding whether to reuse licences or buy more.