How to Track Software Licences: A Practical Guide
An IT software licence tracker is a single register of every piece of software the organisation uses: what it is, who it’s licensed to, when it expires, and what it costs. Without one, licences expire mid-project, the company pays for seats nobody uses, and an audit reveals unlicensed installations. This guide explains how to use the IT Software Licence Tracker properly.
When to Use This
Use the tracker continuously, it’s a living register, not a once-a-year exercise. Add a row every time software is purchased, renewed, or installed; update it when licences are reassigned, upgraded, or retired. The register is most valuable at three moments: renewal time (knowing what’s due and whether you still need it), budget planning (the true annual cost of software), and vendor audits (proof of what you own).
Run a full reconciliation at least twice a year: compare the tracker against what’s actually installed on company machines and against vendor purchase records. The gaps, installed but not recorded, recorded but not installed, paid for but unused, are where the money and the risk are.
Start with what you can verify: purchase receipts, vendor portals, and a scan of installed software. Don’t aim for perfection on day one; an incomplete register that improves beats a perfect one that never gets built.
How to Fill It Out
Section 1: Software details. Product name, vendor, version or edition, and licence type, perpetual, subscription, per-user, per-device, site licence, or open-source (record the licence terms for open-source too, since some carry obligations). Be precise about editions: “Office” could be three different products with three different prices and terms.
Section 2: Licence quantities and assignment. Number of licences purchased, number currently assigned, and to whom or which devices. This is where over- and under-licensing becomes visible. If the tracker says 25 seats purchased and 25 assigned but a machine scan finds 31 installations, you have a compliance problem to fix. Record the assignment so licences freed up by leavers get returned to the pool rather than sitting idle.
Section 3: Dates and costs. Purchase date, start and end of the licence term, renewal date, and annual cost. Set renewal reminders well before the date, at least 30 days, more for enterprise agreements. Auto-renewal clauses catch out many small businesses: know which contracts renew automatically and what the cancellation notice period is, and record both.
Section 4: Vendor and documentation. Vendor contact, account or customer number, and where the proof of purchase lives, invoice, licence key file, vendor portal login. When a vendor audit letter arrives, the first thing they’ll ask for is proof of entitlement. Knowing exactly where it is turns a stressful scramble into a routine lookup.
Section 5: Compliance notes. Any restrictions that matter: can the licence be used on personal devices, is there a geographic restriction, are there limits on virtualisation or concurrent use? Also record the outcome of each reconciliation: date checked, discrepancies found, actions taken.
Common Mistakes
1. Letting leavers keep licences. An employee leaves and their expensive per-user subscription keeps renewing for months. Tie licence recovery into the leaver process: when accounts are deactivated, licences go back to the pool. The savings from this one habit often justify the whole tracker.
2. Ignoring auto-renewals. Contracts quietly renew at full price, sometimes with price increases, because nobody diaried the cancellation window. Record renewal dates and notice periods, and review each renewal actively: do we still use it, do we need this many seats, is there a better-priced tier?
3. Shadow IT. Departments buy their own subscriptions on company cards without telling IT. The tracker only works if purchasing goes through one process. Make the rule simple: no software purchase without a tracker entry, and reconcile company card statements against the register periodically.
4. Confusing users with installations. A licence count of 50 users doesn’t help if 50 installations are on machines of people who left and 10 current staff are unlicensed. Track both dimensions, who’s entitled and what’s installed, and reconcile them. They’re different numbers, and the gap is the risk.
Who Needs to Sign Off
IT owns the tracker day to day. Finance should review it quarterly alongside software spend, they’ll spot unused licences and renewal creep faster than anyone. New purchases above an agreed threshold need the budget holder’s approval before the tracker entry is made. Annual reconciliation results should be reported to management, particularly any compliance gaps found.
How Often to Review and Update
Update the tracker with every purchase, renewal, reassignment, or retirement, it’s a living document. Reconcile installed software against the register at least twice a year. Review renewal dates monthly so nothing lapses or auto-renews unexamined. Review the template itself annually to make sure licence types and fields still cover how you actually buy software (the shift to subscriptions has caught many trackers designed for perpetual licences).
Download the free IT Software Licence Tracker template.
Disclaimer: software licensing terms are contractual and vary by vendor; licence compliance disputes can carry significant penalties. This guide is general information, not legal advice. Check your agreements and consider professional advice if a compliance gap is found.