Evidence-led hardware refresh planning

Refresh budgets are won and lost on evidence. "We think a lot of laptops are getting old" gets cut; "2,140 devices are out of warranty and 880 are due for refresh this quarter, here's the list" gets funded. The difference is having the data — and trusting it.

Why refresh planning goes wrong

  • Age is estimated, not known. Without a reliable purchase or build date per device, “three-year cycle” is a guess applied to a fleet you can’t actually see.
  • Warranty status is invisible. The single most useful refresh signal — when support runs out — usually lives in a procurement spreadsheet nobody reconciles against the live estate.
  • It’s all-or-nothing. Plans swing between “refresh everything” (unaffordable) and “refresh nothing” (rising failures and support cost), because there’s no way to prioritise.

The signals that matter

A good refresh plan ranks devices on a few concrete signals, reconciled onto one record per machine:

  • Age — from a real purchase or first-seen date, not a blanket assumption.
  • Warranty / support status — in support, expiring soon, or already out.
  • Condition signals — repair history, performance, and whether the device still meets the OS and software requirements you’re standardising on.
  • Owner and role — so you can sequence by team, site or risk rather than at random.

Build the plan in cohorts

Don’t think device-by-device; think in cohorts you can schedule and fund:

  1. Out of warranty and ageing — the priority cohort; rising risk and support cost.
  2. Due this cycle — approaching end of warranty within the budget year.
  3. Watch list — healthy now, plan for next year.

Cohorts turn an overwhelming fleet into a small number of fundable decisions, and let you roll out replacements in waves rather than a disruptive big bang.

Make it defensible

Because refresh is a spend decision, the numbers have to survive scrutiny. That means they’re current (reconciled from live systems, not a six-month-old export), complete (no blind spots where unmanaged devices hide), and time-stamped (so you can show the position on any date). Defensible data is what turns a refresh request into a refresh approval.

You don’t need a perfect crystal ball for hardware. You need an honest, current view of age and warranty across the whole estate — and the discipline to plan from it.

How ClearVisibility helps

ClearVisibility reconciles device data from Intune, Entra ID and your directory — and warranty and procurement information — into one record per machine, with age, warranty and lifecycle status in a single view. It builds the refresh and disposal cohorts for you, keeps them current automatically, and can roll out replacements in scheduled waves through its booking and deployment-run tools. You walk into the budget conversation with the evidence already on your side.

See it on an estate like yours

A 30-minute demo shows ClearVisibility doing this on data that looks like yours.

Book a demo

Related

Keeping your CMDB accurateHardware refresh planningDashboards & reporting