THE GROUP SECURITY PROGRAM · WATCHING THE WATCHERS: OPERATIONS
SDR Design Principles
SEC-03 taught you that every surveillance effort has vulnerabilities — repetition, choke points, reaction to the unexpected, communication signature. A surveillance detection route, or SDR, is a route deliberately designed to put pressure on those vulnerabilities until a follower reveals itself. This lesson covers what an SDR is, what it isn’t, and why the design matters as much as the execution. Lesson 02 covers actually running one.
1.1 — What an SDR Is, and What It Isn’t
A surveillance detection route is a planned route walked or driven for the specific purpose of determining whether you are being followed. It is not evasion, and it is not the same thing as being careful. Evasion tries to lose a follower you already know is there. An SDR is built to answer a question you don’t yet have the answer to: is anyone there at all.
This distinction matters because an SDR that looks like evasion — sudden turns, obvious doubling back, checking over your shoulder — defeats its own purpose. The moment a real surveillance team suspects you’re checking for them, they either go static and stop moving (denying you the confirmation you’re looking for) or abort the operation entirely and try again another day, having learned that you’re alert. Either way, you’ve spent the route and learned nothing, and you’ve told a real collector that this target is worth more caution next time.
1.2 — Why Design Matters More Than Execution
A poorly designed route can be executed perfectly and still tell you nothing. If your route doesn’t create genuine choke points, offers no natural reason for the behavior you’re using to check, or doesn’t give you clean observation windows, you can walk it flawlessly and still have no idea whether anyone was behind you. The design does the work; the execution just has to not blow it.
Three things a well-designed SDR must do:
- Create genuine choke points. A point a following team has to pass through if they’re going to stay with you — a bridge, a single-entrance building, a dead-end street you then reverse out of. SEC-03 Section 2.3 covered why this matters: it forces a team to become visible at a place you control, rather than letting them hang back at a distance across an unpredictable route.
- Provide clean observation windows. A moment where you have unhurried, natural sightline behind or around you — a shop window’s reflection, a place where the route naturally requires you to pause and look. This has to be built into the route, not improvised, or you’ll either miss the window or make it obvious you’re using it.
- Have a plausible cover reason for every leg. Every turn, stop, and reversal needs an explanation a bystander — or a following team — would accept without a second thought: you’re running an errand, you forgot something, you’re meeting someone, you’re just walking. A route with no plausible reason to exist is itself an indicator.
1.3 — Choke Points and Observation Windows
These two elements are the load-bearing parts of any SDR, so they’re worth separating out in detail.
The two work together: you want a choke point positioned so that an observation window falls naturally just after it. If someone was behind you before the choke point and you don’t see them in the window afterward, that’s information — either they broke off, or they’re using a technique (like the leap-frog from SEC-03) that you’ll need more than one choke point to confirm.
1.4 — SDR on Foot vs. SDR in a Vehicle
The same principles apply, but the terrain is different.
Foot SDR
More choke points are available (doorways, alleys, footbridges, crosswalks) and observation windows are easier to build naturally (shop windows, waiting to cross). The tradeoff is that a following team on foot has more flexibility to blend in — there are more plausible reasons for a person to be walking nearby than for a specific vehicle to be nearby.
Vehicle SDR
Choke points are more limited but often more absolute — a bridge, a single road in/out of an area, a specific turn lane. Observation is harder to disguise (checking mirrors repeatedly can itself become a tell if overdone) but a following vehicle has fewer places to hide once you’re past a genuine choke point, and vehicles are individually more identifiable than pedestrians. A U-turn at a legitimate point (a gas station, a legal turnaround) followed by continuing your original direction is a classic vehicle check — it forces a following vehicle to either follow you through the turn (highly visible) or lose you.
Scenario Exercise: Planning the Route
You’ve been asked to plan a foot SDR for a MAG member’s route from their vehicle to a meeting location three blocks away, through a small downtown area with a mix of shops, a public library, and one pedestrian bridge over a creek that has no other nearby crossing.
Student task: Identify where you would place your choke point and why. Identify one plausible observation window you could build near that choke point, and explain what cover reason would make it look natural. What would you look for in that window that would tell you something useful, based on the team vulnerabilities from SEC-03 Section 2.3?
(Worked answer provided after submission.)
Knowledge Check
4 questions. 80% required to unlock Lesson 02.
Before moving to Lesson 02, you should be able to: explain the difference between an SDR and evasion; identify the three things a well-designed route must provide (choke points, observation windows, plausible cover); and explain why design quality matters more than in-the-moment execution. If any of these are unclear, reread Section 1.2 before continuing.