Why We Used a ~30-Meter AP Planning Radius in a High-Density Campus Venue?

Published: August 10, 2026 | Last Technically Reviewed: August 10, 2026

Quick Answer

In this campus project, we did not use the AP's ~100 m ideal open-space coverage reference as the actual deployment radius. For the cafeteria, great hall and similar high-density venues, the final planning radius was reduced to approximately 30 meters because expected concurrent-user capacity and real RF conditions mattered more than maximum signal reach. The project also selected 150+ client-class APs for these spaces. These were project-specific planning values, not universal WLAN design standards.

Introduction

This article is based on the original planning document for a real university new-campus network project. The values below are historical design inputs recorded for that project; they are not being retroactively associated with any current AP model.

In this university campus project, several large shared venues-including the cafeteria, great hall/auditorium, and stadium-related open spaces-could experience very high user density. The project document noted that these environments were dominated by smartphones and tablets, with some school and commercial facility devices also requiring stable connectivity. In the busiest spaces, the potential user population could approach 2,000.

Although the project used an ideal open-space AP coverage reference of approximately 100 meters, that number was not used as the actual deployment radius. For the cafeteria, great hall and similar high-density open areas, the engineering team considered a practical range of roughly 30-45 meters and ultimately planned around a radius of approximately 30 meters.

Why? Because the design had to satisfy concurrent-user capacity and usable RF performance-not simply make a Wi-Fi signal visible at the edge of the coverage area.

The Original Planning Problem

The campus did not have one uniform wireless environment. Different buildings had different internal layouts, client types and user densities, so the access strategy had to change with the space. The project document specifically grouped places such as cafeterias, great halls, gymnasiums, swimming pools and libraries as relatively large and open environments with high concentrations of mobile devices.

For the venue type examined in this case, the important characteristics were straightforward:

The space was relatively open. The primary user devices were smartphones and tablets. User density could rise sharply when the venue was occupied, and a smaller number of school or merchant/facility devices still needed stable access. In the highest-density cafeteria, great hall and stadium-related scenarios, the project estimated that the number of terminals could reach approximately 2,000.

That changed the design question.

The question was not:

It was:

Those are not the same calculation.

Why We Did Not Design Around the Maximum Coverage Distance

The project documentation used approximately 100 meters as an ideal open-environment coverage reference. But it immediately qualified that figure: microwave ovens, electromagnetic equipment, other APs, walls and other obstacles can reduce effective coverage and degrade signal quality.

That distinction matters because an RF coverage number measured or specified under favorable conditions does not automatically become a production placement distance.

Even in a relatively open venue, the real RF environment is not empty. Building materials affect propagation. Neighboring APs contribute additional RF energy. Electrical equipment can introduce interference. And the client side of the link matters as well: a smartphone or tablet does not necessarily have the same transmit capability or antenna characteristics as the access point serving it.

Most importantly for this project, a signal reaching a distant client did not prove that one AP should be responsible for every user inside that large coverage area.

A very large cell may look efficient when judged only by geometric coverage. In a high-density venue, however, increasing the area served by each AP also tends to increase the number of clients competing for that AP's available radio resources.

That was the reason the project did not turn the ~100 m ideal coverage reference into the deployment radius.

Coverage Was Only Half of the Calculation

The key engineering distinction in this project was simple:

The project team had to consider both.

If the AP count had been reduced simply because one AP could reach farther in an open environment, each remaining AP would have been responsible for a larger share of the user population.

In a venue where total terminal counts might approach 2,000, that matters. More clients sharing the same AP means more devices competing for airtime. As contention increases, retries and access competition can also increase, and the user experience during busy periods can deteriorate even though the Wi-Fi icon still shows that a signal is present.

The original project document does not provide measured Mbps per client, latency, channel utilization, RSSI or airtime-utilization results, so those values should not be invented. What it does document is the design logic: the team combined the physical coverage requirement with the expected user population before deciding the AP radius and capacity class.

That is the important evidence.

The approximately 30-meter radius was therefore not selected because the AP was incapable of reaching farther. It was selected because increasing cell size would have worked against the capacity requirement of the venue.

The Decision: Approximately 30 Meters

The recorded planning inputs can be summarized as follows:

The original AP coverage-planning section explicitly records the 30-45 m practical range, the potential ~2,000-user population, the final ~30 m planning radius and the decision to select a high-capacity AP class supporting 150+ users.

The page 3 planning diagram also illustrates the project's open-space AP placement concept rather than treating one theoretical maximum-coverage cell as sufficient for the entire venue.

These numbers should not be copied into a different building and treated as a formula. They belonged to this project's assumptions about space, client population and AP capability.

What This Project Taught Us

The engineering principle from this case is narrower-and more useful-than a generic list of wireless best practices:

The project started with physical coverage, but user density changed the deployment decision.

That principle still applies when evaluating a current wireless project, even though today's hardware is different. The actual floor plan, peak concurrent clients, wall materials, application demand, RF environment and current AP radio capability all need to be considered together.

Current enterprise wireless access points vary significantly in radio capacity, antenna design, uplink capability and intended deployment scenario. The appropriate model-and the number of units required-should therefore be selected from the actual site requirements rather than from one maximum-coverage specification.

The point is not that "30 meters is correct."

The point is that coverage radius is only one design input.

Applying the Same Planning Logic to Business Wi-Fi Projects

The same planning logic now applies well beyond university campuses.

Hotels, cafés and restaurants, retail stores, coworking spaces, student housing and SMB offices can all experience the same mismatch between apparent signal coverage and actual busy-hour capacity. An AP may cover the physical area while the network still struggles when many users, POS devices, staff terminals and other endpoints become active at the same time.

For current projects, we therefore start from the floor layout, expected client density and application demand rather than asking only for the maximum advertised AP range.

If you are planning a new wireless network, expanding an existing site, trying to estimate AP quantity, or reviewing an existing BOM, our high-traffic business network solutions workflow is built around this project-specific approach. Floor plans and BOMs can be reviewed for AP capacity and placement together with the surrounding network requirements.

The historical campus values in this case should not be copied directly into those projects. The planning method carries forward; the actual AP count and placement must be recalculated for each site.