The report should help its reader make a decision, not just admire a heatmap.
Lead with purpose and scope
State why the survey was performed and which site, floors and areas were included. Identify the complaint or planned change that prompted the visit. If the survey was only a small evaluation, say so rather than implying complete building coverage.
Describe the measurement type. Signal observations, application checks and internet speed tests answer different questions. Keep their results distinguishable so the reader knows what supports each conclusion.
Make the evidence traceable
Include the floor reference, point positions and relevant network filters. Preserve raw observations for authorized technical readers who need to inspect a summary. A color map without a legend or clear scope is difficult to verify.
Check that the export contains the intended survey and every relevant row. For a large report, inspect the final page as well as the first. A successful download is only the beginning of the review.
Separate findings from interpretation
Use concrete language for observations: what was measured and where. Explain a suspected cause as a hypothesis until it is supported by additional evidence. Note areas that were not accessible or did not produce a fresh reading.
State the next action and its owner. “Repeat this room after the AP change” is more actionable than “optimize the Wi-Fi.” If the evidence is inconclusive, specify the comparison that would make the next visit useful.
Take it into the field
- State purpose, site, floor and measurement scope.
- Inspect the legend, point count and final report page.
- Separate observations, hypotheses and next actions.
- Review location and recipient access before sharing.
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