Ask any IT leader when their laptops need replacing, and you’ll get one of two answers.
The first is confident: a number, a timeline, a plan.
The second is honest: “Let me get back to you on that.”
Most organizations live closer to the second answer than they’d like to admit; not because they don’t care about refresh planning, but because the data needed for confident planning is almost never current enough to support it.
The Problem Isn’t Collecting Data. It’s Keeping It.
IT teams are not short on data. They have MDM exports, procurement records, warranty portals, finance spreadsheets, help desk systems, and HR platforms. Every device that enters an organization leaves a trail.
The challenge is that each of those systems captures a snapshot. The MDM shows what was enrolled. The spreadsheet shows what was purchased. The warranty portal shows what was registered. But none of them automatically update when a device changes hands, gets reallocated after an offboarding, or gets forgotten in a drawer after a team restructures.
By the time refresh planning season arrives, typically when the CFO asks for a 12-month forecast, the data is months behind the reality it’s supposed to describe.
This is the core reason refresh planning becomes reactive. It’s not a planning failure. It’s a data currency failure.
What Reactive Refresh Planning Actually Costs
The immediate costs are visible: emergency hardware purchases, productivity disruptions, and budget overruns.
The less visible cost is strategic. When IT can’t answer the CFO’s question with confidence, it loses credibility in the budget conversation. Requests get scrutinized more heavily. Refresh cycles get deferred. Deferred cycles mean older hardware, more support overhead, and more devices failing at inconvenient times.
There’s also a compliance dimension. Devices that should have been retired and destroyed sometimes remain in circulation because nobody has a current view of where they are or who has them. Morgan Stanley’s $35 million SEC penalty is the most public example of what happens when asset records diverge from operational reality at scale.
Why the Industry Is Moving Toward Connected IT Data
Forrester’s research on the evolution of IT management, most directly in The Graphic Future of IT Management, points toward a significant architectural shift — away from isolated, workflow-driven systems and toward interconnected knowledge models that reflect the actual relationships between people, devices, software, and services in real time.
The reason this matters for refresh planning is straightforward. A device record that connects the employee who uses it, the software assigned to it, the department it belongs to, and the warranty that covers it tells a fundamentally different story than a row in a spreadsheet.
When that connection updates automatically — when an employee leaves, and the device record reflects it, when a warranty expires, and the refresh forecast adjusts — planning stops being a quarterly scramble and becomes an ongoing capability.
What Confident Refresh Planning Actually Looks Like
The CFO asks which laptops will need replacing in the next 12 months.
A team with current, connected asset data can answer in minutes: here are the devices approaching the end of life; here are the ones whose warranties expire in Q3; here are the ones currently assigned to active employees versus sitting unallocated.
A team working from disconnected systems produces a number that is somewhere between accurate and approximate — and they know it, even if they don’t say so.
The difference isn’t effort. Both teams are working hard. The difference is whether the data they’re working from reflects today’s reality or last quarter’s.
The Question Worth Asking Now
The refresh planning season will come around whether IT is ready for it or not.
The organizations that handle it well aren’t the ones that work harder in Q4. They’re the ones whose asset data is current enough that Q4 is just another quarter.
A simple test: if your CFO asked for a complete list of every active laptop assigned to employees right now, how long would it take your team to produce it with confidence?
If the answer involves opening more than one system and reconciling the results, that’s where the refresh planning problem starts.
