A device rollout can look on track from head office and fall apart at the store, depot, or plant. The devices are the same everywhere, so when some sites go smoothly and others don’t, the difference is almost always the site.
If you’re an operations or regional leader watching a rollout succeed in one location and stall in the next, the fix is usually a short list of readiness gaps that nobody checked before the devices arrived.
This post covers why rollouts stall at the site level, what site readiness actually involves, what happens to the old devices, and a checklist to run before the next wave ships.
Why rollouts go well at some sites and badly at others
Rollout plans are usually built centrally, around the devices. Site readiness gets assumed, and every site is a little different in ways the plan doesn’t capture.
One site has strong Wi-Fi and a manager who prepared the team. Another has dead spots in the back room, nobody assigned to receive the shipment, and staff who first see the new devices when the old ones are taken away. Same devices, very different results.
The gaps are rarely technical failures. They’re things that needed doing at the site and weren’t on anyone’s list.
What site readiness actually involves
Site readiness covers everything that has to be true at a location for new devices to work on the first shift. It falls into a few areas.
Coverage. Devices need Wi-Fi or cellular coverage everywhere they’re used, including back rooms, loading docks, freezers, and yards. A coverage check at the front of the store says nothing about the receiving area.
The site survey FAQ for IT deployments covers what to test.
Power and charging. New devices may need different cradles, more outlets, or a new place to charge between shifts. That space has to exist before the devices do.
People. Someone needs to receive the shipment, check it, charge the devices, and hand them out. Staff need to know the new workflow before they need to use it.
Timing. Rolling out during a peak period, a stock count, or a short-staffed week will stall even a well-prepared site. Check each site’s calendar before setting its delivery date, since busy weeks differ by location.
Who signs for the shipment and who trains the staff
Two of the most common site-level failures are simple ownership gaps. The shipment arrives and nobody knows who’s responsible for it, or the devices are handed out and nobody shows staff what’s changed.
Name a site owner for every rollout wave. That person confirms the delivery date, receives and checks the shipment, makes sure devices are charged, and organizes a short walkthrough for staff. The post on planning a mobile device rollout covers how to build site ownership into the plan.
Devices that arrive ready to use make the site’s job much easier. If yours arrived needing setup, the post on why devices arrive at your sites unconfigured explains where that usually breaks.
What happens to the old devices during a swap
Old devices are the most neglected part of a rollout. They’re needed as a fallback for the first days, and then they hold data that has to be dealt with properly.
Keep the old devices working until the new ones are confirmed at that site. Then collect them, count them against your records, and send them for secure data wiping and retirement. In Canada, you remain accountable under PIPEDA for personal information on devices you control, so a box of old devices in a back room is a risk, not just clutter.
Here’s what actually happens when this step isn’t planned. Old devices stay at the site as unofficial spares, some go missing, and months later nobody can say what data is still on them. Our secure decommissioning service covers certified data wiping and chain-of-custody records for exactly that stage.
A site-readiness checklist for the next wave
Run this checklist with each site owner before devices ship. Any item that isn’t confirmed is a reason to delay that site, not the whole rollout.
- Wi-Fi or cellular coverage tested everywhere devices will be used
- Charging cradles, outlets, and storage space in place
- A named site owner to receive, check, and charge the devices
- A confirmed delivery date outside peak or short-staffed periods
- Staff walkthrough scheduled before or on the first day
- Help desk briefed that the site is going live
- A plan to keep old devices as a fallback, then collect and retire them
- French-language interfaces and instructions ready for Quebec sites
For multi-store operations, the retail device overview covers the store-specific factors, such as back-of-store coverage and seasonal timing.
Run a pilot site before the full wave
A pilot at one or two representative sites catches most site-level problems before they’re repeated across the rollout. Choose sites that reflect the hardest conditions you’ll face, not the easiest.
Pick a pilot site with real challenges, such as a large back room, cold storage, or a busy schedule. Run the full process there, from delivery to staff walkthrough to old-device collection, and note every gap. Then update the checklist and the rollout plan before the next wave ships.
Keep a short feedback loop with each site owner after go-live. A quick check-in at the end of the first week often surfaces small issues, like a missing charger or a login problem, before they turn into workarounds.
Track the rollout by site, not just by device count
Rollout reports often show how many devices have shipped. That number can look healthy while individual sites struggle.
Track each site’s status instead, including devices delivered, devices in use, staff trained, help desk tickets, and old devices collected. A site with devices delivered but few in use is stalled, even if the overall rollout looks on schedule. Spotting that early lets a regional leader step in while the fix is still small.
Where outside help fits
Site readiness is detailed, local work, and it multiplies with every location in a rollout. For a handful of sites, a central coordinator with a checklist can manage it.
For larger rollouts, it helps to have devices arrive ready to use, labelled by site and role, with old devices collected and retired as part of the same process. That’s the staging and decommissioning work our in-house Canadian team does. Just know that site readiness itself, such as coverage, power, and people, still needs an owner at each location.
Questions we hear about site-level rollout problems
Why do device rollouts go well at some sites and badly at others?
Because site readiness varies. Coverage, charging space, who receives the shipment, staff training, and timing differ by location, and central rollout plans often assume they’re in place. Checking each site against a readiness list before devices ship usually explains and prevents the difference.
What does site readiness involve for a device rollout?
Coverage tested where devices will be used, charging and storage in place, a named person to receive and prepare the devices, a delivery date outside busy periods, a staff walkthrough, a briefed help desk, and a plan for the old devices. Quebec sites also need French-language interfaces and instructions.
What should we do with old devices after a rollout?
Keep them working as a fallback until the new devices are confirmed at each site. Then collect them, reconcile them against your records, and send them for certified data wiping and retirement. Don’t leave them at sites as unofficial spares, since they still hold data you’re responsible for.
Where to start
Pick the site that struggled most in the last wave and walk through the readiness checklist with its manager. The gaps you find there are likely waiting at the next sites too. Fix them before the next shipment, and name an owner for every site in the wave.