How to Run a Software Licence Audit: A Step-by-Step Framework

A software licence audit sounds like a compliance exercise, but its real value is financial. Organisations that conduct structured licence audits typically discover 15–30% of their software spend is recoverable — through unused licences, duplicated tools, or over-specified tiers.

Step 1: Build Your Inventory

Start with what you know. Pull a list of every software subscription from your accounts payable records, your IT asset management system, and your SSO provider's connected applications. These three sources will overlap but none will be complete on its own. Deduplicate and tag each tool with its owner, contract end date, and annual cost.

Step 2: Map Users to Licences

For each tool, identify how many licences you've purchased versus how many people are actively using it. Define "active" consistently — we recommend a user who has logged in within the last 60 days. The gap between purchased seats and active users is your first optimisation opportunity.

Step 3: Identify Duplicates

Group your tools by function: communication, project management, file storage, analytics, CRM, and so on. Multiple tools in the same category are candidates for consolidation. Document the user count and annual cost for each.

Step 4: Prioritise by Value at Risk

Sort your optimisation opportunities by annual spend — the largest contracts with the most waste should be addressed first. Create a short list of three to five actions that will deliver the highest return, and assign an owner and deadline to each.

Step 5: Execute and Track Savings

Each prioritised action needs an execution plan: a named owner, a target completion date, and a defined saving. For seat reductions, the saving is the number of seats removed multiplied by the per-seat price. For tier downgrades, it's the cost difference between tiers multiplied by the number of affected users. For cancellations, it's the remaining contract value. Document the baseline (what you're paying before the action) and the target (what you'll pay after), so the realised saving can be calculated when the change takes effect.

Track each action through to completion — not just initiation. A seat reduction request submitted to a vendor is not a saving; a revised invoice confirming the lower seat count is a saving. Many optimisation actions get initiated but not followed through, and the savings never materialise. Assign a tracker column for "saving confirmed" with the date the revised billing took effect.

Making the Audit Repeatable

A licence audit that takes eight weeks of manual effort is unlikely to be repeated annually. The path to a repeatable, lower-effort audit is investing in the infrastructure that makes subsequent cycles faster: a maintained software inventory that doesn't start from zero each time, SSO-connected tools where utilisation data is available on demand, and a contract records system with renewal dates and owners pre-populated.

By the second annual audit, organisations with good underlying data infrastructure can complete the four-step process in days rather than weeks — because the inventory already exists, the utilisation data is already tracked, and the duplicate analysis is a report export rather than a manual exercise. The first audit pays for the system; subsequent audits deliver compounding returns with declining effort.

Vendor Audit vs Internal Audit

A software licence audit conducted by your own team — as described in this framework — is distinct from a vendor-initiated audit. Vendor audits are compliance exercises where the vendor's team reviews your licence entitlements against your actual usage. Internal audits are optimisation exercises where your team proactively identifies savings and right-sizes your estate.

Running regular internal audits serves a dual purpose: it surfaces savings opportunities, and it keeps your records clean enough that if a vendor ever does initiate a compliance audit, your documentation is in order. Organisations that run regular internal audits rarely face significant exposure from vendor audits — because they've already corrected the gaps a vendor would find.