Why Your Office Wi-Fi Has Dead Zones (and What a Real Design Pass Fixes)

Quick answers

Why does my office have Wi-Fi dead zones? Almost always because access points were placed by guess instead of by design — too few, too far apart, mounted in the wrong spot, or fighting building materials that eat signal.

Will adding more access points fix it? Usually not. Extra APs on the wrong channels create interference and make the problem worse, not better.

What's the difference between a consumer router and a commercial AP? A commercial access point does one job — radio coverage — with a wired connection back to a switch, centralized channel and power control, and seamless roaming between units.

How much does commercial Wi-Fi installation cost? It's driven mostly by cabling labor and AP count, not the APs themselves; a small office might need four to six APs, a warehouse might need a dozen with different antennas.

Can I keep my existing cabling? Sometimes. If you have Cat5e or Cat6 already run to reasonable ceiling locations, we can often reuse it. Ceiling drops that end above a cubicle wall three rooms away, we can't.

The complaint you're tired of hearing

"The Wi-Fi is down again."

It isn't down. If it were down, everybody would say so at once. What's actually happening is that the sales rep in the northeast corner office drops off her Teams call every afternoon, the warehouse tablets lose connection halfway down aisle 6, and the conference room at the end of the hall works fine for two people but falls apart when eight laptops join.

Those are three different problems with three different fixes, and the reason they all get reported as "the Wi-Fi is down" is that nobody in the building has any visibility into what the wireless network is actually doing. So the default response is to buy another box, plug it in somewhere near the complaint, and hope.

That's how most office Wi-Fi dead zones get created in the first place.

Consumer router vs. commercial access point

Let's get the vocabulary straight, because it drives everything else.

A consumer router — the thing from the big box store — is four devices in one plastic shell: an internet gateway, a firewall, a network switch, and a Wi-Fi radio. It's designed to cover one house from one location and serve maybe twenty devices. It makes all its own decisions about channels and transmit power and it doesn't coordinate with anything else.

A commercial access point is one device doing one job: radio coverage for a defined area. Routing, firewalling, and switching live elsewhere in a rack. The AP gets its power and its data over a single Ethernet cable (Power over Ethernet), it's managed centrally alongside every other AP in the building, and it's designed to hand a device off cleanly to the next AP as somebody walks down the hall.

That last part matters more than people expect. When you install three consumer routers in a building, you get three separate wireless networks that happen to share a name. A laptop that connects to the one by the front door will cling to it all the way to the back of the building, hanging on at one bar rather than switching. Users experience that as "it says I'm connected but nothing works" — the single most common Wi-Fi complaint we get called about.

Mesh systems deserve a specific note because they get pitched hard. Wireless mesh — where APs talk to each other over the air instead of over cable — is a legitimate tool when running cable is genuinely impossible. But every mesh hop costs you roughly half the available throughput, and it consumes airtime that your actual users need. In a commercial building where we can get above a drop ceiling, mesh is a compromise you shouldn't have to make. Wire the APs.

What's actually eating your signal

This is the part that surprises office managers. Wi-Fi doesn't fail over distance nearly as often as it fails over materials. Here's what we run into in Treasure Valley buildings specifically.

Metal studs. Most commercial tenant improvement work in the valley is steel stud framing with gypsum board. Drywall alone is nearly transparent to 2.4 and 5 GHz. But steel studs at 16 inches on center form a partial grid that scatters signal — and once you add insulation and a second layer of board, an interior wall that looks like nothing on the floor plan can cost you meaningful signal. Two or three of those walls between the AP and the user, and you're done.

Low-e glass. Nearly every newer office building in Boise and Meridian has low-emissivity window coatings — a microscopically thin metallic layer that keeps summer heat out. It's also very good at blocking RF. This is why an AP in the hallway doesn't cover the corner office with two exterior walls, and why you can't cover a courtyard or patio from inside the building. It also means Wi-Fi bleed to the parking lot is less of a concern than people think.

Warehouse racking and inventory. In a distribution or storage space, the racking itself is steel and the pallets on it might be liquid, metal, or dense paper — all of which absorb 5 GHz aggressively. Coverage measured in an empty warehouse is worthless. A rack of bottled product is close to a wall as far as the radio is concerned. Aisles behave like waveguides: great signal down the aisle, nothing across it.

Tilt-up concrete and CMU. Common in the industrial parks along Franklin and out toward Nampa. Concrete is a hard stop. Plan on APs on both sides of any concrete wall.

Mirrors, cooler doors, and elevator shafts. Medical and retail spaces have their own culprits. Refrigerated cases, imaging equipment rooms, lead-lined walls in dental and medical suites — all of it real, all of it invisible on a floor plan.

Your neighbors. In a multi-tenant building you're sharing the airwaves with everybody around you. The 2.4 GHz band has effectively three non-overlapping channels, and in a busy office park all three are crowded. If your APs and the suite next door are both blasting at full power on channel 6, you're both worse off.

Why "one AP per hallway" fails

The intuition behind spacing APs evenly down a corridor is fine. The execution usually isn't, for three reasons.

1. Hallways are the worst place to measure from. A corridor is an open path — signal travels down it beautifully. So a phone standing in the hall shows full bars everywhere and everything looks great. Meanwhile the offices on either side, behind steel studs and door frames and file cabinets, are the places people actually sit.

2. Coverage isn't the same as capacity. A single AP can throw a usable signal across a big open office. That doesn't mean it can serve 45 laptops, 30 phones, a couple of wireless printers, and a conference room video call at the same time. Every device shares airtime. In dense areas — open floor plans, training rooms, waiting rooms — you place APs for the number of clients, then turn power down so each one covers a smaller area and they don't step on each other.

3. Transmit power gets cranked to max. When a single AP has to cover too much ground, the instinct is to run it at full power. But Wi-Fi is a two-way conversation, and your laptop's radio is much weaker than the AP's. The AP shouts, the laptop whispers, and the connection is one-directional garbage. Clients hang on to a "strong" signal they can't actually talk back to. Lower power with more APs beats high power with fewer, almost every time.

What a real design pass looks like

Here's what we actually do, and what you should expect from anyone quoting business Wi-Fi design.

1. Walk the building with the floor plan in hand

Not just the plan — the building. We're marking wall types, ceiling heights, hard-lid areas where there's no accessible ceiling, glass lines, and anywhere structure blocks a cable path. In a warehouse we're noting rack height and orientation, and whether the racking will move. In medical we're asking about lead-lined rooms before we design around them.

We're also asking about use, because it changes everything: where do people sit, where do people roam, is there a wireless scanner or VoIP handset fleet, does anyone use the patio, does the tenant next door share your electrical room.

2. Predictive design, then verification

We model coverage against the actual wall materials and mark AP locations on the plan. That gets you a defensible starting point and an AP count you can budget against. After install, we verify with a real survey — walking the space with a measurement tool, checking signal and noise and what a client device actually experiences in the corners of the building.

Predictive design without verification is a guess with a nicer PDF. Verification without predictive design means you find out you're four APs short after the ceiling is closed.

3. Channel and power planning

Every AP gets a channel assignment and a power level chosen so that neighboring APs don't compete. On 5 GHz there's real room to work with; on 2.4 GHz we often disable radios on some APs entirely rather than pollute the band. If you're in a shared building, we look at what's already on the air before choosing.

This is also where band steering, minimum data rates, and roaming settings get tuned. Raising the minimum data rate is a small change that kicks distant, half-dead clients off an AP so they'll go find a closer one — one of the highest-value fifteen-minute adjustments in the whole job.

4. Wired backhaul and PoE

Every AP gets a home run of Cat6 (or Cat6a for higher-capacity APs and longer runs) back to a switch with enough PoE budget to feed them all. This is where most of the labor lives, and it's why cabling and Wi-Fi should be quoted as one job. If you're building new or doing a TI, this is also the moment to decide your cable spec — we broke down Cat6 vs. Cat6a and where the extra cost is actually justified in an earlier post.

Two practical notes: mount APs on the ceiling, not above it. A ceiling tile is fine to shoot through; an AP shoved in the plenum lying on top of a light fixture, facing sideways, is not. And don't put APs in the IT closet. We see it constantly — all the APs mounted in the room where all the cables end, because that was easy. The radio can't do anything about a metal rack and a closed door.

5. VLANs and guest separation

Once you have real infrastructure, separate your traffic. Corporate devices on one network, guest Wi-Fi on another that can reach the internet and nothing else, and cameras, access control, and building systems on their own segment. If your security cameras and door controllers are sharing a flat network with the guest SSID, that's worth fixing while the ceiling is open.

Do you need a full redesign, or a tune-up?

Not every complaint requires ripping everything out. Rough guide:

Tune-up territory — you have real commercial APs, wired back to a switch, but performance is uneven. Channel/power adjustment, minimum data rate changes, firmware updates, and maybe one or two added APs will likely get you there.

Redesign territory — you're running consumer gear or a mesh kit, APs are plugged in wherever a spare jack existed, or the space has changed (you built out offices in what was open floor, added racking, took over the suite next door). Adding boxes to a bad layout compounds the problem.

Cabling-first territory — the building has no usable ceiling drops at all, or everything terminates in a closet with no patch panel and no PoE. Then it's a structured cabling project with APs at the end of it, and honestly that's the version that ages best.

How we approach it

We're a Ubiquiti UniFi shop across the board — networking, Wi-Fi, cameras, door access. The reason is boring and practical: it's one ecosystem, one app, hardware the customer owns outright, and no per-device monthly license to keep the lights on. When your APs, switches, and cameras all live in the same controller, troubleshooting "the Wi-Fi is down" takes minutes instead of an afternoon of finger-pointing. We wrote about the same ownership-vs-subscription tradeoff on the camera side here, and the logic carries over.

Is UniFi right for everyone? No. If you're a hospital or a large campus with hundreds of APs, thousands of concurrent clients, and a full-time network team, enterprise platforms like Cisco Meraki, Aruba, or Juniper Mist have RF management, analytics, and support contracts that go deeper than what we'd deploy. If your IT is outsourced to an MSP that standardizes on something else, use theirs. We'll say so on the site walk rather than force a fit.

For the offices, clinics, warehouses, churches, and retail spaces we work in around the valley — five to forty access points, a few hundred devices — UniFi does the job well and doesn't bill you every month for the privilege.

Frequently asked questions

How many access points does a typical office need?

Depends far more on walls and headcount than square footage, but as a rough starting point for standard office construction, plan on one AP per 2,000–3,000 square feet of enclosed office space, and more in dense areas like open floor plans and training rooms. Open warehouse is a different math entirely — fewer APs but different antenna choices.

Will Wi-Fi 6 or Wi-Fi 7 fix my dead zones?

No. Newer standards improve throughput and handle dense client counts better, but they don't punch through steel studs or low-e glass any better than Wi-Fi 5 did. If your problem is coverage, the fix is placement and cabling, not a hardware generation.

Can you install access points in a building with no accessible ceiling?

Yes, but the approach changes. Hard-lid ceilings, open-deck warehouses, and historic buildings usually mean surface-mount raceway, wall-mounted APs, or routing cable through existing chases. We figure that out on the walk — it affects both the design and the labor number.

Should the Wi-Fi be on the same network as my cameras and door access?

Same physical cabling and switches, yes — that's the efficient way to do it. Same logical network, no. Cameras, access control, and building systems belong on their own VLAN, separate from staff and especially from guest Wi-Fi.

Who fixes it when something goes wrong later?

Whoever installed it should be able to log into the controller and see the whole picture. That's the real argument for having one contractor handle the cabling, the switching, and the APs — nobody gets to blame the other guy's equipment.

If your team is reporting the same dead spots week after week, book a site walk and we'll tell you honestly whether you need a redesign or a tune-up — either way, you'll get a fixed quote before anyone touches a ceiling tile.