What Is a Surveillance Detection Route? How to Plan and Run an SDR

On July 15, 1977, CIA officer Marti Peterson walked onto the Krasnoluzhskiy railroad bridge in Moscow to leave a package for a Soviet source. A KGB surveillance team was waiting. Three men grabbed her, and they knew exactly where the package was. Her source had been discovered three weeks earlier, and the KGB got to the bridge before she did.

A surveillance detection route, or SDR, is a planned journey with a believable purpose, built so that anyone following you has to show themselves more than once at points you have chosen to watch. It answers one question: is someone following me? It cannot tell you whether someone is already waiting where you are going, which is what caught Peterson.

Below, we cover how to plan an SDR, whether to run it alone or with a team, the mistakes that give it away, and what US and UK law lets you do when it confirms a follow.

A surveillance detection route is a deliberate path to a destination, chosen so that a follower has to pass the same few observed points as you. It looks like an ordinary errand, but every turn and stop tests whether the same person or vehicle keeps appearing.

The technique comes from intelligence work, where officers ran long routes before meeting a source. Protection teams use it before moving a principal to a sensitive meeting, a new residence or a predictable event. In the UK, the close protection qualification behind the SIA license requires learners to demonstrate surveillance, anti-surveillance and counter-surveillance "to confirm or deny third party activity."

Three terms get mixed up. Surveillance detection is watching for hostile surveillance during normal work. Anti-surveillance is what the person being followed does, on the move, to draw a follower out. Counter-surveillance is a separate, hidden team watching the watchers. An SDR is an anti-surveillance tool when you run it alone and a counter-surveillance tool when others watch the route for you. Our explainer on surveillance detection and the TEDD test covers the wider discipline.

An SDR works by turning one sighting into several. A single car behind you on a main road means nothing. The same car after two changes of direction, at a narrow bridge and again outside a shop ten minutes later is hard to explain as coincidence.

Practitioners judge those sightings with TEDD: the same person or vehicle seen over time, in different environments, across distance, or showing demeanor that does not fit the setting. The route creates those conditions on purpose instead of waiting for them.

Two features do most of the work. A channel point is a place a follower cannot avoid: a bridge, a one-way street, a single-lane road, a station exit. A decision point is a stop that forces the follower to drive past, park nearby or wait, and each choice tends to give you a clear look at them. Peter Jenkins, writing for Circuit Magazine on counter-surveillance routes, recommends four choke points, because the aim is a pattern "beyond coincidence."

The route also has to look natural. If the follower realizes they are being tested, a capable team drops back, swaps people or vehicles, and tries another day.

Plan an SDR backward from the destination, then check it on the ground at the same time of day you will run it. Most teams work in this order.

The table compares the three ways most routes are run.

Our members' breakdown of how protective details detect hostile surveillance goes further, with the five parts of a route that produce usable sightings and how to look at a residence the way a watcher does.

If you plan routes like this regularly, the Surveillance Detection Route Planner in the Members' Library lays out each leg, choke point and observation post, and what each leg should reveal.

Use a team when the threat justifies the people. A solo route is still far better than none, but it asks one person to do two jobs.

Alone, the person moving is both the subject and the observer. Every glance in a mirror competes with driving, walking and looking normal, so solo routes catch careless followers well and capable teams poorly. Jenkins's companion piece on anti-surveillance when mobile covers the drills a lone driver can use without announcing them.

With a counter-surveillance team, observers sit at the channel points before the subject arrives. They note every person or vehicle passing after the subject and report to one controller, who compares the lists. Anyone on two lists gets attention. One operator can cover several points by leapfrogging ahead, though the subject may need to stop to let them get into position.

With a principal in the car, the driver runs the route and the team leader decides whether to continue, divert or abort. The detail itself is visible, so the useful observers are the ones a follower would not connect to it. It is one reason the planning side of executive protection work takes far more hours than the movement.

Most failed routes fail because they look like routes.

That last point is where most private programs are weakest. Our members' piece on the surveillance blind spot makes the case for one shared log across a whole detail. To see where your own setup stands, our free Counter-Surveillance Self-Assessment runs through 21 checks across seven areas.

Do not confront the follower, do not continue to the sensitive destination, and report what you have. A confrontation confirms the follower has been seen, and the next attempt may come from a person or vehicle you have no description of.

Go to the safe alternative you planned, ideally somewhere public with staff and cameras. Pass the log to whoever leads security, and to the police if the same person or vehicle reappears or the principal faces a known threat.

Following someone can be a crime in both countries. In the US, the federal stalking law, 18 U.S.C. 2261A, covers anyone who travels or uses electronic means to "place under surveillance" another person with intent to kill, injure, harass or intimidate them, where the conduct causes reasonable fear or substantial emotional distress. States have their own stalking laws too. In the UK, the Protection from Harassment Act 1997 lists "following a person" and "loitering in any place" as examples of conduct associated with stalking. A dated log of repeat sightings is the kind of evidence police can act on.

SDR stands for surveillance detection route, and some practitioners say surveillance detection run. The term comes from intelligence tradecraft, where officers ran routes before meeting sources. It is now standard in protection and investigation work.

There is no fixed length. The route needs enough time and distance to pass three or four channel points and at least one stop, with the first test well away from the start. A short urban route can do that in well under an hour; a cautious route before a high-risk meeting can run far longer.

Yes. Choosing your own route and stopping where you like is lawful in the US and the UK, but traffic law still applies, so drills such as running red lights are offenses. Abroad, check local law before running organized counter-surveillance, because some host governments restrict or monitor it.

In the US, the Department of Homeland Security's Center for Domestic Preparedness runs a three-day Surveillance Detection course (PER-346) whose listed audience includes private sector security professionals. In the UK, surveillance awareness is a required unit of the SIA close protection qualification, and the free See, Check and Notify program trains staff at sites to spot hostile reconnaissance.

A route only tells you something if someone plans it, watches it and writes down what they see. The simplest place to start is a journey you already make every week: test it once, and check both ends as well as the road between them.