---
name: wifi-survey-brief
description: Produces a survey scope for a wireless audit or deployment, covering coverage goals, density, roaming, deliverables, and engagement rules.
version: 1.0.0
author: VantagePoint Networks
audience: IT Managers, Network Engineers, Facilities Managers, Procurement Leads
output_format: Formatted Markdown Wi-Fi survey brief with scope, goals, deliverables, day-of checklist, and vendor engagement pack.
license: MIT
---

# Wi-Fi Survey Brief

Writes the brief you hand to an internal engineer or external surveyor so a wireless survey produces an actionable result, not a 90-page PDF full of heatmaps nobody reads.

## How to use this skill

1. Download this `SKILL.md` file.
2. Place it in `~/.claude/commands/` (macOS/Linux) or `%USERPROFILE%\.claude\commands\` (Windows).
3. Run `/wifi-survey-brief` in Claude Code. Describe the site, what the survey is for (new deployment / troubleshooting / validation / refresh), and what outcome you need. Answer the clarifying questions. Receive the brief.

## When to use this

- You're planning a new-site wireless deployment and want a proper predictive + validation survey.
- You inherited a wireless network that users complain about and need an audit that identifies causes.
- A refresh is due and you need data to support the vendor / model choice.
- You're going to tender for survey services and need a consistent brief to compare quotes.
- You're running the survey in-house with an AP-on-a-stick kit and want a checklist so you don't skip floors.

## What you'll get

- **Survey scope** - the specific buildings, floors, zones, outdoor areas to cover.
- **Survey type** - predictive, passive, active, AP-on-a-stick, packet capture - with rationale for which you need.
- **Coverage goals** - signal strength, SNR, data rate, per-area.
- **Density goals** - simultaneous clients per AP, per area type.
- **Roaming goals** - handoff latency, coverage overlap thresholds.
- **Security and SSID requirements** - production of the SSID schedule.
- **Deliverables required** - floor plans with AP positions, heatmaps, BOM, cable runs, RF assessment, rogue AP report.
- **Engagement rules** - access, escorts, hours, H&S, confidentiality.
- **Day-of checklist** - what the surveyor must turn up with and complete.
- **Acceptance criteria** - what "survey done" means.

## Clarifying questions I will ask you

1. **Is this a new install, a troubleshooting audit, a pre-refresh assessment, or a post-install validation?**
2. **Site profile?** (Office / warehouse / factory / clinical / education / hospitality / outdoor)
3. **Floor area and number of floors?**
4. **Approximate simultaneous client count?** (Users + phones + IoT + BYOD)
5. **Special-use zones?** (Auditorium, lab, freezer, bonded store, car park, canteen, exec suite)
6. **Construction / building materials?** (Drywall / concrete / metal-framed / steel shelving / brick / glass)
7. **Coverage target?** (Typical: -67dBm at chair level indoor; -65dBm for voice; different for outdoor)
8. **Density target?** (Typical: 30 clients/AP office; 50-80 for auditorium; 4-5 per laptop-heavy workspace)
9. **Applications?** (Voice on Wi-Fi, video conferencing, dense laptop work, scanner gun / forklift terminals, lab equipment, medical telemetry)
10. **Wi-Fi standard target?** (Wi-Fi 5 / 6 / 6E / 7)
11. **Vendor constraint?** (Cisco Meraki / Catalyst / Aruba / Ruckus / UniFi / open)
12. **Existing infrastructure?** (PoE switches present, cable runs, cabinets, power in ceiling)
13. **Access and timing?** (Business-hours allowed / out-of-hours only, escort required, areas off-limits)
14. **Deadline for deliverable?**
15. **Budget envelope?** (For external surveyor engagement)

## Output template

```markdown
# Wi-Fi Survey Brief: <site> - YYYY-MM-DD

**Brief ID:** WIFI-SURVEY-<slug>-YYYY-MM
**Prepared by:** <name>
**Prepared for:** <internal engineer / surveyor / vendor>
**Survey date window:** YYYY-MM-DD to YYYY-MM-DD
**Site contact:** <name, phone, email>

## 1. Objective
<One paragraph: what we're doing, why now, what decision this survey enables.>

## 2. Scope

### Buildings / floors / zones in scope
| Area | Floor(s) | Approx m2 | Access method |
|---|---|---|---|
| Building A | G, 1, 2 | 3,200 | Escorted |
| Building B | G, 1, 2, 3 | 4,100 | Badge |
| Outdoor courtyard | - | 600 | Open |
| Car park | - | 2,000 | Open |

### Explicitly out of scope
- <e.g. plant rooms>
- <e.g. visitor reception if covered by existing design>

### Special-use zones (require specific attention)
- <Zone> - <reason - e.g. "Large auditorium seating 400, expect 200+ simultaneous clients during all-hands">
- <Zone> - <reason - e.g. "Clinical area; survey only during clinic closure hours">

## 3. Survey Type
**Requested:** <Predictive / Passive on-site / Active on-site / AP-on-a-stick (APoS) / Post-install validation / Combination>

**Rationale:**
- Predictive alone: acceptable for initial planning where floor plans and materials are well known.
- Passive on-site: for troubleshooting, validation, and rogue detection.
- Active on-site: for actual-throughput measurement (needed if voice/video quality is a concern).
- AP-on-a-stick: gold standard for a new install on an unfamiliar site; measures actual RF.
- Post-install validation: required after any new deployment or refresh.

## 4. Coverage Goals
| Zone | Signal target | SNR target | Data rate target |
|---|---|---|---|
| Offices / desks | -67 dBm at chair level | 25 dB | 100+ Mbps |
| Meeting rooms | -65 dBm at table | 25 dB | 200+ Mbps |
| Open collaboration | -65 dBm | 25 dB | 150+ Mbps |
| Voice areas (phones) | -65 dBm | 25 dB | 54+ Mbps stable |
| Outdoor courtyard | -70 dBm | 20 dB | 50+ Mbps |
| Auditorium / dense | -65 dBm (per user) | 25 dB | 50+ Mbps per user |

## 5. Density Goals
| Zone | Max simultaneous clients per AP | Expected peak device count |
|---|---|---|
| Office (open plan) | 30 | 150-200 |
| Meeting rooms | 20 | 50-80 |
| Auditorium | 60 | 300-400 |
| Canteen | 40 | 80-120 |

## 6. Roaming Goals
- Cell overlap: adjacent APs overlap at -72 dBm minimum.
- Handoff latency: <100ms for voice; <300ms for data.
- Band-steering policy: 5 GHz preferred; 6 GHz enabled if Wi-Fi 6E.
- Load-balancing: enabled between APs in same cell.

## 7. SSID Schedule
| SSID | Band | Security | VLAN | Intended clients |
|---|---|---|---|---|
| CORP | 2.4/5/6 | WPA3-Enterprise + EAP-TLS | 70 | Corporate devices |
| BYOD | 2.4/5 | WPA3-Personal + captive portal | 71 | Personal devices with DPC |
| GUEST | 2.4/5 | Open + captive portal + terms accept | 72 | Visitors (internet only) |
| IOT | 2.4 only | WPA3-Personal | 73 | Building devices (isolated) |
| SCANNERS | 2.4 only | WPA2-PSK | 74 | Warehouse barcode scanners (legacy) |

**Note:** Reduce SSID count where possible. Every SSID consumes airtime whether in use or not.

## 8. Deliverables Required
| Deliverable | Format | Acceptance |
|---|---|---|
| Executive summary | PDF, 1-2 pages | Readable by non-technical director |
| Detailed findings report | PDF | All zones covered; all observations evidenced |
| Floor plans with AP positions | Vector (DWG / PDF) per floor | AP model, mount height, orientation, cable run path |
| Predictive heatmaps | PDF per floor | Both 5 GHz and 6 GHz (if WiFi 6E) |
| Validation heatmaps (post-install or on-site) | PDF per floor | Signal, SNR, data rate, overlap |
| Bill of materials (BOM) | CSV / spreadsheet | APs, mounts, switches, cables, adapters |
| Cable run specification | Diagram + CSV | From cabinet to each AP, length, path |
| RF assessment | PDF | Channel plan, interference sources, rogue APs seen |
| Existing infrastructure audit | PDF (if brownfield) | PoE capacity, switch models, cabinets, power |
| Raw survey data files | Native tool format (Ekahau / AirMagnet / iBwave) | Supplied on completion |

## 9. Engagement Rules
### Access
- **Hours:** <business / out-of-hours / specific>
- **Escort required?** Yes / No - if yes, <contact>
- **Areas off-limits:** <list>
- **Access to cabinets / IDF rooms:** <approval process>

### Health & safety
- **PPE required:** <hi-vis, ear protection, hard hat, sterile gown as applicable>
- **Working at height:** <restrictions; permit needed>
- **Lone working:** <restrictions>
- **Incident reporting:** <process>

### Security
- **Confidentiality:** Survey data treated as Internal Confidential. No cloud uploads without approval.
- **Photography:** Permitted / Restricted - <exceptions>
- **Equipment left on site:** Not permitted overnight unless pre-agreed.
- **Network connection:** Surveyor laptop connects only to surveyor's MiFi or a dedicated VLAN if internal access required.

### Confidentiality / NDA
- NDA <signed / required> before survey start.
- Any spectrum / RF finding published externally requires prior approval.

## 10. Day-of Checklist (surveyor)
Before starting:
- [ ] Site induction complete; H&S briefing received
- [ ] Site contact on site
- [ ] Tools checked: spectrum analyser, survey adapter, AP-on-a-stick kit, tripod, battery, tape
- [ ] Floor plans loaded into survey tool
- [ ] Access cards / escorts arranged

During:
- [ ] Photograph each AP location (existing or proposed) before and after
- [ ] Record channel plan for existing APs (if brownfield)
- [ ] Note construction changes from floor plan (e.g. new partitions, new glass walls)
- [ ] Capture passive and active data in each zone per section 4
- [ ] Note any rogue / neighbour APs observed

Before leaving:
- [ ] Export raw data files; confirm on laptop and backup media
- [ ] Remove any temporary APs / tripods
- [ ] Debrief with site contact (10 min verbal summary of findings)
- [ ] Agree deliverable due date

## 11. Acceptance Criteria
The survey is considered complete when:
- [ ] All deliverables in section 8 provided in requested format
- [ ] All zones in section 2 covered
- [ ] Deliverables reviewed by <role> and questions answered within <days> of submission
- [ ] Raw data files supplied and readable by our preferred tool
- [ ] <Any specific acceptance test - e.g. "validated heatmap shows -67 dBm or better in all user zones">

## 12. Evaluation Criteria (for external surveyor RFQ)
If using this brief to solicit quotes:
- **Experience:** Surveys completed in comparable environments (evidence)
- **Tooling:** Professional-grade spectrum + survey kit (named tools)
- **Insurance:** PI, PL appropriate to site
- **Schedule:** Can deliver within our window
- **Price:** All-inclusive of tooling, expenses, revisions (up to <N>)

## 13. Signed-off by
| Role | Name | Date |
|---|---|---|
| IT / Network lead | <name> | YYYY-MM-DD |
| Facilities lead | <name> | YYYY-MM-DD |
| Security / compliance | <name> | YYYY-MM-DD |
| Site manager | <name> | YYYY-MM-DD |
```

## Example invocation

**User:** "/wifi-survey-brief - planning a new wireless install for our 4-storey, 5000 m2 office move in Q3. About 350 staff, laptop-heavy, heavy Teams use, one 200-seat auditorium. Going Wi-Fi 6E. Need a surveyor to produce the design."

**What the skill will do:**
1. Ask about construction (glass + steel mesh can kill 6GHz; drywall is friendlier), outdoor requirement, existing cable runs / cabinets, access and H&S.
2. Propose predictive + on-site passive + AP-on-a-stick for the auditorium as the right survey mix.
3. Produce coverage + density goals tailored to laptop-heavy + Teams use (-65 dBm minimum, 25 dB SNR, 30-40 clients/AP).
4. Specify deliverables including per-floor AP-position DWGs, BOM for Wi-Fi 6E APs, and a channel plan that respects 6GHz regulatory power limits.
5. Give you an evaluation criteria block ready to drop into an RFQ to 3 surveyors for comparison.

## Notes for the requester

- **Specify deliverables by format, not just name.** "Heatmaps" alone yields screenshots. "PDF per floor at 1:100 with signal and SNR layers, plus native Ekahau .esx file" yields something you can re-use.
- **AP-on-a-stick beats predictive alone.** Any serious new deployment justifies APoS for at least the difficult zones.
- **Density targets matter more than coverage targets.** Coverage at -67 dBm is easy. Serving 200 people in a 200-seat room is hard.
- **Reduce SSID count.** Every SSID is airtime tax. Aim for 3-4: CORP + GUEST + IOT is usually sufficient.
- **Ask for raw files.** Vendor-polished PDFs are great for presentations. Raw Ekahau / AirMagnet files let you re-analyse or compare vendors.
- **Validate post-install.** Treat design and validation as two separate deliverables. Otherwise "design complete" becomes "blame the install team".
- **"Good" looks like:** you receive the report and can answer, without more calls, exactly how many APs you need, where they go, what model, and why the auditorium will work for 200 laptops + 200 phones on Teams.