Survey Wi-Fi coverage using declared service requirements

What you should be able to do

Plan and interpret a Wi-Fi survey against declared service requirements. Separate radio coverage evidence from proof that the required applications work for the intended clients and load.

Scope

The table uses original fictional measurements and deliberately stated exercise limits. It is not a universal wireless design standard. This lesson does not perform a network survey, collect traffic or authorize configuration changes. Real work requires the approved scope, site access and test arrangements.

Sources

1. Write A Service Statement

For the fictional warehouse exercise, define the required area as work aisles and the dispatch desk, the client as a specified handheld scanner model, and the application as the approved inventory transaction workflow. Record expected simultaneous use, mobility, target band and relevant operating conditions. Do not begin with “make the map green.”

Each requirement needs a measurable check and an owner. RF targets may include signal and signal-to-noise ratio. Service targets may include completed transaction behavior, throughput where relevant, delay, loss, roaming continuity and supported authentication. Write the applicable criteria before taking data. Do not invent a universal threshold when the owner has not supplied one.

2. Define What The Survey Can Show

A predictive map is an estimate based on a model. A passive walk gathers radio observations without proving an associated client's application path. An active test uses an associated client and can examine service behavior under its particular conditions. Match the method to the question.

A survey adapter may not behave like the actual scanner. Different antennas, drivers, capabilities and placement can affect results. Identify the client and tool used, and arrange representative device validation rather than assuming any laptop stands in for every endpoint.

An internet speed test also includes paths beyond the radio link. If that is the chosen service test, record its destination and limitations. A local authorized test endpoint can answer a different question. Do not label every end-to-end delay as a Wi-Fi fault without isolating the contributing path.

3. Prepare Traceable Evidence

Use the correct floor-plan revision and validate its scale. Label the in-scope areas, unavailable areas, sample path and observation points. Record date/time, survey method, client/tool configuration, band, channel and relevant access-point information. A missing location is unverified, not automatically passed.

Document conditions that matter to interpretation: occupancy, shelving or inventory state, moving equipment and whether the intended application load was present. An empty-site snapshot and a busy shift answer different questions. Avoid extrapolating one into the other without evidence.

Retain the underlying data and test records with the rendered report. Distinguish measured locations from interpolation and predictions. A broad colored region should not imply that every point was directly measured.

5. Do Not Promote A Partial Pass

Point A has passed only two example RF checks. No throughput, delay, loss, capacity or roaming result was supplied. Mark those checks unverified. The whole service cannot be declared accepted.

For an original follow-on record, suppose the scanner completes the required workflow while stationary at A, but fails during a specified aisle transition. Keep both observations. The stationary success does not erase the mobile failure, and the mobile failure does not establish its cause without further evidence.

Likewise, a negotiated radio data rate is not the same quantity as application throughput. Use measurements and criteria that match the actual promised service.

6. Controlled Follow-Up

List the failed criterion, observed location, operating conditions and next authorized investigation. Do not automatically raise transmit power or add access points based solely on a weak reading. Configuration, placement, channel use, client behavior and the wider network require responsible review.

After an approved change, repeat the affected checks and relevant adjacent-area checks. Preserve the before/after records and identify the changed variable. A visually improved map is not sufficient if application behavior was the unresolved problem.

Practice

1. Point D has signal -66 dBm and noise -94 dBm. SNR is 28 dB, so both fictional RF limits are met.
2. Point E has signal -60 dBm but no reliable noise reading. Signal meets the example criterion; SNR remains unknown.
3. Two of three poster points meet the signal threshold, but only one meets both RF thresholds. Do not describe that as whole-floor coverage: the sample set does not define an area percentage.
4. The dispatch desk was inaccessible. Mark it unverified, not excluded from the contract without approval.
5. A predictive map is available but no field records exist. Report prediction, not measured acceptance.

Knowledge Check

Sources

Worked through

At fictional point C, signal is -64 dBm and noise is -85 dBm. Subtraction gives -64 - (-85) = 21 dB SNR. The signal is stronger than the exercise minimum of -67 dBm, but 21 dB is below its 25 dB SNR requirement. Enter "signal passes; SNR fails" and retain the raw readings and location. Do not turn this partial result into service acceptance; application and roaming checks still require their own evidence.

Where beginners go wrong