Software licenses are the only company assets that can go missing while sitting in plain sight. Nothing is stolen and nothing breaks - the subscription simply renews for twelve seats when seven people still use it, the perpetual key lives in a former employee’s inbox, and finance pays the invoice because cancelling feels riskier than continuing. This guide sets out a license register that actually gets reviewed: what to record per license, how to tie seats to real people and devices, and how to reach renewal dates with a decision instead of a shrug.
What you will learn
- Where license spend leaks
- What to record for every license
- Seats and assignments
- Renewals without surprises
- Keeping the register honest
- Tools that make this easier
- FAQ
Where license spend leaks
License waste rarely looks like waste. It looks like:
- Seats that outlive their users. Someone leaves, their laptop is recovered, their accounts are disabled - but the paid seat in the design tool renews for another year, because disabling an account and reclaiming a seat are different actions and only one of them is on the offboarding checklist.
- Auto-renewal as the default decision. The renewal notice arrives 30 days out, nobody owns the question “do we still need twelve seats?”, and the safest individual action is to do nothing.
- Duplicate tools. Two teams each buy a diagramming tool because neither knew the other had one. Without a single register there is nothing to check before purchasing.
- Lost perpetual licenses. A key bought years ago exists only in one inbox. When the machine is rebuilt, the license is repurchased rather than found.
The common thread: nothing physical disappears, so nothing triggers a search. Only a register that someone actually reviews makes the leak visible.
What to record for every license
A license record has to answer “what are we entitled to, what does it cost, and who is using it”. In practice:
| Field | Why it matters |
|---|---|
| Product and vendor | Answers the “what is this charge?” question on every card statement |
| License type | Subscription, perpetual, per-user, per-device - it changes what “assigned” means |
| Key or agreement reference | The proof of entitlement a vendor audit will ask for |
| Seats purchased vs seats in use | The gap between these two numbers is your waste |
| Cost per period | What one idle seat actually costs per year |
| Renewal date and notice period | The decision deadline is renewal minus notice, not the renewal itself |
| Internal owner | The named person who answers “renew, shrink, or cancel?” |
| Assigned users or devices | Who or what consumes each seat |
Attach the original agreement or order confirmation to the record itself. Proof of entitlement that lives in an inbox leaves the company with that inbox’s owner.
Seats and assignments
Treat a seat the way you would treat a piece of equipment: it is either free or assigned to exactly one named person - or one machine, for per-device licenses. Keeping those assignments in the same register as your hardware pays off three ways:
- Offboarding becomes one list. The view that shows a leaver’s laptop and monitor also shows their seats, so reclamation happens in the same conversation as hardware recovery.
- Per-device entitlements survive rebuilds. A license tied to a workstation belongs on that machine’s record, the same way a scanner carries its own service history - reinstall the machine and the entitlement is still findable.
- New seats become deliberate. When a new hire needs access, that is a request against a register with a known seat count, not a quiet expense-card purchase that creates tool number two.
A unique asset ID per license, just like physical kit, keeps the register quotable: “renew SW-0014” is unambiguous in a way “the Adobe thing” never is.
Renewals without surprises
The date that matters is not the renewal date - it is the cancellation deadline, which lands days or weeks earlier depending on the notice period. Build the habit around that:
- Calendar the deadline, not the renewal. A reminder on the renewal date is a receipt, not a decision point.
- Review monthly. Fifteen minutes on everything renewing in the next 60 to 90 days, with the internal owner of each license in the room or on the thread.
- True the seats down before renewing. Compare seats purchased with seats in use and shrink the gap. Renewal is the one moment vendors expect this conversation.
- Perpetual is not “done”. Perpetual licenses skip renewals but often carry support or maintenance contracts with their own expiry dates - record those too.
Tip: record the notice period on the day you sign, while the contract is open in front of you. Hunting for the cancellation clause three days before auto-renewal is exactly how unused seats survive another year.
Keeping the register honest
A license register decays differently from a hardware one - there is no cupboard to walk past, so drift is invisible. Three small rituals keep it true: reconcile the register against actual invoices and card statements once a year, so unrecorded subscriptions surface; review the leaver’s seats at every offboarding, alongside their kit; and spot-check seats-in-use against vendor admin panels a few times a year, because people who changed roles often keep access nobody is using. Each ritual is short. Skipping all three is how a company ends up paying for software it cannot name.
Tools that make this easier
A spreadsheet can hold every column above, and most license registers start as one tab in the IT workbook. The failure mode is the one spreadsheets always have: the sheet records what was true when someone last edited it. Seat counts drift, the renewal column quietly slides into the past, and nothing notifies anyone of anything.
AMPthilly treats licenses as first-class assets in the same register as the hardware they run on. Each license is a record with supplier, purchase date and cost, attached agreements, custom fields for seat counts and renewal dates, and assignment to named people through the same checkout-and-return model used for laptops - so offboarding shows seats and hardware in one place, and every assignment change lands in the audit history. The free plan includes the license register, checkouts and full audit history for 3 users and 25 assets, no card required - enough to get the renewal calendar under control before paying anything.
FAQ
How do I keep track of software licenses? One register: product, vendor, type, entitlement reference, seats, cost, renewal date, named owner. Assign seats to people or devices and review renewals monthly - tied to onboarding and offboarding, not memory.
What should a software license register include? Product and vendor, license type, proof of entitlement, seats purchased versus in use, cost per period, renewal date and notice period, internal owner, and seat assignments - with the agreement attached to the record.
How do I track software license renewals? Record the renewal date and the cancellation deadline, calendar the deadline, and review everything renewing in the next 60 to 90 days each month. Compare purchased seats with used seats before deciding.
Should licenses be assigned to people or to devices? Whichever the license terms say. Per-user seats go to named people so offboarding frees them; per-device licenses live on the machine’s record so they survive rebuilds.
Is license tracking worth it for a small business? Yes - small teams have nobody watching the spend, so idle seats and repurchased keys go unnoticed longest. A one-page register reviewed monthly is enough.
The takeaway
Software licenses leak money precisely because nothing visible goes missing. Put every license in one register with seats, costs, owners and notice periods; assign each seat to a named person or device; and walk into every renewal knowing the gap between what you pay for and what you use. The habit is fifteen minutes a month - the unused seats it catches run on a meter all year.