Wireless problems we solve
Post-Deployment Wireless Validation
Validation proves the installed network meets documented coverage, capacity, roaming and application criteria — before users find out that it does not.
Engineer’s questionHow do I validate a Wi-Fi design after deployment?
1 — Direct answer
The short answer
Validation is the measured comparison of the installed network against documented acceptance criteria. It is not a repeat of the predictive design and not a speed test; it is evidence that the design intent survived installation.
A useful validation defines targets first — cell-edge RSSI, SNR, secondary coverage, data rate, roam duration, capacity per area — then measures them on site with the client types that matter, and records pass/fail per area.
The value is in catching the predictable installation realities: APs relocated during fit-out, antennas mis-oriented, radios left at default power, channels not re-planned after the fact, and areas quietly excluded from the original scope.
Likely causes, roughly in order of frequency
- Prediction versus reality
- Modelled attenuation rarely matches the finished building exactly, particularly after fit-out.
- Installation deviation
- APs moved for cabling, ceiling or aesthetic reasons; antennas mounted in the wrong orientation.
- Default configuration left in place
- Power, channel width, data rates and RRM constraints still at defaults after go-live.
- Scope gaps
- Stairwells, lifts, plant rooms, docks, exterior areas and new fit-out spaces missing from the design.
- Client mix changed
- The device population at go-live is often not the one assumed at design time.
- No documented acceptance criteria
- Without written targets, 'validated' means nothing and disputes cannot be resolved.
2 — Symptoms
Symptoms and what they usually mean
| Symptom | What it usually indicates |
|---|---|
| Complaints begin immediately after go-live | Design or installation deviation, findable by validation. |
| Performance differs sharply between similar areas | Placement, configuration or material differences. |
| The integrator says it meets the design | Common — measured validation against written criteria is how this is settled. |
| Some areas were never tested | Scope gap rather than a fault. |
3 — Do this first
Safe checks you can run yourself
These are non-disruptive checks a competent network engineer can complete with the controller or cloud dashboard already in place. Do them before changing configuration — they frequently identify the cause, and they always make an external investigation faster and cheaper.
- 1
Confirm written acceptance criteria exist
If they do not, define them before measuring anything. This is the single most valuable step.
- 2
Verify the as-built AP inventory against the design
Position, model, antenna, mounting height and orientation.
- 3
Review the applied configuration against the design
Channel plan, width, power ranges, data rates, SSIDs and RRM constraints.
- 4
Spot-check coverage in the areas most likely to fail
Perimeter, stairwells, lifts, corners, high-attenuation rooms and travel routes.
- 5
Check controller health and any down or de-rated radios
A partially failed install can look like a design fault.
4 — Watch out
Common mistakes and misleading indicators
“The predictive design was approved, so we are compliant”
Approval of a model is not evidence about the installed network.
“A speed test at several desks proves it”
Speed tests measure one client at one moment; they say nothing about coverage, overlap, roaming or capacity.
“The dashboard shows all APs healthy”
Operational health is not the same as meeting a coverage, roaming or capacity requirement.
“We will validate if users complain”
By then the remediation window and the installer's involvement have usually closed.
5 — Escalation point
When normal troubleshooting is no longer enough
- A new build, refresh or migration is completing and acceptance needs independent evidence.
- A third party delivered the design or installation and you want an impartial assessment.
- The environment supports voice, medical, scanning or real-time traffic with strict requirements.
- You need documentation for compliance, device certification or handover to operations.
- A multi-site rollout needs a repeatable acceptance standard applied consistently.
6 — Professional investigation
What a professional wireless investigation should measure
- Acceptance criteria definition
- Documented coverage, SNR, secondary coverage, data rate, roaming and capacity targets per area and application.
- Passive validation survey
- Measured RSSI, SNR, overlap, channel plan and data rates across the deployed environment.
- Active validation
- Throughput, loss, latency, jitter and roaming measured as a connected client along real routes.
- Spectrum check
- Confirming the deployed environment is not compromised by non-Wi-Fi interference.
- Configuration conformance review
- As-built configuration compared against the design intent, with deviations documented.
- Pass/fail reporting
- Per-area results against the criteria, with a remediation list for anything failing.
7 — Relevant service
Which NetRobin service applies
Validation Survey
A validation survey is the formal, measured acceptance step: documented criteria, on-site measurement with the relevant client types, and a pass/fail record that either closes out the project or produces a defensible remediation list.
Often combined with
8 — Deliverables
What you should expect to receive
- Documented acceptance criteria per area and application
- Measured coverage, SNR, overlap and data-rate results
- Active performance and roaming measurements along tested routes
- Configuration conformance findings against the design intent
- Pass/fail report with a prioritised remediation list
Direct answers
Frequently asked questions
- How do I validate a Wi-Fi design after deployment?
- Define written acceptance criteria, then measure the installed network on site against them: coverage and SNR, secondary coverage, data rates, roaming behaviour and capacity, using the client types that matter. Record pass/fail per area and list remediation for anything that fails.
- Is a validation survey the same as a passive survey?
- A validation survey usually includes passive measurement but is defined by its purpose: proving the deployed network meets documented criteria. It typically adds active testing, roaming measurement and a configuration conformance review.
10 — Next step
Request a Validation Survey
Share the design documentation and go-live date — validation is most valuable while the installer is still engaged.