Requirements, capacity and accountable wireless design
Begin with the intended outcome
A wireless design starts with users, devices, applications, location, peak concurrency and measurable acceptance criteria. Define coverage and capacity separately. A floor-plan heatmap can predict signal distribution but cannot by itself prove that a crowded room supports its application demand. Record client radio capabilities, traffic direction, roaming, latency, loss and security needs. A requirements document is different from a bill of materials and from a vendor sales preference.
Plan shared airtime and reuse
Wireless clients compete for transmission opportunities under their protocol and configuration. A headline PHY rate is not equivalent to application throughput available independently to every client. Channel width, reuse, protocol overhead, contention, retransmission and client mix affect capacity. A wider channel can improve a particular link’s peak while reducing reuse. Twenty MHz is not inherently too narrow for modern clients, and forty MHz is not a universal dense-office default. Choose from actual regulatory channels, spectrum conditions and demand.
Place and connect the infrastructure
Antenna pattern, mounting, cable loss, power budget and actual building materials affect useful coverage. Outdoor designs also need supported equipment, grounding/lightning provisions, weather and installation safety under the qualified local process. A proposed AP location requires an appropriate uplink, supported cabling, power and maintainability. Cabling category and distance limits depend on the particular Ethernet/PoE standard and installation; do not transfer one generic cable claim to every multigigabit design.
Deliver a testable design
Document assumptions, intended channel/power plan, architecture, security, dependencies, capacity and validation method. Predictive work should be checked against actual representative measurements and client experience. A design review can approve a baseline while later changes remain controlled and traceable. Validate the intended busy and failure conditions, not only one successful speed test. Training material may share design foundations across administrator, professional and expert credentials, but that does not make their official difficulty or application requirements identical. This chapter is written design reasoning and authorizes no site work, AP deployment or production change. Current exam logistics and credential pathways are intentionally not invented.