When broken handhelds take weeks to come back, the repair itself is rarely the slow part. Most of the time is spent waiting, in a box at the site, in transit, in a queue, or on an approval nobody knew was needed.
If you run operations, you feel it as workers sharing devices, sites borrowing from each other, and a growing pile of broken units nobody is tracking.
This post covers where repair time actually goes, why devices sit in limbo, and how a managed spare pool keeps workers working while repairs happen in the background.
Where device repair time actually goes
A repair has many steps, and only one of them is the repair. The rest is handling, shipping, and waiting, and each step adds days.
The device has to be noticed as broken, reported, and packed. It ships to a repair depot, waits in a queue to be diagnosed, and may wait again for parts or for someone to approve an out-of-warranty quote. Once repaired, it ships back, needs to be set up again for its site and role, and then waits at the site until someone puts it back in service.
The post on break/fix for enterprise mobile devices covers each stage of the repair process in more detail.
Why devices sit in limbo
The longest delays happen between steps, where nobody owns the device. A broken handheld in a drawer is nobody’s problem until someone needs it.
Sites often batch broken devices to save on shipping, so a device can wait until the box is full. Repairs aren’t tracked, so nobody notices one hasn’t come back.
Warranty claims need serial numbers and proof of purchase that someone has to dig up. Out-of-warranty quotes sit in an inbox waiting for approval.
Canadian operations face an extra delay when repairs are routed out of the country. Devices shipped across the border for repair add transit and customs time in both directions, which is a common complaint at Canadian divisions of larger companies.
Turnaround matters less than downtime
Repair turnaround is the number most people track, but it’s not the one that hurts the operation. What matters is how long a worker goes without a working device.
Those two numbers don’t have to be the same. If a ready replacement goes into the worker’s hands the same day the device breaks, the repair can take as long as it needs without stopping anyone. That’s the idea behind a spare pool.
Set a target for downtime, not just turnaround
Agree on how long a worker can reasonably go without a working device, and measure against that. For many frontline roles, the honest answer is less than a shift.
A downtime target changes the conversation. Instead of asking a repair vendor to work faster, you ask how a spare reaches the site in time, which is a problem you can solve with stock and logistics. The repair turnaround target can then be set separately, based on what keeps the spare pool full.
Report both numbers to site leaders. They care about the first one, and the second one tells you whether the system behind it is keeping up.
What spare pool management is and how it works
Definition
Spare pool management is keeping a stock of pre-configured, ready-to-use devices so a broken one can be swapped immediately. The broken device goes into the repair process, and a repaired or replacement device refills the pool.
A working spare pool has a few moving parts. Spares are set up for the right roles and sites, kept charged, and sized from real failure rates. Every swap triggers a return and a refill, so the pool doesn’t quietly empty.
The piece on device spares strategies that keep workers working covers how to size and position spares across sites.
How to track repairs so nothing gets lost
You can’t shorten what you can’t see. Every device that leaves service should have a record that shows where it is and how long it’s been there.
- Log each repair with the device’s serial number, site, fault, and date it left service.
- Track each stage, from shipped and received to diagnosed, repaired, and returned.
- Run a weekly aging report that lists every device out of service longer than your target.
- Pre-approve repair spending under an agreed limit, so quotes don’t sit waiting.
- Record the cause of each failure, so repeat problems show up.
The aging report is the most useful of these. It turns lost devices into a short list someone can act on.
Give one person responsibility for that list. A repair process that belongs to everyone tends to belong to no one, and devices drift back into drawers.
What to ask your repair provider
Whoever handles your repairs should be able to answer a few direct questions. If they can’t, the delays you’re seeing will keep happening.
Ask where devices are physically repaired and how long shipping takes each way. Ask how long a device typically waits before diagnosis, and what happens when a part is out of stock. Ask whether repaired devices come back ready to use, or need to be set up again by your team.
Finally, ask what status reporting you’ll get. A provider who can show where every device is, and how long it’s been there, makes the whole process easier to manage.
Fewer repairs is the other half
The fastest repair is the one that never happens. Proactive monitoring catches problems such as failing batteries and devices that keep dropping off the network before they become breakdowns.
The post on proactive support strategies that reduce device downtime covers what to watch for and when to act.
Where outside help fits
Running spares, repairs, and tracking well takes people, space, and logistics that many operations don’t have. That’s why devices end up in drawers.
Through lifecycle management, our in-house Canadian team handles repair logistics, spare pool management, and asset tracking as one process, so a broken device is swapped quickly and tracked until it’s back. Just know that it fits best for fleets spread across many sites. A single location with a few dozen devices may manage well with a local spare shelf and a simple log.
Questions we hear about device repairs
Why do enterprise device repairs take so long?
Most of the time is spent outside the actual repair. Devices wait at sites to be shipped, sit in transit and repair queues, wait for parts or quote approvals, and then need to be set up again before going back into service. Untracked devices can sit unnoticed between steps for weeks.
How can we keep workers working while devices are repaired?
Keep a pool of pre-configured spare devices at or near each site. When a device breaks, swap in a spare immediately and send the broken one for repair. As long as the pool is refilled after each swap, workers stay productive no matter how long the repair takes.
How many spare devices should we keep?
Size the spare pool from your own failure and loss rates, by site and device type, plus how long repairs and replacements take to arrive. Sites with harsh conditions, high turnover, or long shipping times need more. Review the numbers regularly, since failure rates rise as a fleet ages.
Where to start
Count every device that’s out of service right now and how long each has been gone. That list shows where repairs stall. Then put a charged spare at the sites with the longest waits, so the next failure becomes a swap instead of a lost shift.