Designing a summit information desk for session changes
A speaker cancels, a room changes and delegates arrive at the desk asking where to go.
The short answer
The desk works when it holds one current version of the programme and one person decides what counts as a change. Staff the desk with people who can answer the same question the same way, and give them a change log they update and read from.
Delegates need three things at the desk: what changed, where to go and what to do if they miss it. Everything else, such as apologies and explanations, is secondary.
What the desk is for
- Answering where, when and who for sessions that moved.
- Passing real changes to the programme owner and updating all channels.
- Handling lost badges, access questions and queries that belong to registration or the floor team.
- Recording questions that show a gap in signage or communication.
Roles at the desk
| Role | Does | Does not do |
|---|---|---|
| Desk lead | Owns the change log, confirms each change with the programme owner and tells the team. | Answer individual queries while the log is out of date. |
| Desk agents | Answer from the current change log and the master programme. | Improvise answers or promise a session will start at a time they have not been told. |
| Runner | Updates signage, screens and printed sheets after each change and carries messages to room captains. | Decide what counts as a change. |
| Programme owner | Approves changes, including a speaker substitution or room swap. | Handle desk queries directly except by exception. |
A sequence for a session change
- The programme owner or track chair reports the change to the desk lead.
- The desk lead writes it in the change log with time, room, reason and who approved.
- The runner updates signage, the app or screens and the printed sheet, and tells the room captains.
- The desk lead briefs agents with the exact wording to use.
- The desk lead sends a short message to affected delegates through the channels agreed in advance.
- After the session, the desk lead confirms the change was accurate and notes lessons for the final report.
A script for delegate questions
- What changed: state the new room and time in one sentence.
- Where to go: point to signage or a map and offer a runner if the route is long.
- What if they missed it: the room captain or chair decides on late entry; see handling track switches.
- What if the session is cancelled: name the nearest alternative and where slides or materials will be shared, if agreed.
What to avoid
- Several versions of the programme in use at once.
- Agents guessing instead of reading the change log.
- Changes announced in the room but not at the desk, or the other way round.
- No agreed wording, so each agent explains differently.
- Spreading rumours about reasons, such as a speaker's illness or visa. Share only what the programme owner approves.
Worked example · Fictional example
A fictional morning of changes
Fictional organisation and figures, for illustration only.
At a fictional two-day trade summit a keynote speaker is delayed and the opening panel moves 40 minutes later. The desk lead logs the change, the runner updates the app and signage and the room captain announces it. Agents give the same message: new time, same room, and a coffee break first.
An hour later a workshop room is unavailable. The programme owner approves a swap to a smaller room, the desk lead updates the log and the runner moves signage. Agents tell delegates the new room and offer to walk them there.
Use this yourself
Session change log and desk script
Copy this table to the desk and update it for every change. Agents answer from the latest row only.
| Change no. and time logged | Session | What changed (time, room, speaker) | Reason shared with delegates | Approved by | Signage and app updated by | Agents briefed |
|---|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- A single-day summit with two tracks and a small team.
- Changes are rare and one person approves them.
- A single channel such as an app or a screen is the master.
Outside planning help earns its fee when
- Several tracks, rooms and many speakers, with changes expected during the day.
- Delegates, speakers and sponsors all depend on the desk for current information.
- Signage, app and printed material have different owners.
Need the information desk run as a system?
A conference project lead can design the desk roles with your team, set up the change log and approval route, align signage, app and printed materials with the log and brief desk agents and room captains. The programme decisions remain with your programme owner. Send your venue layout, expected delegate numbers and the channels you plan to use.
Questions organisers ask
Who decides whether something is a real change?
The programme owner. Desk agents record and communicate, not decide.
What should we tell delegates about the reason?
Only what the programme owner approves. State the change and where to go; keep reasons brief and factual.
How many staff does the desk need?
That depends on the expected number of delegates and the number of changes. Plan for peak times such as the start of the day and after breaks.
Should the desk sit at the entrance?
It should be where delegates naturally pass or pause. Ask the venue about positions and power.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.