WiFi 6E and WiFi 7 site survey guide
WiFi 6E and WiFi 7 site survey guide
A practical PacketScout guide to WiFi 6E, 6 GHz, WiFi 7, MLO, 320 MHz channels, AFC, PSC channels, client support, and survey validation.
WiFi 6E and WiFi 7 change how a site survey should be scoped. The project is no longer just “does the building have enough 2.4 GHz and 5 GHz coverage?” A modern survey also has to ask whether the clients can use 6 GHz, whether the network should support wide channels, whether the AP model and controller features match the client population, and whether the real floor plan can support the design without creating airtime problems.
Use this guide to scope 6 GHz and WiFi 7 survey work without turning the process into a fragile vendor manual. Exact software views, client support, and AP features change quickly; the survey process should stay grounded in requirements, floor plan scale, measured RF data, and post change validation.
What changes with WiFi 6E
WiFi 6E extends WiFi 6 into the 6 GHz band. The practical difference for a survey is that 6 GHz has more spectrum, more room for clean channels, and different propagation behavior than 2.4 GHz and 5 GHz. It can be excellent for newer laptops, tablets, phones, and high performance areas, but it does not magically fix coverage in every building.
A 6 GHz survey should check:
- whether the client devices actually support 6 GHz
- whether 6 GHz SSIDs are enabled and advertised the way the design expects
- whether AP placement gives usable 6 GHz signal in the intended rooms or zones
- whether the design relies on wide channels that reduce channel reuse
- whether 2.4/5 GHz fallback behavior still supports older devices
- whether wall materials, glass, elevators, shelving, and storage areas create unexpected loss
The mistake is to design for the AP datasheet instead of the client population. If only a small share of devices can use 6 GHz, the project still needs a strong 5 GHz and sometimes 2.4 GHz plan.
What changes with WiFi 7
WiFi 7, based on 802.11be, introduces features such as wider channels, higher modulation, and Multi Link Operation in capable client/AP combinations. In real survey work, those features should be treated as design possibilities, not assumptions. A survey still has to prove where the network works and where clients actually roam, associate, and perform.
WiFi 7 planning should ask:
| Question | Why it matters in the survey |
|---|---|
| Which clients are WiFi 7 capable? | A WiFi 7 AP does not make older clients behave like WiFi 7 clients. |
| Are 320 MHz channels realistic? | Very wide channels need clean spectrum and reduce reuse options. |
| Will MLO be used by the client fleet? | Multi Link Operation is client/AP/software dependent and should not be assumed for every device. |
| Does the design need 6 GHz everywhere or only in performance zones? | Coverage expectations drive AP count and placement. |
| What does fallback look like? | 5 GHz and 2.4 GHz often still carry important devices. |
Survey planning for 6 GHz
A 6 GHz survey should be scoped by room function. A conference room with high density laptops, a design office with large file movement, and a warehouse scanner lane do not need the same target. The floor plan should identify where 6 GHz is expected to matter, where it is optional, and where legacy client coverage is more important.
For PacketScout survey planning, mark these zones before the walk:
- high performance work areas
- conference/training rooms
- executive or customer facing areas
- areas with older 2.4 GHz only devices
- warehouse or manufacturing zones where client support may lag behind office devices
- exterior transitions, loading docks, patios, or other boundary areas
The final report should not simply say “6 GHz available.” It should state where 6 GHz is usable, where it is weak, where the design is intentionally relying on 5 GHz, and where client refresh may be required before 6 GHz benefits are visible.
Channel width is a design decision
Wide channels are attractive because they can increase peak throughput under the right conditions. They can also make reuse harder. A design that looks fast on paper can perform poorly if too many cells compete for the same airtime or if the client population cannot use the channel width effectively.
A practical channel width review should separate environments:
| Environment | Conservative starting point | Why |
|---|---|---|
| General office | 20/40 MHz depending on density and spectrum | Keeps reuse manageable while supporting normal business traffic. |
| High performance rooms | 40/80 MHz when clean spectrum and client support justify it | Useful where capacity matters and AP density is planned. |
| Warehouse/scanner zones | Usually conservative widths | Coverage, roaming, and reliability often matter more than peak throughput. |
| 6 GHz performance zones | Wider channels may be viable | More spectrum can make clean channel planning easier, but validation still matters. |
These are starting points, not universal rules. The survey and controller data should confirm whether the environment can support the plan.
AFC, standard power 6 GHz, and expectations
Some 6 GHz deployments may involve standard power operation and Automated Frequency Coordination depending on country, AP mode, and regulatory details. Many indoor enterprise designs use low power indoor assumptions. Treat AFC and power mode as a scoping item, not a casual promise.
The important project questions are:
- What country/regulatory domain is the site in?
- What AP models and modes are being used?
- Is the deployment low power indoor, standard power, or something else?
- Does the controller/AP documentation support the intended 6 GHz operating mode?
- Does the survey tool and report separate 6 GHz from 5 GHz clearly?
If the project depends on a specific 6 GHz operating mode, verify it before installation and again during validation.
What to measure in a WiFi 6E / 7 survey
A modern survey should still include the classic layers, but the interpretation needs to separate bands and client classes:
- signal by band
- SNR by band
- noise/interference indicators where available
- channel width and reuse
- AP visibility and neighbor count
- client association behavior
- roaming behavior in paths that matter
- throughput or application validation where required
- controller data such as channel utilization, retries, and client health when available
The report should avoid hiding everything behind one combined heatmap. A 2.4 GHz coverage layer, a 5 GHz performance layer, and a 6 GHz readiness layer can tell very different stories.
Example: where 6 GHz helps and where it does not
Imagine a two story office attached to a warehouse. The office has newer laptops and frequent video calls. The warehouse uses handheld scanners that mostly operate on 2.4/5 GHz. A WiFi 6E or WiFi 7 design may provide excellent 6 GHz performance in conference rooms and engineering areas, while the warehouse still needs a conservative scanner focused 5 GHz plan.
The survey recommendation should not be “turn on 6 GHz everywhere and move on.” A better recommendation is:
- Use 6 GHz in office performance zones where compatible clients benefit.
- Validate 5 GHz roaming and SNR for scanners and operational devices.
- Keep 2.4 GHz controlled and intentional for devices that still need it.
- Use channel width discipline so peak speed choices do not reduce reliability.
- Re check after client refresh if the 6 GHz capable fleet grows.
PacketScout next steps
If you are planning AP placement before installation, start with wireless network design services. If the network already exists and you need measured validation, start with WiFi site survey services or WiFi heatmap services. If your team wants to collect data with Ekahau hardware, review the Ekahau Sidekick Field Guide and confirm the tool/client support needed for 6 GHz or WiFi 7 work.
FAQ
Do we need WiFi 7 everywhere?
No. WiFi 7 is useful where the clients, applications, and spectrum support it. Many sites still need strong 5 GHz and targeted 2.4 GHz support for legacy devices.
Does 6 GHz replace 5 GHz?
No. 6 GHz adds capacity and cleaner options for capable clients, but many devices still rely on 5 GHz. The survey should show which bands matter by zone and client class.
Are 320 MHz channels always better?
No. Very wide channels can increase peak throughput in clean conditions, but they reduce reuse options and require compatible clients. Channel width should be chosen based on density, spectrum, and application needs.
Should a WiFi 6E or WiFi 7 survey include older clients?
Yes. A modern AP does not remove the need to validate older client behavior. The report should separate new client performance from legacy client reliability.
6 GHz security and WiFi 7 feature checks
A 6 GHz or WiFi 7 design should include a short standards and client sanity check before anyone promises benefits. In practical terms:
- 6 GHz WiFi requires modern security behavior such as WPA3 Personal/Enterprise or Enhanced Open/OWE for open networks; old WPA2 Personal expectations do not simply move into 6 GHz.
- 6 GHz does not use DFS channels, which can simplify some channel planning discussions compared with 5 GHz DFS behavior.
- WiFi 7 features such as 4096 QAM, Multi Link Operation, preamble puncturing, and very wide channels depend on compatible APs, clients, firmware, drivers, and clean enough RF conditions.
- A survey report should separate “the AP supports this feature” from “the client fleet will benefit from this feature.”
These checks belong in scope before the survey and in validation notes after installation. They keep the conversation grounded in what the actual devices can use.
What WiFi 7 features mean in a survey
WiFi 7 features sound impressive on a spec sheet. In the field, each one turns into a measurement question.
| Feature | Survey question |
|---|---|
| 4096 QAM | Is SNR high enough in the rooms where peak rate claims matter? If SNR is only mid twenties, do not sell peak WiFi 7 rates. |
| Multi Link Operation | Do the actual clients and drivers use it, or is it only an AP feature on paper? |
| Preamble puncturing | Is the channel plan clean enough, and does the controller show how it handles partial interference? |
| 320 MHz channel width | Does the environment have enough clean 6 GHz spectrum, and is reuse still sane? |
| 6 GHz client steering | Are compatible clients landing on 6 GHz, or are they staying on 5 GHz because policy, security, or drivers push them there? |
The report should say which features were validated and which were only design assumptions.
Want PacketScout to review the site?
Send the floor plan, square footage, AP model, critical devices, and the problem you are trying to solve.