You’ve heard the term in vendor conversations, seen it in deployment RFPs, or watched a past rollout go sideways and wondered if someone should have walked the site first. This resource answers what a site survey actually involves, what it covers, why it matters before deploying mobile devices, and when organizations should invest in one. If you’re an IT manager planning device rollouts across Canadian facilities—warehouses, retail stores, healthcare sites, or field locations—this is the practical guide you need.
What is a site survey in IT deployment?
Picture this: you’ve been tasked with deploying 150 Zebra handheld scanners across a 200,000-square-foot distribution centre. The devices are spec’d, the budget is approved, and procurement is ready to pull the trigger. Before a single scanner leaves the staging facility, someone needs to physically walk that floor and answer a simple question—can this site actually support these devices?
That assessment is the site survey.
A site survey is the on-the-ground evaluation of a physical facility before mobile devices are deployed there. It’s not a checkbox exercise or a form someone fills out from their desk. It’s a technician walking the aisles, checking signal strength at operating height, counting electrical outlets, examining mounting surfaces, and watching how workers actually move through the space.
Zebra Technologies’ deployment best practices identify site surveys as a prerequisite step for enterprise mobile rollouts, noting that RF environment assessment and physical infrastructure validation prevent the majority of post-deployment support issues. This isn’t vendor caution—it’s hard-won operational wisdom.
Here’s what actually happens when you skip this step: devices work flawlessly in the staging lab, then drop Wi-Fi the moment they hit the warehouse floor. Nobody checked that the metal racking in aisle 14 creates an RF shadow zone. Nobody noticed that the loading dock has no power outlet within 30 metres of where the vehicle-mounted computers need to charge. These discoveries cost tens of thousands of dollars to remediate after deployment. They cost a fraction of that to catch beforehand.
The site survey is where you find these problems while they’re still cheap to fix.
What does a site survey typically cover?
Most people assume a site survey is just about Wi-Fi signal strength. That’s the most visible component, but a thorough survey covers far more ground—literally.
Wireless and network infrastructure
This is the component everyone thinks of first. A proper wireless assessment maps Wi-Fi access point placement, measures signal strength throughout the facility, identifies RF interference sources (metal structures, competing wireless systems, industrial equipment), checks cellular signal availability for devices that need it, and evaluates whether the existing network bandwidth can handle the device density you’re planning to deploy.
The critical nuance: signal strength measured at desk height tells you nothing about signal strength at scanner operating height—waist level in a pick aisle, chest height on a forklift, or ground level at a receiving dock. Ekahau reports that 80% of wireless network issues stem from environmental and RF design problems, not equipment failure. The Wi-Fi infrastructure may be perfectly functional in isolation. The problem is how it interacts with the physical environment where devices actually operate.
Power and electrical infrastructure
Where are the outlets? Do they match where you need charging stations? Can the circuits handle the load of twelve charging cradles in a back room that was wired for two?
A power assessment documents outlet locations, evaluates circuit capacity, plans charging station placement, and identifies backup power availability for mission-critical devices. For Canadian facilities—particularly older warehouses, hospitals, and retail locations—legacy electrical systems often can’t support modern device density without upgrades that need to be budgeted before procurement begins.
Physical environment and mounting
This component covers the tangible, physical infrastructure that affects how devices will be installed and how they’ll perform over time. The assessment examines wall and surface materials for mounting hardware (drywall, concrete, metal studs all require different approaches), ambient temperature and humidity ranges, dust and moisture exposure, lighting conditions for barcode scanning, and physical security of device storage areas.
Canadian temperature extremes matter here. A site survey for a Winnipeg distribution centre in January needs to assess unheated loading docks and outdoor staging areas where temperatures hit -20°C or colder—conditions that affect battery life, touchscreen responsiveness, and display visibility in ways that don’t show up in a climate-controlled staging lab.
Workflow and user environment
This is the component most often skipped—and the one that causes the most Day 2 problems.
A workflow assessment watches how workers actually move through the space: where devices will be used versus stored, handoff points between shifts, ergonomic considerations for device placement, and the actual paths associates travel during their work.
Here’s the operational reality: a site survey that only checks infrastructure without observing workflow will miss that the pick path takes associates through a freezer section where touchscreens stop responding below -10°C. It won’t catch that the receiving dock workflow requires scanning while standing on a forklift—meaning the device needs a different mounting solution than the desktop cradle someone spec’d from a floor plan.
The physical infrastructure can be perfect. If the devices don’t work the way people actually work, you’ll inherit a stream of support tickets that no amount of technical troubleshooting will resolve.
Why does a site survey matter before deploying mobile devices?
Most deployment failures aren’t device failures—they’re environment failures.
The scanner works perfectly in the staging lab. It passes every QA test. Then it drops Wi-Fi in the warehouse because nobody checked the RF environment where it would actually be used. The barcode reader times out because the facility’s legacy network can’t handle 200 concurrent device connections. The charging cradles arrive and there’s nowhere to plug them in.
These aren’t edge cases. They’re the predictable consequences of deploying devices into environments you haven’t assessed.
When you consider that VDC Research reports unplanned mobile device downtime costs enterprises an average of $20,000–$30,000 per site annually, with environment-related connectivity issues being a leading cause of recurring support tickets, the math becomes unavoidable. For a Canadian retailer or logistics operator with 40+ locations, that’s potentially over $1 million annually in productivity loss—much of which traces back to environment issues a site survey would have caught.
The most expensive site survey is the one you do after deployment. We’ve seen organizations deploy 500+ devices across a retail chain only to discover that half the locations have legacy Wi-Fi infrastructure that can’t handle the device density. The remediation cost—new access points, re-staging devices, re-visiting sites—dwarfs what the original survey would have cost.
These environment failures also create a downstream burden for whoever manages lifecycle management post-deployment. When devices consistently drop connections at specific locations, or when battery life mysteriously underperforms at northern sites, the support team inherits problems that weren’t caused by the devices and can’t be solved by device-level troubleshooting. The root cause is an environment that was never properly assessed.
The question isn’t whether you can afford to do a site survey. It’s whether you can afford to skip one and absorb the consequences across every location, every device, and every support ticket for the life of the deployment.
That raises the practical question of timing—when exactly in the deployment lifecycle should this assessment happen?
When should a site survey be conducted?
The site survey happens before devices are staged—not after they’re ordered, and certainly not after they’ve shipped. In the deployment timeline, it sits between device selection and device configuration: you’ve completed your strategic sourcing process and know what hardware you’re deploying, but you haven’t yet built the software image or ordered the accessories.
The trigger scenarios are straightforward:
- Before any new multi-site deployment
- Before a technology refresh where device form factor or connectivity requirements change
- When expanding operations to a new facility
- When switching wireless infrastructure providers
- When deploying vehicle-mounted or fixed-mount devices for the first time
Organizations doing a like-for-like device refresh often assume they can skip the survey because “nothing has changed.” But the warehouse added two new racking rows last quarter. The IT team upgraded the access points and changed the SSID naming convention. The new devices use a different Wi-Fi chipset than the old ones. “Nothing has changed” is almost never true—and the exceptions create the support tickets.
For organizations deploying across multiple Canadian provinces, timing becomes even more critical. A site survey conducted in July won’t capture the -20°C conditions that affect device performance in a Manitoba distribution centre in January. Seasonal validation may be necessary for facilities where temperature extremes are part of the operating environment.
Who conducts a site survey?
A site survey can be conducted by internal IT staff, by the device OEM’s professional services team, or by a managed mobility services provider as part of a broader deployment engagement. Each approach has trade-offs.
Internal teams know the operational environment intimately—they understand workflow patterns, legacy infrastructure quirks, and organizational politics around facility changes. But they may lack RF survey tools, deployment-specific expertise, and the time to conduct thorough assessments across dozens of locations while managing their existing responsibilities.
OEM professional services teams—Zebra, Honeywell, and others offer these—bring purpose-built survey tools and deep device expertise. They know exactly what RF conditions their hardware requires. But they may not understand your specific workflows, and their scope typically ends at the survey deliverable. The findings land in a PDF that someone else needs to translate into staging decisions.
Managed mobility providers integrate the site survey into the full deployment lifecycle. Survey findings feed directly into device configuration, staging, and deployment planning—no handoff documentation, no translation step, no gap where critical details get lost.
The best site surveys are conducted by teams who will also be responsible for staging and deploying the devices. When the survey team and the deployment team are different organizations, the findings that matter most—the workflow observations, the infrastructure edge cases, the site-specific quirks—tend to get summarized away in handoff documentation. The technician who noticed that associates cut through the freezer section doesn’t write that down because it seemed obvious at the time. Six months later, support tickets start coming in about touchscreens that stop responding, and nobody connects the dots.
How does a site survey connect to staging and deployment?
A site survey produces a set of findings. Those findings need to go somewhere—specifically, into the staging and deployment plan that determines how each device is configured for each location.
This is the step where most organizations lose value. The survey happens. The findings get documented. Then a different team—sometimes in a different company—builds the device configuration without access to the context behind those findings. The Wi-Fi profile gets set to a generic configuration because nobody flagged that three locations use a different wireless vendor. The charging cradles ship with standard power adapters because nobody noted that two sites have legacy electrical that requires a different solution.
When survey findings translate directly into staging decisions, the connection looks like this:
Survey findings about the RF environment inform Wi-Fi profile configuration per site—different SSIDs, different band preferences, different roaming thresholds depending on what each facility’s infrastructure requires. Mounting and accessory requirements from the physical assessment determine kitting specifications—which cases, which holsters, which vehicle mounts ship to which locations. Power infrastructure findings affect charging cradle orders and placement plans. Workflow observations influence MDM policies and app layouts—lockdown configurations that match how workers actually use the devices in each environment.
For organizations working with a managed mobility services provider like PiiComm, the site survey feeds directly into the staging process. PiiComm’s Canadian staging facilities configure devices based on site-specific findings—a “Gold Image” tailored to each location’s infrastructure, not a one-size-fits-all build. The technician who walks the floor in Edmonton is part of the same organization that configures the devices in the staging facility. No handoff gap. No lost context.
PiiComm has staged deployments where the site survey revealed that three of forty retail locations had a different Wi-Fi vendor than the other thirty-seven. Without that finding, those three locations would have received devices configured with the wrong wireless profile—and the IT manager would have spent a week troubleshooting connectivity tickets instead of managing the rollout.
For organizations deploying in Quebec, the site survey also captures bilingual requirements that affect device configuration—French-language user interfaces, localized applications, and compliance with language legislation that the staging team needs to know before building the Gold Image for those locations. PiiComm’s bilingual service desk and Canadian staging operations handle this as a standard configuration requirement, not a translation afterthought.
Learn more about how PiiComm plans and executes enterprise mobile deployments across Canadian facilities.
Frequently asked questions
How long does a site survey take?
Duration depends on facility size and complexity. A single retail location typically requires 2–4 hours. A 500,000-square-foot distribution centre may need a full day or more, particularly if RF spectrum analysis is included. Multi-site deployments often stage surveys over several weeks to accommodate facility access schedules.
How much does a site survey cost?
Costs vary based on scope. Standalone RF surveys from specialist firms range from $1,500–$10,000+ per site. When conducted as part of a managed deployment engagement, the survey cost is typically bundled into the overall project rather than billed separately—making the economics more favourable for multi-site rollouts.
Can a site survey be done remotely?
Partially. Network topology review and floor plan analysis can happen remotely. But the physical environment—RF interference, power infrastructure, mounting surfaces, temperature conditions, and workflow observation—requires an on-site visit. Ekahau’s best practices confirm that remote-only surveys miss the environmental factors causing most deployment issues.
What tools are used in an IT site survey?
Professional surveys use RF spectrum analysers, Wi-Fi heat mapping tools (Ekahau, NetSpot), signal strength metres, laser distance measurers for mounting planning, and thermal sensors for environments where temperature affects device performance. Consumer-grade tools miss the detail required for enterprise deployments.
Do I need a site survey for a device refresh?
Yes—if the new devices have different connectivity requirements, different form factors requiring new mounting hardware, or different power requirements. Even a like-for-like refresh warrants a brief site validation to confirm nothing in the physical environment has changed since the original deployment.
What happens if I skip the site survey?
The most common consequences: Wi-Fi dead zones causing device disconnections, insufficient power infrastructure for charging, mounting hardware that doesn’t fit actual surfaces, and workflow disruptions from devices placed in locations that don’t match how workers move through the space. These surface as Day 1 support tickets and ongoing productivity loss that VDC Research estimates at $20,000–$30,000 per site annually.
The survey that saves the deployment
A site survey doesn’t feel urgent until you’re troubleshooting connectivity tickets at 2 a.m. the week after go-live. It doesn’t seem necessary until you’re explaining to leadership why the deployment timeline slipped by six weeks because half the locations needed infrastructure upgrades nobody anticipated.
The organizations that deploy mobile devices successfully at scale have learned—often the hard way—that the site survey isn’t a preliminary step you can shortcut. It’s the foundation that every subsequent decision builds on. Get it right, and the devices work the way they’re supposed to from Day 1. Skip it, and you’ll do the survey anyway—just after the damage is done, at ten times the cost, with an IT team that’s already exhausted from fighting fires.
Have questions about planning a device deployment? Ask EMMA, PiiComm’s managed mobility AI assistant—built to answer the operational questions that come up before the first device ships.