What Is a Wireless Site Survey?

A wireless site survey evaluates the radio-frequency environment and user requirements for a Wi-Fi network. It helps determine access-point placement, coverage, capacity and performance needs. Depending on the stage, it can use predictive modeling, field measurements or active connection tests. A colored coverage map is one output—not proof that every application will work well.

The survey should begin with the devices and applications the network must support.

Three survey approaches

Cisco’s WLAN site-survey guidance distinguishes passive, active and predictive surveys.

The methods complement one another. Predictive planning is valuable before construction, but the completed building may behave differently from the model. Post-installation validation checks the actual environment.

Coverage is not capacity

A device can receive a strong signal while sharing limited airtime with many other clients. Interference, channel use, client capability and application demand also affect the experience.

An illustrative meeting room has strong signal throughout but regularly hosts video calls from dozens of devices. A coverage-only design can miss the concentrated demand. The survey brief should include expected occupancy and applications, not just a requirement to “cover the floor.”

Similarly, a warehouse’s shelves, stock and moving equipment can affect radio conditions. Testing an empty building may not represent normal operation.

Define acceptance around real clients

Different client devices have different radios, antennas and roaming behavior. An application may require performance that a general browsing test does not evaluate.

Identify the intended devices, required areas and important uses such as voice, video or scanning. Establish appropriate criteria for signal, signal-to-noise conditions, roaming and application performance within the project design. Do not apply one unexplained signal threshold to every environment.

The Cisco wireless site-survey FAQ provides additional context for matching surveys to deployment requirements. Product-specific guidance should be interpreted within its hardware and software context.

The wired network still matters

Access points need appropriate connectivity and power. Switch capacity, cabling, Power over Ethernet capability and upstream services can limit results even when radio placement is sound.

The project should coordinate proposed access-point locations with available routes, mounting, access and maintenance. A technically attractive location is not useful if it cannot be installed or serviced appropriately.

What the report should include

Ask for the requirements, plans used, survey method, equipment assumptions and measured areas. Results should explain both satisfactory areas and exceptions, with a recommended response.

The owner should know where the team walked, which devices were tested and which conditions were absent. Raw survey data can support later review when supplied under the agreed scope.

Recommendations should distinguish radio changes from wired-network or application issues. Adding access points is not the answer to every complaint and can introduce additional interference if poorly designed.

A survey brief should describe the work people do

The survey needs more than a floor area and a desired number of access points. Identify the users, device types, applications and locations that matter. A network supporting ordinary browsing has different practical requirements from one supporting mobile voice, scanners or concentrated video meetings.

For an illustrative warehouse, handheld devices may move through aisles and loading areas while office laptops remain near desks. Testing only the office area would not establish suitability for the operational workflow. The survey route and client tests should reflect the actual use.

State which areas require service and which are outside scope. Outdoor spaces, stairways, temporary work zones or infrequently used rooms should not be included or excluded by assumption. The owner should understand the intended coverage boundary.

A clear brief gives the survey team a basis for selecting methods and acceptance criteria. Without it, an attractive heatmap can answer a question the business never actually asked.

Predictive modeling depends on the building assumptions

A predictive survey estimates radio behavior using plans, materials, equipment and other inputs. It can support design before installation or construction, but its usefulness depends on the quality of those assumptions. A model is not a measurement of the completed building.

An illustrative office fit-out may change partition materials, furniture layouts or equipment locations after the initial design. Those changes can affect the conditions represented by the model. The project should identify which revisions require the wireless design to be reviewed.

Cisco’s site-survey guidance distinguishes predictive work from field approaches. Use each method for its purpose rather than treating a preconstruction model as final proof of installed performance.

The report should identify the plans and assumptions used. That makes later validation more useful: the team can compare the actual environment with the original model and investigate the reasons for a difference.

Passive and active surveys observe different aspects of the environment

A passive survey collects information about the wireless environment without evaluating an associated application session in the same way as an active survey. An active survey uses a connected client to evaluate relevant communication behavior. The appropriate combination depends on the project’s question.

For an illustrative complaint about roaming during a mobile workflow, a static coverage observation alone may not demonstrate the experience. The assessment should include a method that evaluates the relevant client behavior along the intended route.

Likewise, a successful active test with one device does not describe every client population automatically. Device radios, antennas, software and application behavior can differ. The survey should identify which clients were used and how representative they are of the planned environment.

The owner should receive the method and context with the results. A report that labels every output simply as signal testing hides useful distinctions about what was actually measured.

Signal strength is only one performance indicator

A device can receive a strong signal while experiencing poor service for other reasons. Interference, noise, channel use, airtime demand and upstream limitations can affect the result. The survey should evaluate the quantities relevant to the agreed application rather than rely on one color scale.

Signal-to-noise conditions, for example, describe a different relationship from signal strength alone. The appropriate acceptance criteria should come from the application, client and design requirements. A universal threshold copied from another project can be misleading.

An illustrative meeting room may have strong coverage but become congested when many users arrive. The design needs to account for the concentrated demand and the capabilities of the selected equipment and clients. Increasing transmit power is not a general solution to every capacity problem.

Ask the report to connect each significant finding to the observed user effect or design requirement. That makes recommendations more understandable than a collection of unexplained technical charts.

Capacity planning should reflect simultaneous use

The number of people in a building is not necessarily the number of active devices or the pattern of demand. Users may carry several devices, and applications can impose very different traffic and airtime needs. The assessment should establish a reasonable operating model for the intended use.

For an illustrative training room, a largely idle group of devices during a presentation can behave differently from the same group starting a demanding online exercise together. A survey and design brief should identify the relevant busy conditions rather than model only quiet periods.

The goal is not to assume the maximum conceivable demand everywhere. It is to identify credible requirements and document the assumptions. If a planned event or application changes the demand materially, the organization can then evaluate whether the original design remains suitable.

Capacity and coverage should be reviewed together. Additional access points can change the radio environment, so simply adding more equipment without a coordinated design can create new problems.

Roaming needs the actual movement and client context

A mobile device moving through the site may transition between access points. The user experience depends on the client, application and network design. A set of stationary tests does not necessarily demonstrate acceptable behavior during movement.

For an illustrative voice or scanning workflow, the survey should identify the relevant routes and test conditions. The team needs to know where users move, how the application behaves and what interruption is acceptable. The acceptance criteria should reflect that business function.

Cisco’s site-survey FAQ provides context for matching survey work to deployment needs. Its product-specific examples should be interpreted for the actual hardware and software in the project.

Document the devices used in validation and the limitations of the sample. A favorable result for one test client is evidence about that test, not a universal guarantee for every device that may later enter the building.

The installed environment can differ from an empty-site test

People, furniture, shelving, inventory and equipment can change the conditions represented during a survey. A test in an empty building may be useful for a particular stage without fully representing normal operation. The report should identify those conditions.

An illustrative warehouse with changing stock levels can present a different environment from the same building before occupancy. An office’s use of meeting rooms can also vary substantially through the day. The design should consider relevant operating patterns, and validation should acknowledge what was present during testing.

This does not mean every possible condition must be measured before deployment. It means the assumptions and limits should be visible, with a plan to investigate significant problems that emerge under actual use.

When the layout changes, retain the original survey as a baseline and evaluate the affected areas. A new wall or equipment arrangement can matter even when the floor area and access-point count remain unchanged.

Coordinate the wireless design with the wired infrastructure

An access point needs suitable mounting, connectivity and power within the selected design. Its location should be checked against cable routes, switch capabilities and installation access. A strong radio-model result does not resolve those physical and network requirements.

For an illustrative ceiling location, a proposed access point may be difficult to reach for maintenance or may lack an appropriate cable route. Resolve those constraints before finalizing the placement rather than allowing the installer to choose a substantially different location without review.

The upstream service also matters during testing. A slow internet path or application can affect a user test even when the local wireless link performs appropriately. The survey team should distinguish radio findings from broader network or application issues where the scope permits.

A useful recommendation identifies which discipline owns the response. Cabling work, switch configuration, radio design and application investigation are different tasks, even when they contribute to the same user complaint.

Require a report that supports installation and later troubleshooting

The final report should identify requirements, methods, plans, equipment, tested areas and important limitations. Include interpreted findings and proposed responses, not only raw maps. The owner should be able to tell which issues concern coverage, capacity, roaming or another dependency.

Post-installation validation should compare the completed environment with the agreed criteria. If placement or equipment changed during construction, record the change and evaluate its effect. The final accepted layout should match the documentation used for support.

Keep the relevant survey records accessible for future changes. A later team investigating a problem benefits from knowing the original assumptions, client tests and accepted conditions. A heatmap with no date or configuration context loses much of that value.

The practical outcome is a network designed around the way people work, with evidence that its intended functions were evaluated. That is more useful than a promise that every point on the floor plan will always have perfect Wi-Fi.

Common questions

Can a survey be done before the building exists?

Predictive modeling can support early design. Confirm assumptions and validate the installed environment later; a model is not a field measurement.

Does adding more access points always improve Wi-Fi?

No. Placement, channel planning, power levels, client behavior and airtime use matter. More equipment can create additional contention.

Is a phone speed test enough?

It can reveal an experience at one time and place, but it does not characterize the complete site or separate all possible bottlenecks.

When should an existing network be reassessed?

Consider significant layout changes, new applications, different device populations, persistent performance problems or a major equipment refresh.

Start with where and how people work

Share floor plans, device types, occupancy patterns and known problem areas with Soleil Energy’s technology infrastructure team. A clear survey brief connects wireless design to actual business use.