Security for UHNW Family Offices: Guarding the Schedule

Security for UHNW Family Offices: Guarding the Schedule

Security for UHNW family offices starts with the calendar

Security for UHNW family offices is usually discussed in terms of wire controls and cyber hygiene, but the asset that matters for physical protection is far less glamorous: the calendar. The family office knows where the principal will be next Tuesday at 9 a.m., which flight the family is taking to the house in the mountains, which driver is collecting the children, which restaurant has the Friday reservation and which business partner is unhappy about a deal. Anyone who wants to approach a principal in person needs exactly that information.

Three cases from the past two weeks make the point from different directions. In Pennsylvania, federal prosecutors charged a man who allegedly wrote that he had a congressman’s “entire schedule” and knew where he would be “on any given day.” In Visakhapatnam, India, a retired senior tax official was taken from his car on the way to the airport and held while his wife received a call demanding immediate payment. In Hyderabad, a jewellery businessman was abducted on his way to his shop by men police say were posing as officers, and his family paid a ransom before he was released.

Nothing in the reporting suggests that a family office was involved in any of them, and I am not suggesting that anyone failed. I use them because each one turns on information about where a person would be and when. That is the information a family office holds, shares and, too often, leaks without noticing.

In our 2026 guide to high net worth security, I describe payment diversion and principal schedule leaks as one of the gaps that sits between the family office and the protection team. This article goes deeper into that gap. It is about the physical consequences of a known schedule: the route, the airport run, the arrival at a predictable place and the phone call that follows when something has gone wrong.

My focus here is practical. I want a family office to come away with a clear sense of who should see the principal’s movements, how travel and routes should be planned, how to treat a business dispute as a security signal, and what the office should do if it ever receives the call every family dreads.

Security advisor and family office manager review a travel itinerary and route map at a desk at dusk while an SUV waits in the driveway

Key takeaways

  • The calendar is a security asset. Detailed movements should be shared on a need-to-know basis, and the people who hold them should understand why.
  • Interceptions tend to happen on routes that are predictable: the drive to the office, the shop, the school or the airport.
  • A schedule can leak through many ordinary channels, including shared calendars, assistants, vendors, event listings, travel bookings and staff group chats.
  • Business disputes deserve a threat assessment. Two of the cases in this article involved alleged financial or property disputes with people the victims knew.
  • A family office should have a written rule for any urgent payment demand involving a principal: verify the person is safe through an independent channel and involve law enforcement and the security team before money moves.
  • Close protection for UHNW families is planned around known dates and fixed points, where the principal is predictable by necessity.
  • A schedule protocol does not have to make the family office secretive or slow. It needs clear ownership, sensible limits and a direct line to the protection team.

“I have his entire schedule”: the Fitzpatrick case

On October 15, 2026, a 44-year-old man from Perkasie, Pennsylvania, was arrested and charged by indictment with two counts of threatening to assault, murder or kidnap a federal official. According to The Philadelphia Inquirer, the indictment identifies the official as “Congressman B.F.”, a source familiar with the investigation confirmed that this is U.S. Rep. Brian Fitzpatrick, and the congressman confirmed it in a statement the next day thanking the U.S. Capitol Police and prosecutors.

The Inquirer quotes several emails the man allegedly sent. One of them is the reason this case belongs in an article about family offices: “I have his entire schedule for the rest of the summer into fall. I know exactly where and when B.F. will be on any given day.” The same message allegedly continued with a line about making people pay, and added: “And their families too.”

Another email allegedly demanded a $6,000 “stipend” sent to a Cash App account, with another $6,000 expected each month. A third allegedly referred to the next Eagle Scout graduation in threatening terms. The Inquirer notes that Fitzpatrick is an Eagle Scout and celebrates when young people reach that rank. The case was investigated by the U.S. Capitol Police with help from the Bucks County District Attorney’s Office. These are allegations, the man has not been convicted, and the Inquirer reported that it was unclear whether he had a lawyer.

I want to be careful about what this case does and does not show. The reporting does not say whether the man actually had the schedule he claimed, or how he would have obtained it. A claim to know someone’s movements can itself be a pressure tactic. But the structure of the threat is instructive for anyone responsible for high net worth security.

Three elements that show up again and again

The alleged emails combine three things that I see in many threat cases involving wealthy families and public figures.

First, a claim of knowledge about movements. Whether or not it is true, a person who says they know where the principal will be is telling you what they think the vulnerability is.

Second, a payment demand. The amount here was modest, but the pattern of linking money to safety is the same one that appears in extortion and kidnap cases.

Third, an extension to the family. Threats increasingly name spouses, children and relatives, because the family is often less protected and more predictable than the principal.

For security for UHNW family offices, the lesson is direct. If someone claims to have the principal’s schedule, the office should treat that claim as a question to answer: could they? Who has access to the calendar? What is publicly announced? Which events are fixed and widely known? The answers tell the protection team where to focus.

Known events and public commitments

The Eagle Scout reference matters because it points to a category of event that cannot easily be hidden: the public, recurring commitment. Some appearances are public by design: a charity gala, a company meeting, a graduation, a ribbon cutting, a long-standing annual dinner. A principal who supports a cause will be photographed at its events. A family that has attended the same school function every year is predictable to anyone who has watched.

The family office usually knows these commitments months in advance. That makes it the natural place to flag them for the protection team, so that advance work, arrival and departure plans, and coordination with venue security can be done before the date rather than the week of it.

Intercepted on the way to the airport

On Friday evening, October 16, 2026, P Anand Kumar, a retired Indian Revenue Service officer and former audit commissioner in the GST department, was on his way to the airport in Visakhapatnam when a group of people intercepted his car, forced him into their own vehicle and drove away. According to The Times of India, he lived with his family in Hyderabad and had travelled to Visakhapatnam before the abduction.

Police say the kidnappers confined him at a guest house, called his wife, demanded immediate payment and threatened to kill him if the demand was not met. After a complaint was filed, police formed special teams, examined CCTV footage from various locations and analysed his phone’s location data. They traced him to the guest house, rescued him and arrested 10 of the 11 accused within a few hours. The investigation, police say, found that he had been involved in financial transactions with two of the accused and that the kidnapping followed a financial dispute.

Why the airport run is a known window

The airport run is one of the few moments in a travelling principal’s day that is fixed by someone else’s timetable. The flight leaves when it leaves. Anyone who knows the flight, or even the approximate departure, knows the window in which the principal will be on the road, and often the road itself, since there are a limited number of practical routes from a hotel or a business district to an airport.

I do not know how the kidnappers in Visakhapatnam knew when he would be travelling, and the reporting does not say. What the case shows is that a departure for the airport is a moment when a person is in a car, between places, carrying luggage and focused on a deadline. Those are the conditions in which an interception is easier to attempt.

For families who travel often, the airport run is routine. Routine is the problem. The same driver, the same route, the same terminal, the same time before departure: each of these makes the window easier to predict for someone who has been watching or who has been told.

What the rescue shows about response

The speed of the police response in Visakhapatnam deserves attention. A complaint led to special teams, CCTV review and phone location analysis, and the victim was found within hours. That is a reminder that the first hours matter and that the information a family can give police early, such as the planned route, the vehicle, the expected arrival time and any known disputes, can shape the outcome.

A family office that holds the travel plan is in the position to supply that information quickly. It should be able to tell police and the protection team exactly when the principal left, which car, which driver, which route was planned and who knew about the trip. If that information is scattered across several inboxes and personal phones, minutes are lost.

Fake police on the route to work

On October 17, 2026, Hyderabad police announced the arrest of nine people over the October 5 abduction of K. Srinivas Rao, a 53-year-old jewellery businessman. According to Telangana Today, he went missing while on his way to his shop in Ramanthapur and was abducted near the Gollapaka flyover.

A deputy commissioner of police said that the kidnappers reportedly impersonated police personnel, blindfolded him and confined him at an undisclosed location, and threatened to harm him unless his family paid. The gang demanded Rs 15 crore and released him after the family paid Rs 1.30 crore. Police seized Rs 1.07 crore in cash along with gold, silver, five vehicles and nine mobile phones. Police say the kidnapping grew out of a dispute over a real estate venture, that the alleged mastermind conspired with others in August, and that the gang used vehicles with fake number plates and changed vehicles frequently. Two suspects, including an alleged co-conspirator, had not been caught.

The daily commute is a schedule too

The Hyderabad case has two features that matter for any family’s planning. The first is the route. A businessman going to his own shop follows the same road at roughly the same time on many days. Nobody needs access to a calendar to learn that. A few mornings of observation are enough.

The second is the impersonation of authority. A car that appears to be a police stop is one of the few situations in which a driver is expected to pull over and cooperate. It is the roadside version of the false police officer at the front door, and it exploits the same instinct to comply.

The police account also describes planning that began in August, about two months before the abduction. That is a long time for a group to observe, prepare vehicles and choose a location. It is also a long time in which a protection team, if one were in place, might notice repeated vehicles, unusual interest in the shop or a pattern of people watching the route.

What these three cases have in common

Each case involves a different country, a different motive and a different method. One is an alleged threat by email, one an interception on the way to an airport, one an abduction on a daily commute. What they share is knowledge of where a person would be. In two of them, police say the people responsible were connected to the victims through financial or property dealings.

For family office high net worth individuals security, this is where the physical and administrative sides of the office meet. The office controls the calendar, books the travel, employs or contracts the drivers and often handles the disputes. Those four functions together describe much of what an attacker needs to plan an approach. The next part of this article looks at how schedules leak in practice and what a family office can do about fixed routes, airport runs and disputes before they become incidents.

How schedules leak

When I review a family office, I ask a simple question early on: if I wanted to know where the principal will be next Thursday afternoon, how many people could I ask, and how many systems could I look in? The answer is usually larger than the office expects.

Schedules rarely leak through a single dramatic breach. They leak through ordinary convenience. Below are the channels I see repeatedly. None of them is wrong in itself. Each becomes a risk when nobody has decided who should have access and why.

Shared calendars and too many viewers

Many family offices run the principal’s diary in a shared calendar so that assistants, the chief of staff, the house manager, drivers and sometimes outside advisers can all see it. Over time, the list of people with access grows. Former employees are not always removed. A consultant who needed visibility for one project keeps it for years. Some entries are copied into personal phones to make planning easier.

A calendar entry that reads “Dinner, 8 p.m., with partner, at the restaurant on the corner of two named streets, car at 7:40” is a complete operational plan for anyone who wants to be waiting outside. I would rather the full detail sit with the few people who need it, while others see a less specific version, such as “Evening engagement.”

Assistants, vendors and the people around the principal

Executive assistants, household managers, travel agents, aviation coordinators, restaurant hosts, stylists, trainers and event planners all need fragments of the schedule to do their jobs. Each fragment is harmless on its own. Together they describe the week.

The issue is not trust in these people. It is that they are often asked questions by others, sometimes by someone posing as a colleague or a vendor. A caller who says “I am from the restaurant, just confirming Friday for the family of four at eight” will often get a confirmation. The person answering is trying to be helpful, which is exactly what makes the technique work.

Event listings, social media and the press

Charity events publish their honorees. Companies announce speakers. Schools post the dates of ceremonies and games. Social media accounts of friends, staff, venues and the family themselves show where people are, sometimes in real time. Even a delayed post can establish a pattern: the same ski week every year, the same summer island, the same Sunday brunch.

High net worth security services depend on knowing what is public. A protection team should review upcoming public commitments with the family office and decide which ones need advance work, which details can be withheld until afterward and which posts should wait until the family has left.

Travel bookings and aviation details

Flight and hotel bookings move through many hands. Private aviation involves operators, handlers, caterers and ground transport. Commercial bookings involve agents, loyalty programs and confirmation emails that are forwarded around. Hotel staff learn names and room numbers. Car services learn pick-up times and addresses.

I am not suggesting that any of these partners is careless. I am suggesting that each additional party who knows the itinerary is one more place where it can be overheard, forwarded or requested by someone who should not have it. A family office can reduce this without disruption by booking travel through a small number of trusted channels, limiting who receives full itineraries and avoiding the habit of forwarding confirmations to large groups.

Staff group chats

Household staff and drivers often coordinate through group chats, which makes those chats part of private security for high net worth family households whether anyone planned it or not. These chats are efficient and, in many households, essential. They can also become a running log of the family’s movements: “Leaving the house in 10,” “Kids to practice at 4,” “Mr. and Mrs. back from the airport at 6.” If a phone is lost, a former employee is still in the group, or a screenshot is shared, the log goes with it.

The fix is simple. Keep operational chats small, remove people promptly when roles change and avoid naming places and times in more detail than the task requires.

What a leak looks like in practice

The cases in the first part of this article illustrate the outcome rather than the mechanism. The man in Pennsylvania claimed to have a congressman’s whole schedule. The kidnappers in Visakhapatnam struck on the way to the airport. The gang in Hyderabad, police say, planned for about two months and struck on the route to work. Whatever the source of their information, each depended on knowing a time and a place.

That is why I treat schedule control as part of physical protection rather than an administrative courtesy. Security for UHNW family offices is, at its core, about controlling the information that would let someone be in the right place at the right time to cause harm.

Fixed routes and the airport run

Once a schedule is known, the route is where it becomes dangerous. A principal at a meeting is inside a building, often with reception staff, cameras and other people. A principal at home is covered by home security for high net worth individuals: a perimeter, a gate and, ideally, a residential team. A principal in a car is between those protective layers, and the route is where interceptions tend to happen.

Daily routes

The Hyderabad case involved a businessman on his way to his own shop. Daily routes like that are among the hardest to protect, because they are repeated so often that nobody thinks about them. The drive to the office, the school run, the walk to the gym, the regular coffee stop: each happens at about the same time along about the same path.

I do not ask families to live unpredictably for its own sake. That is exhausting and rarely sustainable. I ask them to identify the routes that are both fixed and exposed and to introduce variation where it matters. That might mean alternating between two or three routes, varying departure times within a reasonable window, using different entrances at the office, or changing the vehicle occasionally. Small changes make observation harder and planning less reliable for anyone watching.

Route planning should also identify the places where a car is forced to slow or stop: a narrow street, a long traffic light, a railway crossing, a flyover approach, a gate that opens slowly. Those are the points where a vehicle can be blocked. A driver who knows them can keep space ahead, avoid being boxed in and choose a different path when something looks wrong.

The airport run

The airport run deserves its own plan, because the timing is fixed by the flight. I would want the family office and the protection team to agree on a few basics for every departure:

  • Who knows the departure time, and is that list as short as it can be?
  • Which route will be used, and is there an alternate if the primary route is blocked or something looks wrong?
  • Is the driver briefed on what to do if a vehicle tries to stop the car, including a vehicle that appears to be police?
  • Does someone outside the car know when the principal left, the vehicle details and the expected arrival time at the terminal or FBO?
  • Who will confirm arrival, and what happens if the confirmation does not come?

These are not complicated questions. They become difficult when they are asked for the first time in the hour before departure.

For international travel, the questions widen. The protection team should understand local conditions, recent incidents, the reputation of local drivers and ground transport, and the practical routes between the airport, the hotel and the places the principal will visit. That is the work of travel security, and it starts weeks before the trip, not on landing.

What to do when stopped by someone claiming to be police

The Hyderabad report says the kidnappers impersonated police. A driver confronted by what appears to be a police stop is in a hard position: they must not obstruct real officers, and they must not hand a principal to criminals.

General guidance I give to drivers and families is cautious and should be adapted to local law and conditions. If it is safe to do so, stay in the vehicle with the doors locked, keep the engine running, and call the local emergency number to confirm that a stop is genuine. Look for the signs that a stop is consistent with local practice, such as marked vehicles and uniformed officers. If something does not fit, such as unmarked cars blocking front and rear in a quiet place or people in plain clothes demanding that the passenger step out, the driver should report the situation immediately and look for a safe, lawful way to move to a populated, well-lit area or a police station. The protection team should agree on these steps with the driver in advance, not leave them to judgment under pressure.

Business disputes as a threat signal

In two of the three cases in this article, police say the people responsible had financial or property dealings with the victim. In Visakhapatnam, police say the kidnapping followed a financial dispute with people the victim had done business with. In Hyderabad, police say it grew out of a dispute over a real estate venture.

That pattern is worth taking seriously. Family offices handle investments, partnerships, property deals, loans, employment matters and litigation. Many of these end routinely. A few leave someone angry, financially desperate or convinced they have been wronged. Those people often already know a great deal about the principal: where they live, where they work, who their family members are and how they travel.

Bringing disputes to the protection team

I encourage family offices to create a simple, confidential way to tell the protection team when a dispute has become personal. That does not mean sharing legal strategy or confidential terms. It means a short note: who the person is, what the dispute is about in general terms, whether there have been threatening statements or unusual contact, and whether the person knows the family’s addresses or routines.

The protection team can then make a proportionate assessment. Often no change is needed. Sometimes the right step is to vary routes for a period, brief the residential team on a name and a vehicle, or review who has access to the principal’s schedule. Occasionally, the assessment points to close protection for a defined period, for example around a court date or the closing of a contentious deal.

Signs that deserve attention

Without turning every disagreement into a security event, there are some signs that should prompt a conversation with the protection team:

  • Statements that mention the principal’s family, home or movements.
  • Demands for money linked to threats or to “consequences.”
  • Unexpected visits to the office, the home or places the principal frequents.
  • Contact with staff, drivers or vendors asking about the principal’s schedule.
  • Sudden changes in the other party’s circumstances, such as financial collapse, that may increase desperation.
  • Any indication that the person has recruited others or is talking about doing so.

The point is not to predict who will act. It is to make sure that the people responsible for protection know enough to notice if a dispute starts to move from words toward behavior.

Family office high net worth individuals security: payment demands and the urgent call

Payment fraud is usually treated as a finance problem, and often it is. I raise it here only as a lead-in to the physical scenario that every family office should plan for: a call or message saying that a principal or family member is being held, and that money must be paid immediately.

In the Visakhapatnam case, police say the kidnappers called the victim’s wife and demanded immediate payment. In Hyderabad, the family paid part of the ransom demand before the businessman was released. In Pennsylvania, the alleged emails linked a monthly payment demand to threats. The details differ, but each case shows money being used as a lever against a person’s safety.

Real abductions and false ones

A family office may receive two very different kinds of urgent call. One is a real abduction. The other is a false one, where someone claims to be holding a relative who is in fact safe, relying on panic and the difficulty of reaching that person quickly. Both arrive with the same pressure: pay now, tell no one.

The response to both begins in the same way. Before any money moves, the office must try to confirm the person’s safety through an independent channel. That means calling the family member directly, calling the driver or protection officer with them, checking with the school or the place they were expected to be, or using an agreed duress or check-in procedure. In a false-abduction call, that check often resolves the situation within minutes. In a real one, it establishes facts that police and the protection team will need.

A written rule for the urgent call

I recommend that every family office has a short written rule for urgent payment demands involving a principal or family member. It should state, at a minimum:

  • Who in the office receives and handles such a call, and who is informed immediately.
  • How to verify the safety of the person named, including through drivers, protection officers and agreed check-in procedures.
  • That the protection team and law enforcement are contacted before any payment decision is made, unless doing so would put someone in immediate danger and the family’s advisers decide otherwise.
  • That no single person, however senior, can authorize a ransom or emergency payment alone.
  • How the call is documented: the time, the number, the exact words, any demands and any background noise.

This rule sits alongside the financial controls that family offices already use for wire transfers and payment changes. Those controls are the subject of other articles, including our article on authority control in family offices. The purpose here is narrower: to make sure that when the call is about a person rather than an invoice, the office knows to treat it as a physical security incident first.

Duress and check-in procedures

Families who travel with protection, or whose members have predictable routines, benefit from simple check-in procedures. A protection officer confirms arrival at each planned stop. A teenager traveling with friends sends a check-in at agreed times. A principal driving alone shares their route with the office for the duration of the trip.

A duress procedure goes one step further. It gives the family a discreet way to signal that they are not safe, such as an agreed word or phrase, without alerting anyone nearby. Duress procedures must be simple enough to remember under stress and should be reviewed with the family periodically. They are not a substitute for protection, but they give the office a way to tell the difference between a family member who is late and one who is in trouble.

Personal security for high networth individuals while travelling

Travel compresses all of the risks described so far. The schedule is fixed by flights and meetings. The routes are unfamiliar. The principal relies on drivers, hotels and hosts they may not know. And the family office, which normally holds the calendar at home, now shares it with a chain of partners abroad.

Personal security for high networth individuals while travelling begins with the same principle as at home: limit who knows the detailed plan, and make sure the people who do know it are the ones responsible for protecting it. In practice, that means a few habits.

Plan the itinerary with the protection team, not around it

Too often the protection team receives the itinerary after it has been booked and shared. By then, flight times, hotels and car services are fixed, and confirmations have gone to many inboxes. I would rather the protection team be involved from the start, so that choices about arrival times, hotel locations, ground transport and meeting venues reflect security as well as convenience.

Use vetted ground transport

The Visakhapatnam case began with an interception on the road. For travel, ground transport deserves particular attention, because it is the part of a trip where the principal is between protected places for the longest stretch. It should be arranged through a provider the protection team has vetted or through the team itself. Drivers should be briefed on the route, alternates, check-in procedures and what to do if a vehicle tries to stop them. The principal should know the driver’s name and vehicle in advance and should not get into a car that does not match. I have covered the moment at the car door itself in a separate article on close protection for UHNW families and kidnap risk; here the concern is the road between the doors.

Keep the itinerary small

The full itinerary, with times, addresses and flight numbers, should go to a short list. Others should receive what they need for their part. A host needs to know when to expect the guest, not which terminal the principal departs from. A hotel needs the arrival date, not the onward plan.

Post after, not during

Family members and staff should agree not to post locations in real time. A photograph from a hotel terrace can wait until the family has checked out. It is a simple measure and an easy one to forget.

Know the local picture

Every destination has its own patterns of crime and risk. Some places have a known problem with express kidnappings, where a victim is taken to withdraw cash. Others have problems with criminals posing as police, or with robberies targeting people leaving airports or luxury hotels. The protection team should brief the family on the relevant patterns before departure, based on current reporting and local contacts, so that the advice is specific rather than generic.

Close protection for UHNW families on known dates

Some dates cannot be hidden. A principal who chairs a foundation will attend its annual event. A family with children in school will be at graduation. A business leader will speak at the shareholder meeting. A public figure will appear where they have been announced. In the Pennsylvania case, the alleged emails referred to an Eagle Scout graduation, an example of an event tied to a person’s known commitments.

Close protection for UHNW families is often especially valuable on these known dates, because they are the times when the family is predictable by necessity. I would put it this way: if the date is public and the venue is fixed, the planning has to be stronger, because concealment is no longer an option.

Advance work for fixed events

For a known event, the protection team should visit or study the venue in advance, identify arrival and departure points, understand the venue’s own security arrangements, agree on where the vehicle will wait and plan the route to and from the event, including an alternate. The team should also know who else will be there, whether there has been any public controversy around the event and whether any person of concern is likely to attend.

The family office plays a central role here. It knows the invitations, the RSVP lists, the seating plans and the hosts. It can tell the protection team which events are fixed months ahead and which details have been published.

Arrivals and departures

Arrivals and departures at known events are the moments when the principal is visible, outdoors and close to people they do not know. The protection team should time the arrival to limit waiting outside, use an entrance that is controlled, and stage the vehicle so that departure is quick. For private security for high net worth family members, the plan should include where children will be and who is responsible for them throughout.

Coordinating with venue security and police

Many venues have their own security. Some events involve local police. The protection team should make contact with both before the date, share what is appropriate about the family’s attendance and agree on how to communicate during the event. A family office that is respected by venue operators and local agencies, and that has a clear point of contact, makes this coordination easier.

Good executive protection is quiet on days like these. Guests should rarely notice it. The work has been done in advance, and the team is focused on the moments that matter.

A schedule protocol for the family office

Everything in this article comes back to a practical question: what should the family office actually do? Below is the protocol I recommend as a starting point. It should be adapted to the size of the office, the family’s profile and the threats they face.

1. Assign ownership of the calendar

One person should own the principal’s calendar and decide who sees what. That person should know who has access today, should review access regularly and should remove people promptly when roles change.

2. Tier the information

Not everyone needs the same level of detail. A simple tiering works well:

  • Full detail, including times, addresses and routes, for the few people directly responsible for the principal’s movements and protection.
  • Partial detail, such as “Morning meeting, downtown,” for staff who need to plan around the principal.
  • General availability, such as “Unavailable Tuesday afternoon,” for everyone else.

3. Arrange travel through protocols

Travel should be booked through a small number of trusted channels. Full itineraries should go to the short list. Confirmations should not be forwarded to large groups. The protection team should be involved before bookings are final.

4. Vary fixed routes

Identify the routes that are both regular and exposed, such as the drive to the office, the school run and the airport run, and introduce reasonable variation in routes, timing and entrances. Brief drivers on choke points and on what to do if a vehicle tries to stop them.

5. Flag known dates early

Keep a forward list of fixed public commitments and share it with the protection team months in advance, so that advance work can be planned rather than improvised.

6. Report disputes

Create a confidential way to tell the protection team when a business or personal dispute has become personal, especially when there are threats, payment demands, unexpected visits or questions about the principal’s schedule.

7. Write the urgent-call rule

Adopt a written rule for any urgent payment demand involving a family member: verify safety independently, involve the protection team and law enforcement, require more than one person to authorize any payment and document everything.

8. Agree check-in and duress procedures

Set simple check-in procedures for travel and for family members with predictable routines, and agree a discreet duress signal. Review them with the family periodically.

9. Know your police contacts

Identify in advance who the office would call at local police, and, where relevant, at federal agencies or police in the countries the family visits. In Visakhapatnam, police used CCTV and phone location data to find the victim within hours. A family office that can give police accurate information quickly helps that kind of response.

10. Review after every incident and every change

Review the protocol after any incident, after staff changes and when the family’s profile or routines change significantly. A protocol that is never updated slowly drifts away from how the family actually lives.

Bringing the calendar into the security plan

The cases in this article took place in Pennsylvania, Visakhapatnam and Hyderabad. They involved an alleged email threat, an interception on the way to an airport and an abduction on the way to work. In each, the people responsible relied on knowing where a person would be. In two, police say they were connected to the victim through money or property.

Security for UHNW family offices is not only about protecting accounts and data. It is also about protecting the information that lets someone stand in the right place at the right time: the calendar, the itinerary, the route and the list of people who know them. The family office holds that information. It is therefore in a strong position to reduce risk, by limiting access, planning routes and travel with the protection team, treating disputes as signals and knowing exactly what to do when an urgent call comes.

At MSB Protection, we have in-house research and development to counter threats to UHNW clients, and part of that work concerns how information about a principal’s movements is handled between the family office, drivers and protection personnel. The aim is simple: the people who need the schedule have it, and fewer people who do not need it can see it.

For families evaluating providers, I suggest asking how a team handles the schedule. Recommended HNW security teams should be able to explain who on their side sees the principal’s movements, how they plan routes and the airport run, how they coordinate with the family office and how they respond to a reported abduction or urgent payment demand. High net worth security services that cannot answer those questions clearly are focused on the wrong layer.

These measures also connect with protection at home. Home security for high net worth individuals and private security for high net worth family members both depend on the same discipline: knowing who is expected, where and when, and noticing when that changes. If you are reviewing how your office handles the principal’s movements, our 2026 framework is a good place to start: our 2026 guide to high net worth security sets out how these pieces fit together, and our travel security and executive protection teams can help you put a schedule protocol in place.

Frequently asked questions

What is security for UHNW family offices?

Security for UHNW family offices covers the measures a family office takes to protect the principal and family members, including physical protection that depends on information the office holds. That includes control of the calendar and travel bookings, route planning, coordination with residential and close protection teams, a process for reporting disputes and threats, and a written plan for urgent payment demands involving a family member.

How do recommended HNW security teams protect a principal schedule?

Recommended HNW security teams limit who sees detailed movements, plan routes and alternates with drivers, get involved in travel before bookings are final, do advance work for known events and coordinate with the family office through a single point of contact. They can explain these steps clearly and in writing.

Why are routes to the airport a security concern?

The departure time is fixed by the flight, so anyone who knows the flight knows roughly when the principal will be on the road, and there are a limited number of practical routes. A plan for the airport run should cover who knows the time, the route and an alternate, driver briefing, and someone outside the car who confirms arrival.

Should a family office tell its security team about business disputes?

Yes, in general terms, when a dispute becomes personal. A short confidential note about the person, the nature of the dispute and any threats, demands or unusual contact allows the protection team to decide whether any change is needed. Often no change is needed, but the team can only assess what it knows about.

What should family office high net worth individuals security do if a ransom call comes in?

Family office high net worth individuals security should treat it as a physical security incident first. Try to confirm the family member’s safety through an independent channel, contact the protection team and law enforcement before any payment decision, require more than one person to authorize any payment and document the call in detail.

Sources


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.

Loading comments...