Guides 3 September 2026 5 min read

Wi-Fi that covers a building, not just a room

More repeaters is the wrong answer. Why office Wi-Fi really fails, what a proper deployment involves, and how to tell a survey from a sales visit.

By the PearlFibers Team

The complaint is always phrased the same way: "the internet is slow in the back offices." Nine times out of ten the internet is fine. The line into the building is delivering everything it promised, right up to the point where it has to cross forty metres of concrete to reach a laptop in the last meeting room.

Internet and network are two different purchases, and confusing them is the most expensive mistake in this whole category — because it makes companies upgrade the wrong thing, twice.

Why one router cannot cover an office

This is physics before it is engineering. The 5 GHz band that carries fast connections is also the band that concrete, rebar and plasterboard absorb most enthusiastically. The 2.4 GHz band travels further and through more, which is why the signal bar still shows two bars in the far room — and why those two bars deliver almost nothing usable, on a band already crowded with every other router and device in the building.

Meanwhile the device itself is trying to be polite: your phone clings to the access point it first connected to long past the point where a nearer one would serve it better. So people sit two metres from a strong signal, connected to a weak one, and conclude the internet is broken.

The repeater trap

The standard first response is to buy a repeater or two. It seems to help, then it makes things worse in ways that are hard to attribute:

• A repeater talks to your clients and back to the router on the same radio, so it roughly halves the throughput of everything passing through it. Two hops, one quarter.
• It usually creates a second network name, so devices must be told manually to switch — and never do it at the right moment.
• It repeats interference as faithfully as it repeats signal.
• Devices at the edge of the repeater's range now have two weak options instead of one.

Coverage problems are not solved by amplifying a bad plan. They are solved by putting the signal where people are, which means cable.

What a real deployment involves

Every proper Wi-Fi installation is, underneath, a cabling job with radios attached:

1. A site survey. Someone walks the actual building — floors, wall construction, where people actually sit, which rooms fill with thirty devices at 10am — and measures rather than guesses.
2. Access points placed by coverage, not by convenience. Ceiling-mounted, spaced from the survey, in the rooms that need them rather than in the corridor where the cable happened to end.
3. A cable to each one. Structured cabling back to a switch, with power over the same cable, so each access point needs no socket of its own.
4. Channel planning. Neighbouring access points on non-overlapping channels at sensible power, so they do not shout over each other. Turning everything to maximum power is a classic own goal.
5. One network name, real roaming. Your phone hands off between access points as you walk, without dropping the call you are on.
6. Guests kept separate. A guest network on its own segment that reaches the internet and nothing else — not your file server, not your cameras, not the accounting PC.

Coverage and capacity are different problems

A meeting room with a strong signal and thirty people in it can still crawl. Radio is a shared medium: every device takes its turn, and slow devices take longer turns. A room designed for coverage has one access point in range; a room designed for capacity has enough radios, on enough channels, to serve the number of devices that actually gather there.

This is why a training room, an event hall and a quiet back office with four staff need genuinely different designs even though the floor plan calls them all "rooms".

The things that are not the Wi-Fi

Before blaming radio, three unglamorous culprits are worth ruling out:

• The switch. An unmanaged desk switch daisy-chained through three offices will bottleneck everything behind it regardless of how good the access points are.
• Cable quality and length. Copper runs have limits and site-made patch cables have a talent for intermittent faults that look exactly like Wi-Fi problems.
• Power. In a building where the grid comes and goes, an access point that reboots with every transfer is not a coverage problem, it is a power problem. Put the switch and the access points on a UPS, or accept a network that restarts several times a day. We have written before about designing for the outage rather than around it.

How to tell a survey from a sales visit

A survey produces a document. A sales visit produces a quote. The difference shows up in what you are handed:

Ask for the plan at handover

The most neglected deliverable in networking is documentation. When the installers leave, you should have: a labelled patch panel, a diagram of what connects where, the switch and access-point management credentials in your own possession, and the guest network's separation written down so the next person understands why it exists.

Without that, your network becomes a mystery that only the original installer can service — which is a commercial position for them and a risk for you.

How we do it

Our connectivity work starts with the building, not a brochure: a walkthrough, a written survey report, then a coverage map, an itemised equipment list and a fixed installation price before anyone lifts a cable. Installation is scheduled around your working hours and verified room by room with you before we call it done.

We also run networks that carry more than laptops. At Business Avenue, the same infrastructure carries the door devices on the meeting rooms — cameras, printers, access control and staff traffic properly segmented, because a network that treats every device as equal is a network with a locked door that stops working when someone starts a large download.