A good transport brief is specific without becoming a copy of the traveller’s private calendar. Dispatch needs enough information to identify the passenger, plan the route and communicate about the journey. It does not need the contents of confidential meetings. For an executive assistant, the practical challenge is to separate those two kinds of information before forwarding a booking request, particularly when several people are copied into the same email chain.
Keep the operational core
Provide the passenger name, a reachable contact number, journey date, pickup address, destination and relevant flight details. Include the actual passenger and luggage counts. These details allow the provider to assess the request and communicate about an arrival or change. If an organiser acts as the main contact, make that relationship explicit. A vague description such as VIP guest is less useful than a clearly identified traveller and an agreed meeting instruction.
Remove unrelated attachments
A meeting invitation may contain participant lists, dial-in links or commercial information unrelated to transport. Summarise the street address and required arrival arrangement instead of forwarding the entire document by default. Avoid including passport scans in ordinary booking messages unless a specific requirement is identified and an appropriate method agreed. When a host supplies access directions, send the practical instructions rather than disclosing confidential background about why the meeting is taking place.
Describe assistance without oversharing
Explain the practical help the traveller needs, such as extra time to enter a vehicle or space for a mobility aid. Relevant dimensions can be more useful than a detailed medical history. Suitability and assistance arrangements must be confirmed; a request does not guarantee a specially equipped vehicle. Ask the traveller what information they want communicated to the provider and ensure that an assistant’s description accurately reflects the passenger’s own requirements.
Choose a discreet meeting identifier
Discuss whether the airport meeting sign should use the traveller’s surname, a company name or another agreed identifier. The passenger must know that identifier in advance. A discreet sign should still be recognisable and must not cause confusion with another group. Do not describe a name-sign choice as a guarantee of anonymity or confidentiality in a public arrivals area. If the preference changes, update dispatch and the passenger together.
Control onward sharing
Nominate one organiser to distribute the final booking instructions to the traveller and receiving host. Share only the details each person needs for their part of the handover. Keep the journey reference available for changes and account enquiries, but avoid publishing it in an open group or social post. Airportcab’s website privacy information explains the service’s data handling; ask directly if your company has a specific procurement or information requirement before confirming the booking.
Questions about this journey
Do you need the full meeting agenda?
No. The route, timing, entrance and operational contacts are the useful transport details.
Can an assistant be the main contact?
Yes. Identify the travelling passenger and explain how the assistant will remain reachable.
Should I send a medical history for assistance?
Describe the practical assistance and equipment requirements, and confirm suitability directly without unnecessary personal detail.