A useful survey connects a specific question to a position, a reading and a decision.
Start with the question
“The Wi-Fi is bad” is a starting point, not a survey brief. Identify the rooms, devices and activities affected. A video call that fails in one meeting room needs a different investigation from an entire building losing internet access. Write down what the user was doing and whether the problem is repeatable.
Choose a small initial scope. One floor or a handful of important work areas is easier to measure consistently than an entire property with no route or acceptance criteria. Decide what evidence would support your next decision before collecting it.
Prepare the floor and route
Use an up-to-date floor image with recognizable doors, corridors and room boundaries. Set its scale using a known distance. Mark installed access points where their positions are known; do not infer their physical position solely from a strong reading.
Plan stops at real work locations, transitions between rooms and the reported trouble spot. Include a comparison point that usually works well. A repeatable route makes the next survey more informative than a different collection of convenient stops.
Capture deliberately
In Wi-Fi Master Planner, prepare the site on the web and open the assignment on Android. At each stop, select where you are standing and capture an available fresh reading. Keep the device and its handling reasonably consistent across the route.
Treat permission failures, unavailable readings and stale scans as missing evidence. Do not fill gaps with a remembered value. If the connection to the service is unavailable, preserve the local queue and confirm synchronization when it returns.
Finish with an action
Inspect individual points as well as the coverage view. Separate observations from hypotheses: “we measured a weaker signal here” is different from “this wall caused it.” Export the results and choose one follow-up, such as checking an AP position or repeating the affected room under normal use.
A signal survey does not prove throughput, roaming quality or application performance. Add those checks separately when they are part of the original complaint. Repeat the same points after a change so the result can be compared.
Take it into the field
- Write one clear survey question.
- Prepare a scaled floor and a repeatable route.
- Capture fresh readings at known positions.
- Sync, review, export and choose one next action.
Put your next survey on the map.
Prepare a floor on the web, capture deliberate points on Android and review the observations in one place.
Create free account Explore the workflow