A family office that manages eight figures in assets across four jurisdictions but books private aviation through a single broker contact is operating with a structural blind spot. It is the equivalent of having a sophisticated investment policy statement and no treasury function. The assets are being managed. The movement of the people managing those assets is being improvised.
An aviation protocol is not a contract with a preferred operator. It is a governing document — a set of principles, preferences, and procedures that determines how the principal and their immediate circle travel, under what conditions, with what redundancies, and according to whose authority. Family offices with functioning aviation protocols look, from the outside, like organisations that are very lucky with their travel. Nothing ever goes wrong. Alternatives materialise before problems are announced. Ground transportation is always where it should be. The right aircraft appears for the right trip without apparent effort.
None of this is luck. It is operational design.
A well-constructed aviation protocol addresses six things. First, it establishes a clear hierarchy of trip types — routine, sensitive, and contingency — and assigns different booking and handling procedures to each. A principal flying to close a deal is not managed the same way as a principal flying for leisure. Second, it defines approved operators by region, specifying not just who is preferred but why, and at what point alternatives are acceptable. Third, it establishes FBO preferences, which are rarely neutral choices: FBOs vary dramatically in their discretion, ground handling quality, and the degree to which they attract attention. Fourth, it governs documentation — who holds what, in what form, and what gets retained post-flight. Fifth, it covers security protocols, particularly for travel to jurisdictions with elevated risk profiles. Sixth, and most critically, it designates who has authority to deviate from the protocol, and under what circumstances.
The absence of this framework creates predictable problems. Brokers optimise for what they have available, not for what the principal actually needs. Operators vary in their interpretation of discretion. Handling agents at different FBOs have different standards. Without a protocol, each trip is a fresh negotiation conducted under time pressure — which is the worst possible condition for good decision-making.
The EA who manages a principal’s travel is, in most family office structures, the person absorbing the operational consequences of this absence. They are fielding calls from three different brokers. They are comparing quotes on aircraft they do not have the expertise to properly evaluate. They are making judgment calls about security and discretion that should have been pre-determined by people more senior than them. The protocol does not make the EA’s job easier as a courtesy — it makes the principal’s travel safer and more controlled as a function.
Building an aviation protocol is, in practice, a consulting exercise. It requires someone who understands the principal’s movement patterns, risk profile, jurisdictional complexity, and long-term plans. It requires honest assessment of current arrangements — which often reveals that preferred brokers have significant conflicts of interest, or that habitual FBO choices are not actually optimal. It requires the willingness to formalise what has previously been left to instinct.
Most family offices resist this because it feels like adding process to something that already works. It works, until it doesn’t. The moment it doesn’t — a security incident, a leaked itinerary, an unavailable aircraft at the wrong moment — the cost of the missing protocol becomes immediately and painfully legible.
Build the protocol before you need it. That is the only time it is useful.
