When devices bought in the same year start failing in the same year, it feels like bad luck. It’s actually the predictable result of buying a whole fleet at once and running it until it breaks.
If you’re watching batteries swell, screens crack, and repair tickets climb across every site at the same time, you’re not facing a series of repairs. You’re facing a refresh you didn’t plan for.
This post covers why fleets fail together, how often enterprise devices should be refreshed, how to stagger and budget a refresh, and what to do with the devices you retire.
Why fleets fail all at once
Devices of the same model and age wear out on roughly the same schedule. Their batteries degrade together, their parts become harder to find together, and their operating system support ends on the same date.
That’s manageable when a fleet is replaced in waves. It becomes a crisis when every device was bought in one large order, because the failures arrive in one large wave too.
Signs your fleet is about to age out together
A fleet usually gives plenty of warning before it fails all at once. The signals are in your repair and support data, if someone is looking.
Watch for repair tickets rising month over month on one model, batteries that no longer last a full shift, and spare devices running out faster than they’re replaced. Check whether the model has reached end of sale, since parts and repair options shrink once manufacturers stop selling it.
The clearest warning is a security update end date that’s approaching for most of the fleet. Once that date passes, every device on it becomes a risk at the same time.
How often should enterprise mobile devices be refreshed?
There’s no single number that fits every fleet. The right time to replace a device depends on a few signals you can check, not on a fixed age.
Start with operating system support. Once a device stops receiving security updates, it’s a risk on your network, so check each model’s published support end date.
Then look at battery health, repair frequency, and repair cost per device. When repairs become more frequent and more expensive, keeping the device costs more than replacing it.
Finally, look at the work. If the device can’t run the apps your operation now depends on, or slows workers down, it’s due regardless of age.
Stagger the refresh so it never arrives all at once
A staggered refresh replaces part of the fleet each year instead of all of it every few years. It turns a periodic crisis into a routine.
Group devices into cohorts by site, region, or role, and schedule each cohort for replacement in a different year. The total number of devices replaced over the cycle stays the same, but the work, the cost, and the disruption are spread out.
Time each wave around your operation. Avoid refreshing during peak seasons, and for sites in remote or northern parts of Canada, plan shipping outside the worst of winter so devices arrive when staff can be trained on them.
Staggering also means your newest devices can cover failures in older cohorts, and you learn from each wave before the next. The device lifecycle management guide covers how to plan lifecycle stages across a fleet.
How to budget a device refresh
The purchase price is only part of the cost. A realistic refresh budget includes everything it takes to put a working device in a worker’s hands and retire the old one.
- Devices and accessories, including batteries, cradles, holsters, and mounts
- Staging, configuration, and shipping to each site
- Management licences for the new devices
- Training time for staff
- Secure data wiping and recycling for retired devices
- A contingency for the model or app that turns out harder than expected
Compare that budget with the cost of keeping the old fleet. Rising repair spend, replacement batteries, extra spares, and the hours workers lose to failing devices all belong in the comparison, and they usually grow every year a fleet ages.
A staggered refresh turns that into a predictable annual amount rather than a large, irregular capital request. The post on why device refresh costs blindside Canadian logistics companies covers the costs most often missed.
What actually happens when a fleet ages out
The usual first response is to buy more of the same model to cover the failures. In practice, that adds new devices with the same remaining support life as the old ones.
One Canadian freight carrier we work with was running mobile computers that were nearly six years old. Batteries were swelling, hardware was breaking down, and drivers were losing time to failures. Instead of buying more of the legacy model, the fleet was replaced in full, with about 800 devices staged and deployed across every depot in six weeks and the old devices securely decommissioned.
The full replacement fixed the immediate problem. The lesson for everyone else is to avoid reaching that point in the first place.
What to do with retired devices
Retired devices still hold data, and in Canada you remain accountable under PIPEDA for personal information on devices you control. Plan their retirement as part of the refresh, not as an afterthought.
Wipe each device with a certified data destruction process and keep the record. Then decide whether to redeploy it as a spare, recover residual value, or recycle it responsibly through provincial electronics recycling programs. Devices left in storage rooms tend to stay there for years.
Redeploying old devices as spares can make sense for a short time, but only if they still receive security updates. A spare that’s already out of support just moves the risk from one shelf to another.
When a subscription model makes sense
If large capital requests are the reason refreshes get delayed, consider changing how devices are paid for. Device as a Service (DaaS) bundles hardware, staging, support, and refresh into a monthly cost per device, so the refresh is built in.
We offer DaaS alongside staging, lifecycle management, and secure decommissioning, all handled by our in-house Canadian team.
Just know that it fits best when you want predictable costs and a refresh schedule that doesn’t depend on winning a capital request every few years. If you have capital available and a team to manage the cycle, buying may still be the better fit. The piece on device refresh planning for Canadian retailers shows how one sector approaches the decision.
Questions we hear about device refresh cycles
How often should enterprise mobile devices be refreshed?
There’s no fixed age that fits every fleet. Replace devices when they lose operating system security support, when repairs become frequent and expensive, when batteries no longer last a shift, or when they can’t run the apps your operation needs. Check each model’s published security update end date when planning.
Should we refresh all our devices at once?
Usually not. Replacing the whole fleet at once means it will age out at once again. A staggered refresh replaces a portion of the fleet each year, spreading cost, work, and disruption, and keeps newer devices available to cover failures in older ones.
How do we budget for a device refresh?
Include more than the device price. Budget for accessories, staging and shipping, management licences, training, secure data wiping, and recycling, plus a contingency. A staggered refresh or a subscription model can turn that into a predictable annual cost instead of a large, irregular capital request.
Where to start
List every device model in your fleet with its purchase year and its security update end date. That list shows when each part of the fleet will age out. Then split the next replacement into cohorts, so the refresh after this one never arrives all at once.