Office Wi-Fi planning: design for capacity, not just coverage

Explain the problem in terms of work

A wireless network can appear available while making work frustrating. Users may connect successfully but experience interrupted calls, slow uploads or unreliable movement between rooms. Begin a redesign by describing those failures with their location, time, affected device and application. This helps distinguish radio issues from a congested internet link, an authentication failure or an application problem.

Cisco's wireless design guidance distinguishes coverage and capacity considerations and treats site surveys as part of planning and validation. [1] That principle is useful beyond one vendor: the access-point count should follow the environment and workload rather than a simple floor-area estimate. The checklist here is a practical planning approach, not a universal radio specification.

Build a location-based demand map

Use a floor plan to identify desks, meeting rooms, reception areas, corridors and outdoor spaces that require service. Record normal occupancy and realistic peaks. Count active devices rather than employees alone; laptops, phones, room systems and specialist equipment can create different demands.

For each area, identify the applications that matter. A room used for simultaneous video meetings deserves different testing from a waiting area used for occasional browsing. Include device models and supported wireless capabilities in the assessment. The network should be designed for clients people actually use, including approved older devices, rather than only the newest equipment on a supplier's specification sheet.

Survey the real environment

A predictive design is a useful starting point, but walls, furniture, neighbouring networks and installation constraints can change actual conditions. Ask what information the survey uses, which assumptions remain untested and how the completed installation will be validated. Keep the survey output as a reference for later changes.

Do not treat maximum transmit power as a default cure. A design needs to consider communication in both directions and the way adjacent cells share radio resources. Ask the designer to explain placement, channel planning and power choices in relation to the client population. Fixed signal thresholds should come from the application and device requirements being tested, not from an unexplained template.

Check the wired network and power budget

Wireless access points depend on switches, cabling, power and upstream services. Review switch-port capacity, available Power over Ethernet, cable condition, internet connectivity and resilience requirements. Confirm the complete configuration and licensing needed for the intended features; the purchase price of an access point may not represent the finished system cost.

Identify dependencies on identity services, address allocation, name resolution and management platforms. Document what happens if one of those services is unavailable. Where continuity matters, examine whether the proposed backup connection or power system supports the whole service chain, not merely the radio equipment.

Separate access policies from convenience

Define how employees, guests and non-user devices connect and what each group may reach. A guest network should have a deliberate policy rather than inherit unrestricted access to internal systems. Equally, excessive separation without a clear business model can make legitimate printing, collaboration or support unnecessarily difficult.

Decide who approves access, how credentials or device enrolment are managed, and how a departing employee or lost device loses access. Include monitoring and an escalation path for repeated authentication failures. Test the policy from representative client devices, including attempts to reach resources the client should not be able to access.

Accept the service using realistic tests

Agree acceptance criteria before installation. Walk a representative client through the required areas while running the applications users depend on. Test crowded meeting-room scenarios, file transfers, voice or video continuity, authentication and guest isolation. Record results with device type, location, time and relevant configuration.

A speed test beside one access point is insufficient evidence for a whole office. Keep a punch list for weak areas, roaming problems and operational gaps, then retest the corrections. Hand over the topology, configuration backup, asset register, support contacts and instructions for routine changes.

Evo's Network Infrastructure service covers wireless, switching, routing, firewalls and connectivity foundations. An assessment can connect user complaints to measured conditions and a justified design. The useful deliverable is a network that meets agreed business tests, with the documentation needed to maintain it as people and office layouts change.

Frequently asked questions