Wireless & Wi-Fi

How wireless & wi-fi work is scoped and estimated: what drives the hours, what makes jobs harder than they look, and the effort patterns experienced estimators rely on.

How It Works & Technology Overview

Enterprise Wi-Fi is RF engineering wearing a networking hat. The medium is shared — one device transmits per channel per instant — so design is capacity-first, not coverage-first: peak concurrent device count and application mix set the AP count and cell size; square footage alone reliably under-scopes dense spaces by ~40%. Bands: 2.4 GHz (long reach, three usable channels, IoT-crowded), 5 GHz (the workhorse), 6 GHz (Wi-Fi 6E/7 — clean spectrum, shorter reach, client support still uneven — verify the client's device fleet supports it before paying for it). Materials govern propagation: drywall ~3 dB, low-E glass, concrete shear walls, elevator cores, and metal shelving 10–20+ dB — predictive models don't see the shelving. Design method: predictive survey (software modeling on floor plans — fine for new construction and simple spaces) vs validation/AP-on-a-stick survey (walk the space with instruments — required for warehouses, healthcare, high-density; ~20–30% more labor, much better outcomes). Design for the least capable, most critical device — the legacy warehouse scanner or voice badge, not the newest laptop. Power feeds the design: modern APs need PoE+ (802.3at) minimum, high-end Wi-Fi 6E/7 units often PoE++ (802.3bt) and multi-gig (2.5/5G) switch ports — audit upstream switching before ordering APs.

Common Deployment Scenarios

  • Office deployment/refresh: ceiling-tile APs, predictive design plus post-install validation, 802.1X or PSK by client maturity.
  • Warehouse/industrial: high decks (15+ ft — rigging, directional antennas, lift protocols), racking that moves (inventory height changes the RF), roaming-sensitive scanners; validation survey non-negotiable.
  • High-density (auditoriums, open plan, education): small low-power cells, directional antennas, band steering, capacity math per seat.
  • Outdoor/campus: rated APs, mounting/thermal realities (a black roof in summer thermal-throttles standard units), point-to-point bridges between buildings, lightning/grounding.
  • Voice/roaming-critical (healthcare, retail ops): Wi-Fi calling and badge systems needing fast-roam tuning and tight cell overlap engineering.

Products, Vendors & Characteristics

  • Enterprise platforms: Cisco (Catalyst/Meraki), HPE Aruba (+ Instant On for SMB), Juniper Mist (AI-ops positioning; also HPE since July 2025), Ruckus (dense/difficult-RF reputation), Fortinet (security-integrated), Extreme; cloud-managed licensing per AP per year is the dominant model — a lapsed license usually kills management, not radios (platform-dependent — check).
  • Wi-Fi 7 and 6 GHz power rules: Wi-Fi 7 (802.11be) certification began January 2024 — the gains (320 MHz channels, multi-link operation) need Wi-Fi 7 clients and 6 GHz, so a mostly older fleet gets little from it. Indoor low-power 6 GHz needs no coordination; standard-power and outdoor 6 GHz need an Automated Frequency Coordination (AFC) service (FCC-approved for commercial use February 2024) plus each AP's verified location — confirm the AP model, license, and firmware support AFC before quoting outdoor 6 GHz.
  • SMB/value tier: Ubiquiti UniFi (no recurring license, huge install base, community-grade support), TP-Link Omada.
  • Survey/design tooling: Ekahau and Hamina are the professional standards (hardware + subscription cost real money — price survey work accordingly); NetAlly-class handhelds for validation.
  • Authentication stack: WPA2/WPA3-Personal (PSK) vs WPA3-Enterprise/802.1X against RADIUS (NPS, ClearPass, ISE) or cloud RADIUS (JumpCloud, SecureW2-class) — certificate-based onboarding is a distinct engineering scope with client-IT dependencies.
  • IoT reality: cameras, badge readers, sensors often 2.4 GHz-only — plan SSID/VLAN separation so IoT doesn't drag airtime down for everyone.

What Makes It Hard (Gotchas & Failure Modes)

  • Headcount ≠ device count: every human is 2–3 devices; clients report people. Scope on peak concurrent devices by type or under-build the cell plan.
  • The empty-building mirage: networks tuned before furniture, inventory, and people arrive detune on occupancy day — push final RF optimization post-occupancy and lock performance commitments behind a physical-verification clause; late interior-design changes (glass walls, metal acoustic panels) void predictive models.
  • Politics beats physics: the optimal AP location vs the ceiling tile facilities will actually allow; aesthetic mounting demands (wall-mounting a ceiling AP fires the signal into the floor — a known field defect when electricians mount them vertically for convenience).
  • PoE shortfalls: "PoE switch" ≠ PoE+/PoE++; underpowered APs silently disable radios or throttle — the wattage audit is a pre-order task.
  • 802.1X bureaucracy: certificate onboarding stalls on client IT approvals and PKI decisions — price the coordination as its own milestone with the client's calendar as the risk.
  • Interference archaeology: legacy 2.4-only IoT, neighboring tenants, microwaves, industrial equipment; co-channel interference from well-meaning "add another AP" fixes makes coverage worse — an unplanned AP is self-inflicted interference.
  • Roaming failures: sticky clients and badge/scanner devices with ancient roaming logic need cell-overlap tuning that no default config provides.

Effort & Estimation Patterns

  • Interior AP (ceiling tile, existing drop, adequate PoE): 1–1.5 hours mounted, cabled, adopted, base-configured.
  • Hard ceiling with core drill/conduit: 3–4 hours; outdoor AP with weatherproof mount and conduit: 3–5 hours; high-deck warehouse AP with rigging/lift: 2–4 hours plus lift logistics.
  • Predictive survey (per standard office floor): 4–8 hours including report; validation/heat-map survey: 2–4 hours per floor; AP-on-a-stick pre-deployment survey for complex spaces: 1–2 days.
  • Controller/cloud platform setup (SSIDs, policy, RF profiles): 4–6 hours initial.
  • 802.1X/RADIUS integration: 1–2 days engineering plus client-side coordination calendar; certificate onboarding for BYOD its own scope.
  • Post-occupancy tuning visit: 2–4 hours per site — schedule it in the proposal, not as a favor later.
  • Point-to-point bridge: half-day per link including alignment and throughput validation.
  • Multipliers: new cabling per AP (see structured cabling), switch upgrades discovered by the PoE audit, occupied-site work windows, and density designs (validation survey + more, smaller cells).
  • Recurring: cloud license resale, RF health checks (annual or post-reconfiguration), and monitoring/alerting per site per month.

These figures are planning baselines drawn from common industry practice, not a quote. Real hours vary with site conditions, crew, and scope. DarkBird exists because that variance is measurable: it calibrates your estimates against your own completed-project actuals, so your numbers stop being someone else's averages.

Stop estimating from averages

DarkBird turns this kind of knowledge into Install Cards calibrated against your own completed projects. 45-day free trial, full Pro access, no credit card.