08/10/2026
BUILDLAB
8 min readHow Many WiFi Access Points Does a Multifamily Building Actually Need?
Guessing WiFi access point count off unit count alone leads to dead zones or wasted budget. Here is how real coverage-area math — and a hard look at what multifamily construction does to a vendor’s lab-tested spec — should actually drive AP placement.
Ask five low-voltage contractors how many WiFi access points a 120-unit apartment building needs, and there is a good chance you get five different answers — most of them anchored to unit count, not to the building itself. One AP per floor. One per every ten units. One per corridor. None of those rules of thumb come from measuring anything; they come from habit. And in a building where residents expect enterprise-grade WiFi in every unit, hallway, and amenity space, a habit is not a coverage plan.
Why Unit Count Is the Wrong Starting Point
Two buildings can carry the identical unit count and still need a completely different access point plan. A narrow double-loaded-corridor building with units stacked tight against a central hallway covers very differently than a sprawling garden-style property with breezeways, courtyards, and detached buildings. Unit count tells you how many people live there. It tells you nothing about the floor plate shape, the wall assemblies between units, or how far a radio signal actually travels before it is absorbed, reflected, or blocked outright.
The real question is not how many units sit on a floor. It is how many square feet a given access point can actually cover once you account for the walls, floors, and materials of that specific building — and where those coverage areas need to land on the real floor plate so they overlap enough to prevent dead zones without stacking redundant hardware nobody needed.
Start With the Spec Sheet, Not a Rule of Thumb
Every enterprise access point ships with a published coverage area figure on its manufacturer data sheet. Real enterprise APs such as the Ubiquiti U7-Pro or U6-Mesh publish a coverage area of roughly 1,500 square feet. That number is not marketing fluff — it is a real, testable spec, the same category of figure an engineer pulls before sizing anything else in a building.
The useful move is converting that square-footage figure into something you can actually draw on a floor plan: an effective coverage radius. The math is a simple circular-area approximation — radius equals the square root of the coverage area divided by pi. Run that on a 1,500 square foot spec and the result is a coverage circle with roughly a 22-foot radius, or about 44 feet across. That circle, not the unit count, is the real unit of measurement for AP planning.
Once you have that radius, the process stops being a guess. You draw circles of that radius on the building’s real floor plan, starting from the corridors and unit clusters that are hardest to reach, and you look for where the circles stop overlapping. Gaps on the drawing are dead zones in the finished building. Overlap that runs deeper than necessary is budget spent on access points the building did not need.
The Multifamily Discount: Why the Lab Number Doesn’t Survive Contact With the Building
A published coverage-area figure comes from a lab environment or an open office layout — the kind of space with drywall partitions and clear sightlines, not the kind of construction standing between two apartment units. Multifamily buildings attenuate signal far more aggressively than the environment a vendor tests in, and the gap between the lab number and the real number is exactly where dead zones come from.
- Fire-rated demising walls between units — often two layers of five-eighths-inch drywall with insulation, or full CMU block, each cutting signal far harder than the single interior partition a vendor’s lab number assumes
- Concrete or gypcrete floor and ceiling assemblies between levels — built for fire rating and sound isolation, and both of those properties also make them excellent radio-frequency blockers
- Elevator shafts, stairwells, and mechanical or electrical chases — dense, frequently metal-lined, and physically impossible to run a coverage circle through no matter how the math works out on paper
- Metal-clad entry doors and built-in appliances — full-height metal surfaces reflect and scatter signal unpredictably inside the tight footprint of a typical unit
- Sheer wall density — a multifamily unit layout simply has more walls per square foot than the open floor plan a vendor tested against
None of this makes the published spec useless. It means the spec is a starting point, not a finished plan. The honest approach treats the manufacturer’s coverage-area number as the radius to start drawing with, then checks that radius against the building’s actual construction and floor plan before calling the placement final — not after the drywall is closed up and a resident is standing in a dead zone.
Common Areas Are a Separate Coverage Problem
It is tempting to treat common areas as just an extension of the in-unit AP grid — add a couple more access points near the lobby and call it done. Common-area coverage is a different problem with different variables, and it deserves its own pass rather than an afterthought.
- Leasing office and clubhouse — often the first place a prospective resident tests the WiFi, and because these are typically open floor plans, they behave closer to the vendor’s lab conditions than a unit does, which usually makes this the easier part of the plan rather than the harder part
- Fitness center and coworking lounges — high device density from residents on phones and laptops, plus metal exercise equipment, changes the coverage math even in a modestly sized room
- Amenity decks, pools, and courtyards — outdoor coverage means weatherized access point hardware and accounting for open-air signal loss plus obstructions from site furniture, landscaping, and structural overhangs
- Parking structures and garages — concrete, low ceilings, and vehicles acting as moving obstructions make this one of the hardest coverage zones on the entire property, and it is the zone most often skipped entirely by a plan built off unit count alone
Guessing vs. Measuring
Coverage Count Is Half the Plan — Cabling Is the Other Half
Knowing how many access points a building needs and where they go is only half of a real WiFi plan. Every one of those access points also needs power and a real network connection, which means a matching PoE budget and Cat6A-or-better backhaul cabling run to each placement — a related but separate decision from the coverage math covered here. Get the AP count and placement right first; the cabling and power budget should be sized to match that real plan, not the other way around.
How BuildLab Plans AP Coverage
BuildLab’s WiFi Designer approach starts from a building’s actual floor plans, not an assumption about unit count. Each access point model in the plan carries its own real, published coverage-area spec, converted to an effective coverage radius and placed directly against the building’s real dimensions — unit by unit, corridor by corridor, with common areas planned as their own zones. The result is an AP count and placement plan sized to the building in front of us, paired with the PoE and cabling budget that plan actually requires, rather than a number pulled from a rule of thumb.
