Skip to main content

Help guide

Business Wi-Fi dead spots: what to check before buying equipment

Before buying a Wi-Fi extender or access point, record where the problem happens, when it happens and which devices are affected. Compare those observations with a working location and, where available, an already-connected wired device. The pattern can help your network administrator decide whether to investigate wireless coverage, a device or application, or the shared internet connection first.

This walk-through is for office, retail and multi-site teams. It is an observation exercise, not a technical survey or permission to change equipment.

Record the pattern

With a device you are authorised to use, note the site, floor and specific location, along with the time and the task that failed. Does a laptop lose its Wi-Fi connection, does a page stop loading, or does one application become slow? Record the device type and whether other devices nearby have the same symptom. Include a nearby location where the same task works, if there is one.

Repeat a simple, approved check at a quieter time and during the usual busy period. Note relevant conditions such as a closed meeting-room door or a shop full of people; do not assume either caused the fault. Wi-Fi signal bars are a rough clue, not a measurement of application performance or proof that the internet is working.

The site walk-through

Map the symptom before buying a fix

  1. Where Mark problem locations on a simple floor plan.
  2. When Record the times and how often it happens.
  3. What Note the device and the work being interrupted.
  4. Compare Record existing wired and Wi-Fi observations, if available.

A floor-plan observation is not a wireless survey or a coverage guarantee.

Is it Wi-Fi, the internet or one device?

Wi-Fi connects a device wirelessly to the local network; the internet service is a separate part of the path. NBN Co explains the difference between wired and wireless connections and notes that distance and thick walls can affect Wi-Fi performance.

  • One area: If the same approved device and task work nearby but fail repeatedly in one spot, a local wireless issue is worth investigating. The comparison is a clue, not a diagnosis.
  • Several connection types: If Wi-Fi devices and an already-connected wired computer cannot reach the same ordinary website at roughly the same time, tell the network administrator or internet provider. The shared local network or internet service may need checking; this does not identify the cause by itself.
  • One device or application: If others work in the same place, record the difference and contact the device or application owner. A Wi-Fi connection showing as connected does not, on its own, establish that an internet service or application is working.

Use an ordinary, non-sensitive website and existing connections for the comparison. Do not unplug cables or change networks on payment, safety or operational devices. If there is no suitable wired device, leave that comparison to your authorised IT contact.

Make a floor-plan observation sheet

Use a current floor plan or a simple sketch for each site and floor. Mark where people need connectivity: counters, meeting rooms, stockrooms and the routes staff walk. Add thick walls, metal shelving and the visible locations of existing Wi-Fi equipment, where known. Keep common areas and individual tenancies distinct. Do not enter restricted areas or open cabinets to find equipment.

Example — fictional retail site: At 11:30, a staff tablet loses connection near the stockroom; the same tablet opens an ordinary website at the front counter at 11:35. At 14:00, the stockroom check fails again. A wired counter computer opens the same site at 14:05. The team marks both locations and notes that the stockroom door was closed. This suggests a location-related issue to investigate; it does not prove the door, the Wi-Fi equipment or the internet service is responsible.

For each entry, capture: site and location; date and time; device and approved task; what happened; comparison location or connection; and business impact. Record whether a check was not possible. Share the sheet through an agreed channel, without passwords, one-time codes, customer details or payment information.

Review requirements

Give a survey provider the right context

  1. Spaces Include offices, counters, stores and shared areas.
  2. Users Note staff, guests and operational devices separately.
  3. Workloads Identify critical applications and peak use.
  4. Constraints Record access, power, cabling and building permissions.

Decide responsibilities and privacy requirements with the appropriate owners.

Describe what each site needs

List the areas and routes that matter, the types and approximate numbers of devices at busy times, and the work they do. Voice calls while walking may need different testing from occasional browsing at a desk. For retail, include the needs of staff, guests, payment devices and operational equipment without testing transactions or collecting their data. Record any periods when disruption would be especially costly.

For shared spaces or shopping centres, identify who manages the common area, each tenancy, the internet service and existing equipment. Agree who can grant access, approve work, contact tenants and receive findings. Ask the appropriate security and payment advisers to review who should access which services. The Australian Cyber Security Centre’s network guidance explains that effective separation requires planning and enforcement; simply naming guest and staff networks does not establish that they are securely separated or meet any particular requirement.

Discuss privacy before any guest service or monitoring is proposed: what information would be collected, who could access it, how long it would be kept and who is responsible. Take only the observations needed for the fault; do not capture guest traffic or personal details during this walk-through.

Scope a survey before choosing equipment

If the pattern warrants further work, ask a suitably qualified provider whether a survey is available and request a written scope before committing. Cisco’s site-survey guidance distinguishes predictive plans from on-site measurements and recommends specifying coverage areas, client devices and capacity needs.

  • Which floors, rooms, outdoor areas and walking routes are included or excluded? Will measurements be taken inside the problem areas?
  • Will the work be predictive, measured on site, or both? Which representative devices, activities and busy conditions will be considered?
  • What findings will be delivered? Ask for the measured path, results and limitations, plus options and assumptions for any recommended changes.
  • Who approves access, any disruption, equipment, power and cabling work? How would the parties agree success criteria and check the outcome after any separately authorised changes?

A useful outcome is a prioritised, site-specific list of findings and options, not an automatic equipment order or a promise of perfect coverage. Ask a registered cabler about any cabling work, and confirm responsibilities before it proceeds.

When to stop and get help

If payment, safety, alarm or other critical services are affected, stop testing and follow your organisation’s contingency and escalation process. For a suspected security incident, contact your nominated security lead through a known channel. Do not reset or disconnect equipment, change radio settings, or move or install access points without authorisation.

Give your observations to the person responsible for the network or to the relevant provider. If Comm Centre is responsible for your service, you can also check the Comm Centre Support page. Use an established urgent route where your organisation has one.

Sources and further reading