Office Wi-Fi & Network Site-Survey Checklist

A stronger router cannot compensate for an unknown floor plan, unsuitable placement, missing cabling, unmanaged interference, overloaded shared capacity, or access rules that were never defined.

What the survey must answer

The survey is not just a Wi-Fi signal exercise. It should produce a traceable relationship between what the organization needs and what the network must provide.

A survey is a sequence, not one walk-through

1. Discovery.Gather business operations, users, device types, applications, security needs, floor plans and known problems.
2. Physical inspection.Verify rooms, materials, risers, cable paths, cabinets, power, mounting access and sources of change or interference.
3. Current-state observation.Record existing equipment, links, addressing/segmentation, coverage complaints, performance symptoms and operational ownership.
4. Design and risk review.Map requirements to wired/wireless architecture, access policies, capacity, resilience, installation and future expansion.
5. Implementation validation.Test the installed environment against agreed use cases, then document configuration, labels, diagrams, exceptions and support information.

A predictive design can help plan placement, but a floor plan is an abstraction. A post-installation validation checks the real environment, including actual building materials, neighboring networks, installed positions, client behavior and changing occupancy.

Seven planning layers

1. Business and application requirements

Identify ordinary and critical workflows. Web browsing, cloud applications, large file transfer, real-time voice/video, scanners, printers, cameras, building systems and guest access can have different needs. Record where each activity occurs and whether short interruptions are tolerable.

2. People and devices

Count concurrent use rather than only employees. Include phones, laptops, meeting-room equipment, printers, cameras, access control, IoT and temporary visitors. Device capabilities differ; a design observed with one device does not automatically represent every client.

3. Physical site

Walk the actual paths users take. Mark dense rooms, corridors, closed offices, meeting areas, storage, kitchens, machinery, reflective or absorptive materials, ceiling restrictions, outdoor areas and multi-floor relationships. Confirm where equipment can be safely mounted and serviced.

4. Wired foundation

Access points still depend on cabling, switching, uplinks, power and an organized cabinet. Record cable categories/condition where known, port availability, power delivery requirements, patching, labels, grounding/environmental constraints and any path that cannot be changed.

5. Wireless environment

Observe current coverage and interference in representative operating conditions. Record neighboring networks, rogue or unauthorized access points, channel use, noise/interference sources, client roaming paths and high-density areas. Avoid adopting a universal target before the applications and clients are known.

6. Access and segmentation

Separate identity from connectivity. Decide who may reach internal systems, internet only, printers, management interfaces, cameras, guest services or operational devices. Guest and device networks should be designed from policy and support needs, not created as unlabeled extra Wi-Fi names.

7. Resilience and operation

Document single points of failure, internet dependencies, power/UPS needs where appropriate, configuration backup, monitoring, change ownership, spare capacity, labeling and who responds when service degrades.

A conceptual office topology

The diagram is intentionally generic. Its purpose is to prompt questions: where policy is enforced, which paths are wired or wireless, which systems must be isolated, how management access works, and what documentation is needed to support the environment later.

What useful handover looks like

A network is not finished when devices connect once. The handover should make future support possible without rediscovering the environment. At minimum, retain an approved topology, equipment and location inventory, port/cable labels, network/access purpose, configuration ownership, backup location, known exceptions, validation record and support/escalation boundaries.

Technical sources and context

• Cisco: WLAN site-survey guidelines — survey preparation, coverage, interference, client characteristics and post-validation documentation. Vendor-specific thresholds/examples are not adopted as universal ArmDark requirements.
• NIST: Securing network connections — small-business wireless and remote-access security guidance.