Short answer: Scope a Wi-Fi survey before you price access points, never after. A proper survey starts from how many devices will be used where, what applications they run, and what the building is made of — then produces an AP count, placement plan, channel and power plan, cabling and PoE requirement, and a switching uplink design. An access point count derived from floor area alone is a guess, and it is the most common reason a new Wi-Fi network underperforms on day one.
Key takeaways
Capacity, not coverage, drives AP count in offices, classrooms and auditoriums.A predictive survey needs scaled floor plans and wall construction details to be worth anything.Validate after installation. A design that was never measured is not a design.The switch, PoE budget and uplink decide whether the APs can deliver what they promise.Warehouses and factories need a physical survey. Racking and stock levels change RF behaviour completely.Why area-based AP counts fail
"One access point per 2,000 square feet" is a sales shortcut. It ignores device density, application mix, building materials and interference. A 2,000 square foot open office with 60 people on video calls needs a very different design from a 2,000 square foot warehouse aisle with eight barcode scanners. The first is a capacity problem; the second is a coverage and roaming problem.
Design from these inputs instead:
Concurrent devices per area, counting laptops, phones, tablets, scanners, printers, cameras and IoT separately.Applications in use: video conferencing, voice over Wi-Fi, large file transfers, VDI, scanners that must never drop a session.Roaming requirements: does a device have to keep its session while moving across the floor or between buildings?Building construction: concrete, brick, glass partitions, metal racking, lift shafts, firewalls and cold rooms all change propagation.Ceiling height and mounting constraints, including where cable can physically be run.The three kinds of survey, and when you need each
Predictive (desktop) — When it is done: Before purchase — What it produces: Modelled AP count, placement, channel and power plan — When it is essential: Every project, as the baselinePre-deployment (AP on a stick) — When it is done: Before purchase, on site — What it produces: Measured readings from the real building — When it is essential: Factories, warehouses, heritage or oddly built premisesPost-installation validation — When it is done: After install — What it produces: Measured coverage, SNR, roaming and throughput results — When it is essential: Every project, as the acceptance testTreat the post-installation validation as your acceptance test for the vendor. It is the difference between "the APs are installed" and "the network performs as designed".
What a good survey report contains
A floor-by-floor AP placement plan with mounting type and heightPredicted and, after install, measured coverage in dBm for each required zoneSignal-to-noise ratio targets per area, with voice and scanning zones called out separatelyCell overlap sufficient for clean roaming, without co-channel interferenceChannel and transmit power plan for 2.4 GHz, 5 GHz and, where used, 6 GHzInterference sources identified: microwave ovens, cordless devices, neighbouring networks, machineryCabling schedule with runs, lengths and termination pointsPoE requirement per AP and the total switch power budgetUplink and switching design, including multi-gigabit ports where the AP model needs themGuest, corporate, voice and IoT network separationA validation plan with pass or fail thresholdsThe part most quotes get wrong: switching, cabling and power
Modern access points are only as good as what sits behind them.
Cabling. Confirm category and run lengths. Reusing old cable is a common false economy when the AP needs multi-gigabit throughput.PoE budget. Higher-end APs need PoE+ or PoE++. Add up the real draw across all ports rather than assuming the switch total is enough; check the budget again with cameras and phones on the same switch.Multi-gigabit uplinks. A Wi-Fi 6 or Wi-Fi 7 AP connected to a 1 Gbps port will cap out before the radio does.Switch-to-core uplinks. Aggregate the floor traffic properly, with redundancy where downtime is costly.UPS protection for switches and the controller, otherwise power events take the whole floor down regardless of Wi-Fi quality.Security design, agreed before purchase
WPA3 where client devices support it, with a documented fallback plan for older equipment.802.1X with RADIUS for corporate devices, tied to your identity provider rather than a shared passphrase.Per-device keys for IoT and equipment that cannot do 802.1X, instead of one site-wide passphrase everyone knows.Guest network isolation, with a captive portal, bandwidth limits and no route to internal networks. Contractors and vendors should be treated as guests by default — see Zero Trust Access for Vendors.Rogue AP detection and a policy for personal hotspots.Device onboarding through your MDM, so posture and ownership are known before access is granted. See Endpoint Management for Distributed Teams.Chennai and factory-floor realities
Metal racking and stock levels change RF behaviour week to week. Survey a loaded warehouse, not an empty one.Heat, dust and humidity in production areas require correctly rated enclosures and mounting, especially near paint shops and wash areas.Shop-floor machinery can be an interference source; a spectrum scan during production hours is worth more than one on a Sunday.Older buildings in the city often have thick masonry and unexpected cable routing constraints. Plan for containment and conduit work in the quote.Multi-site rollouts across Chennai, Bangalore and Hyderabad should be surveyed to one standard, so the design and support model stay consistent.Survey and BOQ checklist to send with your RFP
Scaled floor plans per site, with wall construction notedDevice count and type per zone, at peak occupancyApplications per zone, with voice, video and scanning identifiedRoaming requirements and any seamless handover needsExisting cabling: category, age, and run lengthsExisting switches, PoE budget and available portsInternet and WAN bandwidth per siteController preference: cloud managed or on premisesSecurity: WPA3, 802.1X, RADIUS, guest portal, IoT segmentationHigh-density areas: auditorium, cafeteria, training rooms, receptionMounting constraints, aesthetic requirements and civil work expectedValidation thresholds for acceptance, in dBm and SNRWarranty, licence term and support model for APs and controllerMonitoring, reporting and escalation after handoverCommon mistakes
Buying access points before anyone has surveyed the site.Designing for coverage when the actual problem is capacity.Turning transmit power to maximum, creating co-channel interference and sticky clients.Ignoring the 2.4 GHz plan because most devices are on 5 GHz; the scanners and IoT are usually not.Forgetting the PoE budget and uplink speed in the BOQ.No post-installation validation, so poor performance becomes a long argument.Licence and support terms discovered at renewal rather than at purchase.Frequently asked questions
How many access points do we need?
That number is the output of a survey, not an input. It comes from device density per zone, applications, building construction and roaming needs. Any count quoted before a survey is a guess.
Is a predictive survey enough, or do we need an on-site survey?
A predictive survey is enough for straightforward offices with reliable floor plans. Warehouses, factories, older buildings and high-density venues need on-site measurement before purchase.
Should we upgrade to Wi-Fi 6E or Wi-Fi 7?
It depends on client devices and density. The newer standards help most in high-density areas with modern clients. If most of your fleet is older, spend the budget on placement, cabling and switching first.
Do we need new switches when we upgrade Wi-Fi?
Often yes, for PoE budget and multi-gigabit uplinks. Check the power draw of the proposed AP model and the port speed it requires before assuming existing switches will do.
Cloud-managed or on-premises controller?
Cloud management suits multi-site networks and small IT teams, with simpler remote troubleshooting. On-premises suits sites with strict data or connectivity constraints. Compare licence cost over the full term, not just year one.
How do we stop guests and vendors reaching internal systems?
Separate SSIDs with network isolation, a captive portal for guests, and identity-based access for anyone who needs internal resources — not a shared passphrase.
What should acceptance testing include?
Measured coverage and SNR against the agreed thresholds in every zone, roaming tests while walking defined routes, throughput tests at the edge of cells, and a spectrum scan during normal working hours.
Get your Wi-Fi surveyed and designed by Layots
Layots Technologies designs, installs and manages enterprise wireless networks across Chennai, Bangalore and Hyderabad: predictive and on-site surveys, AP and switching design, structured cabling, secure onboarding with 802.1X and MDM, post-install validation, and ongoing monitoring.
Send us your floor plans, device counts and the applications each area depends on. A solution architect reviews the requirement and comes back with a survey plan and a costed BOQ, usually within one business day.
Book a 30-minute virtual meeting with a solution architect — request your free IT assessmentCall +91 99623 95939WhatsApp the team for a quick requirement discussionRelated reading: SD-WAN and Secure Access for Multi-Branch Businesses in Chennai · Managed IT Support for Multi-Site Businesses · Choosing an IT Infrastructure Partner in Chennai