Managing software licenses and SaaS subscriptions across an agency

Reference article · 5 min read

Agency software spending has moved from occasional purchases to a portfolio of recurring subscriptions. A permitting system, a payroll add-on, a design suite, and a long tail of small utilities each renew on their own date, bill to different funds, and answer to different program managers. Individually they look minor. Together they are usually one of the larger recurring lines in a technology budget.

Controlling it is administrative work: a current inventory, a calendar built around cancellation deadlines rather than renewal dates, a routine that removes seats when people leave, a plan for the day a vendor asks what you are running, and a purchasing path departments will use instead of working around.

Keep one inventory, small enough that it stays current

Give the inventory a named owner, usually in IT asset management or procurement, with standing access to accounts payable exports, purchasing card statements, the contract file, the single sign-on application list, and endpoint software inventory. Each source catches what another misses: card statements surface subscriptions that never reached procurement, and sign-on lists surface products in daily use that were never invoiced to IT.

Track fewer fields and keep them accurate:

• Product, vendor, and reseller. The entity you pay is not always the one that holds the terms.
• Term dates and the notice deadline. The date the term ends matters less than the last day the agency can give notice.
• Quantity and metric. Seats, devices, transactions, or a defined population.
• Owner and funding source. The department accountable for the renewal decision, and the fund or grant paying for it.
• Risk flags. Whether the system holds personal, health, criminal justice, or student data, and whether it has had a security review.

Build the calendar backward from the cancellation window

Subscription agreements commonly renew automatically unless the customer gives written notice some number of days before the term ends. That window varies by agreement, so read each one. Record the deadline, not just the expiration, and set the internal review trigger well ahead of it.

A workable order for any significant subscription: confirm the department still needs the product, pull usage data, decide on quantity and tier, request a quote, then choose to renew, reduce, or replace. Replacing a system takes far longer, so flag likely replacements a full budget cycle ahead. Assign each entry to a person, not a shared mailbox, and ask a vendor holding several agreements to co-terminate them so one review covers all.

Reconcile assigned seats against active employees

Quarterly, compare three lists: active employees from the human resources system, accounts in the identity provider, and seat assignments exported from each vendor's administration console. The findings are predictable: separated employees still holding seats, transfers who no longer need the product, duplicate and generic accounts, contractors past their end date, and seats with no sign-in for months.

Tie seat release to the offboarding checklist so separations free seats without waiting for the next review, and finish reclamation before the notice deadline, because most agreements allow quantity reductions only at renewal.

Prepare for true-ups and audit requests

A true-up is a scheduled reconciliation built into some agreements; an audit is a right the vendor exercises on its own timing. Either way, know your own numbers first, and keep order forms, quotes, and amendments where procurement and IT can both reach them. Those documents, not a vendor portal, define what the agency bought.

If an audit notice arrives, treat it as a contract matter. Name a single point of contact, route it through procurement and counsel, and ask the vendor to state the scope and the contract provision it relies on in writing. Review anything before producing it, and be deliberate about running vendor scripts on networks subject to criminal justice, health, or other security rules. For consumption-based services, set billing alerts rather than waiting for a reconciliation.

Find the software departments bought on their own

Decentralized buying is usually a program manager with a deadline and a card, not defiance. Find it in card statements and payables filtered for software merchant categories, in expense reimbursements, in sign-on requests, and in web traffic logs for known service domains.

The risk is more than duplicate spending on something the agency already licenses. Software bought outside the normal path usually has had no security review and no accessibility check, carries no negotiated data protection or exit terms, sits outside records retention planning, and renews with nobody watching.

The durable fix is a path faster than the workaround: a short intake form with a committed turnaround, a published catalog of what the agency already owns, card controls for software merchants, and a window in which departments can register existing subscriptions without penalty.

What to require, and how to start

Terms worth asking for in a subscription agreement:

• Reduction rights at renewal. The ability to lower quantities without penalty.
• A limit on renewal increases. A stated cap on price uplift at renewal.
• Notice of the deadline. A vendor duty to write to the agency before the cancellation window closes.
• Stable terms. No unilateral changes to policies incorporated by link.
• Reporting and exit. Usage reports on request, and data export in a usable format at termination.
• Non-appropriation. Clear treatment of the subscription and the data if funds are not appropriated.

To start, rank subscriptions by annual spend, collect the governing documents for the largest vendors, load the next four quarters of notice deadlines into a calendar, and run one seat reconciliation.

HQT is a technology and software company serving state and local government, with cloud and enterprise IT services that cover software and subscription inventory, renewal planning, and license reconciliation.

Frequently asked questions