WiFi site survey checklist before you start
WiFi site survey checklist before you start
Use this WiFi site survey checklist to prepare floor plans, devices, access, survey goals, AP notes, and reporting requirements before field work.
Most bad surveys fail before the walkthrough begins. The equipment may be fine. The software may be fine. The problem is usually scope: missing floor plans, no clear requirement, unknown device types, rushed access, or no agreement on what the report needs to answer.
Use this checklist before a WiFi survey, heatmap validation, or Ekahau Sidekick data collection project.
1. Define the survey objective
Write the goal in one sentence. Examples:
- validate a new office WiFi deployment
- troubleshoot scanner drops in warehouse aisles
- plan AP placement before cabling
- verify coverage in conference rooms
- collect data for a post installation report
- compare expected predictive design against measured performance
The objective determines how the survey is walked, what data matters, and what the report should contain.
2. Gather floor plans
Before survey day, collect:
- current floor plans for every area in scope
- a known measurement for scale calibration
- floor names and room labels
- warehouse rack layout if applicable
- ceiling height notes
- areas excluded from scope
- outdoor areas or dock/yards if included
Do not treat floor plans as a formality. Survey software depends on accurate map scale. Ekahau’s iOS map import documentation specifically notes that photos of physical maps can be distorted by camera perspective or lens distortion, which can affect calibration. For PacketScout projects, that means a clean digital plan is usually better than a rushed photo.
3. Document the current network
If APs are already installed, gather:
- AP models
- AP count
- controller/platform name
- SSIDs in scope
- bands enabled
- channel and power plan if known
- approximate AP locations
- recent changes
- user complaints by area
You do not need every detail to begin a conversation, but missing network context can slow down field work.
4. Identify critical devices and applications
A survey for laptops is not the same as a survey for scanners, VoIP, tablets, cameras, or guest WiFi. List:
- laptops
- tablets
- phones
- barcode scanners
- VoIP handsets
- cameras
- printers
- mobile point of sale
- medical, classroom, or industrial devices
- any devices limited to older bands or standards
Also list the applications that matter: video calls, inventory systems, ERP/WMS apps, voice, guest access, point of sale, and cloud tools.
5. Mark problem areas before walking
Ask users and operations teams where problems happen. Mark:
- dead zones
- slow rooms
- scanner drop aisles
- docks or staging lanes
- conference rooms
- roaming trouble paths
- outdoor transition areas
- areas where APs cannot be mounted easily
This keeps the survey focused on business impact rather than theoretical coverage alone.
6. Prepare equipment and power
For Ekahau Sidekick style workflows, prepare early:
- measurement device charged
- compatible laptop/tablet/phone ready
- correct cables and charger
- current survey software/app installed
- project file prepared or accessible
- floor plans imported
- spare power and charging plan
- carrying strap/case if walking large areas
The official Sidekick quick guide describes charging before use, using Ekahau provided or recommended cables/accessories, connecting via USB, turning the device on, and starting the compatible Ekahau application. Keep this general rather than trying to replace the current vendor manual.
7. Plan site access
Confirm:
- building access windows
- escort requirements
- safety gear
- after hours restrictions
- lift or warehouse floor rules
- areas that cannot be entered
- badge or visitor requirements
- whether operations can continue during survey
Warehouse and healthcare environments especially need access planning. A survey that skips critical areas because nobody arranged access is a wasted opportunity.
8. Define deliverables
Before starting, decide what the report must include:
- coverage heatmaps
- signal/SNR/noise observations
- channel/interference findings
- AP placement recommendations
- cabling/mounting notes
- warehouse aisle or conference room notes
- executive summary
- technical remediation list
- follow up validation plan
A deliverable should answer the decision maker’s question: what do we do next?
Office vs warehouse survey checklist: what changes before field day
A wireless site survey checklist should start with the same basics for every building: goal, floor plan, access, devices, problem areas, equipment, and reporting expectations. The difference is what each item means once the site is an office versus a warehouse.
Use the existing checklist as the planning base, then tighten the inputs below before the survey window. The goal is not to turn this page into a warehouse design guide; it is to make sure the person walking the site collects the right office or warehouse details before PacketScout has to interpret the data.
| Checklist item | Office survey emphasis | Warehouse survey emphasis |
|---|---|---|
| Survey objective Decide whether this is coverage proof, troubleshooting, validation, or remediation planning. |
Conference rooms, open office density, desks, voice/video calls, guest areas, and complaint spots. | Mobile-device paths, picking/packing zones, dock doors, freezer or cold storage, forklift routes, and shift-time symptoms. |
| Floor plan and access Decide which rooms, aisles, docks, and work paths must be measured instead of inferred. |
Tenant suites, offices, meeting rooms, locked spaces, shared walls, and room names that match how users report issues. | Aisle labels, storage zones, mezzanines, staging lanes, outdoor/dock areas, safety rules, escort needs, and blocked access windows. |
| Devices and applications Decide which client class matters most before field day. |
Laptops, phones, tablets, VoIP handsets, Teams or Zoom rooms, badge systems, printers, and guest devices. | Handheld scanners, vehicle-mounted terminals, tablets, AMRs, label printers, WMS sessions, and devices mounted on forklifts or carts. |
| RF and mounting constraints Decide whether checklist prep is enough or whether deeper warehouse WiFi design best practices should drive AP placement. |
Glass, conference-room density, small cells, AP load, ceiling type, neighboring tenants, and room-to-room movement. | High ceilings, metal shelving, product storage, dock doors, freezer panels, AP height, and lift/cabling limits. |
| Walk path and validation Decide which path becomes the evidence trail in the report, using clean WiFi survey data collection. |
Measure where people sit, stand, present, move between rooms, or join calls; test during representative busy periods when possible. | Measure the path the work takes: receiving, aisles, pick modules, packing, shipping, dock doors, and device transition points. |
| Deliverables and escalation Decide whether the outcome is a simple checklist-backed report, a professional WiFi site survey report, or a warehouse design/validation engagement. |
Coverage, room-to-room movement, density, call-quality, AP-load, and remediation notes that an office IT team can act on. | Mobile-device validation notes, AP/mounting recommendations, dead-zone evidence, validation targets, and a plan that supports operations. |
When it’s a warehouse: use this checklist to gather the inputs, then move to PacketScout’s warehouse WiFi survey and design service page and the deeper warehouse Field Note for device, mounting, and validation detail.
For offices, do not stop at signal bars. Capture the rooms, applications, and user paths that matter. For warehouses, do not rely on a hallway-style walk or a laptop-only test when lift access, moving inventory, and operational paths are the actual risk. A good checklist makes those decisions explicit before field day.
Quick checklist summary
- Survey goal defined
- Floor plans current and scalable
- Network hardware documented
- Critical devices listed
- Known problem areas marked
- Survey equipment charged and checked
- Software/app access confirmed
- Site access planned
- Deliverables agreed
- Report owner identified
Use this checklist with the right guide
If you are still choosing the survey type, start with How to Do a WiFi Site Survey. If you are preparing Sidekick equipment, use the Ekahau Sidekick Pre Survey Checklist. If the survey depends on map quality, review Prepare Floor Plans for Ekahau Survey Work before walking the site.
A checklist should prevent avoidable rework. It should not replace survey judgment. If the site includes high ceilings, metal racks, scanners, docks, freezer areas, or high density meeting rooms, add those conditions to the scope before the survey starts.
Field day checklist for the person walking the survey
The person holding the survey device should have a simple field day checklist rather than a project brief. Before collecting data, confirm that the map displayed in the survey app matches the physical area. Confirm the starting location. Confirm that the Sidekick or survey adapter is detected. Confirm that data is being recorded before walking deep into the building.
During the walk, avoid “teleporting” between far apart points on the map. If you need to stop and talk to a site contact, pause the workflow or make sure the next position mark is accurate. If a room is locked or an aisle is blocked, add a note instead of pretending it was surveyed. If an AP is visible, take a note or photo if the workflow allows it. These small field habits make the difference between a useful report and a pretty but questionable heatmap.
Report review checklist after the survey
After data collection, check the report before sending it to stakeholders:
- Are all scoped areas represented?
- Are thresholds explained?
- Are weak areas tied to business impact?
- Are AP recommendations specific enough for cabling/install work?
- Are limitations documented, such as inaccessible rooms or uncertain floor plan scale?
- Does the report separate facts from recommendations?
- Is there a prioritized next step list?
A survey report should help someone make a decision. If the deliverable only contains screenshots with no interpretation, it is incomplete.
If you want PacketScout to plan, walk, or interpret the checklist items, start with WiFi site survey services so the preparation work turns into a scoped field survey and report.
FAQ
How early should we prepare floor plans?
Prepare them before quoting if possible. Good floor plans help scope the job and reduce rework before survey day.
Should we survey every room?
Survey the areas where wireless service matters. That usually includes user spaces, critical workflows, high density rooms, warehouses aisles, docks, and roaming paths.
What if we do not know the AP model?
You can still start the conversation, but AP model and controller details help determine whether the project is design, validation, or troubleshooting.
Is this checklist enough for an Ekahau Sidekick rental?
It is a good preparation tool, but exact software/device steps should be checked against the current Ekahau documentation and the rental support process.
Related: WiFi site survey data collection best practices.
Can one WiFi site survey checklist cover offices and warehouses?
Yes, the same checklist can organize the work, but offices and warehouses need different details before field day. Offices usually emphasize rooms, conference spaces, density, voice, and video applications. Warehouses need mobile-device paths, product storage, dock doors, mounting height, access windows, and validation tied to the operational workflow.
Want PacketScout to review the site?
Send the floor plan, square footage, AP model, critical devices, and the problem you are trying to solve.