When the device refresh budget is frozen, the fleet doesn’t stop aging. Batteries keep wearing out, repairs keep coming, and the support window on older devices keeps closing, budget or not.
If your capital request for new devices was cut or pushed to next year, you still have to keep frontline workers equipped. The question is how to stretch the current fleet safely, and what to do about the devices that can’t wait.
This post covers how to triage the fleet, how to extend device life without taking on hidden risk, how to make the case for the devices that must be replaced, and the alternatives to a single large purchase.
Start by sorting the fleet into three groups
A frozen budget forces a decision about every device, so make it deliberately. Not every device needs replacing now, and not every device can safely wait.
Sort the fleet into three groups. Devices that are healthy and still supported can stay in service.
Devices that are wearing out but still supported can be extended with care. Devices that no longer receive security updates, or are failing often, need replacing whatever the budget says.
Use your own data to sort them. Repair history, battery health, operating system version, and each model’s published security update end date will put most devices in the right group. The post on planning a healthy device refresh cycle covers the signals in more detail.
How to extend device life safely
Extending device life is reasonable for devices that are still supported. It mostly comes down to replacing the parts that wear out and keeping the software current.
- Replace batteries before they fail. Swollen or weak batteries are the most common reason older devices stop lasting a shift, and a battery costs far less than a device.
- Refresh accessories. Worn charging cradles, cables, and holsters cause failures that look like device problems.
- Keep software current. Apply every available operating system and security update, and retire apps the device struggles to run.
- Grow the spare pool. Older fleets fail more often, so a few more ready spares keep workers working while repairs happen.
- Redeploy within the fleet. Move newer devices to the roles that work them hardest and older ones to lighter duties.
The tips for optimizing the total cost of ownership of mobile technology include more ways to get extra life from a fleet you already own.
Where extending stops being safe
Extension has a limit, and it’s set by security support rather than by how the device looks. A device that still powers on but no longer receives security updates is a risk on your network.
Just know that the savings from keeping unsupported devices can disappear quickly. Repair costs rise, parts become harder to find, and if those devices hold personal information, you remain accountable for protecting it under PIPEDA. That’s the group to defend in the budget conversation.
How to make the case for the devices that can’t wait
A frozen budget doesn’t always mean zero. It often means the request needs to be smaller, clearer, and tied to risk. A short, specific case for the devices that must be replaced has a better chance than a full refresh request.
List the unsupported and failing devices, where they’re used, and what happens if they fail. Show the repair spend on them over the last year and how it’s trending. Then put a number on the operational impact in your own terms, such as workers idled, deliveries missed, or stores short of devices.
Keep the request to what’s necessary now. Leadership can approve a targeted replacement much more easily than a full refresh they’ve already deferred.
Keep the frozen year from making next year harder
A frozen year is a good time to prepare for the refresh, even if you can’t buy anything. The planning work costs little and makes the eventual purchase faster and smaller.
Use the time to confirm which device models you’ll standardize on, what each role needs, and how the next rollout will be staged. Clean up the asset records so you know exactly what you own and where it is. Then, when budget returns, the refresh can start right away instead of beginning with a discovery exercise.
Alternatives to a big capital purchase
If the obstacle is a large, one-time capital request, changing how devices are paid for can move things forward. There are a few common approaches.
| Option | Fits best when | Watch out for |
|---|---|---|
| Phased purchase | Some budget is available, just not enough for the whole fleet | Running two device models for a while |
| Leasing | You want to spread hardware cost over time | End-of-lease terms and what’s included beyond the hardware |
| Device as a Service (DaaS) | You want hardware, staging, support, and refresh bundled into a monthly cost per device | Contract length, scaling terms, and what’s billed separately |
| Extend and defer | Devices are healthy and still supported | Rising repair costs and a bigger refresh later |
Whichever you choose, talk to your finance team about how it would be treated in your budget, since that varies by organization. The piece on how DaaS delivers cost savings covers where a subscription model can help and where it doesn’t, and the breakdown of Device as a Service fees in Canada explains what’s typically included.
What actually happens when a refresh keeps getting deferred
A refresh deferred once is manageable. A refresh deferred two or three years in a row usually ends in the worst version of the problem, where most of the fleet fails within a short period and the replacement has to happen all at once.
Here’s what actually happens in many fleets. Repair spending creeps up, spares run short, sites borrow devices from each other, and workarounds spread. By the time the budget is approved, the replacement is larger and more urgent than it would have been, and there’s less time to plan it well.
That’s the strongest argument for a targeted replacement now, even if the full refresh waits.
Where outside help fits
If the budget freeze is about capital rather than total spend, a subscription model may let the refresh go ahead in a different form. We offer Device as a Service with staging, support, and secure retirement of old devices handled by our in-house Canadian team.
Just know that DaaS fits best when you want predictable monthly costs and a refresh schedule built in. If capital becomes available and you have a team to manage the cycle, buying outright may still be the better choice.
Questions we hear about frozen device budgets
What do I do when the device refresh budget is cut?
Sort the fleet into devices that can stay, devices that can be extended, and devices that must be replaced because they’re unsupported or failing. Extend the healthy ones with new batteries, accessories, and current software. Then build a small, specific case for replacing the devices that can’t wait.
How long can we keep using enterprise mobile devices?
As long as they still receive security updates, run the apps your operation needs, and don’t cost more to repair than to replace. Check each model’s published security update end date. Once a device stops receiving updates, replacing it should become a priority regardless of budget timing.
Are there alternatives to buying devices outright?
Yes. Common options include phased purchases, leasing, and Device as a Service, which bundles hardware, staging, support, and refresh into a monthly cost per device. Each has different contract terms, so compare what’s included and talk to your finance team about how it would be treated.
Where to start
List every device model in your fleet with its security update end date and last year’s repair spend. That list sorts itself into what can wait and what can’t. Bring the short list of devices that must be replaced to leadership as a focused, risk-based request, and extend everything else with care.