Reading a lifecycle page in ten minutes
Four questions settle whether a lifecycle page is useful: is a period published, is a date fixed or a floor, is a successor named, and what happens the moment access ends. Reading for those four in that order takes minutes and skips most of the page. As of 2026-09-12.
| Look for | Why it comes first |
|---|---|
| A period, counted in days or months | It is the only thing that sizes the work |
| Wording qualifying the date | A floor and a deadline need different plans |
| A successor, in the same row | A runway cannot be spent without a target |
| Behaviour after the date | It decides whether software can detect the event |
| Anything about stored material | Rare, and the most expensive when present |
Inclusion rule. Questions this register asks of every lifecycle page it reads. Order. In the order that settles a plan fastest.
1Start with the period, not the dates
Dates are more interesting and less useful. A dated row tells a reader about one model; a published period tells them what every future retirement on that page will owe them, which is the figure a plan is built from.
Pages with many dates and no period exist, and they read as more informative than they are. A reader who finds five dated rows will feel well served and still not know how much warning the next one brings.
2Read the wording around a date, not just the date
The same-looking row means opposite things depending on one clause. A date stated as non-extendable can be put in a calendar. A date described as the earliest a model might go is a lower bound that can quietly become later.
Neither reading is safe if applied to the wrong page. This is the one place where copying the number and discarding the sentence loses the whole meaning.
3Check whether the page has room for a successor
Some lifecycle pages are tables of identifiers and dates, with no column where a replacement could go. That makes the absence structural rather than an omission in a particular row, and it tells a reader not to wait for one.
Where a page does have the column, an empty cell in it is a different fact: somebody could have named a destination and did not.
4Finish with the aftermath
What a request does after the date decides whether a retirement is something software notices or something a person investigates. A named status can be alerted on; an unexplained failure has to be diagnosed.
Anything about stored material is rarer and matters more. A page that says what becomes of files is describing a second deadline, and it is usually earlier than the one in the headline.
5Where each vendor's own wording lives
None of the above is a date. Announced end dates, and the apps still carrying the models they apply to, are kept on the calendar with the announcement each one came from.
- The change calendar — every announced date, with the notice it came from
- The notice period column — which entries publish a figure, and in what units
Guidance rather than a dated entry. No line here is a vendor statement, and none should be read as an announcement. The sourced material is on the calendar. Related: Recording per file, A frozen test set.