The guest Wi-Fi password has not changed since 2019. Visitors use it every day. Yet nobody has checked what the network can reach since it was first set up.
That is an easy thing to overlook. Guest Wi-Fi feels like a courtesy: a password on reception’s noticeboard, a captive portal, perhaps a small access point near the meeting room. In practice, it is part of your IT estate. It has connections, permissions, equipment and ongoing costs, and it deserves the same deliberate oversight as the systems your staff rely on.
For a business, the question is not simply whether visitors can get online. It is whether their connectivity is appropriately separated, managed and supported.
Guest connectivity is part of the estate
A visitor network depends on more than the access point on the ceiling. It may use wireless controllers, switch ports, VLANs, internet circuits, authentication services and a captive portal. Each component can be replaced, reconfigured, patched, or forgotten.
Over time, the network may acquire extra access points, new devices or inherited settings without anyone reviewing the overall design. A portal may still display old terms. The Wi-Fi controller may be managed under an account nobody actively checks. A switch port may have been repurposed. The infrastructure does not stop evolving just because the original password has stayed the same.
This is why guest connectivity belongs on your asset and network diagrams. If your organisation cannot say which equipment carries visitor traffic, where that traffic goes, and who owns its configuration, then you have an oversight gap, not merely a slightly old password.
What does the guest network actually connect to?
Think of the network as a set of shared ducts. If visitor traffic enters the same flat network as business devices, or can route towards internal systems, those ducts may connect places that should remain separate.
Depending on the organisation, that could mean point-of-sale terminals, practice or customer relationship management (CRM) systems, file shares, printer subnets, door controllers or network management interfaces. A guest device does not need to be deliberately targeting any of them for the design to matter. Unmanaged personal devices are simply not under your organisation’s control. Older estates complicate this further: where an on-site IBM i system or other legacy platform still serves the business, its terminals and management interfaces deserve the same separation from guest traffic as anything else.
The right response is not to assume that every visitor is a threat. It is to avoid granting access that a visitor does not need. A considered Network Solutions design treats visitor access as its own zone, with explicit rules about what can, and cannot, communicate across the boundary.

Design the separation deliberately
A sound guest network normally has a dedicated VLAN and its own addressing. Firewall rules should block access to internal business resources by default, rather than relying on the hope that nobody will look. The guest network should also be unable to reach infrastructure management interfaces.
Then consider the visitors themselves. Client isolation prevents one guest device from communicating directly with another on the same wireless network. That matters in a busy reception, clinic, classroom or shared workspace where visitors bring devices you cannot inspect or manage.
Authentication should match the way the site is used. A single shared password is easy to administer, but hard to attribute and often left unchanged. Individual credentials or a suitable portal can make access more accountable. If a shared credential is retained, set an owner and a routine for changing it. Keep the process practical: a control that staff work around is not much of a control.
Logging should be proportionate and useful. Decide what connection and authentication records are needed, who can access them, and how long they are retained under your policies. If a portal collects personal information, make sure visitors are told what is collected and why, and that the organisation’s privacy approach is appropriate.
The NCSC’s network security fundamentals explain the value of asset awareness, least privilege, segmentation and monitoring. The GOV.UK guidance on sharing workplace wireless networks also describes separation between guest and other wireless traffic, including the use of VLANs and client isolation.
Personal devices in the building: policy, not accident
Visitors are not the only people bringing personal devices through the door. Staff may connect their own phones or laptops to guest Wi-Fi, either for convenience or because nobody has explained the approved approach.
That makes guest Wi-Fi an important part of your bring-your-own-device (BYOD) policy, but it does not make it a substitute for a work access policy. Decide whether personal devices may access work information, what approved route they should use, and what support the organisation will provide. A guest network can provide internet access without granting access to internal services; it should not become an informal route into them.
The NCSC’s BYOD guidance sets out issues organisations should consider when staff use personal devices for work, including device management, protecting corporate data and balancing security with privacy. The practical point is simple: define what “guest” means in your organisation, and make sure staff understand the difference between internet access and authorised work access.

Who owns the guest experience?
Guest Wi-Fi serves real people and different operational needs. Customers in retail, patients waiting for an appointment, contractors, interviewees, students and couriers may all need access. Their expectations differ, but the network should have a named business owner and a technical owner.
Check that the captive portal is clear, current and appropriate for your visitors. Consider whether access should be time-limited, whether terms of use are displayed, and what information is collected. Make the connection process straightforward; a portal that frustrates people can turn a small courtesy into a recurring reception problem.
Capacity matters, too. Visitors streaming video or downloading large files may compete for bandwidth with business-critical applications. Consider sensible traffic management so visitor use does not undermine cloud applications, payment operations or Voice and Connectivity services such as cloud telephony.
Support arrangements are part of the experience. If visitors regularly cannot connect, reception staff need a simple escalation path. If the same issue repeatedly reaches the Helpdesk Support queue, investigate the underlying portal, coverage or authentication process rather than treating each ticket as a fresh mystery.
Guest Wi-Fi in continuity planning
Continuity planning should reflect how people actually use your premises. If customers, patients or students rely on visitor access, include the guest network in relevant recovery and service tests. Confirm what happens if the internet circuit fails, if a controller is unavailable, or if a network change leaves the guest VLAN without the right route.
For some organisations, internet failover may preserve both staff services and visitor access; for others, business systems rightly take priority. Make that decision before an outage. Include guest connectivity in appropriate Disaster Recovery exercises, especially where the public-facing service depends on it.
As more work moves to Cloud Solutions, separating guest devices from business systems becomes more important, not less. Cloud-hosted applications may reduce reliance on local servers, but they do not make a poorly segmented local network harmless. They also do not decide how your organisation should prioritise limited connectivity during disruption.
A planned Dynamics 365 Jump Start or other cloud transition should prompt a wider look at network roles and access, not an assumption that the visitor network can be left out of the design.
Review the costs as well as the configuration
Guest Wi-Fi can carry recurring costs: managed wireless subscriptions, per-access-point licences, controller charges, portal services and hardware upgrades. The right question is not whether each line item can be removed. It is whether it still supports a defined business need, meets your requirements and is being used as intended.
A Technology Expense Management review can bring those contracts and licences into view alongside the network design. It may reveal duplicate services, unused capacity or a support arrangement that no longer matches the estate. Any savings should be weighed against the impact of losing coverage, support or useful controls. Cutting the wrong line is an efficient way to create a more expensive problem.

A manageable first-month checklist
A useful review does not need to become a major redesign project. Start with a short, structured assessment:
- Map the guest path. Identify the access points, controllers, switch ports, VLANs, addressing and internet route that carry visitor traffic.
- Test the boundary. Confirm that guest devices cannot reach internal systems, management interfaces or other guest devices.
- Review access and terms. Check credentials, rotation ownership, portal wording, privacy information and any data collected.
- Check operational fit. Ask reception and the helpdesk about recurring problems; review capacity and the impact on business-critical traffic.
- Review resilience and cost. Confirm guest access is handled appropriately in continuity plans, then check associated subscriptions, licences and support contracts.
- Record decisions. Name the business owner, technical owner and review date. Keep the design and rules documented so the next change does not depend on someone remembering what happened in 2019.
Strategy first; execution in support
A Fractal IT Director approach treats guest Wi-Fi as an intentional part of the organisation’s technology strategy: what visitors need, what the business must protect, and what it is worth maintaining. David’s role as an IT Consultancy professional is to shape that strategic direction; Network Solutions and Managed IT Services are bolt-on execution services that support the agreed design. Specialist channel partners can provide focused technical delivery where needed. To explore the wider Evestaff group of services, visit evestaff.co.uk.
The password may date from 2019. The responsibility does not.
SEO keywords:
Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, Fractal IT Director, IT Consultancy
Join The Discussion