A wireless network that looks solid on a floor plan can fall apart within the first week of going live. Coverage rarely fails because someone picked the wrong access point — it fails because nobody accounted for the concrete block wall between two classrooms, the steel racking absorbing signal down a warehouse aisle, or a parking lot that needed coverage for a handheld scanner app nobody mentioned. Indoor and outdoor wireless are related design problems, but they aren’t the same one. They call for different hardware, placement logic, and survey methods.
Indoor AP Placement Starts With What’s Standing in the Way
Ceiling-mount access points often get spaced across a floor plan before anyone walks the building, and that’s usually the first mistake. Distance between APs matters less than what sits between them. A 2.4 GHz signal shrugs off drywall but loses a meaningful chunk of strength passing through a single concrete block wall — common in school corridors, stairwells, and warehouse perimeter walls throughout the Midwest, where masonry construction is standard. The 5 GHz and 6 GHz bands that carry most of the real capacity attenuate even faster through the same materials.
Metal creates a different problem. Warehouse racking, rooftop mechanical equipment, and dense server racks don’t just block signal — they reflect and scatter it, creating multipath interference that shows up as intermittent drops rather than a clean dead zone, which makes it harder to track down later. A design that holds up accounts for these obstacles building by building, not with a blanket “one AP per square footage” rule.
Common offenders worth flagging before placement is finalized:
- Concrete block (CMU) and poured concrete walls, especially stairwells and exterior construction
- Metal warehouse racking and rooftop HVAC units
- Elevator shafts and electrical or mechanical rooms
- Walk-in coolers and freezers in healthcare, retail, and food service spaces
- Low-E window glass and metallic window film, which reflects RF signal
- Dense server racks and network closets
Planning for Capacity, Not Just Coverage
Coverage answers one question: can a device get a signal here. Capacity answers a different one: can this access point handle every device trying to use it at once without becoming the bottleneck. Most of what facilities directors describe as coverage complaints — spotty connections, slow speeds, devices that connect but won’t load — turn out to be capacity problems. The signal is fine. The AP is oversubscribed.
Device density has climbed fast across nearly every vertical we work in:
- Classrooms running 1:1 laptop or tablet programs, often more devices in the room than students once phones are counted
- Warehouse floors combining handheld scanners, forklift-mounted terminals, and a growing layer of IoT sensors
- Hospital units running mobile workstations, patient monitoring devices, and nurse call systems alongside guest WiFi
- Retail floors combining POS terminals, digital signage, IP cameras, and customer-facing guest networks
- Truck yards and dispatch offices where drivers, dock staff, and telematics systems all need a connection at once
Designing for that means sizing access points and channel plans around expected concurrent client counts per radio, not square footage, and separating traffic — guest, staff, and device or IoT — onto their own SSIDs and VLANs so a spike in one doesn’t starve the others.
Outdoor Access Points Have to Survive Before They Can Perform
Outdoor coverage starts with hardware, not placement. An indoor-rated AP stuffed into an outdoor enclosure is not the same as an access point built for outdoor duty. In the Midwest, that means units rated for sustained sub-zero winter temperatures and summer heat and humidity, with enclosures sealed against wind-driven rain and snow — typically IP65 or IP66 rated — plus surge protection on power and data runs, since exposed outdoor cable picks up induced surges even without a direct lightning strike.
Once the hardware is right, outdoor placement comes down to matching coverage to how the space actually gets used. Parking lots for retail, healthcare, and education sites need coverage for security patrol devices and, increasingly, phone-based access requests and camera systems. Loading docks need reliable connectivity for handheld scanners and dock management software. Truck yards are their own category — drivers doing pre-trip inspections, dispatch checking trailers in and out, yard management systems tracking assets — all depending on signal reaching the far end of a yard that can run several acres.
Mesh or Point-to-Point? Getting Backhaul to Outdoor APs
Every outdoor access point needs a path back to the network, and running conduit and cable to every pole and building corner on a large property isn’t always practical. That’s where wireless backhaul comes in, and mesh versus point-to-point depends on the layout of the site.
Point-to-point wireless bridges make sense when connecting two fixed locations with a clear line of sight — a gatehouse at the edge of a trucking yard, a detached warehouse building, a parking structure — back to the main building’s network. They’re predictable and carry serious bandwidth, but they need a clean sightline and lose reliability fast if something later blocks the path.
Mesh works better for covering an open area with several outdoor APs where trenching cable to each one isn’t realistic — access points relay traffic to each other and back to a wired root AP. It’s more flexible to deploy, but every wireless hop adds latency and eats into throughput, so the design needs enough wired root APs to avoid stacking too many hops in a row.
Controller-Based vs. Cloud-Managed: Choosing How the Network Gets Managed
Once placement and hardware are settled, the network needs a management layer, and that choice affects daily operations more than most people expect. Controller-based systems run management on a physical or virtual controller on-site, keeping management traffic off the internet and giving IT staff granular control over RF settings, firmware, and policy — a good fit for larger single-site deployments with in-house networking staff.
Cloud-managed systems push that management layer to a vendor’s dashboard, reachable from anywhere with a browser — a real advantage for lean IT teams or facilities staff who need visibility into the network without deep networking expertise. The trade-off is an ongoing licensing cost and reliance on internet connectivity for full management functionality, though most cloud-managed APs keep serving already-connected clients locally even if that connection drops. Neither approach is universally right; the decision should follow the size of the IT team, not just sticker price.
Why the Site Survey Comes Before the Install, Not After
The single biggest factor in whether a WiFi design holds up in the real world is whether anyone surveyed the site before mounting hardware. There are two methods, and a well-run project typically uses both.
A predictive survey uses software to model coverage from floor plans and known building materials before a single access point goes up. It’s useful early — for budgeting, for new construction where there’s no building yet to walk, and for a starting point on AP count and rough placement. But it’s only as accurate as the assumptions behind it, and real buildings rarely match their blueprints exactly.
An active survey — sometimes called AP-on-a-stick — puts a real access point at the proposed mounting location and physically walks the space with a laptop or scanner, measuring actual signal strength, noise, and channel performance. It catches what predictive modeling misses: the walk-in cooler that wasn’t on the original floor plan, a racking layout that changed since the drawings were made, a concrete column standing in exactly the wrong spot. Skipping this step doesn’t save money — it moves the cost to after installation.
Every decision covered here — indoor density, outdoor hardware ratings, backhaul method, management platform, survey approach — depends on the specific building, yard, or lot in front of it. There’s no universal access point count or generic design that holds up equally well across a school, a distribution center, and a trucking yard.
That’s the approach we bring to wireless projects across Chicago and the greater Midwest: survey the site that actually exists, design around the materials and device density that are actually there, and build the coverage and backhaul plan around how the space gets used day to day rather than around a one-size template. Our team’s Cisco, Fortinet, and CompTIA certifications give those design decisions a foundation in how the underlying hardware and RF actually behave.