Your Salt Lake City office has a $200/month fiber connection, a router that cost $400, and a back conference room where Zoom calls are a coin flip. You have rebooted the router. You have called the ISP. You have been told your internet is fine.
It is not the internet.
Dead zones are not a hardware problem. They are a network design problem. The router you just replaced was probably fine. The WiFi extender you plugged in made things marginally better near the closet and measurably worse everywhere else. And the technician who told you your signal was strong was standing three feet from the access point when he said it.
This guide explains the seven real causes of WiFi dead zones in commercial offices, what professional network design actually looks like, how many access points your building needs, and why Utah’s specific construction landscape creates wireless problems that no out-of-state provider will diagnose correctly. By the end, you will know exactly what questions to ask any WiFi vendor and exactly what answers should disqualify them.
Key Takeaways
- Dead zones are a design problem. Buying better hardware solves the wrong problem in most cases.
- Sticky roaming is the most common culprit. A configuration fix, not new equipment, is usually the answer.
- You need more access points than you think. A single router cannot cover a business-sized office reliably.
- Utah buildings are not generic. Brick, concrete, and glass each kill WiFi signal differently and require different solutions.
- No heat map before the quote means no real design. A provider who skips the RF survey is guessing.
Why Your Office Has Dead Zones
Seven Root Causes That Are Not Your Router
Most dead zone conversations start in the wrong place. The frustrated office manager calls the ISP. The ISP confirms the internet is working. The manager buys a better router. The conference room still drops calls. Then they call the router manufacturer. And so on.
The reason this loop never ends is that the wrong variable is being changed. Here are the actual causes:
| Root cause | What you notice | Common Utah context | Fix category |
|---|---|---|---|
| Too few access points for the floor area | Weak signal in far rooms; constant "1 bar" near elevator banks | Single-router deployments in 3,000 to 8,000 sq ft Provo or Sandy office suites | AP density planning based on floor area and device count |
| 6 GHz band range limitations | WiFi 6E/7 devices get fast speeds near the AP, then drop to slower bands 20 ft away | New WiFi 7 deployments in any office with rooms deeper than 20 ft from the AP | 6 GHz AP placement at shorter intervals than 5 GHz deployments |
| Physical obstructions | Strong signal on one side of a wall, nothing on the other; stairwells always dead | Concrete tilt-up construction in Ogden/West Valley; brick buildings in downtown SLC | RF survey to identify attenuation sources before placing APs |
| Co-channel interference | Network slows between 10 AM and 2 PM; conference rooms feel slower than open areas | Multi-tenant buildings across the Wasatch Front, where 10 to 20 competing SSIDs per floor is normal | Spectral intelligence: automated channel steering away from congested bands |
| Incorrect AP placement height | Inconsistent coverage pockets; devices roam erratically between APs | APs mounted on walls at 6 ft instead of ceiling; common in DIY deployments | Ceiling mount, correct height and angle per manufacturer spec |
| Client "sticky" roaming | Device holds a distant weak AP rather than roaming to the closer one; calls degrade mid-meeting | Any multi-AP office without 802.11r/k/v configured, extremely common in self-managed networks | 802.11r fast roaming, 802.11k neighbor lists, 802.11v BSS transition |
| Underpowered PoE switch port | AP works intermittently; resets randomly; performance inconsistent even in direct line of sight | Budget switches providing 15.4W when WiFi 7 APs require 60W or more | PoE budget, switch capacity, and cabling assessment before deployment |
A few of these deserve more explanation than a table row allows.
Co-channel interference is the invisible problem in dense Utah office buildings. When your network and the dozen others on your floor are all broadcasting on the same 5 GHz channel, they are not cooperating. They are competing. Every packet one network transmits forces all the others to wait. The symptom is a network that feels slow at 10 AM on a Tuesday for no obvious reason. The fix is spectral analysis and automatic channel steering, not a faster router.
Sticky roaming is the most common cause of perceived dead zones in multi-AP offices, and the least understood. Here is what happens: you walk from the front lobby into the back conference room. Your phone connected to the lobby AP when you arrived this morning. It is still connected to that AP, even though you are now 80 feet away and there is an access point 10 feet from the conference room table. Your device is “sticky.” It holds that distant connection until the signal degrades catastrophically, rather than smoothly transitioning to the closer AP. The result is a call that sounds fine in the lobby, degrades as you walk back, and drops or stutters in the conference room, even though the conference room AP has full signal. The fix is a configuration change: 802.11r (fast roaming), 802.11k (neighbor lists), and 802.11v (BSS transition management). These protocols instruct your devices to roam proactively. Most DIY and self-managed deployments do not configure them. Most of the “my WiFi is worse in the back of the office” complaints we hear are this problem.
What Professional Network Design Actually Involves
“Professional network design” sounds like an expensive consultant with a clipboard and impenetrable jargon. The reality is a methodical set of steps that any competent WiFi provider should follow before touching hardware. If a vendor skips any of these, you will end up with the same dead zones you have now, just with more expensive hardware generating them.
Step 1: RF site survey. A technician physically walks the space with spectrum analysis tools. Not a smartphone app, but actual spectrum analysis equipment. They map existing signal strength, identify physical obstructions, and catalog every interference source: neighboring networks, microwave appliances, Bluetooth devices, and building materials that attenuate signal. This step happens before any AP is specified.
Step 2: Device census. Every device that will connect to the network gets counted. Not just staff laptops, but IoT devices, building management systems, point-of-sale terminals, BYoD phones, printers, and guest devices. A 50-person medical office may have 200 connected devices. A 50-person law firm may have 65. Those are different network designs.
Step 3: Predictive RF modeling. Software models how signal will propagate through the building based on the floor plan, construction materials, and AP specifications. This happens before a single AP is installed. The output is a heat map showing predicted coverage across every square foot of the space.
Step 4: Coverage visualization. The heat map gets delivered to you before the quote. You can see exactly where the coverage zones are, where the APs will be placed, and where the edges of coverage fall. If a vendor cannot show you a heat map of your building before they recommend hardware, keep looking.
Step 5: Roaming configuration. 802.11r, 802.11k, and 802.11v get configured at deployment, not as an afterthought. Fast roaming means your devices transition between APs in under 50 milliseconds, which is invisible during a video call. Without it, every AP transition is a brief disconnect.
Step 6: Ongoing RF optimization. A channel assignment that was correct when the network was installed may be wrong six months later when a new tenant moved in upstairs with 30 of their own APs. Automatic channel and power adjustment means the network keeps optimizing as the RF environment changes, without requiring a technician to come back and manually reconfigure.
1Wire provides a coverage visualization before any quote. If a provider cannot show you a heat map of your building before they recommend hardware, keep looking.
How Many Access Points Does Your Office Actually Need?
The most surprising fact for most Utah SMB owners: a 5,000 square foot open-plan office needs 4 to 8 access points depending on density. Not one. Not a router and an extender. Four to eight dedicated access points, correctly placed and properly configured.
| Environment | Sq ft per AP | Key planning notes | Utah building example |
|---|---|---|---|
| Open-plan office, low density (less than 1 device per 30 sq ft) | 1,200 to 1,500 sq ft | 5 GHz handles most load; 6 GHz intervals can match 5 GHz at this density | Single-floor suites in Sandy or Murray office parks |
| Open-plan office, high density (1 or more devices per 30 sq ft) | 600 to 800 sq ft | WiFi 7 multi-link operation is critical here; device contention is the bottleneck, not range; reduce power levels to limit co-channel interference | SLC downtown tech offices; call center floors |
| Private offices and cubicle partitions | 800 to 1,000 sq ft | Partition materials significantly increase attenuation; always err toward shorter intervals in grid-partitioned floors | Law firms and financial services offices in Lehi or Draper |
| Conference-heavy floor (multiple meeting rooms) | One AP per room over 400 sq ft | Conference rooms generate burst-mode traffic spikes; a dedicated AP per room prevents congestion from bleeding into adjacent zones | Any multi-tenant building with shared conference floors |
| Warehouse or light industrial | 3,000 to 5,000 sq ft | Range increases in open warehouses; reduce to 1,500 to 2,000 sq ft with racking, machinery, or inventory present; 2.4 GHz needed for legacy scanner and IoT devices | West Valley, Ogden, or Clearfield industrial parks |
| Healthcare clinic or medical office | 600 to 800 sq ft | High device count; VLAN segmentation for clinical vs. guest adds complexity; design before you deploy | Provo, Orem, or St. George medical office buildings |
| Multi-floor with stairwells and elevators | Per-floor + vertical planning | Each floor is treated as an independent coverage zone; stairwells and elevator lobbies need dedicated APs because they are the highest-traffic roaming transition points in any multi-floor building | Any mid-rise in downtown SLC or University Research Park |
The 6 GHz Range Trade-Off
WiFi 6E and WiFi 7 access points operate on the 6 GHz band, which offers dramatically less interference than 2.4 or 5 GHz, but also a significantly shorter range. In a commercial office environment, plan for reliable 6 GHz coverage within 15 to 20 feet of the access point. An office designed for 5 GHz AP spacing will have 6 GHz coverage gaps between APs. This is not a defect in the standard. It is a physics trade-off that must be factored into AP placement from the start. Any vendor who installs WiFi 7 hardware without accounting for shorter 6 GHz range is giving you a $1,200 AP that performs like a $200 one in every room that is not directly adjacent to it.
For a deeper look at how WiFi 7 and 6E compare in real Utah office environments, see our guide: WiFi 7 vs WiFi 6E for Utah Businesses in 2026.
The fastest WiFi standard in the world cannot compensate for an AP you forgot to install.
Utah Buildings Are Different: Construction Challenges by Building Type
No national content, no out-of-state vendor, and no generic WiFi guide can write this section accurately. The construction materials and building types common across Utah’s commercial real estate create wireless challenges that are specific to this market. Here is what they are and what professional network design has to account for.
| Utah building type | Typical dead zone causes | Design considerations |
|---|---|---|
| Downtown SLC mid-rise Pre-1980s brick | Thick masonry walls severely attenuate 5 GHz and 6 GHz; elevator shafts and stairwells create hard signal voids | Higher AP density required (600 to 900 sq ft per AP); dedicated APs in stairwells; 2.4 GHz retained for range; budget for longer cable runs |
| Lehi/Draper tech corridor 2000s to 2020s glass and steel | Low-E window glass reflects and attenuates 5 GHz and 6 GHz signals; open-plan floors create co-channel interference across large distances | Reduce AP transmit power to limit co-channel range; place APs toward the interior rather than window-adjacent; spectral scanning is essential in dense tech park buildings |
| West Valley/Ogden tilt-up industrial Concrete construction | Concrete walls and ceilings heavily attenuate all WiFi bands; metal shelving and machinery create additional signal-blocking pockets | 2.4 GHz required for range in warehouse sections; 5 GHz and 6 GHz for office areas; APs must be mounted at or above racking height; consider directional antennas for long warehouse aisles |
| Provo/Orem medical office buildings 1990s to 2010s | Mix of drywall partitions and lead-lined radiology rooms; high device density from medical equipment; elevator lobbies consistently problematic | RF survey must identify lead-lined rooms before AP placement; VLAN design for clinical, IoT, and guest must precede hardware order; elevator lobby AP mandatory |
| University of Utah Research Park / Cottonwood Heights mixed-use Multi-tenant | Multi-tenant floors with independent networks on the same spectrum; high interference density from neighboring SSIDs | Spectral scan required before deployment; 6 GHz band is highest priority; DFS channel awareness for 5 GHz |
| St. George/Cedar City professional offices 1990s to 2000s wood frame | Wood frame and drywall attenuate less than masonry; dead zones are usually caused by layout rather than materials | Fewer APs needed than equivalent urban offices; the primary issue is often AP count (too few) rather than placement; single-AP deployments fail past approximately 2,500 sq ft |
DIY vs. Professionally Designed: An Honest Comparison
Plenty of IT managers and technically capable business owners have built solid WiFi deployments. This section is not an argument that self-managed networks are always bad. It is an explanation of where specific failure modes are structural, not because the person was incompetent, but because certain things are very hard to get right without specialized tools and ongoing attention.
| Factor | DIY / self-managed | Professionally designed + managed | Business impact of getting it wrong |
|---|---|---|---|
| AP placement | Where the cable already runs or where it looks tidy | RF site survey determines placement based on signal propagation, obstructions, and device density | Incorrect placement is the number one cause of dead zones and cannot be fixed by upgrading hardware |
| Channel assignment | Auto or default, which often collides with neighboring networks | Spectral scan identifies clear channels; auto-optimization adjusts in real time | Channel collisions in multi-tenant buildings cause 30 to 60% throughput loss with no obvious symptom |
| Roaming configuration | 802.11r/k/v often not configured; devices stay stuck to the wrong AP | Fast roaming protocols configured at deployment; client transitions in under 50 ms | Sticky clients cause Zoom and VoIP degradation that users blame on internet speed; replacing the ISP does not fix it |
| PoE infrastructure | Existing switch assumed to have sufficient PoE budget; often does not | Infrastructure audit confirms PoE class, cabling category, and switch port availability before any hardware is ordered | WiFi 7 APs require 802.3bt (PoE++); a 802.3af switch will brownout the AP under load, causing random reboots |
| Capacity planning | Based on headcount; IoT, BYoD, and guest devices usually not counted | Full device census including staff devices, IoT, BYoD, guest, and a future growth buffer | A 50-person office with 200+ connected devices needs different density than a 50-person office with 60 devices |
| Ongoing optimization | Static configuration until something breaks | Real-time RF optimization; power and channel adjustments happen automatically as the environment changes | A building that adds new tenants changes the RF environment; static configs degrade over months |
The PoE Trap
WiFi 7 access points commonly require 802.3bt (PoE++) at up to 60 watts per port. Many existing office switches provide 802.3af (15.4W) or 802.3at (25.5W). Connecting a high-power WiFi 7 AP to an underpowered PoE switch does not produce a clean “not enough power” error message. It results in the AP appearing to work, then rebooting randomly under load. That is exactly the symptom most people blame on the ISP or the WiFi standard itself. If your brand-new WiFi 7 AP reboots at 11 AM every day when your team is on calls, check your switch’s PoE class and total budget before assuming the AP is defective.
If cabling or switch infrastructure is part of the problem, our guide on 8 signs it is time to upgrade your office cabling can help you assess whether the upstream infrastructure needs attention first.
The question is not whether you can set up a WiFi network yourself. The question is whether the design will hold up as your team grows, your building changes, and the RF environment shifts. Most self-managed networks are designed once and left static. Every month after that, the gap between the design assumptions and the reality grows a little wider.
If you are evaluating managed WiFi vendors, our top business WiFi vendor comparison for Utah SMBs walks through what separates a competent provider from one that will leave you with the same problems six months later.
What to Expect From a Managed WiFi Provider That Actually Solves Dead Zones
By this point in the article, you have a clear picture of what causes dead zones and what fixing them actually requires. What follows is a description of what good looks like, the baseline you should hold any WiFi vendor to before signing anything.
A competent managed WiFi provider should deliver the following.
Before the quote: An RF site survey of your space and a coverage visualization, which is a heat map of your building showing exactly where APs will go and what coverage looks like. This is not a premium add-on. It is the minimum due diligence before any hardware is specified.
At deployment: 802.11r, 802.11k, and 802.11v configured and verified. A full device count, not just a headcount. PoE infrastructure confirmed before hardware arrives, not discovered as an issue after the fact. A complete VLAN design for any environment with clinical, IoT, or guest traffic requirements.
After deployment: Real-time spectral monitoring that identifies channel conflicts as they develop. Automatic power and channel adjustments that keep the network optimized as the RF environment changes. Proactive AP monitoring that catches a failing unit before your staff notices it. A single point of contact for hardware, configuration, and support.
Get a Map of Your Building Before You Spend Anything
1Wire’s Managed Business WiFi includes all of this: coverage visualization before any quote, spectral intelligence radio for ongoing RF optimization, and proactive monitoring that flags AP issues before they become outages. Hardware, installation, and ongoing management start at $19.95/month. There is no capital outlay for hardware, no separate maintenance contract, and no refresh cycle to plan around.
Schedule a free consultation »
You can also explore the full range of 1Wire Managed IT Solutions if your needs extend beyond WiFi to network management, security, or infrastructure support.
Frequently Asked Questions
Why does my WiFi work fine near the router but slow down in the conference room?
The most likely cause is sticky roaming. Your device connected to the main router when you walked in and is holding that connection even though a closer access point sits near the conference room. The fix is enabling 802.11r/k/v roaming protocols, which is a configuration change, not a hardware purchase. A secondary cause may be signal attenuation. If there are masonry walls, HVAC equipment, or elevator shafts between the router and the conference room, the signal is losing strength before it arrives. An RF survey identifies which of these is driving your specific problem.
Will buying a WiFi 7 router fix my dead zones?
Almost certainly not, if the problem is AP placement, roaming configuration, or co-channel interference. A $1,200 WiFi 7 AP placed in the wrong location will underperform a $300 WiFi 6E AP placed correctly. WiFi 7 is a meaningful upgrade for high-density environments where throughput and multi-link operation matter, but it does not compensate for incorrect network design. Buy the design first and let the design determine the hardware. See our WiFi 7 vs WiFi 6E guide for a full breakdown of when the upgrade actually makes sense.
How many access points does my office need?
Rough starting points: for a 3,000 sq ft open-plan office, 2 to 3 APs; for 5,000 sq ft, 4 to 5 APs; for 10,000 sq ft, 7 to 10 APs. These numbers change significantly based on device density, construction materials, and the presence of conference rooms or partitioned private offices. A high-density call center in a downtown SLC brick building needs more than double the AP count of the same square footage in a wood-frame St. George professional suite. These are starting points for an RF survey, not final specifications.
What is the difference between a WiFi extender and an access point?
A WiFi extender repeats the signal it receives from your router, including any interference and noise on that signal. It also creates a separate network name, which means your device may not roam cleanly between the router and the extender. A wireless access point is a dedicated device wired back to your network infrastructure via Ethernet cable. It broadcasts a clean, full-strength signal and participates in the same managed network as every other AP. Extenders add coverage at the cost of signal quality. Access points add coverage without that trade-off.
How does co-channel interference affect my office WiFi?
When multiple networks, yours and your neighbors’, broadcast on the same channel, they are required by the 802.11 protocol to share that channel by taking turns. The more networks on the channel, the longer each network waits before transmitting. In a dense multi-tenant building like those common in Lehi or downtown Salt Lake City, peak-hour co-channel interference can reduce effective throughput by 30 to 60 percent with no obvious symptom other than a network that feels slow. The fix is spectral scanning to identify clear channels and automatic steering to keep your network on them.
Can you fix an existing network, or does it have to be replaced entirely?
It depends on what is wrong. If the existing cabling runs to reasonable AP locations and the switch infrastructure supports modern PoE requirements, an existing deployment can often be reconfigured and supplemented rather than replaced. If APs are wall-mounted in the wrong locations, if the cabling only reaches one location per floor, or if the switch cannot support the PoE requirements of current hardware, a redesign is usually more cost-effective than patching. A site survey tells you which situation you are in before any money is committed.
