Most disappointing drone-detection deployments were doomed at survey time, not install time. These are the checks we run — in this order — before we quote anything. Print it, walk the site, write on it.

The twelve checks

• 1. Define the asset — what are you protecting, and where does the alarm actually need to come from?
• 2. Define the threat direction — approach paths, likely launch points, historical incidents
• 3. Perimeter walk — sightlines, fence lines, gates, and where a node can physically live
• 4. RID layer expectation — which aircraft in your airspace will broadcast, which will not
• 5. RF environment scan — 2.4/5.8 GHz occupancy; count the site’s own Wi-Fi first
• 6. Mounting survey — poles, roofs, mast permissions, bonding and surge points
• 7. Power — PoE runs, distances, breaker positions
• 8. Connectivity — where a cable can reach, what the firewall allows
• 9. Alert routing — who is notified, on what channel, and who ignores it at 3 a.m.
• 10. Data handling — where logs live, retention, who owns them
• 11. Walk-test plan — grid, pilot, date, acceptance criteria
• 12. Expectation note — one paragraph, in writing, on what this system will not detect

Check 12 is the one that saves relationships. A system that sees compliant drones cannot see a silenced FPV — and the survey that says so out loud is worth more than any datasheet. If you want a second pair of eyes on a completed survey, that is exactly what the free screening is for.

Content last reviewed: 2026-09-11. Interface draft v0.9 — locked against firmware 1.0. Questions: contact engineering.