What Advance Work Really Looks Like

By the time a client meets the Raven team on site, the real work has already been happening for days. Sometimes weeks. Sometimes months.

That part is invisible on purpose. A well-run advance is supposed to look like nothing — a quiet arrival, a smooth route, a calm room, the right person standing in the right doorway at the right moment. Clients see the handshake. They don't see the forty hours of phone calls, site walks, map study, and contingency planning that made the handshake possible. That gap between what people see and what actually keeps them safe is the gap this post is about.

Advance work is the job, not the prep for the job

There's a tendency in our industry to talk about "the detail" as the work and the advance as setup. We think that's backwards. The detail is the visible expression of decisions that were already made during the advance. If the advance is good, the detail looks easy. If the advance is bad, no amount of talent on the ground can fully fix it.

So we treat advance work the way a surgeon treats pre-op. You don't improvise it. You don't skip steps because the calendar got tight. You don't trust the version of the venue someone described to you over email — you go look at it, and if you can't go look at it, you find someone you trust who can.

How an advance actually unfolds

Somewhere between the conversations with the client and the day we deploy alongside them, we settle in for the advance. It has a rhythm, and we follow it on purpose.

It starts in the office. We map out every location the client will touch, study the surrounding area, pull the medical resources within realistic transport distance, and start identifying go and no-go areas — neighborhoods, routes, times of day, specific addresses we'll want to avoid and the reasons why. This is where the open-source intelligence work, the threat reporting, and the historical context all come together into a first draft of the operating picture.

Then we get on a plane or make the drive to the venue(s).

Once the remote work has told us what we need to look at, we prefer to deploy a person or two to physically visit the venues, put eyes on the actual areas the client will be using, and start building the local network we'll need on game day. We walk the rooms the principal will sit in. We drive the routes at the time of day they'll actually be driven. We meet the hotel security manager and the venue ops lead and the driver and the local liaison — face to face, on their turf, before anyone needs anything from anyone.

That networking and relationship building is paramount to our success — every bit as important as the conversations we have with the client at the start of the engagement. The people we'll be coordinating with on the day of need to know who we are before something goes sideways, not during. A name and a phone number in a contact roster is fine. A name, a phone number, a handshake, and a memory of the coffee you bought them is what actually picks up the phone at 11 PM.

We know some firms try to do this remotely. It's possible — satellite imagery, video walk-throughs, second-hand reports — and there are situations where it's the only option. But the personal touch and physical presence of a real site advance is the difference between thinking you understand a venue and actually understanding it. Photos don't show you the smell of the loading dock or the way the side exit funnels into a blind alley. Video calls don't introduce you to the front desk supervisor who's going to be the most valuable person in the building when something goes wrong.

Everything we learn — the remote work, the site visit, the relationships, the contingencies — then goes into a draft operations plan. That plan gets run by the client or their representative for review and approval, because the advance belongs to them, not to us. Once it's approved, the deploying team gets briefed off that document, and we go to work.

That's the sequence. Conversations. Remote advance. Site advance. Operations plan. Client approval. Team brief. Deploy. Skip any step and the whole structure gets weaker.

What the advance is actually looking for

Inside that sequence, here's what we're actually building:

Site picture. Entrances, exits, choke points, sight lines, stairwells, service corridors, the loading dock nobody ever thinks about, the restroom layout, the room where the principal will actually sit. We note where cell coverage drops and where it doesn't. We photograph what matters and we sketch what photographs can't capture.

Seamless coordination at a grand entrance highlights the value of meticulous planning in managing arrivals and departures.

Route study. Primary, secondary, and emergency routes — not just to the venue but from every position the principal will occupy that day. We drive the routes at the time of day the movement will happen, because rush hour and Sunday morning are different cities. We mark the choke points where a vehicle could be boxed in and we plan what to do if one of them goes bad.

Medical mapping. For every location the principal will be in, we know the nearest trauma center, the nearest cardiac facility, the nearest pediatric ED if children are involved, and the realistic transport time at that hour. We know which hospitals are good at what, because not every ER is created equal. When the worst day happens, the decision of where to go has already been made — we're not Googling it from the back of an ambulance.

Go and no-go areas. Neighborhoods, blocks, specific venues, times of day. Where we'll route through and where we won't. Where the principal can walk and where they can't. Where a backup driver should stage and where they shouldn't. These calls get made up front so nobody is making them under pressure.

Historic alleyways of a bustling market in Doha, Qatar, showcasing traditional architecture and vibrant shops filled with spices and goods.

Communications plan. Radio frequencies, backup channels, who-talks-to-whom under stress, what gets escalated and to whom, what the principal hears and what stays off the principal's plate. We test the comms before they matter — in the actual buildings, in the actual elevators, in the actual basement parking structure where the radios are about to go quiet.

Contingency planning. Medical emergency. Civil disturbance. Severe weather. Vehicle failure. A protest that materializes on the route. An attendee with a grievance. Family separation in a crowd. We don't plan for every possible thing — that's a waste of time — but we plan for the categories of things, and we rehearse the handful of decisions that have to be made in the first sixty seconds of each.

Reading the ground

A good advance is also a cultural read. The bespoke post talked about learning the client's culture. The advance is where we learn the venue's culture, and the city's.

Cape Town's cityscape glows under a starlit sky with the iconic Table Mountain in the distance, creating a breathtaking nocturnal view.

Is the hotel staff used to executive protection clients, or are we going to look conspicuous the moment we walk in? What does law enforcement presence mean to the local population — reassuring, or provocative? What's the polite distance to stand from a principal in this city? Are there religious or family observances during the visit window that change what's appropriate? Is the political situation on the ground today the same as it was when the trip was booked six months ago?

The answers to those questions change how we deploy, what we wear, who we deploy, and sometimes whether we recommend the trip happen at all. Our network of professionals has operated, educated and consulted in the US, Europe, Russia, China and Asia Pacific, and that range matters because the advance for a board meeting in Frankfurt is not the advance for a logistics tour in Jakarta is not the advance for a charity gala in Detroit. The framework is the same. The execution looks completely different.

Where the advance pays off

You can usually tell whether an advance was done well by what doesn't happen.

The motorcade doesn't get caught behind a parade nobody knew about. The principal doesn't end up in a holding room with no second exit. The medical issue at the dinner gets handled in four minutes instead of forty because the closest cardiac facility was already loaded into the driver's nav. The protester who shows up at the side entrance encounters a team that already knew that door existed. The press scrum that materializes outside the lobby gets routed around because someone walked the building on Tuesday and noticed the service elevator. The hotel manager who lets your team into a back stairwell at 2 AM does it because the person who walked the property last month bought him a coffee and asked how his son's football season went.

None of those moments make it into a highlight reel. None of them generate a thank-you email. They're the dog that didn't bark — and they're the whole point.

Raven's team navigating through the airport, a sense of accomplishment radiating from each member aft their successful mission abroad. The atmosphere, a mix of excitement and fatigue, as they reflected on the challenges they had overcome.

People, Protection, Peace of Mind

The mantra runs through the advance the same way it runs through everything else. The advance protects the people we're hired to protect, and the people we're hired alongside — the hotel staff, the venue crew, the drivers, the family members, the bystanders who never knew they were inside a security plan. It builds the kind of peace of mind a client can actually feel: the quiet confidence that when something unexpected happens, somebody already thought about it.

If you've got an event, a trip, or an operation coming up and the advance plan is "we'll figure it out when we get there," we'd like to have a conversation before that's the plan you go in with. The hours before the handshake are where good outcomes get built.