- Warranty, end-of-sale and end-of-support are the three dates that predict the whole estate.
- Lifecycle dates belong on the model, not the unit — set once, inherited by every asset.
- Written-down value plus fault history is the language finance actually funds.
- Deliverable: a rolling 3–5-year refresh forecast bucketed by Australian financial year, smoothed.
AV refresh conversations usually happen at the worst possible moment: something critical has failed, the model is discontinued, the replacement doesn't match the other six rooms, and the money has to be found mid-year. None of that was bad luck. The equipment aged on a completely predictable schedule — it just wasn't being read.
The three dates that predict everything
Lifecycle planning runs on dates the register should already hold:
- Warranty expiry — the line between "the vendor's problem" and "a budget decision". Repairs on the wrong side of it need approving, not just booking.
- End-of-sale — the vendor stops selling the model. From this point you can't buy matching units, which quietly breaks room standardisation the next time one fails.
- End-of-support — firmware, security patches and repairs end. Every unit of the model is now on borrowed time, and in a conferencing world where devices sit on the network, unsupported firmware is a security posture problem as much as an AV one.
Crucially, end-of-sale and end-of-support are properties of the model, not the unit — set them once against the model in the catalogue and every asset of that model inherits the horizon. AVDesk tracks both per model and turns them into a refresh forecast, bucketed by Australian financial year, so "what's falling due" is a report rather than a research project.
Let depreciation do the arguing
A register that carries purchase cost and straight-line depreciation knows each asset's written-down value — and that changes the tone of refresh conversations. "The theatre projector is old" is an opinion. "The theatre projector is fully written down, out of support next FY, and has consumed eleven tickets this year" is a business case. Finance teams respond to registers that speak their language; it's also how the estate's total value stops being a guess at insurance time.
Read the service history as a leading indicator
Dates predict the fleet; fault history predicts the individual. A device whose ticket cadence is accelerating is announcing its retirement early, whatever the calendar says. This is where the loop between the register, monitoring and the support desk pays off: because alerts and tickets accrue against the asset, the register can tell you which specific units to pull forward in the refresh plan — and which healthy ones can safely run another year.
Build the forecast, then defend the smoothing
With dates, values and history in one place, the forecast almost writes itself: group assets by financial year of expected retirement, sum the exposure, and smooth the peaks — pulling some replacements forward and pushing some back so no single year spikes. The smoothed plan is the deliverable: a rolling three-to-five-year refresh schedule that turns AV capital from an annual emergency into a boring, fundable line item.
The best refresh plan is the one nobody notices happening — rooms upgraded on schedule, models retired before they strand you, and no year where everything fails at once.
AVDesk's register carries the costs, the depreciation, the per-model lifecycle dates and the refresh forecast natively. Book a demo and see what your next three financial years actually look like.
