Core Definition (BLUF)
Surveillance detection (SD) is the disciplined practice of discovering whether a person, facility, or team is under hostile observation. Detection is not paranoia. It is baselining normal, designing opportunities for a watcher to reveal themselves, logging correlations, and escalating only when the standard of proof set in advance is met.
Doctrinal Framework
- Coverage: original. No complete open ARSOF ATP is the single source of truth for SD TTPs.
- Feeds protective work and force protection; pairs with Counter-Surveillance when the element actively works the watchers.
- Relies on Pattern of Life baselining of the protected target and the environment.
Mechanics
Baseline first
Abnormal requires normal. Build Pattern of Life on the protected target and on the environment (who belongs on this street at 0700?).
Multiple sightings logic
One sighting is coincidence until proven otherwise. SD hunts correlation:
- same face/vehicle across time and place
- appearance at choke points that only make sense if the protected party is the interest
- reaction to induced, lawful deviations in route or timing
Surveillance detection routes (SDR)
Design routes that:
- force a follower to make decisions (turns, holds, channelization)
- offer cover for status for the moving party
- include legitimate stops that create observation opportunities
- avoid theater (illegal maneuvers, endangering public)
SDRs are planned. Random gut zigzags train the practitioner, not the adversary.
Static detection
- note takers, loiterers, vehicles with odd dwell
- correlation across shifts (morning OP and evening OP)
- logging standards: time, place, description, imagery if lawful, confidence
Technical signatures (awareness)
Device tracking, cameras, and RF anomalies at a detection level. Deep TSCM is a different skill stack.
Escalation ladder
- Notice
- Correlate
- Confirm
- Report / hand off
- Change behavior or trigger Counter-Surveillance / protective response
Application
Protective details, advances, and small elements should treat SD as a standing function, not a special event. Fixed principals with public schedules are always under some level of observation interest; the analytic question is hostile vs benign, and the operational question is whether confirmation thresholds justify behavior change or CS.
Integrate SD findings into running estimates and into Detachment Mission Planning when the threat picture changes mid-cycle.
Related Concepts
Active complement: Counter-Surveillance.
Baseline: Pattern of Life.
Environment recon: Urban Reconnaissance.
Command culture: Mission Command (initiative inside intent when SD confirms).
Failure Modes
- Calling everything surveillance (cry wolf; team tunes out).
- Never logging, so correlation is impossible.
- Burn maneuvers that confirm hard-target status and break law or ROE.
- Confronting suspected watchers without a plan (fight, not detection).