Lifecycle status

A lifecycle status is the stage a tracked software contract has reached in its own renewal cycle. Rather than a single date, it is a state that moves as the calendar does: active while the term runs, upcoming and then due soon as the renewal approaches, inside the notice window when a keep-or-cancel decision has to be made, and notice missed once that window has closed on a contract that will now roll over.

Recording a status alongside the dates is what turns a register into a worklist. A date tells you when something happens; a status tells you whether anyone has acted on it. In StackTrackr most states are derived from the renewal date, the notice period and whether the contract auto-renews, while trial, notice given, cancelled and expired are set by hand and take precedence, because a decision a person has made should never be overwritten by arithmetic.

An annual tool renews on 1 June, needs 60 days of notice and auto-renews, so its cancellation deadline is 2 April. Through the winter it reads Active. From 3 March, 90 days out, it moves to Upcoming. On 19 March, two weeks before the deadline, it becomes Notice window: the badge the product exists to show, because this is the last fortnight in which cancelling is still a choice.

If nobody acts, 3 April turns it to Notice missed and it stays there until the renewal lands. That is the useful part. The renewal is still two months away, so a date-only view would read as calm, when in fact the decision has already been made by default and another full year has been bought. The state says so while there is still time to plan for the spend rather than discover it on an invoice.

Trial, Active, Notice given, Cancelled and Expired are set by hand, and they win over anything the dates imply. The rest are derived for records left as Active: Upcoming inside 90 days, Due soon inside 30, Notice window in the last fortnight before the cancellation deadline on something that auto-renews, Notice missed once that deadline has passed with the renewal still ahead, and Overdue when a date has gone by on something that does not roll over. Notice missed is raised only on quarterly billing and longer, because on a monthly tool the window closes every month, and one more month is not the news one more year is.

There is also No renewal date, for a record carrying no renewal or expiry at all. It is a state rather than a quiet Active because a tool with no date can never trigger a reminder, and a register whose gaps look identical to its healthy rows is the one way to reach zero alerts without noticing. Its neutral counterpart is Does not renew, for a one-off purchase or a perpetual or open-source licence with nothing billed each cycle, where having no date is the right answer rather than a gap. A perpetual licence still billed every year is paying for support, which renews, so it keeps the No renewal date warning until that date is added.

The status appears as a badge on every row of the register and on the tool’s own page, and the register’s Status column sorts by how much attention a row needs rather than alphabetically, so Overdue and Notice window come to the top and Cancelled sits at the bottom. You can filter the register by status to work one state at a time.

The same derivation drives the reminder emails, so the badge on screen and the message that goes out can never disagree about where a contract stands.