Software licence counts can drift away from the people who actually need them. New starters receive access, leavers retain assigned seats, temporary users disappear from view and a client eventually reaches a renewal or capacity limit without a reliable picture of what is in use. For a small MSP, the useful task is not simply reducing the number. It is reconciling assignments against authorised users and current business requirements so the client can make an informed licensing decision.
Start with the provider's current assignment record
Use the relevant administration platform to establish which seats are assigned and which are unallocated. Treat this as the technical starting point rather than proof that every assignment remains justified. A licence can be correctly assigned in the platform while belonging to a user who no longer needs the service.
Match seats to the client's current user context
Compare assignments with the client information the MSP is authorised to use, including known starters, leavers and role changes. Do not infer that an unfamiliar account is unnecessary merely because its purpose is not obvious. Service accounts, shared functions or specialist users may require confirmation from the client.
Separate licence assignment from access review
Licence reconciliation can reveal an account that deserves further access review, but it should not silently become a permission-removal exercise. Follow the client's agreed offboarding and access processes where a user account itself needs changing. The licensing task is to establish whether the paid entitlement remains appropriately allocated.
Identify inactive-looking seats carefully
Usage information can help raise questions, but low activity does not automatically mean a licence is redundant. Some users need a service intermittently or for a specific business process. Present uncertain cases to the appropriate client owner instead of removing access from usage data alone.
Make renewal decisions visible to the client
Before a renewal or quantity change, provide the client with a clear view of confirmed assignments, unallocated seats and unresolved cases. Commercial decisions about reducing or increasing quantities should follow the agreed client-authority route rather than being made implicitly by a technician cleaning up the console.
Record removals and reassignments
When a seat is removed or moved to another authorised user, keep an appropriate operational record. This helps explain later why the licence position changed and avoids another technician interpreting a deliberate reduction as a platform fault.
Check connected subscriptions rather than assuming one-to-one licensing
Some products have bundles, add-ons or dependencies. Reconcile according to the actual service arrangement rather than assuming every visible licence behaves independently. If the commercial or technical relationship is unclear, confirm it through reliable provider or client information before recommending a change.
Turn reconciliation into periodic housekeeping
A lightweight review at sensible business points can prevent years of accumulated uncertainty. This topic is distinct from general user-access reviews and starter/leaver processing because it focuses specifically on aligning paid software entitlements with confirmed current need while preserving the client's authority over commercial licensing decisions.