Build a travel brief a virtual assistant can book from

Start with fixed constraints

A travel brief starts with the dates that cannot move, the cities the traveler must reach, and the appointments that shape each day. Write those fixed points before discussing airlines, hotels, or seat preferences. The assistant needs to know which meeting justifies an early flight and which evening can absorb a delay. A brief built from constraints produces fewer rebookings than a brief built from a list of likes.

Ask the traveler for the latest arrival time that still works and the earliest departure that does not cut a commitment. Add the ground transport window between the airport and the venue, because a short flight can hide a long transfer. Record any visa, passport, or vaccination requirement that affects the plan. These facts belong at the top of the brief where the assistant reads them first.

Separate preferences from approvals

Preferences are useful only after the constraints are clear. List the seat, hotel, and schedule choices the traveler cares about, then mark which ones are firm and which are flexible. A window seat matters less than a connection that protects the meeting. Separating the two helps the assistant trade a preference for a constraint without asking again.

Write the preference list in the traveler's own words and keep it short. Note the hotel features that actually affect the trip, such as a quiet room, a gym, or a location near the venue. Remove brand habits that no longer serve the schedule. A short list is easier to apply than a long profile that the assistant must interpret.

Add any accessibility or medical need that affects the booking, such as a wheelchair-accessible room or a seat near the front. Ask the traveler whether the need should be shared with the airline or the hotel in advance. Record the answer rather than assuming privacy is preferred. These details are easy to overlook and hard to fix on the day of travel.

Name the booking authority and budget

State the total budget, the cabin class, and the maximum single transaction the assistant may complete without approval. Name who can approve an overage and how quickly that person responds. If the traveler wants to see options before purchase, say so explicitly. A budget without an approval path invites either a stalled trip or an unapproved charge.

Decide whether the assistant may book refundable fares by default or must choose the lowest logical fare. Refundable tickets cost more but protect a schedule that may change. Record the client's policy on change fees, baggage, and seat selection. The assistant should not have to infer the trade-off during a live search.

Require a comparison before purchase

Ask for two or three viable options with the total cost, the arrival time, and the main risk for each. A comparison that lists only price hides the connection time and the hotel transfer. Require the assistant to mark the option that best protects the fixed appointments. The traveler can then approve a plan rather than reconstruct one.

Set a rule for when the assistant should stop searching. Three strong options are usually enough for a short trip, while a multi-city itinerary may need more. Record the search window so the assistant does not book a fare that expires before approval. A clear stopping rule prevents both rushed choices and endless tabs.

Plan the disruption path

Write what the assistant should do when a flight is delayed or cancelled during the trip. Name the traveler's contact route, the airline app, and the hotel desk as possible first steps. Set a threshold for rebooking without approval, such as a same-day arrival that protects the next meeting. The disruption plan should fit on one screen.

Include the backup airport and the ground option for short routes when those choices are realistic. Record who pays for a hotel night caused by an airline delay and how the receipt should be filed. Tell the assistant which meetings to notify and who owns that message. A delay handled by a written plan is far cheaper than one handled by guesswork.

Set the confirmation and sharing routine

Require a confirmation packet with the itinerary, the booking references, the cancellation terms, and the traveler's contact details. Send it to the traveler and to the person who covers the calendar. Store a copy where the team can reach it without the assistant. The packet becomes the single source during the trip.

Check that the traveler's name matches the passport or government ID before purchase. Confirm the time zone on every calendar entry and the local time on the invitation. Ask the assistant to read the final itinerary back against the brief. That last check catches most of the expensive mistakes.

Share the packet with the executive assistant or chief of staff who manages the traveler's day, not only with the traveler. That person needs the arrival time and the hotel address to plan the surrounding meetings. Confirm that the calendar entries appear on the correct account. A booking that only the traveler can see creates a scheduling gap.

Review the trip after return

After the trip, compare the plan with what actually happened. Note the delays, the unused bookings, and the changes that required a call. Ask the traveler which part of the brief helped and which part was missing. One short review improves the next trip more than a longer policy.

Update the traveler profile with the confirmed preferences and remove the assumptions that proved wrong. Keep the trip file for the recordkeeping period the client requires. Share the lesson with the assistant who covers the next trip. A travel routine improves through these small, documented corrections.