The software license register: every key, seat, and renewal on one page

Licenses are the part of the estate nobody inventories until one fails. A seat count drifts quietly until payroll audit; a renewal fires silently until the card declines on the one tool the whole company runs on; a serial number lives in one ex-employee's email until the machine is rebuilt. This is the register that makes all three boring — one spreadsheet, one owner column, one calendar feed.

1. One row per thing you pay for

• Eight columns, one sitting. Product and vendor; what breaks without it (also the delete-me test); plan and seat count; annual cost; renewal date with an auto-renew flag; one owner's name; where the key or credential lives; the support tier you actually bought. The asset inventory counts machines; this counts the money and the keys behind them.
• Every blank is a future incident. No owner = renews forever by accident. No key location = outage waiting on mailbox archaeology. No renewal date = surprise invoice.
• Start from the card statements, not memory. Walk twelve months of recurring charges and make a row for each. Memory-based registers are missing exactly the tools bought in a hurry during an incident — the ones with the worst terms.
• Row changes are changes. New tier, new seats, new owner — one log line each, same as maintenance windows. That log is the answer to "how do you manage third-party software?" on customer security questionnaires.

2. The sixty-day renewal decision

• Calendar every renewal 60 days out. Two months is enough to decide — renew, downgrade, cancel — before auto-renew decides for you.
• Write the three-word decision down. "Renew at current tier." "Downgrade to X seats." "Cancel, alternative is Y." The written line stops the quiet default where everything renews forever. If the answer is negotiate, that is when you climb the vendor escalation ladder — not the week after paying full price.
• Trials are rows on a leash. Trial started on a company card = register row with trial-end date in the renewal column and auto-renew flagged red. Cancel on trial-end day, not when the first real invoice lands.
• One line per quarter in the ops report. "Q4 renewals: 7 due, 5 renewed, 1 downgraded (−$960/yr), 1 cancelled." That line is the business case for the register.

3. Seats: the count nobody reconciles

• Quarterly true-up, tied to the access review. Compare each row's seat count against headcount + active contractors + actual last-login lists. Same meeting as the quarterly access review; this is the licensed slice of it.
• Offboarding removes the seat the same day. Deprovision the account and revoke or reassign the license rows. A departed employee's seat renewing for six months is money leaking — and sometimes still a login.
• Contractors get named seats with expiry dates. A contractor seat without an expiry is a permanent line item for a temporary person — the most common recoverable spend in a small stack.
• SSO turns seat hygiene into mechanics. Connect products to your identity provider where possible: deprovisioning the identity account revokes the seat automatically, and the true-up becomes a five-minute confirmation.

4. Where the keys actually live

• The key column points to a place, not a person. License keys, serials, and credentials live in a shared, access-controlled vault — the same pattern as backup key escrow. The register row holds the pointer. The test: can a new admin find every key on day one without asking a human?
• API keys are rows with a rotation habit. Any row with an API credential also carries its last rotation date, and the key rotation checklist owns the schedule. Blank rotation column = credential treated as permanent = how leaks become breaches.
• The license file rides the backup. Export the register and key vault on the backup schedule, encrypted before upload. A register that dies with the laptop was never a register.
• Break-glass vendor logins are red-flagged rows. The support-portal login that saves you during an outage gets its own row and owner — one hop, not one hunt, when you need it.

5. The annual prune

• One annual pass, three verdicts. Keep, watch (renew once more), or kill (cancel, name the replacement). The delete-me test does the work: if you cannot finish "without it, … breaks," the row is a kill candidate.
• Zombie rows are the prize. Every pass finds one or two: the plan the free tier replaced, seats sized for a team that shrank, the tool duplicated by a vendor feature. Killed at renewal time, they pay for the register's upkeep many times over.
• The register is insurance evidence. Cyber insurance applications ask what you run and how you manage access; the register is one attachment of answers.
• The verdict log is the year's story. "2026 review: 23 rows, 18 keep, 3 watch, 2 killed, −$2,140/yr recurring." Evidence, not adjectives.

The honest small-team version

A five-person company does not need license-management software; it needs one spreadsheet, one owner column, one calendar feed, and the habit of updating the row in the same five minutes as the renewal email. The trap is register drift — a beautiful register nobody has updated since the quarter it was born. A stale register is worse than none: none makes you look; stale makes you sure.

The full one-page version lives on our site: Software License Register Template for Small Teams — along with related notes on the asset inventory checklist, the user access review, the maintenance window policy, and the backup key escrow card.

If you want templates instead of prose: the Ops Starter Kit ($14) covers incident response, and the Automation Starter Pack ($19) covers the pick-first automations.