Route Surveys That Hold Up

A route survey is the systematic evaluation of the paths a movement will use — not just where they go, but where they fail. The output is a set of routes another team member could drive cold, with the decision points, choke points, and contingencies already worked out.

This is one way we think about route work. Teams differ, and the details below aren't doctrine — they're a starting framework you adapt to your principal, your city, and your day.

One thing worth stating up front, because it's a common misconception: the team executing the movement owns the route. In protective work that's the detail — the agents on the ground have the final say on route and path, not an analyst back at a desk. Intel supports the decision (area studies, known problem spots, recent incidents) but doesn't make it. And on most details, the principal has the last word on their own movement unless something is actively going wrong. Good route work respects that chain instead of pretending a survey overrides it.

What a route survey answers

Strip the format away and a route survey answers five questions:

1. What's the primary, and why this one? "Fastest" is a reason. So is "most predictable," which often beats it. A route chosen on purpose can be defended and adjusted; a route a navigation app picked is just a default nobody owns.
2. Where does it fail? Every route has points where options collapse — bridges, tunnels, one-ways, dense merges, a single venue approach. You don't get to remove them. You get to know them, know the hours they're worst, and know what you'll do at each.
3. What's the alternate, and from where? An alternate you can only join from the start point is a second route, not an alternate. Useful alternates branch from decision points along the primary — named places where you can still choose. Past the last one, you're committed, and it helps to know exactly where that is.
4. How long when it matters? Timing runs at the hour of the actual movement. A route driven Sunday morning tells you about Sunday morning.
5. What's along it? Trauma centers and safe holding you'd want under pressure. Fuel on long movements. And the environment near the route on the day — a survey-day snapshot of ground that keeps moving until execution.

How much redundancy is realistic

You'll see PACE — primary, alternate, contingency, emergency — applied to routes. It's a useful mental model, but be honest about what small teams actually run.

In practice, most teams don't survey a full four-tier PACE per leg. It's usually a primary, an alternate, and maybe a third option on the harder movements. That's not a shortcut to apologize for — it's the realistic product of limited time and people. What the layered model is good for is naming what you're trading when you stop at two: you're accepting that if primary and alternate are both gone, you're solving it live. Knowing that is planning. Not knowing it is luck.

Two contingencies worth building in regardless of how many route tiers you run:

The bump plan. If a vehicle in the convoy goes down — mechanical, blocked, whatever — everyone bumps: the occupants shift into the other vehicles per a pre-briefed order, and the movement continues. It's an SOP, rehearsed cold, so nobody's improvising seating under stress.

The medical fallback. Nearest appropriate trauma center and the route to it, from anywhere along the movement — not just from the start. This isn't a route to the destination; it's a route off the X.

Under fire is a different mission set entirely. That's its own set of SOPs — blocking, cover, maneuvering the vehicle for the safest transfer — and the one rule that overrides the rest is that the vehicle with the principal doesn't stop. This post is about planning routes, not fighting through an ambush. Don't confuse the two.

Documentation that survives handoff

The test for route documentation is transferability: could someone who wasn't in the car execute this? That means, per route —

• the line itself, in a form that doesn't live in one person's app history;
• decision points, each with the trigger and the turn ("if the approach on 5th is stacked at the garage, commit to the dock approach at Pine");
• choke points with their bad hours;
• timing from the runs, with the run time and day noted;
• the medical fallback from the far half of the movement, not just from the start.

One page per route is usually enough. The format matters less than the property: decisions pre-made, written where the team can reach them, current enough to trust.

Local knowledge beats a cold survey

Here's the part no survey template fully solves: the best route intelligence is usually a local. Someone native to the city — a driver, a fixer, a local security asset — knows the road system, the daily rhythms, the streets that stack at 5pm and the shortcut that isn't on the map, in a way an agent dropping in cannot.

It's why serious EP operations hire local drivers. An agent parachuting into an unfamiliar city won't have real feel for the ground inside 72 hours, and even after that won't match someone who's driven it for years. A route survey done by an outsider is a good discipline; a route survey informed by a trusted local is a better product. Where you can, get the local input — it's the highest-leverage source available and it's rarely on any feed.

Where route surveys actually fail

Three failure patterns account for most route problems, and none is a surveying error.

The survey ages out. Routes are surveyed days or weeks ahead. Construction starts, a closure lands, an event takes the street — and the survey quietly describes a city that no longer exists. The fix is a delta check close to movement time: not a re-survey, just a deliberate look at what changed along lines you already know.

The knowledge stays in the driver. One person drove the runs, the plan lives in their head, and they're sick or in the other vehicle when it matters. Documentation discipline is the whole fix, and it costs one page.

Alternates that were never real. An alternate nobody drove, timed, or checked for the same choke points is a cosmetic entry. Pressure is exactly when you're least equipped to solve a route from scratch — so an alternate deserves the same standard as the primary, or an honest admission that you don't have one.

A route survey that holds up, then: chosen on purpose, failure points named, contingencies real, timing honest, written down, informed by local knowledge where you can get it, and checked again near movement time. None of it is complicated. All of it is work — which is exactly why the shortcuts are common.