WiFi site survey data collection best practices
WiFi site survey data collection best practices
WiFi site survey data collection best practices: floor plan scale, walk paths, Ekahau modes, notes, active tests, and when to hire PacketScout.

WiFi site survey data collection is only useful if the data can support a real decision. A polished heatmap can still be wrong when the floor plan scale is off, the walking path skips rooms, the survey mode does not fit the building, or the field notes do not explain what happened onsite.
This guide turns WiFi survey data collection lessons into a PacketScout checklist for customers who need decision-grade survey data, whether they hire PacketScout onsite, rent survey equipment, or use a hybrid approach.
If the survey will decide where access points get mounted, where cabling goes, whether warehouse scanners will roam, or why a client is dropping during business hours, data collection is the work. The report comes later.
Start with the reason for the survey
The first mistake is treating every survey like the same walk.
A design validation survey is not the same as a complaint investigation. A warehouse scanner survey is not the same as a hotel coverage check. A new office survey is not the same as a migration from old access points to WiFi 6E or WiFi 7 hardware.
Before anyone opens Ekahau Survey or starts walking with a Sidekick, the project needs a clear objective.
Common objectives include:
- confirm the existing coverage before a redesign
- validate a new access point layout after installation
- find dead spots, roaming failures, or bad scanner behavior
- measure coverage in rooms, aisles, docks, and user work areas
- compare predicted coverage against measured data
- collect active test data for latency, throughput, packet loss, or jitter
- document AP locations, mounting heights, and obstacles
- support a cabling, remediation, or budget decision
This matters because the objective changes the collection method. A quick health check can tolerate less detail than a survey that will drive cabling and lift work. A warehouse design needs different evidence than a conference room complaint. A speed problem may need active testing even when the RF heatmap looks fine.
If you are not sure what kind of survey you need, start with the WiFi survey learning center or the WiFi site survey checklist. If the work is high risk, the cleaner path is to hire a professional onsite WiFi site survey and make sure the scope is right before field day.
Prepare the floor plan before field day
A floor plan is not decoration. It is the coordinate system for the survey.
If the plan is wrong, the survey path is wrong. If the scale is wrong, the heatmap is wrong. If rooms are missing, areas are mislabeled, or the plan is stretched, the report can look professional while the evidence underneath it is weak.
Before the walk, check these items:
- the plan matches the current building layout
- the scale is set from a reliable long distance, not a tiny reference object
- important rooms, aisles, docks, closets, labs, and work areas are visible
- north, floor number, and building area are clear
- restricted rooms and locked areas are known before arrival
- outdoor or campus areas have a map workflow that makes sense
- the survey file is ready on the device that will be used onsite
Use a laser measure or a known building dimension when possible. A long measurement is better than a doorway because small errors get magnified across the whole floor. If the drawing is poor, fix it before the appointment or choose a workflow that can help capture the space.
For more detail, use prepare floor plans for Ekahau survey work before the site visit.
Choose the collection mode before you walk
Collection mode is where many surveys start going sideways.
Ekahau gives several ways to collect field data. The best choice depends on the site, the device, the floor plan, and the purpose of the survey.
- Continuous works well for efficient mapped walks when the surveyor can click at starts, turns, stops, speed changes, and door pauses.
- Stop and Go is slower but useful for controlled samples, dangerous areas, crowded rooms, or spots where the surveyor should stand still.
- Auto Pilot can reduce manual position marking when the iOS tracking workflow, map, scale, and walking conditions are good.
- Just Go can help when there is no usable floor plan, provided the hardware supports the workflow and the resulting sketch is reviewed.
- GPS belongs outside, where the device can get a usable location fix and the map workflow makes sense.
- Inspect is for review and QA after data has been collected.
Do not reduce this to automatic versus manual. Each mode moves the risk. Auto Pilot can reduce tapping mistakes but still needs calibration and judgment. Just Go can keep collection from stalling when plans are missing, but only when the device and current app support it and the sketch is reviewed. Continuous can be fast, but a bad click can smear measurements across a hallway or through a wall.
The deeper breakdown is in Ekahau Survey modes explained. Read that before choosing the field workflow.
Walk where the users actually work
A hallway only survey is tempting because it is fast. It is also where a lot of bad data starts.
The survey should cover the places where people and devices actually use WiFi. That means offices, patient rooms, classrooms, conference rooms, docks, pick modules, freezer doors, scanner paths, break rooms, carts, and counters. If the room matters, collect data in the room.
Walls, doors, shelving, glass, product, machinery, people, and furniture all change RF behavior. Walking one side of a wall and asking software to infer the other side is weaker than measuring both sides when the area matters. Interpolation is useful, but it is not a substitute for field evidence.
A good walking path has a few habits:
- it follows real physical paths through the building
- it does not cut through walls in the map
- it enters important rooms instead of tracing only the corridor
- it keeps sample spacing tight enough for the design goal
- it pauses and re clicks when the surveyor stops, opens a door, changes speed, or changes direction
- it avoids rushed zigzag paths that do not match real movement
- it gets reviewed before the surveyor leaves the site
If the surveyor cannot enter an area, note it. A missed room is not a moral failure. Pretending it was measured is the problem.
Capture the context, not only the colors
A heatmap layer does not explain everything.
Two spaces can show similar signal strength and still behave differently because the client mix, roaming behavior, channel reuse, noise, airtime, switch uplink, VLAN path, or application traffic is different. That is why field notes matter.
Useful survey notes include:
- AP location, model, mounting height, and antenna orientation
- obstacles, metal, glass, freezer panels, racks, doors, and machinery
- locked or skipped rooms
- areas surveyed during unusual traffic conditions
- scanner complaint locations
- places where users actually stand, sit, drive, pick, or scan
- cabling limits or mounting constraints
- photos of problem areas and access point locations
Good notes make the report easier to trust. They also protect the customer from making a bad fix for the wrong reason.
RF site survey measurements: what gets captured in the field
An RF site survey is not one signal strength screenshot. It is a controlled record of what was measured, where it was measured, and whether the data is strong enough to support a design, troubleshooting, or validation decision.
The exact measurements depend on the scope, tool setup, building access, and complaint being investigated. A basic validation walk may not collect the same evidence as a scanner-roaming investigation or an active application test. PacketScout treats the survey objective as the guide for which RF and client-experience data belongs in the file.
| Measurement | What PacketScout records | Why it matters | Where it shows up in the report |
|---|---|---|---|
| AP, SSID, BSSID, band, and channel details | The visible WLANs, serving APs, radios, channel assignments, and nearby competing networks observed during the walk. | Shows which APs and channels are actually serving the area instead of relying on a design drawing or controller name alone. | AP/channel inventory or channel-plan findings. |
| Primary signal and secondary AP candidates | Measured signal from the serving AP and other APs that clients may hear in the same area. | Helps separate simple coverage gaps from overlap, sticky-client, or wrong-AP problems. | Coverage map and roaming/overlap notes. |
| SNR and noise-floor context | Signal-to-noise context and noise observations captured by the survey workflow where the tool and adapter support it. | Explains why a space can show “good signal” but still perform poorly when usable signal quality is weak. | SNR/noise map or RF-quality note. |
| Channel reuse and co-channel pressure | How many APs or networks are heard on the same or nearby channels, plus where channel overlap is visible. | Identifies contention and reuse problems that can make WiFi slow even when coverage looks adequate. | Channel overlap or airtime findings. |
| Airtime, retries, active tests, or application checks when in scope | Optional active test evidence such as reachability, latency, jitter, packet loss, throughput, or retry symptoms, depending on the survey setup. | Connects RF evidence to the user complaint without pretending that every survey includes the same active test package. | Performance validation or application-test note. |
| Floor-plan scale, walk path, access gaps, photos, and field notes | Survey path quality, skipped areas, scale assumptions, locked rooms, wall types, mounting constraints, photos, and onsite observations. | Shows whether the heatmap evidence is trustworthy enough to drive cabling, AP placement, or remediation work. | Methodology note and limitation callouts. |
The fourth column is intentionally a pointer, not a full report template. For report structure and deliverables, use what a professional WiFi site survey report should include.
For the RF mechanics behind SNR, noise, and channel overlap, use PacketScout’s WiFi signal, SNR, noise, and channel overlap guide. For the end-to-end field workflow, use how to do a WiFi site survey. If the scope needs Ekahau planning, Sidekick data collection, or professional interpretation, start with Ekahau WiFi survey services or PacketScout’s professional onsite WiFi survey service.
Passive, active, spectrum, and speed tests answer different questions
A passive WiFi survey listens. It can collect signal, SSID, BSSID, channel, noise, security, data rate, and related RF information without joining the network.
An active survey joins the WLAN and sends traffic. It can answer client experience questions such as throughput, latency, packet loss, jitter, and reachability, depending on the setup.
Spectrum analysis looks for RF energy that is not normal WiFi traffic. It can help explain interference that a normal WiFi view may miss.
A mapped speed test can suggest problems outside the RF layer, especially when run against a controlled endpoint and interpreted with the RF data. One area can have good signal but poor performance because of a switch uplink, VLAN path, firewall, ISP handoff, or backhaul bottleneck.
That is why PacketScout does not treat a survey as one magic heatmap. The right data type depends on the complaint.
Use active vs passive WiFi surveys for the deeper explanation. Use WiFi signal, SNR, noise, and channel overlap when you need the RF analysis side.
AP on a stick is risk control
AP on a stick survey work is not for every project. It makes sense when the cost of being wrong is high.
If moving an access point later only means shifting a drop above a ceiling tile, AP on a stick may be overkill. If the AP will be mounted forty feet up in a warehouse, over production equipment, inside conduit, near freezer panels, or in a space that requires a lift and safety coordination, guessing gets expensive.
A useful AP on a stick test tries to match the planned install:
- use the intended AP model or a close equivalent
- set power and channel deliberately
- keep the temporary AP stable
- match final height and antenna orientation as closely as practical
- separate bands or radios when needed so the collected data is clear
- survey around the AP instead of measuring one convenient direction
- collect to the coverage edge that matters for the design
- check same channel reuse and adjacent floor effects when relevant
For warehouse and manufacturing sites, this can be the difference between a believable design and a nice looking guess. The full walkthrough is in AP on a stick WiFi survey.
Site access can decide survey quality
Some buildings are easy. Many are not.
Hotels have guest rooms. Hospitals have clinical spaces. Schools have schedules. Warehouses have forklifts, loading activity, shift changes, freezer areas, and blocked aisles. Offices have locked conference rooms and tenants who do not want someone walking through meetings.
The best survey window is not always outside business hours. A hotel may be easier between checkout and guest arrival. A warehouse scanner issue may only appear during a live shift. A conference center may need access between events. A medical or manufacturing site may require an escort, PPE, or a planned route.
Plan access before the survey window starts:
- confirm who opens locked rooms
- define which areas must be measured
- decide what percentage of the floor is acceptable if full access is impossible
- schedule around the problem you are investigating
- document areas that were unavailable
- plan a return window if required areas are blocked
This is one reason onsite service matters. The technical work is not only using the tool. It is knowing what must be measured before the day runs out.
Review the data before leaving
The worst time to discover a missing room is after the surveyor gets home.
Before leaving the site, review the project while you can still fix it. Look for broken paths, skipped rooms, bad scale, odd jumps, missing notes, and results that do not match what users reported.
A simple exit check should include:
- all scoped areas have measured data or a note explaining why not
- rooms, aisles, docks, and complaint spots are covered
- AP locations and mounting details are documented
- the map scale still looks sane
- survey paths do not jump through walls or outside the building
- active tests were taken where performance matters
- photos and notes are attached to the right places
- the project file is saved and backed up
If the data looks wrong onsite, fix the data onsite. A pretty report built from bad data is still bad data.
When to rent equipment and when to hire PacketScout
There are three good paths.
Rent WiFi survey equipment when your team has the skill, the access, and the time to collect clean data. This is a solid option for teams that already understand floor plans, survey modes, walking paths, and report review.
Hire PacketScout onsite when the building is complex, the cost of bad data is high, the findings need to support spending, or the survey has to answer a specific operational problem. Warehouses, scanner complaints, healthcare spaces, plants, hotels, schools, and deadline driven deployments usually benefit from an experienced surveyor.
Use a hybrid approach when you want to collect the data yourself but want help with planning, file review, report interpretation, or remediation. That can mean renting an Ekahau Sidekick, using the Sidekick field guide, then having PacketScout review the results before the next spend decision.
If the outcome matters, the goal is not to own a heatmap. The goal is to collect evidence good enough to act on.
FAQ
What is WiFi site survey data collection?
WiFi site survey data collection is the onsite work of measuring RF and client experience data against a physical map. It includes the floor plan, survey mode, walking path, notes, photos, AP locations, and optional active or spectrum testing.
Why does survey data quality matter?
Survey data quality matters because the report is built from the measurements. If the scale, path, coverage, or notes are wrong, the heatmap can support the wrong design decision.
What causes bad WiFi heatmap data?
Common causes include bad floor plan scale, skipped rooms, hallway only walks, paths drawn through walls, rushed clicking, wrong survey mode, missing notes, and collecting data during a window that does not match the real problem.
Should a WiFi survey be passive or active?
Passive survey data is usually the baseline because it measures RF and beacon information. Active testing is useful when the question involves client experience, reachability, throughput, latency, packet loss, jitter, or an application problem.
Which Ekahau Survey mode should I use?
Use the mode that matches the site and goal. Continuous fits many mapped walks. Stop and Go fits controlled points. Autopilot can reduce manual tapping when the setup is right. Just Go can help when no usable floor plan exists. GPS fits outdoor work. Inspect is for review after collection.
Do I need to walk inside every room?
You should walk inside rooms that matter to the survey objective. If users work in the room, scanners roam through it, or the coverage decision depends on it, hallway only data is usually not enough.
When is AP on a stick worth doing?
AP on a stick is worth doing when moving the AP later would be expensive or disruptive. It is common in warehouses, manufacturing, healthcare, high ceiling spaces, and areas with difficult cabling or mounting conditions.
Should speed tests be part of a WiFi survey?
Speed tests are useful when performance is part of the complaint. They can reveal wired backhaul, VLAN, switching, firewall, or ISP problems that a signal heatmap will not explain by itself.
Can I rent WiFi survey equipment and do this myself?
Yes, if your team can prepare floor plans, choose the right collection mode, walk carefully, and interpret the results. If the site is complex or the findings will drive spending, a professional onsite survey is usually safer.
When should I hire PacketScout for onsite survey work?
Hire PacketScout when the survey needs to support AP placement, cabling, remediation, scanner troubleshooting, warehouse operations, or an executive decision. The value is in collecting and interpreting data correctly, not only producing a heatmap.
Does a WiFi RF site survey only measure signal strength?
No. Signal strength is only one layer. Depending on scope, a WiFi RF site survey may also capture SNR and noise context, AP, BSSID, SSID, and channel data, channel reuse, airtime or retry symptoms where available, floor plan and walk-path quality, field notes, photos, and optional active tests. PacketScout uses the survey goal to decide which evidence belongs in the report.
Want PacketScout to review the site?
Send the floor plan, square footage, AP model, critical devices, and the problem you are trying to solve.