Programme, agenda, run of show: three documents, one source
People use these words loosely, but they describe different readers. The programme or agenda is for guests: sessions, times, rooms, speakers, short descriptions. The run of show is for the team: cues, who walks on when, which slide is up, when the doors close, when catering clears the tables. The speaker schedule is for the people on stage: their slot, their room, their technical check and who introduces them.
Keep all three on the same times and the same room names. The most common failure in an event schedule is not a bad plan but two versions of a good one — the guest agenda says Hall B at 14:00, the run of show says Hall B at 14:15, and both were right on different days. Decide which document is the source, and let the others be drawn from it.
Start with the shape of the day, not the sessions
Before you place a single talk, draw the frame: when guests arrive, when the doors open, the fixed points that do not move (a keynote, lunch, a closing drinks reception), and when the venue needs the rooms back. Then count the rooms you actually have and the hours each one is usable. That frame tells you how many sessions fit, which is usually fewer than the number of people who want to speak.
Put the most important session where attention is highest and arrival is complete — rarely the first slot, because some guests are still at registration. Put sessions that need a full room after a break, not before lunch when people drift towards the food.
Timings and buffers that survive a real day
Every schedule is optimistic. Speakers overrun, the previous session ends late, the walk between rooms takes longer than it looks on the floor plan, and a coffee break with four hundred people and two urns lasts longer than fifteen minutes. Build the slack in rather than hoping for it.
- Leave five to ten minutes between sessions in different rooms, more if the rooms are on different floors.
- Give a keynote a hard end time and tell the speaker it is hard; a moderator with a clock is cheaper than a late afternoon.
- Make breaks long enough for the queue, not for the coffee: a break is over when the last person has been served.
- Hold one floating slot late in the day that can absorb an overrun or a speaker who did not arrive.
- Agree with the venue when each room must be empty, and end the last session there with time to spare.
Rooms, speakers and session details
Each session needs the same few fields, filled the same way: title, start and end, room, speakers, a two-line description, and, for larger events, a track or topic so guests can find what is for them. Keep titles short enough to read on a phone; a title that needs a subtitle to make sense needs a better title.
Give each room a name guests can find: the name on the door sign, not the venue’s internal code. If the building has two rooms with similar names, rename one for the day. And collect speaker details once — name, role, organisation, photo, a short biography — early enough that changes do not arrive the night before printing.
Publishing the agenda to guests
A programme is only useful if guests can open it when they need it, which is usually on a phone, in a corridor, with a weak signal. A link that opens a page beats an attachment: it can be corrected after it is sent, it fits a small screen, and it does not need to be found again in an inbox. Send the link with the invitation or the confirmation, and again in the last reminder before the day.
Publish the programme when it is stable enough to be useful, and mark what may still change. Guests forgive "speaker to be confirmed"; they do not forgive a session that silently moved. If you print anything, print the frame of the day and the room names, and point to the live version for the details.
Personal agendas and full rooms
At an event with parallel sessions, every guest is really attending a different event. Letting them save the sessions they plan to attend into their own day turns a long programme into a short personal agenda — and gives you an early signal of which rooms will be too small. A session that half the guests have saved should not be in the smallest room.
When a room does fill up, the worst answer is a closed door and nothing else. Have a plan before the day: a similar session the guest can go to instead, an overflow room with the stream, or a repeat later. Tell guests at the door and on their phones, not only on a sign they will see after the walk.
Changes on the day
Something will change. A speaker falls ill, a room’s projector fails, a session is moved to make space for one that overran. The rule is the same each time: change the source first, then tell the people it affects. A guest who saved the moved session needs to hear about it; a guest in another track does not.
Give one person on the team the authority to change the programme on the day, and make sure the speakers, the room hosts and the person at the information desk all see the same version. Announcements from the stage are for changes that affect everyone; everything else belongs in the agenda itself.
An agenda checklist
Before you publish the event programme, check that each line below is true.
- One source for times and room names; guest agenda, run of show and speaker schedule drawn from it.
- The frame of the day fixed: arrival, doors, fixed points, room handback.
- Buffers between sessions and breaks long enough for the queue.
- Every session with title, time, room, speakers and a short description.
- Room names that match the signs on the doors.
- A link guests can open on a phone, sent with the confirmation and the last reminder.
- A plan for full rooms and one person who can change the programme on the day.