The renewal list belongs to today's organisation

## A prior renewal is not a present business owner

The list contained 186 software entitlements. It had a history of purchase and renewal, but that history did not by itself explain the current business need. Responsibilities had changed, supplier arrangements had moved and some tools were attached to teams that no longer existed in the same form. We identified forty-two entitlements for reassessment. I wanted to know who could explain each continuing obligation, not simply who had approved the invoice in an earlier organisation.

A usage report was useful evidence, but it was not the whole decision. An application may be used infrequently because it supports an occasional but important process. It may retain records that the business still needs to access. Contractual terms may also affect what can be removed and when. None of those questions should be settled by an IT usage count alone. I asked procurement, legal and business owners to examine their respective parts of the decision so that a low activity figure did not become an automatic cancellation instruction.

The proposal to cancel all forty-two and reinstate any later demonstrated need had an appealing simplicity. It would create a visible reduction at renewal and make users justify continued expenditure. The weakness was the point at which the justification would occur. A dependency discovered after removal can affect a live process or require an expensive recovery. I wanted the relevant owner to make that decision before the business lost the capability, with the transition consequences understood rather than treated as an inconvenience somebody else would solve.

This did not mean every uncertain entitlement deserved indefinite protection. Lack of ownership can itself become a reason that spending continues without examination. My aim was to give the decision a responsible route and a deadline supported by evidence. Some items would be retired. Others would remain because a defined need justified them. The distinction mattered more than achieving the largest cancellation count. A renewal programme should improve the quality of the obligation the organisation accepts, including the obligations it deliberately chooses to continue.

## Price the transition before claiming the benefit

We approved twenty-seven lakh rupees for review, transition and necessary support. Thirty entitlements were retired. Twelve were retained with named owners and documented reasons. Those outcomes belong beside the cost, because the act of stopping a payment is not always costless. Records may need to remain accessible, processes may need an alternative and users may need support through the change. The business should understand that work before treating the future renewal amount as an immediately available saving.

Estimated annualised avoided renewals were nineteen lakh rupees. I used those words deliberately. The figure described an estimate of renewal expenditure avoided under the changed position. It was not cash received and not a claim that the first year had produced a nineteen-lakh net benefit. The programme expense was twenty-seven lakh rupees. Readers could assess the timing and economics only if both figures remained visible. A persuasive headline that omitted the transition would have made the investment case easier to approve and harder to understand.

Procurement and legal colleagues retained interpretation of the contracts. Business owners confirmed the operational consequence of removal. My team provided the systems evidence and implemented the agreed changes. The review did not become a broad software-licensing compliance opinion, and I did not present it as one. A CIO can coordinate a decision without taking over every professional authority involved in it. That boundary improves the account because it tells the board which judgement has been made and by whom.

The twelve retained entitlements were also a result. Each now had an owner who could explain the continuing need. It would have been easy to describe them as a failure to complete the retirement ambition, but that assumes retirement was always the correct answer. The purpose was to align the obligation with the organisation that existed now. In some cases that meant keeping the tool and making its responsibility explicit. A smaller unresolved list was useful only if the resolved items represented informed decisions, not simply the disappearance of an awkward question.

## Leave a reason that survives the next renewal

The review would have limited value if the next renewal team inherited another unexplained list. I wanted the reason for retention or retirement to survive beyond the programme. The record should identify the business owner, the relevant need and the decision made. It should not depend on locating a person who remembered an old meeting. That continuing account helps a future reviewer distinguish a genuine change in circumstances from a question that was already examined and settled under different conditions.

An organisation also needs to notice when those conditions change. A retained entitlement can become unnecessary after a process is redesigned. A retired tool may be proposed again under a new name or by a different team. The prior decision should inform the discussion without dictating it forever. I favour an account that explains the reason and evidence, because that gives the next owner something to test. A bare status of active or cancelled says little about whether the present business need resembles the one management previously considered.

Directors can ask whether a cost-reduction proposal includes the transition required to make it workable. They can also ask how estimated avoided expenditure differs from realised benefit and which retained obligations remain important. Those questions do not require the board to select software products. They help assess whether management has confused a smaller renewal total with a complete economic result. A proposal may still be sensible when its initial cost exceeds the first annual estimate, but the justification should be made openly rather than hidden in the timing of the figures.

Our account was 186 entitlements reviewed, forty-two reassessed, thirty retired and twelve retained with owners, following twenty-seven lakh rupees of programme expense. Estimated annualised avoided renewals were nineteen lakh rupees. I find that account more useful than a percentage reduction because it explains what the organisation decided and what it paid to make the decision work. The renewal list should represent the business that exists today. Keeping it intelligible requires ownership, transition planning and an honest description of when the financial benefit might arrive, not only a willingness to cancel yesterday's purchases.