Coordinating travel between principals and planners

How the person who flies and the people who plan for them share one flight in FlightWiseOS: roles, visibility, change requests, and notifications.

The short answer

In FlightWiseOS, every flight names a principal, the person the trip is for, and can name a planner, the person who coordinates it. Both work on the same flight, both can approve decisions, and each one chooses which updates reach their phone and inbox. The planner does the coordinating. The principal follows along and steps in when a decision is theirs to make.

The situation

A private flight usually involves at least two people on the client side. One of them flies. The other requests the trip, collects quotes, adds passengers, orders catering, and books the car.

Without one system, the planner becomes the relay. A time change arrives by email from one provider and by text from another. The planner forwards it to the principal, then to the driver, then to the other passengers. The principal asks “what time are we leaving?” and the answer depends on which message is newest. If the planner is out for the day, the details sit in an inbox nobody else can open.

How it works in FlightWiseOS

1. Give each person a flight role

An account Admin adds the people who will use the account. A new user gets a welcome email and signs in with an email code. Each person gets a flight role:

  • Principal. An authorized traveler who can request, manage, and make travel decisions.
  • Planner. Someone who coordinates and makes travel decisions on behalf of principals.
  • Billing. Someone who works with invoices, statements, receipts, and travel spend.

A person can hold more than one role. An executive assistant who also handles invoices can be a Planner and a Billing contact.

2. Name the principal and planner on every flight

When you Start a Flight, you choose the principal and, if there is one, the planner. A principal is required before a request can be sent. The principal list shows people with the Principal role, and the planner list shows people with the Planner role.

A principal who books their own travel simply leaves the planner empty.

3. Decide who hears about what

Before you send the request, you see what each person will be notified about. Each type of update has a switch for the iPhone app and, where an email exists, a switch for email:

  • Quote ready or updated
  • Booking confirmed
  • Itinerary and tail changes
  • Services confirmed, such as catering or ground transportation
  • Departure time changed
  • Date or route changed
  • Flight cancellation confirmed

Booking Confirmed always stays on. Everything else is a choice.

4. Work the flight together

Once the flight is booked, both people open the same flight. Either one can add passengers, order catering, arrange a car service or rental car, ask for a new departure time, or request a route change. Requests go to the FlightWise Flight Desk, which reviews each change and confirms it before anything is altered. When the change is confirmed, the people on the flight are notified.

Every update for a flight also lands in that flight’s activity feed and in the notifications panel on desktop. If someone has switched off a push or an email, the update is still there when they open the flight.

See how flight updates reach the Principal and Planner on desktop and iPhone.

5. Change the people when the plan changes

If a different assistant takes over a trip, change the planner on the upcoming flight. The new planner picks up the flight with its full details and activity in place.

Who sees what

Visibility comes from the app role each person holds on the account. See Account structure, permissions, and sharing for the full picture.

PersonWhat they seeWhat they typically do
AdminEvery flight, quote, and record on the accountSets up users, books and manages any flight
User who is a plannerThe flights and quotes where they are the planner or the principalRequests flights, manages passengers and services, approves decisions
User who is a principalThe flights and quotes where they are the principal or the plannerFollows the itinerary, approves decisions, requests changes
Passenger with an itinerary linkThat one flight’s itineraryReads the trip details and manages their part of the trip

Passengers do not need an account. From any upcoming flight you can send the itinerary as a guest link by email or text.

How the principal follows along on iPhone

The FlightWiseOS iPhone app shows the same flight the planner sees on desktop. The principal opens it to check the route, times, aircraft, passengers, and departure details. Push notifications arrive for the updates they have switched on, such as a confirmed booking or a tail change.

A principal can also act from the phone: approve a decision, start a request, or ask for a change. Because both apps share one record, a change the planner makes at a desk is what the principal sees on the phone.

Getting more from it

  • Set each person’s notification defaults once. Every user has default notification settings on their profile. New flights start from those defaults, so a principal who only wants confirmations and changes does not have to say so each trip.
  • Adjust a single flight when it matters. For a complex or last-minute trip, turn more updates on for that flight only. The flight keeps its own settings and the person’s defaults stay as they were.
  • Always fill the planner seat when someone is coordinating. The planner seat is what sends that person the flight’s notifications and, for a User, what puts the flight in their list.
  • Give covering assistants Admin access. An Admin sees every flight on the account, so a colleague can step in on a trip they did not set up.
  • Send the itinerary link to passengers. It saves the planner from retyping details into an email, and the link always opens the current itinerary.
  • Add the flight to the calendar. From the flight, the trip can be added to Apple Calendar or Google Calendar.

Where this fits

Principals and planners are one part of how a team shares travel. For examples across assistants, executives, finance, and leadership, see How teams use FlightWiseOS. For the details each flight carries, see Keeping itineraries, passengers, and flight records organized. For the wider feature set, see Book & Manage Flights.

Frequently asked questions

How do I associate each private flight with a specific executive?

Every flight request in FlightWiseOS names a principal, the person the trip is for. You pick the principal from your account's users when you start the flight, and you can change the principal or planner on an upcoming flight later.

How can multiple assistants coordinate travel for the same executive?

Each flight names one planner, who can approve decisions and receives that flight's notifications. Other assistants with Admin access to the account see the same flight and can manage it, and the planner on an upcoming flight can be changed when coverage shifts.

How can executives view upcoming flights without managing bookings?

A principal signs in on desktop or iPhone and sees their upcoming flights, itineraries, and updates. The planner handles requests, passengers, and services on the same flight, so the principal can follow along without doing the work.

Can executives and assistants have different permissions?

Yes. Each person has a flight role, such as Principal, Planner, or Billing, and an app role of Admin or User. Admins see the whole account, and Users see the flights where they are the principal or the planner.

Can a principal and a planner get different notifications for the same flight?

Yes. Each person has their own notification settings, with a switch for the iPhone app and for email on each type of update. The settings can also be adjusted for a single flight without changing that person's defaults.

See FlightWiseOS with your own flying.

Request Demo Take the feature tour

Search every guide, section, and question. Try “jet card” or “safety ratings”.