Designing wireless for office and classroom density

A thirty-person professional services firm complains that the Wi-Fi keeps dropping during all-staff meetings. The IT vendor’s response is to add another access point. A few weeks later, the symptoms come back. The actual problem was never coverage. It was capacity. Modern wireless networks fail differently than older ones, and the failure mode is invisible until you look for it.

For an office of thirty staff or a classroom of forty students on iPads, the wireless architecture that ships with a typical consumer router (and many small-business routers) is not designed for the load you are placing on it. The difference between business-grade and consumer-grade wireless is rarely the headline speed. It is the way the access point behaves when twenty devices try to talk at once.

Coverage versus capacity

Coverage is whether the signal reaches the corner of the room. Capacity is whether every connected device can actually get useful network throughput at the same time. Most consumer-grade gear is sold on coverage (range, claimed Wi-Fi 6 speed). The capacity story is rarely mentioned because it is hard to put on a box.

In a thirty-person office, every staff member typically has at least two wireless devices on the network: a laptop and a phone, often a tablet too. Add the connected printer, the conference-room display, the security cameras, and the doorbell, and a thirty-person office is running fifty to eighty wireless devices. A classroom of forty students on iPads is fifty to sixty devices in a single room.

A consumer access point handles a handful of devices well. At twenty active devices, it starts to throttle. At fifty, it falls over. Adding a second access point makes the coverage problem look better and the capacity problem worse, because both access points are now contending for the same spectrum.

What enterprise wireless does differently

Three architectural choices set business-grade wireless apart from consumer gear.

Density-aware radio. Enterprise platforms (Ruckus, Cisco Meraki, Aruba) include radio technology designed specifically for high-density environments. Ruckus BeamFlex is the version we deploy most often: the access point shapes its signal to favour devices that are actively transmitting, rather than broadcasting a single omni-directional signal that every device on the floor has to compete for.

Wireless controllers and centralised management. Multi-access-point deployments need a controller that coordinates channel assignment, transmit power, and client roaming behaviour. Consumer mesh products do a simplified version of this. Enterprise gear does a serious version, and exposes the radio-frequency picture to the IT team via a real management console.

Hardware that handles the load. A consumer access point is built around a low-power chip with limited memory. An enterprise access point has the processor, memory, and antenna design to handle a hundred concurrent associations without dropping frames. The cost is higher. The behaviour under load is fundamentally different.

What a proper deployment looks like

A working business-grade wireless deployment starts with a site survey. The survey measures the actual radio-frequency environment in the building (other networks bleeding in, building materials that absorb the 5 GHz band, locations where the signal has to land cleanly). The survey informs access-point placement, count, channel assignment, and the cabling that needs to be installed.

The deployment itself involves business-grade access points (Ruckus is the platform we deploy most often), a controller (cloud-managed or on-premises depending on the client), structured cabling that supports Power-over-Ethernet (PoE), and PoE switching with enough power budget to feed every access point on the network.

After commissioning, the network needs ongoing tuning. Wi-Fi is the most volatile layer of the network stack. New devices, new physical obstructions, neighbouring networks all change the radio picture over time. A managed network service that reviews wireless health monthly catches most of these before they become user-visible problems.

When to think about this

The right time to think about wireless capacity is before the next staff hire that pushes the headcount past thirty, before the next iPad rollout in a school, or before the next all-staff meeting where the Wi-Fi falls over in front of the founder. After any of those, the conversation is reactive.

Wi-Fi is the part of the network most users notice. A wireless deployment designed for capacity rather than just coverage is the difference between a network the staff complains about every week and one nobody mentions because it just works.