Travel and transport administration
Event driver briefing pack
The supplier has confirmed vehicles, but the driver on the day has only seen a forwarded email with half the details.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
A driver briefing pack is a one-page extract that tells each driver where to be, who to collect, who to call and what to do when something changes. It is built from the master list and contains only what that driver needs for that day.
It names a single event contact for the driver, states the waiting and no-show rule, and says which changes the driver accepts and from whom. It does not state journey times.
What a driver actually needs
- Pickup and drop-off points by name, with the entrance confirmed in writing by the venue or hotel.
- The sign name and party size for each pickup, taken from the airport transfer manifest extract.
- The window or time for each run, as in the shuttle departure schedule.
- A single event contact who answers during the run, plus a second contact.
- The waiting and no-show rule, and what to do with delegates who need assistance.
- The rule for accepting changes: only from the named contact, never directly from delegates.
What to leave out
Do not send drivers the full delegate list, dietary or medical information, or reasons behind an assistance request. Send the arrangement only, for example that a step-free vehicle is needed.
Keep the pack to a page or two. Drivers read it on a phone before the run, and a long document is not read.
Briefing table
| Item | What to write | Confirmed by |
|---|---|---|
| Run reference | Date, wave and vehicle. | Transport coordinator |
| Pickup point | Name and entrance as confirmed in writing. | Venue or hotel |
| Drop-off point | Name and entrance as confirmed in writing. | Venue or hotel |
| Passengers | Sign names, party size, luggage notes. | Coordinator, from manifest |
| Event contact | Name and a number or channel used on the day. | Organiser |
| Waiting rule | How long the driver waits and who decides afterwards. | Organiser and supplier |
| Assistance | The arrangement agreed, not the reason. | Coordinator |
| Changes | Accepted only from the event contact, by message with a time stamp. | Organiser |
Sending and checking the briefing
- Ask the supplier for the names and vehicles that will actually run, not just the booking.
- Send each driver their extract at an agreed time before the run, through the supplier.
- Ask the supplier to confirm each driver has read it, and keep that confirmation.
- Hold a short call or message check with the first driver of the day.
- Have the event contact log changes and no-shows during the run for the review.
Typical gaps
- The briefing goes to the supplier's office and not to the driver.
- The pickup point is given as a landmark that is not an entrance.
- Two contacts are named but only one is reachable.
- The driver is given the whole list and shares it in a group message.
- The waiting rule is not written and each driver decides alone.
Worked example · Fictional example
A briefing for the first morning of a regional summit
Fictional organisation and figures, for illustration only.
A fictional manufacturers' council uses two vehicles for the first morning. Each driver receives a one-page briefing with the run reference, the hotel entrance the hotel confirmed, the drop-off entrance the venue confirmed, sign names for the passengers on that run and two contacts.
The waiting rule says the driver waits for the stated period, calls the event contact and then follows the contact's instruction. The coordinator logs one no-show and one change that morning, both for the review.
Use this yourself
Driver briefing one-page template
Copy into a document and fill one page per driver per day.
- Run reference (date, wave, vehicle):
- Pickup point and entrance (confirmed by, date):
- Drop-off point and entrance (confirmed by, date):
- Passengers on this run (sign names, party size, luggage):
- Assistance arrangement, if any (arrangement only):
- Event contact and second contact (name, channel):
- Waiting rule and who decides after it:
- Changes accepted only from the event contact, in writing:
- Return runs and marshal at the venue:
- Driver acknowledgement received (time):
Handle it in-house, or bring in help?
Your team can usually handle this when
- One supplier and one or two vehicles on a single day.
- The organiser can send the pack and stay reachable during the run.
Outside planning help earns its fee when
- Several suppliers, several drivers and changes during the day.
- Speakers or officials need a separate arrangement and different briefing.
- No one on the committee can be the event contact for the whole window.
Need driver briefings prepared and run?
A conference project lead can prepare each driver's one-page extract from the master list, send them through the supplier, confirm that drivers have read them and act as the event contact while runs are on. Drivers and vehicles remain the supplier's responsibility, and decisions on waiting and changes stay with you. Send the supplier's confirmation and your pickup points.
Questions organisers ask
Who sends the briefing to the driver?
Send it through the supplier, and ask the supplier to confirm the driver has it. A pack that reaches only the supplier's office has not briefed the driver.
Should drivers have delegate phone numbers?
Only if the delegate has agreed and only for that day. Otherwise route contact through the event contact.
What should the waiting rule say?
State how long the driver waits, whom they call and who decides next. Agree it with the supplier in advance.
Do we brief drivers on accessibility?
Tell them the arrangement, such as a step-free vehicle, and not the reason. See accessibility transport requests.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.