Article
Most office networks do not fail in one dramatic moment. They degrade: a new team fills a meeting room, a switch loses its management access, and suddenly the Wi-Fi that was fine last year is the first complaint in every staff meeting.
A refresh is not automatically a replacement project. The useful question is which parts of the design have run out of headroom, and which parts can be reused with better configuration and documentation.
Coverage is not the same as capacity
A wireless survey can show strong signal in every corner and still miss the problem. Signal strength says a device can hear the access point; capacity says the access point can carry the number of devices and applications in that room at the same time.
High-density spaces, guest networks, and cloud applications all change the calculation. If the design was sized for one laptop per desk, a room full of video calls will expose it.
The switch cabinet tells the story
Unlabelled cabling, daisy-chained switches, and a firewall doing three jobs are reliable signs that the network grew by addition rather than design. None of those things is a disaster on its own, but together they make every change slower and every outage harder to diagnose.
A documented IP plan, clean patching, and a clear separation between users, guests, devices, and servers make the biggest difference to day-to-day support.
What a refresh should include
Start with an assessment of traffic, coverage, and risk. Then agree a target design, a migration sequence, and the rollback plan for each cutover. The final deliverable should include as-built diagrams and an IP plan your own team can use.
That approach lets you replace only what needs replacing, keep the business running during the work, and leave with an estate that is easier to support than the one you started with.