White paper · 6 min read · HP services series

Refresh on evidence, not on the lease

Most organisations replace PCs on a calendar set by a lease term. The result is predictable: working machines go out the door on schedule while failing ones wait their turn. The data to do better already exists in most fleets — and HP services are the levers that act on it.

An employee working on an HP notebook with two monitors

Imagery courtesy of HP Inc.

1. The calendar problem

The standard commercial PC lease runs three years, and most refresh programs are built around it: a device is ordered in year one and replaced in year three regardless of its condition.1 Depreciation schedules, budget cycles and contract renewals all reinforce the same rhythm. It is administratively simple, and for a long time it was the only practical option — nobody had device-level evidence to make a better call.

The cost of the calendar shows up in two ways. The first is early replacement: a large share of three-year-old business notebooks are still performing well for the person using them, and replacing them buys nothing except a newer date stamp. The second is late replacement: a device that started failing in month 18 — a swollen battery, a degrading SSD, a thermal problem — waits for its slot while the employee works around it and the help desk absorbs the tickets. The calendar is wrong in both directions at once.

In the public sector the effect compounds. A statewide program can span dozens of agencies or counties on different lease start dates, with hardware that is identical on paper and wildly different in the field. The refresh wave is planned by cohort, not by condition.

2. What "refresh on evidence" means

An evidence-based fleet replaces the calendar with per-device signals and a rolling cadence. Each device is classified — refresh now, keep, or upgrade later — from what you can actually observe about it, and procurement runs in waves against that list rather than against a cohort's anniversary. The three-year term still exists as a budget envelope; it stops being the trigger.

The signals are less exotic than they sound, and most organisations already hold them: device age and model; HP warranty and Support Services status; help-desk ticket history per serial; endpoint health data from tools such as HP Workforce Experience Platform; Windows 11 hardware eligibility; and, where you collect it, what the user says. The point of this paper is not a particular analytics tool — it is that once those signals sit in one place, the classification is usually obvious, and HP's service catalogue provides a lever for every outcome.

If you run HP Workforce Experience Platform (WXP), much of the classification is automated. The HP Insights Agent on each PC reports health, performance and sentiment, and WXP's Smart PC Refresh sorts the fleet into refresh now, keep or upgrade later on the Pro and Elite plans. WXP also reports Windows 11 readiness on every device and warranty status on HP devices.6 It supplies the performance half of the evidence; the coverage, order and retirement half lives in the per-device record described in section 5.

3. The evidence

The clearest public data point comes from HP itself. HP's own IT organisation, managing roughly 81,000 PCs, moved from an age-based refresh to a performance-based one using WXP data and reports a 40% reduction in PC refresh costs as a result.2

"Gone are the days of policy-driven change. We're now able to drive change at individual employee level, linked to their use of our equipment."Niall Johnston, Chief Information Officer, HP2

The University of Kansas Health System offers a second, independent case across a 25,000-device fleet managed in WXP. UKHS shifted refresh decisions "from age-based replacement to performance and utilization-based planning," and — the part that matters most for this paper — began replacing failing components like batteries under warranty instead of replacing the notebook. The system reports saving up to $1,500 per device when analysis showed the hardware was not the problem.3

"We've never been able to do that in the past."Shawn Bennett, Director of IT Support, The University of Kansas Health System, on warranty-first remediation3

These are HP's published customer outcomes and any fleet's results will differ. But the direction is consistent, and the mechanism is not complicated: replace fewer working machines, fix more failing ones under coverage, and refresh the rest when the evidence says so.

4. An illustration

Consider a 6,000-device fleet on a straight three-year cycle: 2,000 devices refreshed every year. Suppose the evidence shows that one in five of the devices due this year is healthy — good ticket history, in coverage, Windows 11-eligible, user satisfied — and that one in ten of the devices not due this year is already failing.

The evidence-based program defers the 400 healthy devices and pulls the 400 failing ones forward. Annual volume is unchanged at 2,000 — but every one of those 2,000 is a device that needed replacing, and the 400 people with failing machines got them a year or more early. Repeat the classification each quarter and the deferrals compound: a deferred device is re-evaluated, not forgotten. (Illustrative arithmetic, not a forecast; the ratios in your fleet come from your data.)

The second-order saving is the one the calendar hides. A deferred device needs coverage for the extra year, and that is precisely what HP post-warranty Support Services are for: onsite support with Defective Media Retention, bought before the original term lapses, at a fraction of a replacement.4 Component failures on retained devices become warranty events, not procurement events — the UKHS battery case in miniature.

5. The operating model

Running a fleet this way is an operating model, not a report. Five steps, on a rolling cadence, with an HP service behind each one:

  1. Assess. Put every device's evidence in one record — age, model, HP warranty and Support Services status, ticket history, Windows 11 eligibility, Protect & Trace enrollment. Milestone's VAR360 carries this per serial for every device we ship.
  2. Plan. Set the policy — what combination of condition, coverage and cost-to-keep means "refresh now" — and review the resulting list quarterly rather than annually. Decide the keep list's coverage at the same time: 4-year terms up front for devices likely to stay, post-warranty extensions for the rest.4
  3. Procure. Order against the list, in waves, on the contract vehicle you already hold, through HP2B or a SmartStores storefront, with HP Support Services and Wolf Protect & Trace attached at quote so they ship with the device.
  4. Deploy. Image at a staging bench — golden image, customer-validated build or Windows Autopilot — asset-tag, register Protect & Trace, and deliver to the door or to the desk depending on the site's IT capacity.
  5. Retire. Return outgoing devices on a documented chain of custody, sanitize to NIST SP 800-88 with destruction evidence, and buy out, remarket or recycle.5 The residual value of a device retired on time is part of the economics; so is DMR, which keeps the failed drives in your custody all the way to that certificate.

Milestone's role is steps three to five, and as much of one and two as a customer wants to hand off. We have been an HP partner for over two decades and run this loop every week: quoting and ordering, imaging and Autopilot builds, deployment with onsite assist, HP Support Services and warranty service, and returns with sanitization evidence. For customers who prefer one number per device per month, the whole loop is available as Device-as-a-Service, managed in VAR360.

6. Where to start

The first step costs the least: assemble the evidence you already have for one cohort — the devices due for refresh this year — and classify them. Most organisations discover both halves of the calendar problem in the first pass: scheduled replacements that do not need to happen, and failing devices that were not on anyone's list. The refresh policy writes itself from there, and the HP Support Services decision for the keep list is a quote away.

Key takeaways

  • Three-year, age-based refresh replaces working PCs early and failing PCs late; both cost money.
  • HP IT cut PC refresh costs 40% by refreshing on WXP performance data; UKHS reports up to $1,500 saved per device by fixing under warranty instead of replacing.
  • The evidence — age, coverage status, ticket history, Windows 11 eligibility — mostly exists already; the work is putting it in one record per device.
  • Run it as a loop — assess, plan, procure, deploy, retire — with post-warranty HP Support Services covering the devices you keep and NIST 800-88 closing out the ones you do not.

Sources

  1. Three-year lease cycles: standard HP commercial lease term, as documented in state and county refresh program guides Milestone administers.
  2. HP, HP IT Elevates Employee Experience and Engagement, customer case study 4AA8-4075ENW, March 2026.
  3. HP, UKHS Enhances Patient Care with Deep IT Insights (The University of Kansas Health System), customer case study 4AA8-5234ENW, December 2025.
  4. Milestone HP Support Services quotations for a state agency notebook fleet, June 2026 — HP 3-year and 4-year Onsite DMR Notebook Support; HP 1-year Post Warranty Onsite DMR Notebook Support (NASPO ValuePoint contract vehicle).
  5. NIST Special Publication 800-88 Rev. 1, Guidelines for Media Sanitization.
  6. HP, HP Workforce Experience Platform — Datasheet, 4AA8-4726ENW, November 2025 — plans, Smart PC Refresh, warranty status, HP Insights Agent and system requirements.

Continue the series

All HP services content →
HP Milestone

Ready to see what your fleet evidence says?

A coverage review of your HP devices — what is protected, what is lapsing, what is exposed — and a plan from Milestone to close the gaps.