An unused subscription is a question, not a saving

A software renewal list can make an organisation look less disciplined than it is, or more efficient than it has become. The same subscription may appear inactive because its work is seasonal, because its assigned user has changed, or because nobody needs it any longer. Those situations deserve different decisions. I become concerned when a technology team moves directly from an activity report to a saving claim without explaining which situation applies. The report can identify a population for review. It cannot supply all the evidence needed to remove the expense.

At Orelvi, we reviewed 186 named specialist-software subscriptions before renewal. Forty-one did not have a current active requirement. That was a useful finding, but the initial suggestion to cancel the whole population ran ahead of the work. Some requirements had moved to other colleagues; others had genuinely ended. The contracts also did not all permit the same action. We needed business owners, application support and procurement to examine the seats together before deciding what could be reassigned, what should remain and what could be cancelled at the appropriate date.

## Ask what the activity measure leaves out

The first question is what the measure actually records. A login count, application launch or recorded processing session may each tell a different story. A person can use software intensively for a short period and then have no need for it until the next project. Another person may open an application regularly without needing the specialist entitlement being renewed. I do not want teams to dismiss activity data because it is incomplete. I want them to use it with an understanding of the work it can and cannot observe, and to make the remaining question explicit.

A business owner should be able to explain the expected requirement in terms more specific than keeping a seat just in case. That does not mean forecasting every future assignment with certainty. It means naming the work, the likely timing and the consequence if the entitlement is unavailable. The review should also consider how long it takes to obtain a replacement and whether the contract makes short-term provision practical. A cautious retention decision can be reasonable, but its basis should be visible rather than concealed inside an untouched renewal list that nobody feels responsible for challenging.

Technical teams need commercial colleagues in this discussion because a configuration option is not necessarily a contractual permission. Software that can be activated on another machine may still be subject to named-user restrictions, approval steps or other conditions. In our fictional case, twenty-eight subscriptions could be reassigned through the permitted process. That conclusion came from reviewing the relevant terms, not from a general belief that licences are freely transferable. A CIO who treats the technical ability to make a change as sufficient authority for it creates a problem that a good utilisation report cannot repair.

## Keep reassignment and cancellation in different columns

Our final decision cancelled thirteen subscriptions at renewal and reassigned twenty-eight. At ₹3 lakh per cancelled subscription, annual expense fell by ₹39 lakh. The reassigned subscriptions continued to be paid for. Their value was that the existing entitlement now served an established requirement; they were not another ₹84 lakh reduction in the same annual bill. I rejected a draft presentation that combined the two figures into one saving. It would have made the intervention sound larger while making the board's understanding of our recurring commitment less accurate.

There may be cases where reassignment avoids a planned additional purchase. If so, the comparison needs to show the approved or credible counterfactual and avoid counting the same benefit twice. It should also distinguish a budget that was never spent from a cash expense that has actually ended. In our case we kept the account narrower because the evidence supported cancellation savings and improved allocation, not a second quantified benefit. That discipline is particularly useful when several teams contribute to a programme and each is tempted to claim the full value in its own performance report.

Timing matters as much as classification. A decision made after a notice deadline may not reduce the next bill, even when the underlying need has ended. Conversely, cancelling too early can interrupt work whose completion date has moved. The renewal paper should identify when the financial effect begins and what transition is required. I prefer a smaller, dated commitment reduction that finance can reconcile to a larger annualised number whose start date is unclear. The company needs to manage its obligations, not merely produce an attractive estimate of what a cleaner estate might cost.

## Make the renewal calendar a management responsibility

The technology function should not be left to discover business need during the final week before a contractual deadline. Application owners need a calendar that gives them time to review demand, procurement time to confirm options and support colleagues time to implement approved changes. That preparation is ordinary management work. It does not require a dramatic cost campaign every year. Our review took effort from people whose main jobs lay elsewhere, and some reassignments moved while the contractual process was confirmed. Beginning earlier would reduce that pressure without removing the need for judgement.

The process also needs a reasonable route for disagreement. An engineering lead may expect work that finance cannot yet see in a firm order, while a finance colleague may challenge a requirement that has been retained for several cycles without use. Neither should win merely by holding the renewal paperwork. I want the responsible business executive to understand the cost, the evidence and the consequence of the choice. Where uncertainty remains, a time-limited retention with a named review point may be more honest than either a permanent exception or an immediate cancellation presented as obvious efficiency.

Directors should ask whether the company can reconcile its reported benefit with the commitment it has actually changed. They should also ask whether management has preserved capability needed for credible work and complied with the terms governing its use. Those are oversight questions; directors do not need to arbitrate individual seat assignments. A useful board paper can show the reviewed population, the decisions, their financial timing and the principal unresolved risks. It should be possible to understand the result without treating every inactive account as waste or every reassignment as a cash saving.

I would judge the next renewal cycle by whether these distinctions have become routine. The aim is not to make every subscription continuously busy, which could encourage pointless activity or conceal legitimate intermittent need. The aim is to maintain a defensible relationship between entitlement, work and expense. When that relationship is clear, a cancellation can be made confidently, a retention can be explained and a reassignment can be valued for what it actually does. The organisation becomes more disciplined because its decisions are better grounded, even when the reported saving is less dramatic than the first spreadsheet suggested.