Software renewal

A software renewal is the moment a subscription or licence agreement reaches the end of its current term. At that point the contract typically either rolls over for another term, is renegotiated on new terms, or lapses if it is cancelled in time.

Renewals matter because they are the natural decision point for a piece of software: the one time you can change seat counts, switch plan, negotiate price, or walk away without paying for another full term. Miss the date and that leverage is gone until the following cycle.

A renewal has two dates and only one of them is a deadline. The renewal date is when the next term starts and the next invoice is raised. The cancellation deadline is the last day notice can be given, and it sits a notice period earlier: a 60 day notice period against a renewal on 31 March puts the real decision on 30 January.

Diarising the renewal itself is therefore the most common way to miss one. By the time it arrives the notice window has closed, the auto-renewal clause has already done its work, and the decision you thought was still ahead of you was settled two months earlier. Everything worth doing at a renewal (repricing, dropping seats nobody uses, moving plan, or leaving) has to happen before that earlier date.

A tool records its renewal date, its notice period in days and whether it auto-renews, and those three fields produce the cancellation deadline rather than leaving it to be worked out by hand each cycle. Reminders default to 90, 60, 30 and 7 days ahead and are set per tool, so a contract with a six month notice period can be raised earlier than one you can leave on a fortnight.

When notice does go out the record moves to notice given rather than being deleted, which keeps the tool in the estate and in the spend figures until the term genuinely ends. The dashboard is ordered by what renews next, so the part of the estate with a decision attached to it is the part you see first.