Travel Briefing

name: travel-briefing
description: Assembles a complete trip briefing from itinerary details and meeting information - day-by-day logistics, per-meeting context and pre-departure checklist. Use when the user is preparing a business trip, travel pack, executive itinerary or trip brief.

Assemble the trip book an executive actually uses: everything in one document, in chronological order, with the gaps found before departure instead of discovered at a hotel desk at 11pm. The assistant's standard applies: the brief has failed if the principal ever has to search an inbox mid-trip and every logistics claim in it is either backed by a confirmation or visibly marked as unverified.

Inputs

• Travel details: flight, hotel and ground transport confirmation emails, a pasted itinerary or notes.
• The meetings on the trip: who, where, purpose and any prep materials or background on the counterparties.
• Optional standing context: the principal's preferences (airline seating, hotel chains, dietary needs, how much buffer they like) and the trip's overall objective.

Workflow

1. Build strictly from the confirmations. Every time, address, confirmation number and flight detail comes from a provided confirmation or note. Anything stated without backing. "I think the dinner is at 7". Goes in marked "unconfirmed. Verify." Never fill a logistics gap with a plausible value; a guessed address is worse than a blank one.

2. Sanity-check the physical sequence. Walk the itinerary as the principal will live it: Can they get from the 2pm meeting across town to a 3:30 international departure? (No.) Is there ground transport for every segment between airport, hotel and meetings. Including the return legs, which are the ones most often forgotten? Do meeting times in the calendar match local time after the zone change? International connections under 90 minutes, domestic under 45 and airport arrivals inside 2 hours for international departures all get flagged as tight. Overnight flights get a note on arrival-day scheduling ("lands 6:10am after a red-eye; first meeting at 9am. Flag if that's not intentional").

3. Identify what is structurally missing and ask rather than leaving it silently absent: no hotel on a multi-night trip, no transport from the airport, a free evening in a city where the notes mention someone worth seeing, no return journey in the materials.

4. Assemble the trip book:

Trip overview: dates, cities, purpose in one line and the one or two meetings that make the trip succeed. So if things go sideways, everyone knows what to protect.

Day-by-day: chronological, all times local with the time zone restated at every city change:

Tuesday, March 10: London (GMT) 07:40. Car from Claridge's to Canary Wharf (booked, conf #CW-2214; driver Amir, +44 7…; allow 40 min) 08:30. Breakfast, Marcus Webb, Halcyon Partners. Private dining room, Level 39 (his EA confirmed 3/4) 10:30. [GAP. No transport arranged back to the City for the 11:30] 11:30. Meeting: Thornfield Family Office. 22 Bishopsgate, Floor 54 (unconfirmed. Verify with their office)

Meeting context: a block per meeting: who the counterparties are (from provided materials), relationship history ("last met at Milken; he followed up twice about co-invest"), what the principal should walk in knowing, the desired outcome and the prep pointer ("skim their Q3 letter. Attached in materials"). Where no background was provided, say "no background on file". The principal should know they are walking in cold rather than assume otherwise.

Pre-departure checklist: documents (passport validity, visa or entry requirements framed as items to verify officially. These change and must not be stated as authoritative); every "unconfirmed. Verify" item consolidated in one list with who can confirm it; materials to print or load; and reminders to check weather and currency needs before packing.

Contacts: one consolidated list: every counterparty and their assistant, every driver, hotel front desks and the home-office contacts, each with phone numbers as given in the materials. Mid-trip, this page is the one that gets used.

Guardrails

• Never invent confirmation numbers, addresses, times or contact details. "Unconfirmed. Verify" flags are the honest state.
• Do not book, change or cancel anything. This skill assembles and checks; the user executes.
• Buffer flags are advisory and stated with their reasoning ("40 minutes across Manhattan at 5pm is optimistic") so the assistant can apply judgment about this principal's tolerance.

Optional: Connect Microsoft 365

Out of the box, the user pastes confirmations and meeting details. If a Microsoft 365 connector is available, you can pull the trip's calendar entries from Outlook and search the inbox for booking confirmations to assemble the brief. Reducing the risk that a confirmation sitting in email never makes it into the book. If no connector is connected, ask the user to forward or paste the confirmation emails.