Wi-Fi 7 Headlines Tout Speed; the Checklist That Matters Is Somewhere Else

Archi4 min read

networkingwifiinfrastructure

Contents
  1. The Speed Number Is the Least Interesting Part
  2. 1. Audit the cable plant before anything else
  3. 2. Recalculate the power budget
  4. 3. Plan 6 GHz as a separate design
  5. 4. Map the client mix honestly
  6. 5. Check the uplink and the backhaul
  7. 6. Retune channels and reduce overlap
  8. 7. Do not skip the controller and management layer
  9. 8. Test with the applications people use
  10. 9. Budget for the refresh cycle you are starting
  11. 10. Write down the rollback
  12. What the Headlines Left Out

The Speed Number Is the Least Interesting Part#

Every Wi-Fi 7 announcement leads with a multi-gigabit figure measured on a bench with one client and no walls. Network teams who read only those numbers buy access points expecting a transformation and then wonder why the office still stutters at 2 pm. The upgrade is real, but the bottleneck moved. It now sits in cabling, switch power budgets, channel planning and the client devices people actually carry. This checklist covers what the launch coverage skipped.

1. Audit the cable plant before anything else#

Wi-Fi 7 access points can push traffic that older Cat5e runs will not carry over distance. Walk the building and confirm what is in the walls. If a run is Cat5e and longer than roughly 45 meters, plan a recable or accept that the radio will not reach its ceiling. Count the runs that terminate in telecom closets with no spare ports. This is unglamorous work and it decides whether the new hardware performs.

2. Recalculate the power budget#

Access points that draw more power need switches that can supply it. Add up the draw of every access point on a switch and compare it with the switch's total power envelope, not just the per-port rating. The gap shows up at 9 am on a Monday when every radio wakes at once. If the budget is tight, either replace the switch or accept a lower radio configuration on some units.

3. Plan 6 GHz as a separate design#

The new band is wide and mostly empty, which makes it tempting to treat as free capacity. It is not free. It has shorter range and behaves differently through walls. Survey the floor with 6 GHz in mind and check whether your client fleet even supports it. A large share of laptops and phones in service today do not, so the band may sit idle while 5 GHz carries the load.

4. Map the client mix honestly#

Pull a client inventory from the controller and count by capability. If most devices in the building are three or more years old, the practical gain from the upgrade will be smaller than the marketing implies. The upgrade pays off on the newest clients and in dense spaces like meeting rooms and warehouses. It pays off less in a call center full of aging thin clients.

An access point with a 2.5 Gbps or 10 Gbps port is only useful if the switch port behind it matches. Many deployments end up with a fast radio feeding a 1 Gbps uplink. Trace the path from access point to switch to core and confirm no link is the old bottleneck in new clothing.

6. Retune channels and reduce overlap#

With more spectrum available, the temptation is to widen channels everywhere. Wider channels mean fewer non-overlapping options and more interference in dense areas. On a floor with 30 access points, narrow channels usually win. Test both configurations in a real area with real users before committing a whole site.

7. Do not skip the controller and management layer#

New radios often need firmware that the management platform handles differently. Check that your controller version supports the models you are buying, that guest portals and authentication still work, and that monitoring produces the same alerts. A silent gap here can leave an access point online but unmanaged.

8. Test with the applications people use#

Benchmarks rarely reflect a video call in a corner office. Run a pilot in one zone for two weeks and measure what users feel: call quality, file transfers, video streaming, and the time it takes to join the network. Keep the old access points nearby for comparison. Numbers from a pilot in your own building beat any spec sheet.

9. Budget for the refresh cycle you are starting#

Wi-Fi generations now arrive faster than most buildings replace hardware. Plan the refresh as a rolling program rather than a one-time event. That means standardizing on a model line, keeping spares, and setting a replacement horizon in the capital plan. The teams that struggle are the ones that treat each upgrade as a project instead of a schedule.

10. Write down the rollback#

Before the first access point goes live, document how to revert to the previous configuration, who holds the credentials, and what triggers a rollback. Most failed rollouts are not hardware failures. They are change management failures at 11 pm on a Friday.

What the Headlines Left Out#

The launch stories measured the ceiling. The work happens at the floor: cables, power, channels, client devices, and a pilot you can defend with data. Teams that run this checklist will get most of the value the spec sheets promise. Teams that skip it will buy faster radios and wonder why the network still feels the same.

More articles