When I protect a CEO visiting Los Angeles, one of the first things I want to know is not how many agents are assigned.

I want to know who owns the schedule.

That sounds administrative.

It is not.

A CEO may land at LAX or Van Nuys, move to a hotel, attend a board meeting, stop at an office in Century City, add a private dinner in Beverly Hills, visit a residence in Malibu and decide at 8:30 p.m. to meet somebody who was never on the original itinerary.

If the executive assistant has one schedule, the chief of staff has another, the driver is working from yesterday’s text message and the protection team finds out about changes when the principal gets into the vehicle, the problem is not lack of manpower.

The problem is operational control.

That is where I start.

For a visiting corporate executive, executive protection should make a complicated day easier, not harder.

The executive should not be standing at a curb while security figures out which vehicle is theirs.

The principal should not be waiting in a hotel lobby because the driver received the old departure time.

The chief of staff should not have to call four people to determine whether security knows the dinner location changed.

And a last-minute schedule adjustment should not force the protection operation to rebuild itself from zero.

Good executive protection is often less about what the principal sees and more about how well the people behind the movement stay on the same operating picture.

That is especially important in Los Angeles.

The city is geographically spread out.

Executives may use commercial aviation, private aviation, hotels, corporate offices, production facilities, private residences, restaurants and event venues during a single visit.

Traffic conditions change constantly.

Airport procedures change.

Meetings run late.

Vehicles get repositioned.

Assistants add stops.

Weather, demonstrations, road closures or other emergencies can alter the day.

The protection team needs a structure that can absorb those changes without disrupting the executive.

That is what this article is about.

Not how to put a bodyguard next to a CEO.

How to keep the entire movement synchronized.

Key takeaways

• There should be one authoritative itinerary. Security, transportation and executive support should not operate from competing versions of the schedule.
• Schedule changes need an owner. The protection team should know who can legitimately add, cancel or relocate a movement.
• Last-minute changes should be classified, not automatically rejected. A time change is different from a new private address, unknown driver or completely new meeting.
• Airport planning must be airport-specific. LAX commercial arrivals operate differently from a corporate aircraft arriving through an FBO at Van Nuys.
• Driver identity should be verified. A new name in a text message should not automatically result in the CEO entering an unfamiliar vehicle.
• Real-time traffic information should inform the movement. A static route created the night before is not enough for Los Angeles.
• Transitions deserve disproportionate attention. Hotel exits, curbside pickups, parking structures, loading zones and building entrances are temporary spaces where control can decrease.
• The chief of staff and executive assistant are part of the protection system. They often know about schedule changes before anybody else.
• Need-to-know still applies. Operational coordination does not require distributing the CEO’s complete itinerary to everyone supporting the trip.
• Executive protection should preserve business tempo. A good program allows legitimate schedule changes without making security the reason the executive cannot operate.
• Corporate security and the local protection team need a clean handoff. Relevant threat information, principal preferences and movement requirements should arrive before the executive does.
• Contingencies should already exist. Vehicle failure, blocked entrances, delayed flights and unavailable meeting locations should not be treated as unprecedented emergencies.

The real protection problem is schedule control

Corporate executives tend to run on dynamic schedules.

A family vacation may have a relatively stable itinerary.

A CEO visit often does not.

The 11:00 meeting moves to 10:30.

The board wants lunch afterward.

A private-equity partner is suddenly available.

The CEO wants to see a facility on the way back.

A dinner changes restaurants.

Someone important invites the principal to a private residence.

The return flight moves two hours.

None of that is unusual.

A protection program that can only function when the itinerary stays fixed is not well designed for corporate executive protection.

One itinerary must be the source of truth

I want one current operational itinerary.

Not:

the executive assistants calendar;

plus a PDF emailed yesterday;

plus the driver’s text thread;

plus a document created by corporate security;

plus something the principal verbally changed over lunch.

There may be several systems involved.

There still needs to be a defined authoritative version.

The itinerary should show operationally relevant information

I do not need the CEOs entire corporate calendar.

I need what affects the movement.

For each relevant stop:

time;

location;

full address;

meeting contact;

expected duration;

vehicle requirement;

arrival point;

departure point where relevant;

and any security information necessary for the team.

If an aircraft is involved:

airport;

terminal or FBO;

flight identification;

expected arrival;

baggage or passenger considerations;

and receiving vehicle.

Version control matters

If the protection team receives a schedule at 6 a.m. and another at 9 a.m., everybody should know which one is current.

The easiest way is simple:

date;

time;

version;

authorized source.

I do not need software complexity for the sake of complexity.

I need to eliminate ambiguity.

The chief of staff or EA should not have to manually rebuild security every time the schedule changes

Executive support has its own job.

The chief of staff should be able to say:

“Dinner moved from Beverly Hills to West Hollywood at 7.”

The security operation should know what to do with that information.

Who updates transportation?

Who checks the new location?

Who confirms the arrival point?

Who updates the driver?

Who decides whether the change materially affects staffing?

The executive assistant should not need to understand the protection team’s internal deployment structure.

Not every schedule change carries the same security significance

I like to separate changes into practical categories.

Low-impact change

Meeting moved 20 minutes.

Same building.

Same people.

Same vehicle.

The team adjusts.

Moderate-impact change

Dinner moves to another established restaurant.

The team verifies the destination, arrival and route.

Higher-impact change

Principal adds a meeting at an unfamiliar private residence.

Or:

the vehicle changes;

the driver changes;

an unknown person is now receiving the principal;

a new public appearance is added;

or the executive wants to travel somewhere outside the planned operating area.

That deserves more attention.

Change control should be fast

I am not trying to stop the CEOs day every time something changes.

I want a process that allows the security lead to say:

“Received.”

“Address confirmed.”

“Vehicle updated.”

“Driver has it.”

“We are ready.”

That is the standard.

Los Angeles airport planning has to be specific

A visiting CEO can arrive in Los Angeles through very different aviation environments.

That changes the movement immediately.

LAX is one of the country’s largest commercial airports. Los Angeles World Airports currently describes LAX as the sixth-largest U.S. airport and says it serves more than 200,000 guests per day. The airport is also still undergoing a multibillion-dollar landside transformation.

That is not an environment where I want pickup instructions based on what the executive remembers from their last trip.

LAX ground transportation is still changing

As of October 2026, LAX-it remains the pickup location for taxis and ride-app vehicles.

But LAX specifically says limousine and executive-car pickup is not handled through LAX-it and can continue from the outer curb at the baggage-claim level.

That distinction matters when a corporate team is coordinating an executive arrival.

The principal should know exactly where the professional vehicle and driver will be.

Not:

“Call him when you land.”

The airport plan should answer five questions before the flight lands

Which terminal?

Where will the executive actually emerge?

Who is meeting them?

Where is the vehicle?

What happens if the arrival changes?

If international processing, baggage or aircraft parking changes the expected exit point, somebody should own the update.

Airport pickup should use positive identification

The executive walks outside.

There are dozens of black vehicles.

Several professional drivers.

People holding signs.

Ride-share traffic.

Family pickups.

I do not want recognition based entirely on:

“He said he would be in a black Suburban.”

That describes half the curb.

The protection team should know:

driver name;

driver photograph where appropriate;

vehicle;

license plate;

and provider.

Last-minute driver substitutions need verification

Drivers get sick.

Flights change.

Companies substitute personnel.

That is normal.

The new driver should be verified through the established transportation provider or another trusted channel.

Not solely through a message from the person claiming to be the replacement.

Van Nuys creates a different operating environment

Many corporate and private aircraft movements use Van Nuys Airport.

Los Angeles World Airports describes VNY as one of the world’s busiest general-aviation airports, dedicated to noncommercial aviation, with more than 100 businesses on the airport and four major fixed-base operators listed by LAWA.

That is a very different executive movement from walking out of baggage claim at LAX.

The FBO may provide a more controlled interface.

The vehicle may be positioned differently.

Passenger and baggage movement are different.

The protection team should coordinate with the actual FBO rather than treating “Van Nuys Airport” as a single pickup point.

FBO details should be confirmed, not assumed

Which operator?

Which entrance?

Can the vehicle access the appropriate area?

Where does the driver wait?

Who handles luggage?

Who is meeting the aircraft?

If the aircraft diverts to another airport, who rebuilds that arrival?

Those are operational questions.

Do not send the CEO the airport problem

The principal should not land and receive:

“What FBO are you at?”

Security should already know.

The executive should not be calling the driver from the aircraft while the protection team tries to locate the car.

The handoff should feel simple because the work happened earlier.

Ground transportation is part of executive protection

The vehicle is not merely a logistical tool.

It determines:

movement;

timing;

exposure;

privacy;

and the teams ability to adapt.

I want the vehicle appropriate for the principal and assignment.

Not automatically the largest SUV available.

The driver matters more than the vehicle badge

A beautiful executive car with a driver who:

does not know the itinerary;

does not understand the security team;

keeps checking a phone while driving;

does not know alternate arrivals;

or disappears when the meeting runs late

is not a strong transportation solution.

I want a professional driver who understands the assignment.

The driver needs the correct amount of schedule information

Enough to perform the movement.

Not necessarily the CEOs entire day.

If the driver is responsible for:

hotel to office;

office to lunch;

lunch to hotel;

give them the information required for those movements.

There is no operational reason every vendor needs the complete corporate itinerary.

Route planning in Los Angeles has to be live

The route that looked perfect at 6 a.m. may not be the route I want at 4 p.m.

Collision.

Lane closure.

Construction.

Demonstration.

Weather.

Police activity.

The team should have real-time information.

Caltrans QuickMap provides current traffic speeds, lane and full closures, CHP incidents, highway information, message signs and camera views. That is a practical source for movement monitoring, especially before longer freeway movements.

I do not believe in one sacred route

Some security programs mistake route repetition for the entire transportation threat.

Then they create artificial variation every day.

Different is not automatically safer.

A new route may be:

slower;

less familiar;

more isolated;

more congested;

or operationally worse.

I want the team to know sensible alternatives.

Then choose based on current conditions.

Build route options around the destination, not theory

Primary route.

Reasonable alternate.

Known problem areas.

Arrival configuration.

That is usually enough.

We are protecting a business executive.

Not conducting a military convoy.

Road closures should affect timing before they affect the principal

If Caltrans shows an incident that materially changes the movement, I want that recognized while the CEO is still inside the meeting.

Then security can quietly adjust:

departure time;

vehicle position;

route;

or the next appointment.

The principal should not need to stand beside the vehicle while everyone discusses traffic.

Hotel departures are important because they become predictable

A visiting CEO may use the same hotel entrance several times in two days.

Morning departure.

Return from meetings.

Dinner departure.

Late return.

That repetition makes the hotel interface operationally important.

I want to know:

where the car stages;

whether it can remain there;

which door the principal uses;

where luggage is handled;

what happens during heavy arrival traffic;

and whether another entrance is available if needed.

The hotel lobby should not become the waiting room for transportation problems

The principal comes downstairs at 7:30.

The vehicle should be ready.

If it is not, the executive should remain somewhere appropriate rather than becoming a stationary target in a public entrance while everybody searches for the driver.

Hotel staff should receive only what they need

Security may coordinate with:

valet;

concierge;

security director;

front office;

or event personnel.

They do not all need the executives complete itinerary.

“Vehicle expected at 7:25 at this location.”

That may be enough.

Room numbers deserve basic information discipline

I do not want the CEOs room number casually circulated through transportation and event threads.

The driver does not need it.

The restaurant does not need it.

The venue does not need it.

Need-to-know remains simple.

Private meetings create a different protection problem than corporate offices

A CEO may leave a controlled corporate building and say:

“We are stopping by someone’s house.”

That is a real executive-protection situation.

I want to know:

whose house;

exact address;

whether they are expecting us;

how the vehicle enters;

how long the executive expects to stay;

and whether security remains with the principal or stages elsewhere.

A last-minute private residence should receive more scrutiny than a known corporate office

Not because private residences are automatically dangerous.

Because the team has less information.

A Fortune 500 office may have:

security;

reception;

access control;

parking procedures;

and emergency plans.

An unfamiliar residence may have none of those.

The change should be assessed accordingly.

Corporate offices require coordination, not duplication

If the host company already has a professional security department, I want to work with them.

I do not need to recreate their entire building-security system.

I need:

arrival;

parking;

entry;

meeting location;

relevant access requirements;

emergency contact;

and departure.

Simple.

Host security should know enough to prevent friction

If the CEO arrives with a protection agent, the lobby should not discover that fact when the protector reaches the magnetometer.

If weapons or regulated equipment are involved, appropriate legal and site-specific coordination needs to occur in advance.

Professional protection should not create a confrontation with the host security team.

Offsites need a different level of review than the normal office

Corporate offsites often feel internal.

“It is just our leadership team.”

But the physical environment may include:

hotel staff;

catering;

AV technicians;

contractors;

entertainment;

other guests;

shared parking;

and multiple public entrances.

That is a different operating environment from headquarters.

For CEO protection, I care about the executive movement through the offsite

This keeps the function distinct from broader event security.

Where does the CEO arrive?

Where do they work?

Where do they take private calls?

How do they leave?

If the company event has its own security, how do those personnel communicate with the CEOs protection team?

The local event team protects the event.

The executive protection team remains responsible for the principal.

Speaking engagements change the CEOs exposure

An internal meeting becomes a stage appearance.

Employees take photographs.

Attendees know where the principal is.

Departure may become predictable.

I want the protection team to know that beforehand.

Not find out when somebody hands the CEO a microphone.

Restaurants are primarily transition problems

For most corporate dinners, I am less concerned about standing next to the CEO at the table than I am about:

arrival;

vehicle staging;

public entrance;

departure time;

and pickup.

The protection posture should fit the environment.

A last-minute dinner is usually manageable

Security should not become the reason a CEO cannot have dinner.

The team can quickly establish:

exact location;

reservation;

arrival point;

vehicle plan;

and whether anything in the current threat picture changes the decision.

Then move.

Spontaneous stops need the same discipline

“Pull in here.”

“I want coffee.”

“Let’s stop at that store.”

Executives are human.

A good protection program can handle that.

I do not want an agent telling the principal:

“No, it was not on the itinerary.”

Unless there is an actual reason.

The protection team should think quickly without making the principal wait unnecessarily

Where can the vehicle stop?

What does the entrance look like?

Is there anything currently known that makes the stop inappropriate?

Fine.

Proceed.

Executive protection has to support life, not eliminate spontaneity.

The exception is when the change materially changes exposure

Principal wants to walk three blocks through a demonstration.

Different issue.

Principal adds a meeting with an unknown person at a private address.

Different issue.

Principal wants to enter a venue that just received a threat.

Different issue.

The team should be comfortable distinguishing inconvenience from actual risk.

Corporate security should provide a clean pre-arrival threat handoff

I do not need 200 pages of corporate intelligence.

I need what affects this executive during this trip.

Known unwanted contacts?

Recent threatening communication?

Employee termination creating specific concern?

Litigation?

Activist attention associated with an announced appearance?

Known person who repeatedly approaches the executive?

Recent incident at headquarters?

Give the local protection team the relevant information.

Corporate security should separate confirmed information from concern

“Former employee threatened the CEO on September 12.”

That is specific.

“Leadership thinks people are angry.”

Different.

I want to know what is fact, what is assessment and what is still unknown.

Do not bury the local detail in irrelevant corporate reporting

A short useful briefing is stronger than a document nobody can operationalize.

Name.

Photo if relevant and lawfully held.

Behavior.

Last contact.

Known location.

Law-enforcement involvement.

What security should do if the person appears.

That is actionable.

The local detail should report back too

A protection assignment is not information flowing in one direction.

If someone appears repeatedly during the LA visit, corporate security should know.

If unusual contact occurs at the hotel, record it.

If an individual tries to reach the CEO at an offsite, report it.

The information may matter after the executive flies home.

Driver and security communications need defined roles

I do not want five people calling the driver.

One person updates the driver.

The driver confirms.

The protection lead knows.

Simple.

Use acknowledgement for material changes

The itinerary changes from Beverly Hills to Malibu.

A message is sent.

I want acknowledgement.

“Received.”

Otherwise nobody knows whether the driver is actually working from the update.

Do not depend on one group text for the entire operation

Messaging applications are useful.

They are not an operating concept by themselves.

The team should know:

where the authoritative schedule lives;

where urgent changes are communicated;

who is authorized to change movements;

and who confirms those changes.

Use separate channels for operations and noise

If the movement thread includes:

restaurant menus;

flight memes;

assistant chatter;

photos;

and 150 unrelated messages,

the important update can disappear.

Operational communication should remain operational.

Who can change the CEOs movement?

This should be explicit.

CEO.

Chief of staff.

Executive assistant.

Maybe corporate security.

Maybe spouse for certain private movements.

Not every employee who believes the CEO should attend another meeting.

Senior title does not automatically equal itinerary authority

A division president texts the driver:

“Bring the CEO to our office instead.”

The driver should not silently redirect the principal.

The request goes through the established itinerary authority.

This protects against:

confusion;

miscommunication;

and impersonation.

Last-minute electronic instructions deserve verification when they materially change the plan

Email compromise happens.

Messaging accounts can be spoofed.

Phones can be lost.

The answer is not paranoia.

It is independent verification for high-impact changes.

“Switch to this new driver.”

“Go to this private address.”

“The CEO wants the protection detail to stand down.”

Those deserve confirmation.

Security should know the principal’s normal decision style

This helps immensely.

Some CEOs constantly change the schedule.

Others almost never do.

Some communicate changes personally.

Others always go through the EA.

Some want the vehicle ten minutes early.

Others leave meetings unpredictably.

Protection should adapt to the actual principal.

Principal preferences are operational information

Which vehicle side do they normally use?

Do they carry bags?

Do they want the agent immediately beside them or several steps away?

Do they take unscheduled walks?

Do they smoke outside?

Do they regularly bring unexpected guests?

These preferences affect movement.

They should be briefed.

The protection team should not force the principal into a generic template

Good executive protection is personalized.

The security plan should adapt to the executive’s working style while still managing risk.

A CEO who spends the entire trip fighting their protection team will eventually bypass it.

Temporary details require unusually good handovers

A local Los Angeles team may protect the executive for only 48 hours.

That makes the initial handoff more important, not less.

I want:

principal profile;

photo;

current itinerary;

authorized schedule contacts;

medical information legitimately required for protection;

relevant threat information;

vehicle details;

airport information;

and principal preferences.

Enough to do the job.

Do not over-distribute sensitive executive information to a temporary team

A local driver does not need corporate legal files.

A hotel does not need family details.

A restaurant does not need flight information.

The protection lead can maintain the broader picture while distributing operational slices.

Hotel and itinerary names should not appear everywhere

The CEO’s hotel, room details and exact movement schedule can become sensitive information.

Use controlled distribution.

A visiting CEO should be treated as a temporary local operation

This is how I think about it.

For 48 hours, Los Angeles becomes the principals operating environment.

The local protection team needs enough structure to function as if the executive belonged there.

Airports.

Hotel.

Office.

Drivers.

Medical resources.

Current threat information.

Local emergency information.

Then, when the executive leaves, the operation hands back cleanly.

Emergency alerts can be built into a temporary LA visit

The City of Los Angeles uses NotifyLA for emergency notifications by phone, text and email.

Current city guidance says users can register multiple addresses and multiple points of contact, which makes the system useful not only for residents but potentially for teams monitoring a hotel, office or other relevant location during a visit.

For movements outside the City of Los Angeles, Alert LA County and the alert systems operated by individual cities may be relevant instead.

Los Angeles County maintains a current directory showing that jurisdictions including Beverly Hills, Malibu, Calabasas, West Hollywood and others use their own or regional notification systems.

Jurisdiction changes quickly in Los Angeles

A CEO can leave the City of Los Angeles and enter:

Beverly Hills;

West Hollywood;

Santa Monica;

Culver City;

Malibu;

or another jurisdiction without the principal noticing much difference.

Police, fire and emergency-notification systems can change with those boundaries.

The protection team should know where it is operating.

Weather can change a CEO movement too

This is particularly relevant in the current 2026 operating environment.

Los Angeles Emergency Management has spent September preparing residents and businesses for the 2026-27 El Niño period and warns that storms can produce closures and delays. Current city guidance specifically recommends anticipating delays and planning alternate routes during wet weather.

For executive protection, that is an operational issue.

A mudslide or flooding problem does not care that the CEO has an investor dinner at 7.

Routes need current information.

Earthquake and wildfire planning should remain proportionate

A two-day visiting CEO detail does not need a hundred-page disaster binder.

It does need basic continuity.

If a major earthquake, wildfire or other local emergency occurs:

where is the principal?

where is the vehicle?

can the team communicate?

is the planned airport still practical?

does the hotel remain usable?

who in corporate leadership receives updates?

Those are enough to begin.

Medical readiness is part of the detail but should not dominate this assignment

A CEO is statistically much more likely to experience an ordinary medical issue than an assassination attempt.

The team should know:

how to call 911;

how responders reach the current venue;

whether the principal has relevant medical information that the team is legitimately responsible for;

and what immediate medical capability the assigned personnel possess.

The City of Los Angeles directs people to 911 for life-threatening emergencies requiring police, fire or paramedic response.

The plan should include vehicle failure

Vehicles break.

Tires fail.

Warning lights appear.

Minor collisions happen.

What is the replacement plan?

If the detail depends on one vehicle, the team should at least know how a replacement will be obtained without leaving the CEO standing beside the road.

Vehicle collision procedures should prioritize people first

Is anyone injured?

Is the vehicle safely positioned?

Does the principal need to transfer?

Who handles the collision information?

The principal should not become the accident administrator.

A delayed flight should not create uncertainty about coverage

The CEO was expected at 6.

Now arrival is 10:45.

Who confirms the driver remains?

Who adjusts hotel arrival?

Does staffing change because duty hours change?

Do not leave that unresolved until landing.

Duty-hour management matters in professional protection

A team that began working at 5 a.m. may not be the team I want making critical driving decisions at midnight simply because the CEO’s day expanded.

Staffing should reflect actual hours.

Fatigue is an operational risk.

Corporate travel departments and protection teams should not work around each other

Travel books the flight.

EA books hotel.

Office books transportation.

Corporate security hires protection.

If none of them share operationally relevant information, the executive experiences the seams.

I want those seams removed.

One travel coordinator can simplify complex trips

Not necessarily a new employee.

One identified person with authority to resolve:

flight change;

hotel change;

vehicle change;

and executive schedule question.

The protection lead then has one counterpart.

What should be shared with the CEO?

As little operational noise as reasonably possible.

The CEO should know:

who their protection lead is;

who the driver is;

how the team communicates with them;

and any decision that materially affects their plans.

They should not receive every route discussion.

The executive should not be the communications hub

Driver asks CEO about dinner.

Agent asks CEO about the airport.

Assistant asks CEO where the vehicle is.

Hotel asks CEO when they are leaving.

That is not support.

The support system should communicate around the principal.

Executive protection should reduce cognitive load

This is one of the biggest values a professional detail provides.

The CEO can focus on:

investors;

employees;

customers;

board members;

or the transaction that brought them to Los Angeles.

Security manages movement.

Protection should not become performative

A visiting CEO may not need:

four agents;

a convoy;

visible earpieces;

and an entourage filling the lobby.

Or they may have a legitimate risk that justifies more substantial protection.

The level follows the principal.

Not the job title.

I start with exposure

Public visibility.

Threat history.

Current company issues.

Events.

Litigation.

Personnel issues.

Travel schedule.

Family involvement.

Locations.

Then we build the detail.

Local temporary protection can be discreet without being passive

A one-agent or small-team detail can still have:

good advance work;

reliable transportation;

schedule control;

strong communication;

and current information.

Visible manpower is not the only measure of capability.

What companies can review before sending a CEO to Los Angeles

Identify the itinerary owner

One person or system is authoritative.

Identify who can change the itinerary

CEO.

EA.

Chief of staff.

Others only through them.

Send the protection team the current schedule early

Not five minutes before arrival.

Provide relevant threat information

Current and actionable.

Confirm the arrival airport

LAX?

Van Nuys?

Burbank?

Another airport?

Confirm terminal or FBO

Airport name alone is insufficient for a clean pickup.

Verify the driver

Name.

Vehicle.

Plate.

Provider.

Define driver substitution procedure

Do not accept an unknown replacement without confirmation.

Check real-time road conditions

Use current tools such as Caltrans QuickMap rather than relying exclusively on a static route.

Review the hotel interface

Pickup.

Drop-off.

Vehicle staging.

Review private-address meetings separately

They deserve more verification than known corporate sites.

Coordinate with host corporate security

Avoid access surprises.

Separate executive protection from event security

Understand who owns the principal and who owns the event.

Build reasonable route alternatives

Do not overcomplicate them.

Create a vehicle contingency

Know how replacement transportation appears.

Plan for flight delays

Coverage and driver hours should adjust.

Limit itinerary distribution

Need-to-know.

Subscribe to relevant local emergency alerts

NotifyLA allows multiple locations to be monitored inside Los Angeles. Other cities and LA County have separate systems.

Define the emergency corporate contact

Who receives updates if something significant happens?

Brief the principal’s preferences

Help the local detail fit the executive immediately.

Conduct a clean post-trip handoff

Any relevant incident observed in Los Angeles should return to corporate security.

How MSB Protection approaches visiting CEO protection

At MSB Protection, I approach a visiting CEO assignment as a temporary operating system built around one principal.

I do not start with:

“How many bodyguards can we put around the CEO?”

I start with:

Who is the executive?

Why are they here?

What is their exposure?

What is the schedule?

Who controls it?

Where are they arriving?

Who is driving?

Where are they staying?

Which movements are known?

Which parts of the day are likely to change?

What relevant security information already exists?

Who at the company makes decisions?

Then we build the protection around that.

The assignment may integrate:

• executive protection;
• travel security;
• protective driving;
• airport and FBO coordination;
• advance work;
• corporate-security liaison;
• schedule-change control;
• protective intelligence;
• and local contingency planning.

The executive should experience one smooth movement.

Airport.

Vehicle.

Hotel.

Office.

Dinner.

Airport again.

Behind that simple experience is disciplined coordination.

The itinerary is not the mission

This is important.

A protection team can become obsessed with keeping the schedule exactly as written.

The CEOs business is the mission.

The schedule supports it.

If the business requires a change, security adapts unless there is a legitimate reason not to.

The security team should explain risk when a request creates a real problem

If the CEO wants to add a stop that materially changes exposure, say so.

Briefly.

Clearly.

Offer an alternative if possible.

“We can do it. Give us ten minutes to reposition the vehicle.”

Or:

“That entrance is closed. We will use the west side.”

Or, when genuinely necessary:

“I recommend we do not make that stop right now because of this specific issue.”

That is professional advice.

Do not dramatize routine problems

Traffic is not a security crisis.

A delayed driver is not a threat.

A busy lobby is not hostile activity.

A protest several blocks away may or may not affect the movement.

The protection team should maintain perspective.

Corporate leaders need decision support, not fear

A strong executive protector helps the CEO make decisions.

They do not create anxiety to prove their value.

The executive should hear:

what changed;

why it matters;

what security recommends;

and what alternatives exist.

Then continue operating.

Frequently asked questions

Does every CEO visiting Los Angeles need executive protection?

No. Protection should follow actual exposure, not title alone. Public profile, threat history, company issues, itinerary, event participation, location and personal preferences all affect the appropriate posture.

What does Los Angeles executive protection for a visiting CEO include?

Depending on the assignment, it can include airport or FBO coordination, professional transportation, schedule management, advance work, close protection, corporate-security coordination, route monitoring, hotel movements and contingency planning.

Why is itinerary control a security issue?

Because transportation, staffing, advance work and timing all depend on the team knowing where the executive is actually going. Competing or outdated schedules create avoidable exposure and operational confusion.

Who should own the CEO itinerary?

Usually the executive assistant, chief of staff or another clearly designated executive-support function. Security should know which source is authoritative and who can approve material changes.

Should security have access to the CEOs entire calendar?

Not necessarily. Security needs enough information to protect relevant movements. Sensitive business information that does not affect the assignment should remain appropriately restricted.

What should happen when a meeting changes at the last minute?

The change should be communicated through the established channel. Security evaluates whether the new time, location or participants materially alter the movement, then updates transportation and advance information as necessary.

Does every schedule change need a full new advance?

No. A twenty-minute time change at the same office is very different from adding an unfamiliar private residence. The response should match the change.

How should an unknown last-minute meeting location be handled?

Confirm the exact address and meeting contact, understand the arrival and departure environment, verify who expects the executive and determine whether the current protection and transportation plan remains appropriate.

Is LAX-it used for executive-car pickup?

LAX currently says LAX-it handles ride-app and taxi pickups, while limousine and executive-car pickup remains available at the baggage-claim level outer curb.

Why does LAX require specific arrival planning?

LAX serves more than 200,000 guests per day and continues to undergo major landside infrastructure changes. Terminal, pickup and ground-transport procedures should therefore be confirmed for the actual trip rather than assumed from a previous visit.

What is happening with the LAX SkyLink system?

Los Angeles World Airports still described SkyLink as forthcoming in September 2026 as part of the airports broader landside transformation. Current pickup procedures should therefore be checked directly rather than assuming the future system is already in operation.

Is Van Nuys Airport commonly used for noncommercial aviation?

Yes. Los Angeles World Airports describes Van Nuys as one of the world’s busiest general-aviation airports, dedicated to noncommercial aviation, with more than 100 airport businesses and multiple FBOs.

What is an FBO?

A fixed-base operator provides services for private and business aviation such as aircraft handling, fueling, parking and passenger facilities. For executive protection, the specific FBO is the operational arrival point, not merely the airport name.

Should the protection team know which FBO the CEO is using?

Yes. Vehicle positioning, access and passenger handoff can differ among operators.

How should a driver substitution be handled?

Verify the replacement through the established transportation provider or trusted travel coordinator. Do not rely solely on a message from the person claiming to be the new driver.

What vehicle information should the team have?

Driver identity, provider, vehicle make or type, license plate and appropriate contact information should be available to the protection team before pickup.

Should a visiting CEO use ride-share transportation?

That depends on the risk and assignment. A low-exposure executive traveling privately may make different choices from a high-profile CEO on an organized protection detail. The protection model should follow the principal.

Should executive protection use the same route every day?

There is no blanket rule. I prefer reasonable route options and current traffic information rather than artificial variation for its own sake.

What tools can a protection team use for current Los Angeles road conditions?

Caltrans QuickMap provides real-time traffic speeds, CHP incidents, lane and full closures, highway information, message signs and camera views.

Why are hotel departures important?

They can become predictable and can place the principal temporarily in a public or semi-public environment while moving between the controlled hotel and controlled vehicle.

Should an agent wait in the hotel lobby all day?

Not necessarily. Positioning should match the risk, hotel environment and principal preference. Executive protection is not improved simply by making personnel more visible.

Should hotel staff receive the CEOs complete schedule?

No. Provide the information necessary to support the movement or hotel security function and restrict the remainder.

How should private-residence meetings be handled?

Confirm the host, address, expected arrival, access and departure plan. An unfamiliar private residence should generally receive more scrutiny than a known corporate location.

Is corporate offsite security the same as executive protection?

No. Event or offsite security protects the broader environment. The executive protection team remains focused on the CEO and should coordinate with the event-security function rather than assume one replaces the other.

What should happen if the CEO adds an unscheduled restaurant?

Most legitimate spontaneous changes can be handled quickly. Confirm the location, organize the vehicle and arrival, check whether any current security issue changes the decision and continue.

Should security prevent spontaneous stops?

Not without a reason. A protection program that unnecessarily restricts normal executive behavior will eventually lose cooperation.

What information should corporate security provide before the trip?

Relevant current threat information, known persons of concern, recent significant incidents, special event concerns and any other information that materially affects the local protection assignment.

Should the Los Angeles team receive every corporate threat report?

No. Provide what is relevant and actionable for the trip.

How should local security report something unusual back to the company?

Use the established corporate-security liaison or case-reporting path so information from the LA visit becomes part of the principal’s continuing protective picture.

Can a visiting executive subscribe to Los Angeles emergency alerts?

NotifyLA allows users to register multiple contact points and addresses for City of Los Angeles alerts. That can be useful for teams monitoring locations relevant to a visit. Other LA County cities may operate separate systems.

Why does a protection detail need weather information in Los Angeles?

Weather can affect roads, airport operations and movement timing. Los Angeles is currently preparing for the 2026-27 El Niño period, and city emergency guidance recommends anticipating closures and travel delays during significant wet weather.

Should every visiting CEO have a disaster plan?

The level should remain proportionate. A short visit still needs basic continuity for major disruptions such as earthquakes, wildfire, severe weather or airport problems, but the plan does not need to become unnecessarily complicated.

What if the CEO’s flight is delayed for several hours?

Transportation, staffing and hotel coordination should be updated before arrival. Duty hours should also be reviewed so drivers and protectors are not operating excessively fatigued.

Why does fatigue matter in executive protection?

Driving, observation and judgment all degrade when personnel are excessively fatigued. Staffing should reflect the executives actual operating day rather than the original schedule alone.

What should happen if the vehicle breaks down?

The team should move the executive to a safe practical location and activate replacement transportation. A high-end detail should not rely on one vehicle with no contingency.

Does the CEO need to know all contingency routes?

No. The protection team and driver should manage those operational details unless a change materially affects the executive’s schedule.

How visible should CEO protection be?

As visible as the risk requires and no more. Some executives require a substantial protective presence. Others are best supported through discreet personnel, planning and transportation.

Should the protection team control the CEO’s decisions?

No. The team advises on risk and manages protection. The CEO runs their business. When a legitimate security problem exists, the protection lead should explain it clearly and provide workable alternatives where possible.

How early should Los Angeles executive protection be arranged?

Earlier allows better coordination, but professional teams should also be able to support short-notice visits. At minimum, the team needs enough time to receive the itinerary, understand the principal, arrange transportation and identify significant operational issues.

What makes a local Los Angeles executive protection team useful for a visiting CEO?

Local familiarity can improve airport coordination, route decisions, hotel movements, venue planning and adaptation when the itinerary changes. It should complement, not replace, good corporate threat information and executive-support coordination.

How is this different from general travel security?

This article focuses specifically on the operating problem created by a visiting CEO’s rapidly changing Los Angeles business schedule: itinerary authority, transportation handoffs, change control, temporary local-team integration and corporate-security coordination.

Final thoughts: protect the CEOs operating tempo

The visible agent beside the CEO is only a small part of a successful executive protection assignment.

The real work is making sure the movement stays coherent when the day changes.

The plane lands early.

The meeting moves.

The investor adds dinner.

The driver changes.

Traffic closes the route.

The offsite runs long.

The CEO wants to stop somewhere.

The flight home gets pushed.

That is normal executive travel.

A professional protection program should be built for it.

One authoritative itinerary.

Clear authority to change it.

Fast communication.

Verified transportation.

Correct airport and FBO planning.

Real-time route information.

Advance knowledge of important destinations.

Alternatives when something stops working.

Need-to-know information control.

Corporate security feeding relevant intelligence into the local team.

The local team feeding relevant information back.

And a protection lead who understands that the goal is not to force the CEO into the security plan.

The goal is to make the security plan move with the CEO.

That is how I approach Los Angeles executive protection for a visiting corporate leader.

The executive should be able to land, work, meet, travel and leave without spending the entire trip thinking about security.

If we are doing the job properly, the complexity stays behind the scenes.

The CEO experiences a smooth day.

The team maintains the operating picture.

And when the schedule changes, the protection program changes with it.

---

About Michael Braun

Michael Braun is a former Special Unit Operator, former Manager at Gavin de Becker & Associates, and Founder & CEO of MSB Protection, an executive protection and residential security firm serving high-net-worth and ultra-high-net-worth clients.

Braun has built his career at the intersection of specialized protective operations, executive protection, residential security, protective intelligence, and security risk management. His experience spans special-unit operations, leadership within Gavin de Becker & Associates, and the development and oversight of private protection programs within demanding UHNW environments.

He has been recognized by The Top 100 Magazine as a leading CEO in the private security field and is the subject of an upcoming Marquis Who’s Who feature highlighting his leadership and contributions to the profession.

Today, Braun is recognized for his work in executive protection, UHNW estate security, residential protection, protective intelligence, adversarial security assessments, and security auditing throughout Beverly Hills and Southern California.

His work focuses on moving private security beyond simply “providing a body” and toward intelligence-led, risk-based protection programs designed to identify vulnerabilities before an adversary can exploit them.

---

Looking for Executive Protection or Residential Security Services?

If you are a high-net-worth or ultra-high-net-worth individual, family office, estate manager, chief of staff, or executive in Beverly Hills, Los Angeles, Malibu or Southern California, MSB Protection provides executive protection, residential security, 24/7 protection, protective intelligence, medical-readiness planning, and security risk management.

We evaluate the complete security environment, from threat exposure and residential vulnerabilities to personnel, technology, procedures, protective intelligence, and emergency response, and build a program around the risks that actually exist.

Contact us for a confidential consultation or message us at +1 (805) 285-2807.