The key idea

A short, precise record is more useful than a folder of screenshots with no explanation.

Write down the user’s task

Start with the application or activity that failed, the device involved and the real-world position. Ask what success would look like. Avoid translating every complaint into “low signal” before collecting evidence.

Record whether the symptom is repeatable and whether it affects other devices or locations. These simple distinctions help the next person choose a relevant test instead of restarting the investigation from the beginning.

Keep observation and explanation separate

A reading at a named floor position is an observation. A suspected source of interference or a misplaced AP is an explanation that may need additional testing. Put them in separate sentences so a later reader can tell which parts are established.

Include the BSSID and band when they matter to a comparison, and note the device used. If an area was inaccessible or a scan was unavailable, record the gap. Missing evidence should remain visible rather than becoming an assumed good result.

Record each change and its owner

When a network administrator makes an adjustment, note what changed and why. Preserve the baseline survey before collecting the follow-up. If several things changed together, acknowledge that you may not be able to attribute the outcome to only one of them.

Keep the next action specific. Identify the location to revisit, the comparison to make and the person responsible. A clear handoff prevents the same preliminary questions from consuming every visit.

Build a record someone else can repeat

Retain the floor reference, route and scoped report in the authorized project records. Use consistent names for sites and floors. Link the report to the troubleshooting question rather than sharing it as an unexplained attachment.

Wi-Fi Master Planner keeps completed survey observations available for review and comparison. Pair that evidence with concise project notes in your team’s normal workflow. The aim is a repeatable investigation: another person should be able to understand what you measured, what changed and what still needs an answer.

Take it into the field

  • Describe the task, device and position.
  • Separate measurements from suspected causes.
  • Preserve the baseline and record authorized changes.
  • Give the next visit a specific question and owner.

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