I’m looking at an office where users report bad Wi-Fi during the busiest parts of the day, especially around meeting rooms and open workspace areas.
The confusing part is that signal strength itself doesn’t look terrible. The complaints are more like lag, slow page loads, random call quality drops, and things getting worse when the office fills up.
How do you usually distinguish between a pure coverage issue and a capacity / airtime issue when signal level alone doesn’t look alarming?
It’s a classic pitfall: confusing “coverage area” with actual throughput. Everyone usually focuses on Wi-Fi “sticks” because they’re the easiest to see. But if everything in the office starts slowing down as soon as people arrive, it’s clearly not the signal. I’d immediately look at airwave congestion, how channels overlap, and how many devices are connected to a single point. It seems the network was designed simply to “get everywhere,” not to handle the real workload.
I’d check three things: Where the complaints cluster, whether those areas are overloaded at peak occupancy and whether channel planning is forcing too much co-channel contention. Meeting rooms are notorious for this. People see a strong signal and assume design is fine, but strong signal from the wrong AP, plus too many clients, is still bad Wi-Fi.
This is why I like validating with something like NetSpot instead of relying on signal alone. A heatmap may show decent RSSI, but that doesn’t tell you much about what happens once the room is busy. With NetSpot you can at least survey the area properly and compare signal/SNR patterns with real active test results.