Applies to: initial planning for commercial premisesContent reviewed: 10 October 2026 (Hong Kong time)

Engineering SOP and labelling

Put the website’s delivery requirements into each project record: SOP, labels, test evidence, defects and handover lists.

View SOP and labelling

01 / Understand the site

A site survey involves more than a heatmap

Understand the users, client devices, applications and site constraints before choosing an assessment method. A new site and an operational site may require different workflows.

Predictive Planning

Initial planning based on drawings, material assumptions and equipment characteristics helps estimate and compare options. It usually excludes on-site measurements, and its assumptions should be identified.

On-site passive measurements

Primarily observes AP signals, channels and the RF environment without connecting a client to generate test traffic. The results alone cannot establish two-way application performance.

Active testing

Connect representative client devices to the network and test traffic, connectivity and application performance, covering aspects that a signal map alone cannot reveal.

Post-Installation Validation

Check coverage, capacity, interference, roaming and functionality against the agreed design and usage scenarios, and record any non-conformities.

02 / Design for real use

Assess coverage and capacity separately

Receiving a signal and completing work during busy periods are two different questions. Assess AP locations and numbers alongside concurrent devices, application load, walls and channel planning.

Bands, channel widths and client compatibility

The 2.4 GHz, 5 GHz and applicable 6 GHz bands each have conditions of use. Wider channels or newer Wi-Fi standards are not necessarily better suited to a site; consider nearby networks, client support and local requirements. Check equipment regional versions, permitted bands, certification and indoor/outdoor restrictions for the project location before finalising the design.

Roaming Takes More Than Matching Network Names

The same network name does not ensure a consistent roaming experience. Test adjacent AP coverage, authentication, client support and real routes together. The benefits of 802.11k, 802.11v and 802.11r depend on equipment and configuration; uninterrupted operation cannot be promised for every device.

Agree design targets for the specified applications and client devices. This website does not treat any single RSSI, SNR, data rate or AP count as a universal guarantee for all sites.

03 / Connect the whole path

The Wired Path Must Be Reliable Too

  • PoE power: Check the AP power standard, per-port output and the switch's total power budget; insufficient power may affect functionality.
  • Copper Cabling and Fibre:Assess cable routing and testing scope against distances, cable condition, uplink requirements and site constraints.
  • Uplinks and switching:An AP's advertised wireless rate is not the same as usable application throughput. Switches, uplinks and firewalls may also be bottlenecks.
  • Internet and power: Improving Wi-Fi does not automatically increase internet bandwidth; backup connections, UPS provision and failover requirements need separate design.

04 / Access with intention

Separate Networks and Clarify Responsibilities

Define access rights for staff, visitors and operational devices before implementing SSIDs, VLANs, authentication and access policies. Adding another Wi-Fi name alone does not establish secure isolation.

Guest access

Confirm access to internal resources, communication between clients, and whether a login portal or usage restrictions are required.

Controllers and centralised management

Compare local, cloud and other management options, including licence fees, administrative access, data location and behaviour during service outages.

Cross-border data, visitor information and record retention require separate confirmation against project policies and local requirements. This page does not provide legal or information security compliance advice.

05 / Agree on acceptance

Write the acceptance plan before work begins

Agree the test areas, representative devices, applications, load and pass criteria in advance. Record the conditions at the time of testing to support future troubleshooting.

VALIDATION / FIELD NOTES

Choose an item to explore its test context

Select a card to see its illustration and observation points. Illustrations do not replace agreed test conditions.

01

Coverage and Interference

Observe signal quality, channel use and problem areas within the agreed scope.

02

Capacity and applications

Test real applications under the agreed concurrent connection conditions, distinguishing wireless bottlenecks from upstream limitations.

03

Roaming and compatibility

Test movement, reconnection and application continuity along specified routes using representative client devices.

04

Access and Segmentation

Confirm that staff, visitors and devices can reach the resources they need, while restricting unauthorised access.

05

Installation and records

Check AP locations, cable labels, configuration and test records.

06

Administrative access and handover

Confirm administrative accounts, configuration backups, licence information and follow-up contact arrangements.

Observation points and illustrations

View illustrationCoverage and Interference
01 / OBSERVE

Coverage and Interference

Observe signal quality, channel use and problem areas within the agreed scope.

Coverage and InterferenceGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTAPPOSITIONS · BAND · ENVIRONMENTNOT TO SCALE

How to observe

Observe signal quality, channel use and problem locations at specified areas and positions.

What to record

  • Record measurement positions, clients, bands and the environment so conditions can be compared.
  • Illustrative rings are not a heat map. Validate actual quality and coverage on site.
View illustrationCapacity and applications
02 / OBSERVE

Capacity and applications

Test real applications under the agreed concurrent connection conditions, distinguishing wireless bottlenecks from upstream limitations.

Capacity and applicationsGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTAPCONCURRENT CLIENTS · NOT DEVICE COUNTSNOT TO SCALE

How to observe

Observe main areas under agreed concurrent-connection, device and application conditions.

What to record

  • Record concurrent-connection conditions and application behaviour; an AP’s advertised rate is not application throughput.
  • Capacity can involve wireless, switching, uplink and service layers. Check each part separately.
View illustrationRoaming and compatibility
03 / OBSERVE

Roaming and compatibility

Test movement, reconnection and application continuity along specified routes using representative client devices.

Roaming and compatibilityGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTAPAPAGREED ROUTE · OBSERVE RECONNECTIONNOT TO SCALE

How to observe

Use representative clients along an agreed route to observe connectivity and application behaviour while moving.

What to record

  • Record where and when disconnections, reconnections or application interruptions occur, together with the client model.
  • Clients and the network both affect roaming. The illustrated route does not guarantee seamless transitions.
View illustrationAccess and Segmentation
04 / OBSERVE

Access and Segmentation

Confirm that staff, visitors and devices can reach the resources they need, while restricting unauthorised access.

Access and SegmentationGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTSTAFFGUESTINTERNALVERIFY ALLOW / DENYNOT TO SCALE

How to observe

Check permitted and restricted resource access for agreed identities and network segments.

What to record

  • Specify both permitted and denied scenarios; record target resources and the identity used for each test.
  • Different Wi-Fi names do not establish isolation, and this illustration is not a security certification.
View illustrationInstallation and records
05 / OBSERVE

Installation and records

Check AP locations, cable labels, configuration and test records.

Installation and recordsGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTAPLABELPOSITION / LINE / CONFIGNOT TO SCALE

How to observe

Cross-check agreed installation, cabling, configuration and test records so issues can be traced later.

What to record

  • Check positions, orientations, heights, labels or power information as required by the project scope.
  • Agree record types, formats and deliverables. The illustrated documents are conceptual.
View illustrationAdministrative access and handover
06 / OBSERVE

Administrative access and handover

Confirm administrative accounts, configuration backups, licence information and follow-up contact arrangements.

Administrative access and handoverGeometric illustration of an engineering context. Devices, routes, network separation and records explain what to observe; they do not indicate a test pass.VALIDATION CONTEXT / CONCEPTOWNER / CONFIGBACKUP / SUPPORT SCOPENOT TO SCALE

How to observe

Check management access, configuration backups and follow-up arrangements against the agreed scope.

What to record

  • Specify account ownership, backup methods, licensing information and contact arrangements.
  • Agree maintenance scope, response times and site attendance separately. The illustration makes no service commitment.

Concept illustration, not a measurement, completed project or acceptance promise. Device counts, lines and ring sizes do not specify equipment configurations or coverage.

A single speed test, one phone screenshot or a heatmap without test conditions cannot represent the experience across an entire site.

06 / Keep responsibilities clear

Agree the maintenance scope in advance

After handover, alerts, firmware updates, configuration backups, equipment maintenance and capacity reviews can be discussed. Service hours, response times, site attendance, spare parts and licence renewals should all be included in the formal scope.

Refurbishment, changes to shelving, new devices or different applications may alter the original design conditions. Reassess the network where needed.

Technical references and scope

The following official references explain design concepts; they do not imply brand partnerships, authorised reseller status or certification. Product and regulatory requirements may change, so each project must be checked against the selected equipment and local requirements.

Information reviewed: 10 October 2026, Hong Kong time. This page provides education on engineering planning and helps organise requirements; the formal design and scope of work must be confirmed separately.