Executive Assistants · Fundamentals
Compare complex travel options against real constraints
Three ways to get your executive to a Thursday morning board meeting in London. One costs an extra hotel night. One lands two and a half hours before the meeting starts. One is cheapest and hangs on a 55-minute connection. None of them is wrong, and the catch in each is easy to miss at 6 p.m. on a Friday. This guide puts the options side by side so you can see every catch before you book.
What AI is for here, and what it isn't
Travel decisions go wrong in the gaps between facts: a flight that lands at 06:30 local time when the meeting is at 09:00 and the airport is an hour from the office; a connection that works on paper but not with a checked bag; a return flight that leaves before the meeting is likely to end. Each fact is easy. Holding them all in your head at once, across time zones, is where mistakes happen.
AI is good at the holding. Give it the options and the fixed points, and it will convert time zones, calculate buffers, and flag every conflict it finds. It does this consistently, which is more than any of us manage on a busy afternoon.
It can't book anything, it doesn't know current fares or schedules, and it doesn't know your traveler. It doesn't know that your executive will happily take a red-eye but won't take a connection, or that "arrive the night before" is a firm rule for board meetings. Those preferences, the booking and the final choice stay with you.
Write down the fixed points
Before looking at options, list what the trip has to fit around. Each item needs a time, a time zone, and whether it can move.
- Hard commitments: meetings that can't move, with their real start times and locations.
- Soft commitments: calls the traveler can take from anywhere with a connection, but not from a plane.
- Ground time: how long from the airport to the first commitment, and back. Use a realistic figure for the time of day, not the best case.
- Rules: for example, "arrives the evening before any board meeting", "no connections under 90 minutes", "aisle seat", "no red-eyes unless the next morning is free".
- Time zones: every city involved. Note if the trip crosses a daylight saving change, because countries change their clocks on different dates.
Build the comparison
Paste the options exactly as your booking source shows them, with local times and airport codes.
Compare these travel options for one traveler. Use only the flights
and times I give you. Do not suggest other flights.
FIXED POINTS (time, time zone, can it move?):
[list from Step 1]
GROUND TIME: [airport to venue, venue to airport, realistic]
TRAVELER RULES: [list]
OPTIONS (as shown by the booking source, local times):
Option A: [flights]
Option B: [flights]
...
FOR EACH OPTION produce:
1. Every flight leg in local time AND in the traveler's home time zone.
2. Total door-to-door travel time.
3. The buffer before each hard commitment, after ground time.
4. Connection times, and whether bags are checked through.
5. Every conflict with a fixed point or a rule, labelled
CONFLICT (breaks a rule) or RISK (works only if nothing goes wrong).
6. What the traveler is doing during each soft commitment.
Then a table: options as rows; buffer, conflicts, risks and
door-to-door time as columns. Do not recommend an option.
The instruction not to recommend is deliberate. You want the trade-offs laid out, not a winner chosen on criteria the AI has guessed.
Verify every critical time
AI tools do make time zone mistakes, especially across daylight saving changes and overnight flights. Each conversion can go wrong on its own, so one correct line doesn't prove the rest. For executive travel, check every time the trip depends on, independently of the AI:
- Every departure and arrival, against the booking source or confirmation, which shows local times. Convert any you need with a world clock, not by reusing the AI's figure.
- The day of each arrival. Overnight flights land the next day. Check that "Thursday 06:30" isn't really Wednesday.
- Every connection: minutes from arrival to the next departure, against the airline's minimum connection time for that airport, and whether bags are checked through.
- Every buffer: add the ground time to each arrival yourself and compare it with the commitment that follows.
If anything is wrong, correct it in the prompt ("Option B lands Thursday, not Wednesday") and ask for the table again. Don't fix it silently in your head, because other rows may depend on it. Then check the corrected table the same way.
Decide, then book
Now apply what the AI can't know. Which risks does your traveler accept? Is the cheaper fare worth a connection? Would they rather lose an evening at home or arrive tired? If you'd normally ask, send your executive the table and a one-line recommendation of your own. A quick choice between clear options is a better use of their attention than a description of the problem.
Book through your normal channel. Then check the confirmation against the option you chose, line by line: dates, times, airports, names exactly as on the passport, and seat.
Worked example: the London board meeting
Fictional example; flights and times are illustrative. Elena is based in New York and must be at a board meeting in central London on Thursday 11 February 2027, from 09:00 to 13:00. On Wednesday she has a video review from 10:00 to 11:00 New York time, which she can join from anywhere except a plane. Her rules: arrive the evening before a board meeting if possible, aisle seat, connections only if the fare saving is significant. Ground time from Heathrow to the office: allow 90 minutes in the morning peak.
New York is five hours behind London in February. Her assistant, Sam, pastes three outbound options from the travel agency:
- A. Nonstop, departs New York (JFK) Tuesday 18:30, arrives London (LHR) Wednesday 06:30.
- B. Nonstop, departs JFK Wednesday 18:30, arrives LHR Thursday 06:30.
- C. Via Boston on one ticket: JFK Tuesday 16:05 → BOS 17:25; BOS 18:20 → LHR Wednesday 05:55. Lowest fare.
The comparison flags:
| Option | Buffer before board | Conflicts | Risks |
|---|---|---|---|
| A | About 25 hours | None | Arrives 06:30; hotel early check-in needed (or book from Tuesday night). Review call is 15:00–16:00 London time, after a night flight. |
| B | About 60 minutes, before passport control and bags | Breaks "arrive the evening before" | A modest delay or a long passport queue puts the start of the board meeting at risk. |
| C | About 25½ hours | None | 55-minute connection in Boston; a missed connection likely means a later arrival. Leaves the office by about 14:30 Tuesday. |
Sam checks every departure and arrival against the agency's itinerary, the Boston connection, and each buffer, independently of the AI. For example: 18:30 in New York is 23:30 in London; seven hours later is 06:30 Wednesday. Every line holds.
Option B is out: it breaks Elena's rule and puts the board meeting at the mercy of one flight. Between A and C, the fare saving on C doesn't justify the connection for a board trip. Sam books A, adds Tuesday night at the hotel so Elena can go straight to a room, and blocks Wednesday morning in London as rest time.
Record the decision
Trip: [traveler] — [purpose], [dates] Prepared by: [your name]
FIXED POINTS
- [commitment] — [local time, time zone] — can move? [yes/no]
TRAVELER RULES APPLIED
- [rule]
OPTIONS CONSIDERED
Option | Buffer | Conflicts | Risks | Fare (relative)
A | | | |
B | | | |
CHOSEN: [option], because [one line]
Verified independently: every departure, arrival, connection and buffer — by [name], [date]
Booked via: [channel], confirmation [code], on [date]
Time zone notes for the traveler: [e.g., clocks change on ...]
What stays with you: the booking, the preferences only you know, and the call on which risks your executive will accept.