Wireless Site Survey Checklist for Better Wi-Fi

A wireless network can look excellent on a floor plan and still fail where people work. A conference room fills, a cart enters an elevator, or a client roams between access points, and the real design assumptions are exposed. This wireless site survey checklist helps network teams collect the evidence needed to design, validate, and document Wi-Fi that performs under actual business conditions.

The checklist is not a substitute for engineering judgment. A small office with predictable usage can often use a lighter process than a hospital, warehouse, campus, or high-density venue. The goal is to match the survey scope, measurement method, and acceptance criteria to the applications the network must support.

Start With Requirements, Not Access Point Locations

A survey should begin with a clear statement of what the wireless network must deliver. Access point placement is a design outcome, not the starting point. Meet with application owners, facilities teams, security stakeholders, and operational leaders before collecting RF data.

Document the primary client types and applications. Voice handsets, barcode scanners, medical devices, tablets, laptops, cameras, and guest devices do not behave the same way on Wi-Fi. Determine which applications are business-critical, whether traffic is real-time, and what level of interruption users can tolerate during roaming.

Establish measurable targets for coverage, capacity, and quality. These may include minimum signal level, signal-to-noise ratio, maximum channel utilization, required data rates, roaming thresholds, packet loss, latency, and jitter. A design intended for basic office productivity may accept different thresholds than one supporting voice, industrial mobility, or clinical workflows.

Also confirm the physical and operational constraints: available cabling paths, switch capacity, PoE budgets, mounting restrictions, plenum requirements, security policies, and maintenance windows. These details often determine whether a sound RF design can be deployed as designed.

Wireless Site Survey Checklist: Pre-Survey Inputs

Before arriving on site, confirm that the survey team has current documentation and the right test resources. Missing floor plans or outdated drawings can create expensive rework, particularly when sites have additions, mezzanines, shelving, or revised room layouts.

Use this pre-survey checklist to organize the work:

• Obtain scaled floor plans for every area in scope, including outdoor spaces, storage areas, stairwells, loading docks, and mechanical rooms where coverage is required.

• Review construction details, such as concrete walls, low-E glass, metal racking, elevators, fire doors, and dense inventory that may attenuate or reflect RF energy.

• Identify existing access points, network closets, cabling routes, switch models, uplink speeds, PoE capabilities, and any known network issues.

• Define user density by location and time of day, not just total headcount. A training room and cafeteria may create short, intense capacity demands.

• Confirm the target wireless standard, preferred bands, client capabilities, authentication method, VLAN and segmentation requirements, and guest access policy.

• Schedule access to secure areas and coordinate around production, patient care, classes, events, or other activities that could affect measurements.

For new deployments, a predictive survey can establish an initial design from a calibrated floor plan and modeled building materials. For a refresh or troubleshooting engagement, it should usually be followed by an on-site validation survey. Predictive modeling is valuable, but it cannot fully account for installed materials, neighboring networks, changing inventory, or unexpected noise sources.

Inspect the Environment Before Measuring RF

A walkthrough gives the engineer context that a map alone cannot provide. Verify dimensions, ceiling heights, wall types, likely access point mounting locations, and access restrictions. Photograph unusual construction features and record areas where devices cannot be mounted at the intended height or orientation.

Warehouses deserve special attention. Racking, product levels, aisle widths, and forklift traffic can materially change propagation and multipath. A warehouse surveyed while empty may not represent the environment once inventory is in place. In healthcare and education, thick walls, specialized equipment, secure zones, and high-density gathering areas can create similar gaps between plans and real conditions.

During the walkthrough, look for non-Wi-Fi interference sources. Bluetooth devices, wireless video systems, microwave ovens, cordless equipment, industrial controls, and poorly shielded electronics may affect the 2.4 GHz or 5 GHz bands. Wi-Fi measurements show symptoms; spectrum analysis can help identify the source of persistent non-Wi-Fi energy.

Choose the Right Survey Method

Most projects use one or more of three methods: predictive, passive, and active surveying. Each answers a different question.

A predictive survey estimates coverage and capacity before hardware is installed. It is efficient for budgeting, early design, and identifying potential access point locations. Its accuracy depends on quality inputs, correct material assumptions, and realistic antenna and transmit-power settings.

A passive survey listens to the RF environment. It measures observed signal strength, noise, channel use, neighboring access points, and coverage overlap. This method is well suited to validating RF conditions and identifying co-channel or adjacent-channel issues.

An active survey connects a test client to the network and measures the service users receive. It is the stronger choice when validating throughput, latency, jitter, packet loss, DHCP, DNS, authentication, and application reachability. For voice or other real-time traffic, active testing should reflect the expected client type and roaming behavior whenever possible.

Using Ekahau survey and design tools can provide a consistent workflow for predictive modeling, passive validation, active testing, heat maps, and project documentation. The value is not just a visual map. Properly configured survey data gives teams defensible evidence for design decisions and acceptance testing.

Validate Coverage, Capacity, and Roaming

Coverage is only one element of wireless performance. A client may detect an SSID at a low signal level yet still experience poor application performance, delayed roaming, or unusable capacity. Validate against the requirements defined at the beginning of the project.

Check the intended bands separately. A strong 2.4 GHz signal does not confirm usable 5 GHz or 6 GHz coverage. Verify that channel plans, channel widths, transmit powers, and minimum basic rates support the client population without unnecessarily increasing contention or creating oversized cells.

Capacity validation should focus on the busiest locations and realistic demand. Test areas where users gather, such as conference rooms, classrooms, waiting areas, auditoriums, and production zones. Review channel utilization, airtime demand, retry rates, and client distribution. Adding access points can improve capacity, but it can also increase co-channel contention if channel reuse and power levels are not engineered carefully.

Roaming requires its own test path. Walk the routes used by voice users, mobile workers, carts, or scanners, and record whether clients maintain connectivity as they transition between access points. Poor roaming can result from coverage gaps, excessive overlap, inconsistent SSIDs, authentication delays, client driver behavior, or controller configuration. The fix depends on the evidence, not on a single signal-strength reading.

Verify the Wired Foundation

Wireless troubleshooting often leads back to the wired network. Confirm that each access point receives the expected PoE class and that switch ports negotiate at the intended speed. A modern access point connected through an undersized uplink, a damaged copper run, or an overloaded switch can create performance symptoms that resemble RF problems.

Validate VLAN assignments, DHCP scope capacity, DNS resolution, gateway reachability, authentication services, firewall policy, and internet or WAN paths where relevant. For critical deployments, capture baseline performance from the access layer through the network core. Network visibility platforms and packet analysis can shorten the time required to separate an RF issue from a transport, service, or application issue.

Document Results and Define Acceptance

A survey deliverable should allow another engineer to understand what was measured, why decisions were made, and whether the installation met its stated requirements. Include floor plans, access point locations, mounting details, channel and power settings, cable identifiers, survey paths, heat maps, assumptions, and exceptions.

Document areas that fall outside the target and explain whether they are acceptable. A stairwell may not require the same service level as a patient room or warehouse aisle. Transparency prevents an acceptance report from becoming a collection of attractive maps with unclear operational meaning.

Finish with a remediation plan that ranks findings by business impact. Address failed coverage or roaming requirements first, then capacity risks, interference, configuration inconsistencies, and future expansion needs. Keep a baseline report after deployment so the team can compare conditions when the environment, client mix, or application demand changes.

A well-run survey gives the organization more than an access point count. It provides a practical record of design intent, measured performance, and the actions required to keep Wi-Fi aligned with the work people depend on every day.