Private jet booking checklist for executive assistants: run the mission like ops
A private jet booking checklist for executive assistants is not the same document as a first-time flyer’s “what to expect at the FBO” orientation. Assistants already know principals are busy. What they need is a repeatable brief that survives multi-city strings, passport drama, approver lag, and passenger churn—without waking the CEO for trivia or surprising the aviation desk at midnight.
This LUKS Aviation checklist is built for EAs and travel coordinators. It deliberately differs from our passenger-facing first-time private jet flight checklist. Use it with book a private jet, corporate shuttle thinking, and charter in Turkey.
Contents
- Your role vs the passenger checklist
- Multi-city corporate trips
- Passports and identity data
- Hard deadlines and buffers
- Bags, catering, and cabin preferences
- Ground transport and hotels
- Privacy and communications
- Passenger and schedule changes
- Approvers and cost centers
- Plan B
- Copyable brief template
- Common mistakes
- Frequently asked questions
- Conclusion
- Sources and official references
Your role vs the passenger checklist
The first-time flyer checklist teaches arrival timing, cabin etiquette, and calm expectations. Your checklist owns the file: who flies, who pays, which clock is sacred, which city is flexible, and which vendor is waiting on a passport scan. If you only forward a CEO voice note saying “jet to Geneva Thursday,” you have transferred chaos, not a brief.
Multi-city corporate trips
Multi-city strings fail when each city is briefed as a separate surprise. Build one itinerary spine:
- City order and airport codes if known
- Which legs are hard vs soft
- Which meetings create the critical path
- Whether the aircraft should wait, swap, or release
- Whether local ground teams change by city
Tell aviation about the whole spine in message one. Mid-string inventions are how crew duty collapses.
Passports and identity data
Collect passport scans early—especially for mixed-nationality boards. Flag dual nationals and which document will be presented. Keep a private secure folder; do not paste passport numbers into oversized email threads. Entry rules are nationality-specific; point legal/mobility teams to official government sources rather than asking the charter desk to invent visa advice. For Türkiye aviation regulatory context, SHGM is a starting reference; immigration remains a government matter for each destination.
Hard deadlines and buffers
| Clock type | EA action |
|---|---|
| Hard meeting start | State local time + required arrival buffer |
| Board photo / ceremony | Treat like a hard start; build dress buffer |
| Soft preference | Label it soft so ops can trade for aircraft options |
| Latest wheels-up | Needed when the principal is leaving another event |
Assistants create value by separating sacred clocks from preferences. Everything-is-hard is how options disappear.
Bags, catering, and cabin preferences
Send a baggage outline before aircraft lock—volume surprises change category. Catering should list allergies, religious constraints, and whether the cabin is a working lunch or a rest sector. Wi‑Fi is a preference that may constrain airframes; never promise the principal a specific call unless ops confirmed the equipment. For bag discipline detail, see pricing factors only as cost context and keep the operational bag list in the brief (a dedicated baggage guide in this cluster expands the topic).
Ground transport and hotels
Aviation arrives at airports; principals live at addresses. Include:
- Exact drop-off and pick-up pins
- Whether cars must be anonymous or branded
- Hotel confirmation numbers if the same vendor stack is coordinated
- Who greets at each ramp
Unclear ground plans create the false impression that “the flight was late” when the curb was the problem.
Privacy and communications
Limit passenger-name distribution. Use a need-to-know list for deal teams. Keep a single WhatsApp or email thread with the aviation coordinator—parallel cousins and board members creating contradictory instructions is a classic EA failure mode you can prevent with polite process.
Passenger and schedule changes
Assume churn. Build a rule with the principal: who can add a passenger after quote, and until when. Every late add needs passport data and bag notes. Schedule slips should trigger Plan B automatically rather than a panic rewrite.
Approvers and cost centers
Know the approver before you request the aircraft. Include invoice entity, PO if required, and who can say yes to an upgauge. Nothing burns broker goodwill like a perfect ops brief with no paying authority.
Plan B
- Acceptable later departure window
- Alternate airport on the Istanbul side if relevant (IST vs SAW)
- Overnight vs forced late return
- Commercial fallback only if the principal explicitly accepts it—and still tell aviation if you cancel
For true last-minute corporate moves, keep urgent booking guidance handy—but urgent still needs a brief.
Copyable brief template
Copy, fill, send once:
- Principal / EA contacts: names, phones, decision hours
- Itinerary spine: cities, dates, airport preferences, wait/release notes
- Hard clocks: meeting starts / latest arrivals (local times)
- Passengers: full names, nationalities, passport status, dual-national notes
- Bags: counts/types; oversized/sports/fragile flags
- Cabin: work vs rest; Wi‑Fi preference; catering constraints
- Ground: addresses, car style, greeters
- Hotels: if relevant to the same day
- Approver / billing: entity, PO, approval limit
- Privacy: who may know passenger names
- Plan B: flexible window + alternate airport + overnight tolerance
- Open questions: visas pending, plus-one maybe, press sensitivity
Common mistakes
- Forwarding incomplete voice notes instead of a spine brief
- Collecting passports the morning of departure on international strings
- Letting three executives brief aviation separately
- Hiding a fourth city until after aircraft lock
- Treating the first-time flyer checklist as a substitute for EA ops discipline
Board travel and NDAs
On sensitive board trips, the private jet booking checklist for executive assistants should include an explicit privacy paragraph: who may receive the passenger list, whether hotel names are confidential, and whether arrival photos are forbidden. Share only what handlers need. If an NDA covers the meeting, do not put deal nicknames in the flight open text. Use neutral mission labels. Your calm process protects both aviation coordination and corporate confidentiality.
After-action notes for the next trip
Within one business day, jot what worked: airport pair, car timing, catering, and any passenger-data friction. Store it with the principal’s travel profile. EAs who keep after-action notes spend less time reinventing briefs and more time preventing repeats of the same failure. Share constructive feedback with the aviation coordinator; good operators fold it into the next file. This is how corporate flying becomes a system rather than a heroic improvisation every Thursday.
Time zones, local times, and confirmation language
Multi-city briefs collapse when times omit time zones. Always write local time with city label, and confirm the aviation desk echoes the itinerary in a single confirmation message. If the principal’s calendar is in one zone and the meeting invite in another, reconcile before you brief aviation. EAs should also confirm whether “morning” means a hard 08:30 appearance or a flexible before-lunch preference. Ambiguity here creates either unnecessary empty legs or missed meetings. When daylight-saving transitions approach, re-check the spine. Send the confirmation PDF or email summary to the approver and the principal’s backup assistant.
Vendor stack coordination
Jets, cars, hotels, and security vendors often sit in different inboxes. You are the integration layer. Share only necessary ramp times with car vendors; share only necessary hotel arrival windows with concierges; do not broadcast the full passenger list to every supplier. If a hotel late checkout interacts with a return wheels-up, resolve it before travel day. If a security detail is company-arranged, introduce their lead to the handler’s contact with clear apron rules. Integration is the EA craft that passengers never see when it works.
Handoff when you are offline
Executive assistants also sleep. Build a handoff note for a backup colleague: open items, approver phone, aviation coordinator phone, Plan B tolerances, and whose passport is still missing. A two-paragraph handoff prevents nocturnal improvisation. Store the filled brief template in a shared secure location with access limited to need-to-know staff. After the trip, close the loop with after-action notes so the next multi-city string starts smarter.
Frequently asked questions
How is this different from the first-time private jet checklist?
That guide orients passengers on the flying day. This one is an EA operations and multi-city booking control document with approvers and Plan B.
When should I contact aviation relative to board approval?
As soon as dates are likely—flag that approval is pending so holds and expectations stay honest.
What is the minimum I must send to get a real quote?
Itinerary spine, hard clocks, passenger count, and whether return/wait is required—then passport details as soon as available.
How do I handle a last-minute plus-one?
Send name, nationality, passport status, and bags immediately; ask whether the locked aircraft still fits.
Should I negotiate two brokers silently with identical briefs?
You can compare quotes, but keep mission facts identical and watch inclusions—see quote comparison discipline on our prices and booking pages.
Can you support recurring corporate patterns?
Yes—recurring spines resemble shuttle design. Start the conversation via contact or booking.
What if the principal changes the city order overnight?
Send a revised spine immediately and ask what breaks: crew duty, permits, or aircraft fit.
Conclusion
Executive assistants win private aviation days by issuing one complete spine brief: clocks, passengers, bags, ground, approvers, privacy, and Plan B. Multi-city corporate travel rewards process; it punishes fragmented voice notes.
When your template is filled, To request a route-specific quote, use book a private jet or reach the team via contact.
){kind=link}