Regional briefings and multi-city programmes
Planning travelling speakers across consecutive event days
One speaker is meant to present in a different city each day this week, and nobody has checked the gaps between sessions.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Plan each transition as its own item: finish time, pack-down, journey window, arrival buffer, setup and sound check. A day is feasible only when the journey window is a range you have asked someone to confirm, not a number you assumed.
Name one person who owns the speaker's itinerary, and agree a fallback speaker or format before the first day.
Treat every transition as a chain
Between the end of one stop and the start of the next sit several steps: the Q and A overrun, collecting materials, leaving the venue, the journey, arrival, registration with the host and a technical check. Each has a range, not a single figure.
Add the ranges, then compare the total with the gap you have. If the gap only works when everything goes well, the plan has no room for a late start.
Questions to settle before confirming the speaker
- Is the speaker travelling by road, rail or air, and who books and pays?
- What journey window does the speaker or their assistant give for each leg, in their own words? Record it as a range.
- Is a rest period or a local meeting expected between stops?
- Who meets the speaker at each venue, and who has their mobile number?
- If the speaker is delayed, who decides to start with a substitute, shorten the session or move it?
- Does the speaker need a different slide version, language or equipment at each stop?
Order the stops to protect the speaker
Where the programme allows, put the longest transition on the lightest day and avoid a morning session straight after a late evening one. Leave the final stop with the most buffer if it feeds into a deadline such as a flight.
If a speaker cannot reasonably do every stop, consider recording a short segment, using a second speaker for one city, or splitting the dates. That decision belongs to the content owner.
Day-of coordination
- Send each host a one-page arrival note: expected arrival range, who greets, where the speaker waits.
- Confirm departure from the previous stop by message, not assumption.
- Keep a spare copy of slides at each venue, in the agreed version.
- Log actual start and end times so the next round of planning uses real figures.
Worked example · Fictional example
Three days, three cities, one keynote speaker
Fictional organisation, speaker and figures, for illustration only.
A fictional professional body, Institut Fiktif Pengurusan Projek, books one guest speaker for briefings in Kuala Lumpur on Tuesday, Shah Alam on Wednesday and Seremban on Thursday. Each briefing is a morning session of 2 hours.
The planner asks the speaker's assistant for a journey range for each leg and lists setup needs per venue. The Shah Alam host requires a technical check before registration opens, so arrival is planned as a window with a buffer, and a co-presenter is briefed to open the session if the speaker is late. Thursday carries the most buffer because the speaker flies out that afternoon.
Use this yourself
Speaker journey-window sheet
Copy this per speaker and complete one block per transition. Ask the speaker or their assistant for the journey range rather than filling it in yourself.
- Speaker and itinerary owner:
- From stop (city, venue, planned end time):
- To stop (city, venue, planned start time):
- Overrun and pack-down allowance (range):
- Journey window confirmed by (name) as a range:
- Arrival buffer and technical check needed:
- Total of ranges versus gap available:
- Fallback if late (substitute, shorten, move) and who decides:
- Local meeter and contact method:
Open the tool: KL-Selangor-Seremban briefing circuit planner
Handle it in-house, or bring in help?
Your team can usually handle this when
- One speaker, two stops, with a comfortable gap between them.
- A single person holds the itinerary and every host has their contact.
- A substitute is already agreed.
Outside planning help earns its fee when
- Several speakers cross paths between cities on the same days.
- Tight transitions rely on ranges nobody has confirmed.
- No one is sure who decides if a speaker is delayed.
Want the itinerary held by someone who is not also presenting?
Recurring programme management can build the stop-by-stop transition chain with you, confirm journey ranges with speakers, brief each host and keep a fallback plan for every day. Send the stop dates and the speakers involved. A conference project lead can take the same task if recurring support is not available for your dates.
Questions organisers ask
Can I use the circuit planner for this?
Yes. The briefing circuit planner takes your stops and journey ranges and shows transitions that do not fit. It will not produce a result if journey windows are missing.
Who books the speaker's travel?
Decide this before confirming the speaker. Write down who books, who pays, and who changes the booking if the programme moves.
What if the speaker will not give a journey estimate?
Ask for a range in writing, or add a larger buffer and record that the transition is unconfirmed.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.