Event transport delay communication
A vehicle is late, delegates are standing at the pickup point, and three different people are about to send three different messages.
The short answer
Delay communication works when one person owns every message, messages state only what is known, and delegates are told what to do next. Agree this before the event, because during a delay nobody has time to decide who speaks.
Say what has happened, what is not yet known, when the next update will come and what delegates should do now. Do not state an estimated arrival time unless the supplier has given it, and attribute it to the supplier.
Decide before the day
- The single message owner, and a named back-up.
- The channels used, such as the event messaging group, a text to waiting delegates or a notice at the pickup point.
- What the supplier must tell you, and how quickly the supplier is asked to report a problem.
- Which decisions the owner can take alone, for example sending a second vehicle, and which need the event owner.
- How delegates with assistance needs are reached first. See accessibility transport requests.
The four-part message
| Part | What it says | Example wording |
|---|---|---|
| What happened | The fact, in plain words. | The 08:00 shuttle from the hotel has not yet left. |
| What is known and not known | Cause if confirmed by the supplier, and what is still unknown. | The supplier is checking. A new departure time is not yet known. |
| What to do now | Where to wait, or the alternative on offer. | Please wait in the lobby. A second vehicle is being arranged. |
| Next update | When you will write again, even if nothing has changed. | Next update at 08:20 in this group. |
What not to say
- Do not give an arrival estimate that is your own. Quote the supplier and say so.
- Do not blame a person or a supplier in a delegate message.
- Do not promise that a connection or session will be held unless the event owner has agreed.
- Do not post personal details of delayed delegates in a group.
- Do not go silent between updates.
After the delay
- Confirm to delegates that the situation has ended and where to go.
- Tell the venue and programme owner if the session start is affected, and let them decide on any change.
- Record the times, the messages sent and the supplier's explanation.
- Raise the cause with the supplier in writing and ask what will change.
- Update the driver briefing pack or schedule if a rule needs adjusting.
Worked example · Fictional example
A late vehicle before a morning plenary
Fictional organisation and figures, for illustration only.
A fictional engineering institute has delegates waiting at a hotel for the first shuttle, and the vehicle has not arrived. The message owner posts the four-part message, quoting the supplier's statement that a replacement is being sent without stating a time of arrival.
The owner tells the programme manager that the first session may start late, and the manager decides. A second update goes out at the time promised, the replacement arrives, and the log records every message and time for the supplier review.
Use this yourself
Transport delay message set
Prepare these before the event and fill the brackets on the day.
- First message: [what happened]. [What is known and not known]. [What to do now]. Next update at [time].
- Update with no change: Still [situation]. The supplier has [last confirmed statement]. Next update at [time].
- Resolved: [Vehicle] is now [status]. Please go to [point]. Thank you for waiting.
- Message to venue or programme owner: [vehicle] delayed, possible effect on [session], decision needed from [name].
- Message to supplier: please confirm cause, new status and any change to later runs.
- Log line: [time], [message sent], [by whom], [supplier statement].
Handle it in-house, or bring in help?
Your team can usually handle this when
- Small numbers of delegates and a single supplier.
- The committee has agreed who speaks and the organiser can be reached on the day.
Outside planning help earns its fee when
- Several vehicles and groups, with delegates across hotels.
- Speakers or officials are affected and decisions touch the programme.
- No one on the team can own messages while also running the event.
Want a delay plan and someone to run it?
A conference project lead can agree the message owner, channels and decision rules with you before the event, prepare the message set and act as the single voice to delegates, suppliers and the venue if transport runs late. Decisions about the programme stay with your event owner, and the supplier remains responsible for its vehicles. Send your transport arrangements and who is on site.
Questions organisers ask
Should we give delegates an estimated arrival time?
Only when the supplier has stated one, and attribute it to the supplier. Otherwise say when the next update will come.
Who should send delay messages?
One named person with a back-up, so delegates receive a single consistent voice.
What if the delay affects the programme?
Tell the programme owner and the venue straight away and let the programme owner decide. The transport message owner does not change the programme.
How soon should we send the first message?
As soon as you know a vehicle is late. Say what you know, and set the time of the next update.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.