I have reviewed hundreds of wireless site survey reports over the past 25 years. Notably, most of them share one common trait. They look polished and say almost nothing useful.
The problem is not the tools. Ekahau, iBwave, and similar professional platforms produce clean, colorful heatmaps. However, a heatmap is not a recommendation. It is a picture. What matters is the analysis behind it, and too many reports stop at the picture.
If your organization is planning a Wi-Fi deployment, upgrade, or post-installation validation, you need to know how to evaluate what you are reading. Here is what a credible wireless site survey report should contain.
The Survey Methodology Must Be Explicit
Before reading a single data point, look for a methodology section. Specifically, the report should identify what hardware collected the data, what applications drove the survey requirements, and how many measurement points were captured per area.
Furthermore, the report should state what signal thresholds the engineer applied as pass/fail benchmarks. An RSSI of -70 dBm may be acceptable for basic email but completely inadequate for VoIP or real-time inventory systems. Consequently, if the report does not tie its benchmarks to your actual application requirements, the numbers are meaningless.
Additionally, the survey type matters. Three distinct types exist: a passive survey captures received signal levels, an active survey measures actual throughput, and a predictive survey models coverage before any hardware is installed. Each serves a different purpose, and a report that does not identify which type was conducted is missing critical context from the start.
Heatmaps Are Starting Points, Not Conclusions
Coverage heatmaps are useful visualization tools. However, a good report does not just show you where signal exists. It shows you where signal is adequate for your specific workloads.
For example, a warehouse environment running voice-over-Wi-Fi forklift headsets needs a minimum RSSI of -67 dBm and an SNR above 25 dB at every point in the facility. A heatmap showing -72 dBm looks acceptable on screen but represents a failed deployment for that use case. In practice, the gap between covered and performing is the most common failure point I see in the field.
Consequently, the report should include co-channel interference analysis. Overlapping channels reduce throughput significantly. Furthermore, poor channel planning in dense environments causes performance problems even when signal strength appears fine. If the report does not address channel reuse, push back.
Moreover, roaming analysis matters in any environment where devices move. The report should confirm that roaming thresholds are set correctly and that no coverage gaps exist at roaming boundaries. Missing this step leads to sticky client problems and dropped VoIP calls.
Recommendations Must Be Specific
In my experience, the recommendations section is the weakest part of most survey reports. Too often it reads as a list of generic best practices rather than site-specific guidance.
Ultimately, a strong report ties every finding to a concrete corrective action. Therefore, if the report identifies a coverage gap near a loading dock, it should specify exactly where an additional AP belongs, what mounting height is appropriate, and what channel it should run on.
Similarly, if the report flags interference from adjacent networks or rogue devices, it should prescribe specific mitigation steps. Noting a problem without recommending a solution is documentation. It is not consulting.
Additionally, the report should include a validation step. After any remediation work, a post-installation survey confirms that the changes achieved the intended outcome. If your vendor does not include this in their scope, ask for it. That step is the difference between a completed project and a verified one.
When to Commission a New Survey
Network environments change over time. Specifically, physical renovations, new equipment, furniture changes, and shifts in device density all affect RF performance. Generally, the following situations each warrant a fresh survey: a major physical renovation, a change in application requirements such as adding VoIP or real-time video, a significant increase in device density, or persistent user complaints that standard troubleshooting cannot resolve.
In practice, most enterprise environments benefit from a re-survey every three to five years even without major changes. RF conditions drift gradually and problems accumulate well before they become obvious to users.
A wireless network is an engineered system. Therefore, like any engineered system, it requires periodic inspection to confirm it still performs as designed. Neglecting that step produces the kind of performance failures that are expensive to diagnose and disruptive to fix.
At Baiden Group, RF site surveys are a core part of what we do. We work with enterprises across Canada to validate existing networks, design new deployments, and identify root causes of persistent performance problems. Have questions about how these developments affect your network? Reach out to the Baiden Group team.