← All articles

WiFi Site Surveys in Canada: 3 Key Moments, Security, and Sign Off

Canadian teams can run WiFi site surveys using Cisco and ISED targets, Ekahau field practices, and security checks, and know when to call a managed partner.

Technician checking Wi-Fi signal in an office

A Wi-Fi site survey delivers validated heatmaps, access point placement recommendations, and measurable pass/fail metrics that confirm the network supports its target applications. We run surveys at three key moments: before deployment to model coverage, immediately after installation to validate the build, and during troubleshooting when performance degrades. Success looks like documented coverage, capacity data, and a clear acceptance report, not a verbal assurance that “the Wi-Fi works fine.”

TL;DR:

  • Choose predictive surveys for early design, passive scans for interference, active testing for throughput and latency, and validation surveys for post installation acceptance.
  • Voice criteria include signal at negative 67 dBm, SNR of 25 dB, packet loss below 1%, jitter under 100 milliseconds, and channel use below 50%.
  • Use Android apps only for quick checks; acceptance testing needs laptop software with an external calibrated adapter, while spectrum analyzers locate interference from other equipment.
  • For 6 GHz deployments, confirm compliant equipment and Automated Frequency Coordination availability before design approval, since allowed frequencies and power levels vary by location.
247techify
Build a More Secure, Reliable Network
247Techify provides cybersecurity-first managed IT services for Canadian businesses, helping keep technology systems secure and efficient.
Visit 247Techify

Table of Contents

Types of Wi-Fi Site Surveys and How to Pick the Right One

Each survey type answers a different question, and choosing the wrong one wastes field time or produces data that cannot support a real acceptance decision.

A predictive survey uses floor plans and modeling software to estimate coverage before any hardware goes up. It works well for early budgeting and cabling plans, but it depends entirely on accurate wall attenuation values and known construction materials, so treat its output as a draft design, not a final answer.

A passive survey scans existing RF energy without associating to any access point. It is fast, requires minimal setup, and is the right tool for discovering rogue devices, mapping existing interference, or doing a quick pre-renovation baseline.

An active survey associates the client device to the network and measures real throughput, retries, and latency, which is why it is the preferred method for voice and high-density applications where a passive scan cannot reveal capacity problems.

A validation survey runs after installation to confirm the live network meets the acceptance criteria defined during scoping, closing the loop between design intent and field reality.

  • Predictive surveys estimate coverage before hardware is installed and are best for early design and budgeting.
  • Passive surveys scan RF energy without associating and suit rogue detection and interference baselining.
  • Active surveys associate to the network and measure throughput, retries, and latency for voice or data-heavy environments.
  • Validation surveys confirm the finished deployment against acceptance criteria established during scoping.

Scoping the Survey Before You Ever Open a Laptop

Every productive survey starts with a scope document that turns business requirements into numbers a technician can measure in the field. Skipping this step is the single most common reason surveys produce pretty heatmaps that nobody can act on.

  1. Translate each application’s service level into measurable RF and throughput targets, for example a VoWLAN rollout needing a defined cell-edge signal strength rather than a vague “strong enough” standard.
  2. Define in-scope and out-of-scope areas explicitly, including stairwells, parking structures, loading docks, and elevator shafts that are easy to forget until a device drops connection there.
  3. Collect wiring paths, available Power over Ethernet budget, and mounting constraints ahead of time so the survey does not stall waiting for facilities information.
  4. Set acceptance criteria in writing before data collection begins, covering signal strength, noise floor, throughput, and packet-loss thresholds so the final report has something concrete to compare against.

A scope document that names these constraints up front saves a second site visit later and gives the client a report they can actually sign off on.

Choosing Survey Tools: Phones, Laptops, and Spectrum Analyzers

Tool selection depends on what the survey needs to prove, not on what happens to be in the technician’s bag. Each option answers a different depth of question.

Phone-based survey apps running on Android give quick, portable signal readings and are useful for spot checks, client walkthroughs, or confirming a complaint before committing to a full survey. iOS restricts access to the raw RF data these apps need, so Android remains the practical mobile platform for this work. Phone surveys are fast but limited: they rarely expose channel utilization, true noise floor, or packet-level detail, so treat them as a screening tool rather than a substitute for a full survey.

Laptop-based predictive and active survey software paired with an external, calibrated Wi-Fi adapter produces the detailed heatmaps, SNR maps, and throughput data that acceptance testing requires. The external adapter matters because built-in laptop radios are inconsistent and rarely calibrated for survey accuracy.

Dedicated hardware like an Ekahau-style Sidekick combines a spectrum analyzer with calibrated Wi-Fi radios, which is the right tool when hunting for non-Wi-Fi interference or validating a voice-critical deployment where guesswork is not acceptable.

  • Phone apps: fast, portable, good for spot checks, weak on channel utilization and noise floor detail.
  • Laptop survey software with an external calibrated adapter: the standard for predictive and active surveys with full heatmap output.
  • Dedicated Sidekick-class hardware and spectrum analyzers: best for interference hunting and validation on voice or high-density networks.

Pro Tip: Always survey with the exact access point model and antenna configuration planned for production, since substituting hardware can skew the predicted coverage you hand to the client.

The Survey Workflow: Prepare, Collect, Analyze, Validate, Hand Off

A repeatable field process keeps survey quality consistent across technicians and sites, and each stage feeds directly into the next.

  1. Prepare. Gather accurate floor plans, confirm which SSIDs and test SSIDs will be used during collection, reserve PoE and power where needed, and decide in advance which survey type (predictive, passive, active, or validation) answers the scope’s requirements.
  2. Collect. Choose a collection method suited to the space: continuous surveys work well in open areas and long corridors at a steady walking pace, while stop-and-go sampling gives more precise readings in small rooms or dense environments where accuracy matters more than speed. Outdoor or campus-scale surveys benefit from GPS-assisted collection to keep location data accurate across large distances.
  3. Set up instruments. Configure the survey tool to scan the correct channels and SSIDs, point active tests at ping or iperf hosts that represent real traffic paths, and run a dedicated spectrum capture pass if voice or high-density capacity is part of the scope.
  4. Analyze and iterate. Review the resulting heatmaps for coverage holes, poor SNR pockets, and co-channel interference, then adjust access point placement or power settings and re-survey the affected areas rather than accepting a single pass as final.
  5. Document and hand off. Produce annotated floor plans, heatmaps covering signal strength, SNR, and channel utilization, and a remediation log that records what was found, what was changed, and what remains open.

On continuous surveys through long wings or corridors, Ekahau’s own guidance recommends periodically ending and restarting the survey segment, since interpolation errors compound over long, uninterrupted walks and shorter segments are easier to correct later. For multi-floor buildings, practical survey guidance also recommends taking samples directly above and below candidate access point mounts, because vertical signal coupling between floors is one of the most frequently overlooked causes of post-deployment surprises.

Pro Tip: Keep a running remediation log during collection rather than reconstructing it from memory afterward: it becomes the backbone of the final acceptance report.

AP Placement and Overlap Rules That Prevent Rework

Placement decisions made during the survey determine how much rework happens after installation, and a handful of consistent rules avoid most of it.

Industry guidance recommends roughly 20% cell overlap for 2.4 GHz and 15 to 20% overlap for 5 GHz coverage to allow clients to roam between access points without dropping connections. On a heatmap, that overlap shows up as adjacent cells sharing a defined signal boundary rather than a hard edge where coverage ends abruptly.

Antenna choice and mounting height should match the environment: ceiling-mounted omnidirectional antennas suit open offices, while warehouses with high racking often need directional antennas aimed down aisles, and exterior mesh deployments need hardware rated for the elements and mounted to avoid line-of-sight obstructions.

  • Avoid mounting access points inside metal ceiling cavities or directly behind structural beams, both of which block RF and create coverage gaps that a predictive model will not catch.
  • Avoid clustering too many access points on the same channel in adjacent spaces, which produces co-channel interference instead of added capacity.
  • Avoid stacking access points directly above one another on different floors without checking vertical bleed, since concrete and rebar do not block signal as consistently as assumed.
  • Stagger access point placement between floors where possible so that overlapping cells from the floor above or below do not concentrate on the same channel.

Numeric Targets and Pass/Fail Metrics for Acceptance Testing

Acceptance testing only works when the pass/fail line is a number, not an impression. Cisco’s VoWLAN design guidance gives technicians a defensible baseline to build acceptance criteria around.

Cisco’s published VoWLAN design targets call for a cell-edge signal strength of -67 dBm, a minimum signal-to-noise ratio of 25 dB, a noise floor near -92 dBm, packet loss under 1%, jitter under 100 milliseconds, and channel utilization below 50%. These numbers matter because a network can look fully covered on a basic signal map while still failing voice calls due to poor SNR or saturated channels.

Six numeric Wi-Fi acceptance thresholds

Data-only applications can tolerate looser packet-loss and jitter thresholds than voice, so the acceptance criteria defined during scoping should state which standard applies to which traffic type rather than applying one blanket target everywhere.

Capture these metrics during the active survey pass by running real traffic against a ping or iperf host, then overlay the results on the same heatmap used for signal strength so a reviewer can see coverage and performance together rather than as separate reports. A channel-utilization map read alongside the noise-floor map helps distinguish a congestion problem, which calls for better channel planning, from an interference problem, which calls for locating and removing the interfering source.

Post-Deployment Validation and Troubleshooting Checklist

A validation survey differs from a pre-deployment survey in one key way: it measures the network exactly as production devices experience it, using the final SSIDs, security settings, and access point firmware rather than a planning model.

  • Measure signal strength, SNR, and throughput at the same test points used during the original design survey so results are directly comparable.
  • Run a passive spectrum scan to detect rogue access points and non-Wi-Fi interferers such as microwave ovens, cordless phones, or industrial equipment that a predictive model could never have accounted for.
  • Adjust capacity where validation data shows saturation, whether that means adding access points, rebalancing channel and power plans, or re-anchoring SSIDs to different radios.
  • Document every change made during remediation and close out the project with a final acceptance report that ties back to the criteria set during scoping.

Cisco’s own site survey guidance notes that many deployments skip proper validation entirely, particularly for voice, and that wired-side quality of service settings deserve the same scrutiny as the wireless design itself.

Compliance Considerations for Regulated Industries

Healthcare and payment-card environments add a compliance layer on top of the standard coverage and capacity goals, and a survey for these sites needs to account for it from the scoping stage rather than retrofitting it afterward.

HIPAA-covered organizations need wireless segmentation that keeps clinical devices, guest traffic, and administrative systems on separate logical networks, which affects where access points sit relative to patient areas and how SSIDs map to VLANs. PCI-DSS environments carrying card data have similar segmentation expectations, plus stricter controls on rogue access point detection, since an unmonitored wireless network is a direct path into cardholder data environments.

Separate wireless zones across a healthcare floor

A survey for a regulated site should capture not just coverage and throughput but also whether the planned access point placement supports the segmentation the compliance framework requires, and whether rogue detection coverage reaches every clinical or point-of-sale area rather than just the open office space. Our network security checklist for small business covers the segmentation and monitoring controls that regulated deployments typically need alongside the physical survey work.

None of this replaces a formal compliance assessment, and organizations in regulated sectors should confirm their specific obligations with a qualified compliance advisor before finalizing a wireless design.

Building Security Into the Survey, Not Just the Network

A site survey is also a security exercise, since the passive and active scans that map coverage are the same scans that reveal unauthorized access points, open SSIDs, and misconfigured encryption left over from a previous installation.

During collection, flag any access point broadcasting that is not on the known inventory list, and treat it as a rogue until proven otherwise rather than assuming it belongs to a neighboring tenant. Passive spectrum scans run during the survey double as a baseline for ongoing rogue detection once the network goes live, since the survey technician has already mapped what normal RF activity looks like on-site.

After deployment, the access points and controllers themselves need the same hardening attention as any other network device: default administrative credentials changed, management traffic kept off the same VLAN as client traffic, and firmware kept current against known vulnerabilities. Guest networks deserve particular attention during scoping, since they are often the segment with the weakest isolation from internal systems. Our guest Wi-Fi setup checklist covers the segmentation steps that keep a guest SSID from becoming a path into business systems.

Treat the survey’s rogue-detection pass as the start of an ongoing monitoring habit rather than a one-time check, since new rogue devices can appear well after the original installation is complete.

Turning Survey Data Into a Better-Performing Network

Collecting clean data is only half the job. The value comes from how that data gets read and acted on.

Compare heatmaps against the acceptance criteria set during scoping rather than eyeballing color gradients for a general impression of “good enough” coverage. A cell that looks green on a basic signal-strength map can still fail if the same location shows poor SNR or high channel utilization on the overlay maps, so review all three together before approving a placement decision.

Look for patterns across problem areas rather than treating each weak spot in isolation: three unrelated coverage holes might share a common cause, such as the same type of wall construction or a single rogue device sitting on an overlapping channel. Re-survey any area where a fix was applied rather than assuming the adjustment worked, since access point power and channel changes can shift coverage in ways that are not always intuitive from the floor plan alone.

Keep the raw survey files and heatmaps on hand after the project closes. They become the baseline for the next troubleshooting call or capacity expansion, saving a full re-survey when only a partial check is needed.

How Wi-Fi 6, Wi-Fi 6E, and 6 GHz Change Survey Planning

Newer Wi-Fi standards add planning variables that did not exist in earlier surveys, particularly around the 6 GHz band.

Wi-Fi 6 improves efficiency in dense client environments through better scheduling, which means capacity surveys for high-density spaces like classrooms or open offices need to account for client count and application mix, not just raw coverage. Wi-Fi 6E and the move into 6 GHz spectrum introduce regulatory requirements that a 2.4 and 5 GHz survey never had to consider. In Canada, ISED’s RSS-248 standard governs RLAN devices operating across the 5925 to 7125 MHz band and requires SAR or APD testing depending on frequency range, along with testing through an ISED-recognized lab before equipment can be deployed.

Standard-power 6 GHz devices also depend on an Automated Frequency Coordination system, which uses geographic and licensed-service data to determine which frequencies and power levels are actually available at a given site. That means a 6 GHz survey plan can change depending on location, so confirming AFC availability and compliant equipment before committing to a 6 GHz deployment saves a redesign later.

What Our Field Team Prioritizes on Every Survey

Three priorities separate a survey that gets used from one that gets filed away: survey with the actual production access point model rather than a substitute, budget for spectrum analysis whenever voice or another critical application is in scope, and set acceptance metrics in writing before anyone starts walking the floor.

Predictive-only surveys are not enough for any site with unusual construction, high client density, or a voice deployment. If 6 GHz hardware is part of the plan, confirm it is compliant and AFC-registered for the deployment location before finalizing the design.

— 247techify Team

How We Support Your Wi-Fi Survey and Deployment Project

We approach every Wi-Fi survey and deployment with a cybersecurity-first lens, which means rogue detection, segmentation, and compliance considerations are built into the scope from day one rather than bolted on afterward. Our team backs that with live support around the clock and a rapid response when something needs attention after the network goes live.

247techify

Our Discovery engagement maps a current environment and its requirements before any survey work begins, and our Implementation service carries the design through installation, acceptance testing, and documented hand-off. For businesses that want ongoing monitoring and remediation after deployment rather than a one-time project, managed IT plans provide continuity. If your site includes wiring or rack planning alongside the wireless design, our network infrastructure services and resources on secure small office network design cover the cabling and cabinet side of the project, and for dense equipment rooms, practical rack space planning guidance is worth reviewing before the installation phase starts.

Ready to scope your next survey or deployment? Request pricing or book a discovery call and we will outline the deliverables for your site.

FAQ

Is there an app to measure Wi-Fi strength?

Yes, several Android apps provide real-time signal strength readings and basic heatmap generation, making them useful for quick spot checks or confirming a complaint before a full survey. iOS restricts the low-level RF access these apps need, so Android remains the more practical platform for mobile Wi-Fi measurement.

How do you conduct a site survey?

A site survey starts with scoping requirements and acceptance criteria, then moves through site preparation, data collection using continuous or stop-and-go methods, analysis of the resulting heatmaps, and a validation pass against the original targets. The process closes with documented deliverables, including annotated floor plans and a remediation log, so the findings can be acted on rather than just filed away.

What are the different types of wireless site surveys?

The four main types are predictive surveys, which model coverage before installation; passive surveys, which scan RF activity without connecting to the network; active surveys, which connect and measure real throughput and latency; and validation surveys, which confirm a finished deployment against acceptance criteria. Each type answers a different question, so the right choice depends on whether the goal is early planning, interference discovery, performance testing, or final sign-off.

Is there a free version of NetSpot?

Survey software vendors vary in how they structure free versus paid tiers, and feature limits change over time, so the most reliable way to confirm current availability is to check the vendor’s own site directly rather than relying on older reviews. Whatever tool is used, pair it with a calibrated external adapter for any survey where the results will support a formal acceptance decision.

What signal strength is good enough for a Wi-Fi deployment?

For voice and other latency-sensitive applications, Cisco’s design guidance targets a cell-edge signal strength of -67 dBm along with a minimum signal-to-noise ratio of 25 dB. General data traffic can tolerate a somewhat lower signal strength, but the acceptance criteria should state the target explicitly for each traffic type rather than relying on a single number for the whole site.

Sources