Plenty of organisations in London have already had “the big Wi-Fi upgrade” – new access points, shiny dashboards, maybe even a move to Wi-Fi 6. And yet the complaints keep coming:
- “Teams drops every time I walk to the meeting room.”
- “Guests can’t get online before their pitch.”
- “The warehouse scanners are still hit and miss.”
In most cases the problem isn’t that you bought the wrong kit. It’s that the original project didn’t line up design, cabling, configuration and validation in a way that matches how your business actually works today.
The good news: you rarely need to rip everything out and start again. With a structured rescue plan you can stabilise an underperforming WLAN, protect your investment, and give users the experience they thought they were getting the first time.
1. Know the symptoms of a “missed” Wi-Fi project
If you recognise two or more of these, you’re not alone:
- Great speed tests, terrible calls
Speedtest numbers look fine at a desk, but Teams/Zoom calls glitch the moment a room fills up. - Good in the morning, awful by mid-day
Wi-Fi feels OK at 8:30, then falls apart around 11:00 when more people and devices arrive. - Guests are always “having issues”
Sales and visitors struggle to join the guest network, or captive portals hang at busy times. - Roaming roulette
Calls drop when people move between meeting rooms or through lift lobbies. - Blame ping-pong
The ISP blames the Wi-Fi. The Wi-Fi vendor blames the ISP. Users blame both.
These symptoms point to design and configuration gaps more than fundamental hardware failure.
2. Step one: collect evidence, not opinions
Before touching settings, build a clear picture of what’s happening.
Listen to users – but structure what you hear
- Where are the “pain zones”? (Boardrooms, warehouse aisles, café, reception…)
- Is it time-specific? (Mid-mornings, after lunch, Friday afternoons…)
- What apps are failing? (Voice/video, scanning, VPN, simple browsing…)
Map this onto a floor plan so you can compare it with where the original APs were placed.
Pull data from the controller
Most platforms will show you:
- Client failure reasons (DHCP timeouts, bad PSKs, RADIUS issues)
- Airtime utilisation and retry rates per radio
- Channel usage and DFS events
- APs that are regularly overloaded vs those that sit idle
Export a week of data covering your busiest days – usually Tuesday to Thursday in hybrid offices.
3. Check the wired foundations first
A surprising number of “Wi-Fi” issues are actually wired ones.
- PoE headroom
Check each switch’s PoE budget. If you’re running close to the limit, radios can quietly downgrade or flap under load. - DHCP & DNS health
Slow or exhausted DHCP scopes and sluggish DNS resolvers are top causes of “I can’t get online” reports. - Cabinet hygiene
Over-long patch leads, mystery cables, poor labelling and blocked airflow all increase failure rates and make repairs slow. - Backbone capacity
If several busy APs, cameras and other devices share a single 1G uplink, you’ll see congestion at busy times no matter how good the RF is.
Fixing these doesn’t just help Wi-Fi; it strengthens everything that rides on your network.
4. Audit the RF design against reality
Next, compare what was designed with how the space is actually used now.
Coverage vs capacity
- The heatmap might be green everywhere, but how many concurrent devices were the APs in each area sized for?
- Boardrooms, collaboration zones and cafés often need more APs at lower transmit power, not a single high-power unit.
Channel widths and planning
- In dense London environments, 80 MHz channels on 5 GHz usually collide with neighbours.
- Starting with 20 or 40 MHz channels gives you more clean lanes and fewer clashes.
Minimum data rates and sticky clients
- Very low minimum data rates (1–6 Mbps) let devices cling to weak signals, hogging airtime for everyone.
- Stepping minimums up to 12–24 Mbps encourages clients to move onto healthier cells.
Roaming paths
Walk the paths people take – from desk to meeting room, through lift lobbies, along warehouse aisles. Look for:
- Sudden drops in signal
- APs that overlap too much (or not enough)
- Dead spots behind pillars, glass or metal fixtures
This tells you whether you need more APs, better placement, or just power and channel tweaks.
5. Apply the “no new hardware” quick wins
You can often achieve a big improvement just by cleaning up configuration and RF hygiene:
- Reduce SSIDs
Every SSID adds management overhead. Aim for:
- Corporate (802.1X)
- Devices/AV (per-device PSKs)
- Guest (isolated, rate-limited)
- Corporate (802.1X)
- Right-size channels
Move 5 GHz radios to 20/40 MHz. Keep 2.4 GHz only where it’s truly needed for legacy or IoT devices. - Tune transmit power
Cap TX power so cells are small and intentional, with enough overlap for roaming but without bleeding through floors and walls. - Raise minimum data rates
This alone can transform call quality in busy rooms, because clients stop whispering at the edge of coverage. - Segment traffic logically
Put AV/IoT and guest devices on their own VLANs with least-privilege access, so noisy or compromised kit can’t bother the corporate side.
At this point you should already see a reduction in complaints, especially in the busiest areas.
6. Decide where investment will actually help
If problems remain after quick wins, you’re probably looking at one (or more) of these:
- Under-coverage in high-density zones
Meeting spaces, lecture rooms or packing areas may simply need more APs at lower power. - Consumer-grade gear in business spaces
Home-style routers and extenders struggle badly with dense client counts. - Starved uplinks and PoE
A couple of upgraded switches and properly planned fibre backbones can unlock performance your current APs never had the chance to deliver. - Outdated client estate
Some very old devices behave poorly on modern networks; building a plan to retire or isolate them is part of the fix.
If you want a structured, engineer-led approach – survey, RF model, cabling review, configuration and post-fix validation – it’s worth bringing in a specialist Wi-Fi installation partner in London like ACCL’s dedicated wireless team to own the design and give you a clear set of before/after metrics.
7. Define acceptance tests for the “rescued” network
A rescue project isn’t finished when the tickets go quiet for a week. Set formal tests so everyone agrees what “fixed” means:
- Join time: New devices should authenticate, get DHCP and resolve DNS in under five seconds at peak.
- Call quality: In defined rooms, median and p95 latency/jitter should stay within agreed bounds during real meetings.
- Roaming: Calls should remain stable as people move along agreed paths (e.g., between meeting rooms or across the shop floor).
- Guest experience: Visitors connect first time and reach the internet without hanging at the portal.
- Stability: No more regular AP flaps from PoE issues or random channel changes that weren’t planned.
Capture “before” and “after” screenshots and exports – they’re invaluable when you need to show stakeholders what’s improved.
8. Make “care and feeding” part of normal operations
Finally, build a lightweight operational rhythm so the network stays healthy instead of slowly drifting back into trouble:
- Quarterly health checks
Review RF stats, PoE headroom, DHCP/DNS performance, and any new high-density areas created by office moves. - Firmware cadence
Plan, test and stage controller and AP upgrades rather than hitting “update all” in one go. - Change control that actually gets used
Simple, documented steps for adding an SSID, moving an AP or changing VLANs – plus who updates the floor plans and patch schedules. - Review new projects early
Treat big AV installs, office moves and warehouse re-layouts as triggers for a quick Wi-Fi and cabling review.
The bottom line
A disappointing Wi-Fi deployment doesn’t mean you chose the wrong vendor or need a total rip-and-replace. It usually means key pieces – cabling, RF design, configuration, validation – weren’t properly aligned with how your business works day to day.
By gathering evidence, fixing the wired basics, cleaning up RF and SSIDs, and then investing only where it truly matters, you can turn a flaky network into a reliable platform that quietly does its job. Users stop talking about the Wi-Fi – and start focusing on the work they came to do.
