If your store, depot, or plant managers spend part of every shift rebooting scanners, hunting for chargers, and boxing up broken devices, you have an IT function you never planned for. You’re also paying manager wages for it.
Nobody decided this. It happens gradually at sites without local IT, because the person in charge is the one who gets the complaint when a device stops working.
This post covers how site managers end up doing device support, how to measure what it costs in your own numbers, and what central support with the right spares looks like instead.
How site managers end up doing device support
Most frontline sites don’t have IT staff, and the help desk is somewhere else. When a scanner won’t connect or a handheld dies mid-shift, the worker goes to the nearest person with authority, and that’s the site manager.
Calling the help desk takes time and may not fix it quickly. So the manager tries a reboot, swaps batteries, borrows a device from another role, or resets it. Over time, they become the local expert, and the devices become their problem.
It doesn’t show up anywhere as a job. It shows up as managers who are always behind on the work they were hired to do.
Signs device support has drifted to your sites
The drift is easy to miss from head office, because the help desk sees fewer tickets, not more. Sites stop calling when they’ve learned to fix things themselves.
Look for the patterns instead. Managers mention devices in every regional call, and some sites have far fewer tickets than others of the same size. Spare devices appear and disappear without records, and broken devices arrive back in batches months after they failed.
The strongest sign is a site manager who knows the device admin passwords. When that’s true, support has already moved to the site, whether anyone planned it or not.
What it costs, measured in your own numbers
The cost is real, but it’s different at every operation, so build it from your own data rather than an industry figure. A short survey of your site managers is enough to start.
Ask each manager how many hours a week they spend on device issues, including troubleshooting, swaps, chasing returns, and calls to the help desk. Multiply by the number of sites and the loaded hourly cost of a manager. That’s the direct cost.
Include the hours outside the normal shift. Managers at sites that run early mornings, nights, or weekends often handle device problems when nobody else is available, and that time rarely gets counted.
Then add what those hours displaced. Managers who are fixing devices aren’t coaching staff, serving customers, managing safety, or running the floor. That cost is harder to count, but it’s usually the one regional leaders notice first.
What actually happens when sites fix devices themselves
Local fixes feel efficient in the moment. Over time, they create problems that cost more than the original issue.
Here’s what actually happens in many fleets. Spares end up in a drawer with no record, devices get factory reset and drop out of central management, staff share logins to get through a shift, and broken devices go into a box that may sit for weeks before anyone ships it. Each workaround solves today’s problem and makes tomorrow’s harder to see.
The result is a fleet that head office believes is managed and the sites know isn’t.
What sites should and shouldn’t do
Site managers shouldn’t be technicians, but they shouldn’t be helpless either. A clear split lets them get a worker back up quickly without creating new problems.
- Sites should keep spares charged, swap a broken device for a ready spare, report the problem through one channel, and send the broken device back in the provided packaging.
- Sites shouldn’t reset or reconfigure devices, repair them, share logins, or ship devices without a tracked return.
Write the split down and post it where devices are kept. A one-page card does more than a policy nobody reads.
What central support looks like
Central support works when it’s faster for the site than fixing things locally. That means remote tools, a quick answer, and a replacement already on site.
A mobility help desk can see the device through your management platform, push a fix, restart an app, or lock and wipe a lost device without anyone on site touching it. The overview of an enterprise mobility help desk covers what that support should include.
Set a response target the sites can rely on, such as how quickly a call is answered and how quickly a replacement arrives when a swap isn’t possible. If calling the help desk is reliably faster than fixing it locally, managers will stop fixing it locally.
For Canadian operations, support has to reach every site in a language staff can use. Quebec locations need French-language support, and remote sites need help that doesn’t depend on someone driving out.
Spares at the site, repairs at the centre
The fastest fix for a broken device is a working one already on the shelf. A small, managed spare pool at each site turns a device failure into a two-minute swap instead of a manager’s afternoon.
Keep the pool small and visible. A labelled shelf with charged devices and a simple sign-out sheet works better than a drawer that only the manager can find.
The broken device goes back to a central repair process, and a replacement spare goes back to the site. The site never repairs anything. The piece on device spares strategies that keep workers working covers how to size and manage those pools.
Where outside help fits
Building central support yourself is possible if you have the people and the logistics. Many operations with dozens or hundreds of retail stores, depots, or plants don’t, which is why the work drifted to site managers in the first place.
Through lifecycle management, our in-house Canadian team provides help desk support, spare pool management, and repair logistics, so site managers hand off the problem instead of solving it. Just know that it fits best for multi-site operations. A single site with a capable on-site IT person may not need it.
Questions we hear about site-level device support
How do sites without IT staff support mobile devices?
Usually informally, with site managers or experienced staff troubleshooting devices themselves. A better model combines remote support from a central help desk, a small charged spare pool at each site for quick swaps, and a tracked process for sending broken devices back for repair. Sites swap and report, and the centre fixes.
How much time do managers spend on device problems?
It varies widely by operation, so measure it directly. Ask site managers to estimate weekly hours spent troubleshooting, swapping, and chasing device issues, then multiply by the number of sites and the loaded hourly cost. Add the work those hours displaced, such as coaching, customer service, and safety.
What is a site spare pool?
A site spare pool is a small stock of ready-to-use devices kept charged at each location. When a device breaks, staff swap in a spare immediately and send the broken one back for central repair. A replacement spare is then sent back to the site, so the pool stays full.
Where to start
Ask five site managers how many hours they spent on devices last week, and what they’d have done with that time instead. Their answers will tell you whether this is a minor irritation or a cost worth fixing. Then define what sites should and shouldn’t do, and make sure every site has a charged spare to swap in.