OTR Movements: Planning for the Unplannable

An off-the-record (OTR) movement is an unscheduled, unannounced stop or trip the principal decides on in the moment — no advance, no notice, often no destination until the vehicle is already rolling. The planning question is not how to prevent them; it's how to be ready for something you can't plan.

Every working protection team deals with OTRs. The principal finishes dinner and wants to walk two blocks to a bar a friend mentioned. The motorcade is headed home and the principal remembers a bookstore. A meeting ends early and suddenly there's an unplanned gym session across town. None of this was on the schedule, none of it got an advance, and all of it is now your problem. This post covers what a team can do before, during, and after, so that an off-the-record movement lands on prepared ground instead of improvisation. It's one way we think about the problem, not the only way.

The principal decides where the principal goes

Start with the part some teams get wrong. OTRs are principal-driven, and they are legitimate. The principal has final say over their own movement — it's their life, their schedule, their call. The team's job is to make the spontaneous stop survivable, not to talk them out of living their life.

A team that treats every OTR as a policy violation trains the principal to stop telling them things. That's the actual failure mode: not the unplanned stop itself, but the principal who starts slipping the detail because the detail made spontaneity feel like a negotiation. Once that happens, what you're protecting is a schedule the person no longer follows.

The team advises. The principal decides. The only time to push back is when something is actively going wrong: a specific threat, a deteriorating situation, a destination you have concrete reason to flag. Save your objections for those moments and they'll carry weight when you need them to.

Unpredictability is not the enemy

Here's the part of the OTR conversation that gets skipped: spontaneity has a security upside. Pattern-based surveillance (the kind that precedes most planned attacks) depends on predictability. Hostile planning needs to know where the principal will be and when. A movement nobody knew about is a movement nobody planned against.

An OTR defeats the surveillance cycle in a way no countermeasure can, because there was nothing to surveil. What makes an OTR risky is not the spontaneity but the arrival: an unknown door, no drop point, no trauma destination, no plan for who does what.

So the goal is a team for whom OTRs are routine, not a principal who takes fewer of them.

Pre-work beats reaction

You can't advance a destination you don't know. But you can do a surprising amount of work before an OTR ever happens, because OTRs are less random than they feel.

Build a pattern file on the principal. Everyone has favorites — restaurants, gyms, a bookstore, a barber, a friend's building. OTRs rarely go somewhere new; they draw from a knowable set the principal returns to. Keep quiet pattern notes: where the principal actually goes when the schedule doesn't say. Then pre-work the recurring destinations. A standing hasty file per frequent venue doesn't need to be elaborate:

• Entrance and exit options, and which door the principal uses
• Drop point and pickup point
• Trauma destination for that location, with drive time

When the principal says "let's go to the usual place," the advance already exists. It was done on a quiet Tuesday, not in the back seat at speed.

Do area studies, not just venue studies. A venue advance covers one address. An area study covers a district, and OTRs happen in districts. Know the areas the principal lives, works, and socializes in: which hospitals take trauma, where police coverage is dense and where it's thin, the choke points, the one-way grids, the comms dead zones. When the destination is an address you've never heard of, an area study means it still sits inside terrain you know. See what a security advance covers for the baseline this compresses from, and the trauma center problem for why the district-level medical question deserves its own file.

Write standing SOPs for the unplanned stop. Default vehicle spacing. Default drop and pickup logic. Default comms procedure. Who dismounts first, who stays with the vehicle, who owns the door. These decisions cost nothing to make in advance and everything to make on arrival. Decide once, brief once, rehearse until the unplanned stop runs like a planned one. The team that argues about who takes the door in the moment is doing planning work at the worst possible time.

And invest in the driver. Local knowledge is the OTR safety net. A driver who knows the city turns an unknown address into a known neighborhood: they already know the parking situation on that block, the hospital ten minutes north, the street that backs up after 1700. Hours spent on route familiarization drives are advance work for every OTR you haven't had yet.

The passenger-seat hasty advance

When the OTR is happening, you get a compressed window — the few minutes between "let's stop" and arrival. Use them in a fixed order:

• Pull the destination. Address, venue type, layout if imagery is available.
• Scan what's around it. Anything scheduled nearby, meaning events, protests, road closures, crowds.
• Confirm the trauma destination for that district, not the one from this morning's plan.
• Agree the drop point before the door opens, not after.

That's a hasty advance run from the passenger seat, and it follows the same logic as any compressed advance: sequence the essentials, skip nothing critical, say out loud what you didn't get to. We've written up the fuller method in the hasty advance. The OTR version is that method with the clock turned down further.

One boundary worth stating plainly: everything here is planning under time pressure, done before anything has gone wrong. It is not actions-under-fire. If the situation turns kinetic, you're in a different problem set with different drills. Don't confuse the two.

Write it down afterward

The cheapest improvement available to any team is the OTR log. Five minutes after the stop: where did we go, what worked, what didn't, and what does this add to the pattern file. New favorite venue? Start its hasty file. Drop point turned out bad? Note the better one.

An OTR you don't log is an event. An OTR you log is preparation for the next one.

Teams that write these down watch their OTRs get smoother over months, because each spontaneous stop quietly becomes a pre-worked destination. Teams that don't are improvising the same venue for the fifth time.

What not to do

• Don't fake an advance you didn't do. If the venue is unknown and the picture is thin, say so on the net. The team can cover a known gap; it can't cover one you papered over.
• Don't crowd the principal with process. If your OTR procedure is visible to the principal, it's too heavy. The work should happen in the front seat and on the radio, not in their ear.
• Don't treat every OTR as an emergency. It's an unplanned stop, not a crisis. A team that spins up to full alert for a coffee run exhausts itself and erodes the principal's trust in its judgment.

The OTR is a fact of protective work, and it isn't going away; no schedule survives contact with a principal who has a life. The teams that handle them well are not faster thinkers. They did the thinking earlier.