How to plan a multi-leg private jet trip with your broker

Build a leg matrix before requesting options

Write one row for each flight movement. Include the date, origin, destination, passenger count and the timing constraint. Add an owner for any unresolved detail. If you are still choosing a city or airport, show that uncertainty rather than hiding it behind a placeholder that could be mistaken for a decision.

Differentiate the flight from the event it supports. A meeting start time belongs in the brief as a constraint, while a proposed landing time is an arrangement for the broker and operator to confirm. The ground journey between those points also needs an owner.

Leg / date:
Origin and destination:
Passengers on this leg:
Required event arrival or preferred departure:
Time basis:
Ground transfer owner:
Overnight or waiting requirement to discuss:
Flexible items:
Open decision, owner and due date:

Track passengers and services by leg

Do not assume the same people travel on every movement. Record joins, departures and different return arrangements explicitly. A passenger who leaves the party after the second stop should not automatically remain on later passenger lists.

Apply the same discipline to luggage, catering and transport. Equipment may travel with the group for one leg and be collected separately later. A return transfer may have a different owner from the outbound transfer. Ask the broker to confirm which details need operator or service-provider acknowledgement.

• Who is traveling on each leg?
• Which service requirements change between legs?
• Which arrival feeds a meeting, transfer or separate flight?
• Who owns each overnight, pickup and onward arrangement?

Review the effect of each revision

When a time or airport changes, review the connected movements rather than editing only that line. Ask the broker which later legs need reconfirmation. Aircraft availability, crew and operational feasibility are for the broker and operator to resolve; a planner should not infer them from an unchanged screen.

Send the broker a consolidated revision with the affected legs identified. If multiple assistants contribute, designate one person to approve the updated brief. Preserve requested and confirmed states so colleagues do not tell travelers that a proposed schedule is final.

Walk the whole journey once before travel

Read the trip from the traveler’s perspective: leaving the first pickup point, finding the departure location, arriving for the event, moving to the next stop and returning home. Each handoff should have current information and a contact route.

Ask your broker to show how the legs appear in WingStack and how planners and travelers access them. Use the same trip in a joint walkthrough so the team can test a realistic change. A successful plan lets a backup assistant identify the current arrangement and the next unresolved decision without reconstructing the history from email.