Last-minute room changes

The projector in the Workshop Lab dies at 13:40. A talk you expected 40 people for has 120 queuing outside. A speaker's train is running an hour late. Every event has a moment like this, and what attendees remember is not the change itself but whether they ended up in the right room. This playbook covers the whole routine — deciding, updating the agenda once, writing a banner, putting up a sign, telling speakers and closing the loop afterwards — without reprinting a thing.

Decide once, then announce

Name one person per day who makes schedule calls — usually the program lead — and make sure every volunteer knows who it is. Changes go wrong when three people each fix the problem a different way. Before anything is announced, that person checks:

  • The new room is free for the whole slot, including setup time.
  • It seats the expected audience, and has the screen, sound and power the session needs.
  • It has step-free access if the original room did.
  • The speaker, moderator or workshop host can be reached and can get there in time.
  • The move doesn't push another session out of its room.

Don't announce a guess. A wrong correction costs more trust than a five-minute wait for the right one.

Update the agenda once

The agenda is the single source of truth. Change it first, then point everything else at it — the MC, the signs, the chat channel. If the printed program, a chat message and the agenda disagree, people trust whichever one they saw last.

In AgendaKit, a change is one short routine in the Live changes console:

  1. Pick the session or sessions that changed.
  2. Set the new room or time, or mark the session as cancelled.
  3. Write an optional banner of up to 280 characters.
  4. Preview it, then publish.

Agenda screens that are open show the banner within seconds over a live connection, and the changed session is marked — for example “Moved to Room B” with its new time. A screen that can't hold a live connection checks for updates every 60 seconds, so the slowest open screen is about a minute behind.

A banner is read in two seconds on a phone in a crowded hallway. Make it do one job:

  • Lead with the kind of change: “Room change”, “Time change”, “Cancelled”.
  • Name the session exactly as it appears in the agenda, plus its original time.
  • Say where and when it happens now, and what stays the same.
  • Leave out apologies, explanations and blame. Those can wait for the MC.

Some examples using our fictional Harbourline Dev Day:

  • Room changeRoom change: “Testing without tears” (14:00) is now in Room B, not the Workshop Lab. Same time, same speaker.109 of 280 characters
  • Time changeTime change: the hiring panel now starts at 14:15 instead of 14:00, still in the Main Hall. Everything after it runs as planned.128 of 280 characters
  • Room swapRoom swap at 13:00: “Shipping a design system with two people” is now in the Main Hall, and “Queues, retries and other ways to lose a message” is in Room B. Times unchanged.173 of 280 characters
  • CancellationCancelled: “Queues, retries and other ways to lose a message” (13:00, Main Hall). The speaker is unwell. Room B and the Workshop Lab run as planned.148 of 280 characters

What to avoid: “Change of plans! Please check the agenda for updates.” It tells people something is wrong but not what, so everyone has to go looking — and half of them won't.

Put a sign on the old door

Not everyone has the agenda open, and some people will walk to the room they remember. Tape a large sign to the old room's door:

MOVED: “Testing without tears” is now in ROOM BSecond floor, left of the stairs · Still at 14:00

Write it in thick marker, big enough to read from down the corridor, and include directions — “Room B” means nothing to someone who hasn't found it yet. For the first ten minutes of the session, put a volunteer by the old door to redirect people. Tell the room host and the AV crew in both rooms, and take the sign down when the slot is over so it doesn't mislead the next session's audience.

Tell the speakers yourself

AgendaKit doesn't send email or text messages, so speakers hear about a change from you. Use whatever channel they actually read on the day — usually a text or chat message — and ask them to confirm. For a panel, message the moderator and every panelist. Here is a message you can copy and adapt:

Hi Ilse, a quick change for your talk “Testing without tears”: it has moved from the Workshop Lab to Room B (second floor, left of the stairs). The time is the same, 14:00–14:45.

Room B has HDMI and USB-C at the lectern. A volunteer will meet you there at 13:45 for a quick sound and screen check.

Updated agenda: [paste your agenda link]

Could you reply to confirm you've seen this? Thank you!
[Your name], program team

If you don't hear back within ten minutes, send a volunteer to the speakers' room or the registration desk to find them in person.

What attendees see

  • Open agenda screens show the banner at the top and mark the changed session with its new room or time.
  • My schedule keeps the attendee's stars and shows the updated details. If the move makes two starred sessions overlap, both are flagged.
  • Screens that are closed or offline pick up the change the next time the agenda is opened online.
  • Calendar subscriptions to a personal schedule pick up the change on their next refresh. Calendar apps decide how often that is, and it can be hours, so don't rely on calendars for a change that happens in twenty minutes.
  • Single sessions added as an .ics file or a Google Calendar link are copies made at the time, so they keep the old details. Worth a mention from the stage: “If you added this talk to your calendar, update the room.”

Say it out loud too

Ask the MC to announce the change before the next block starts, and put it on the screens between sessions if you show slides. Post it in your event chat channel, and tell the registration desk — it's where lost people go first. Every announcement should match the banner word for word, so nobody hears two versions.

After the event: a short after-action

Within a week, while it's fresh, spend fifteen minutes with your team on a few questions:

  • What caused each change, and could the venue walkthrough have caught it?
  • How long did it take from the decision to the published banner?
  • Did anyone end up in the wrong room? Did the sign and the volunteer help?
  • Did every speaker confirm, and how quickly?
  • What goes on next year's checklist — a spare adapter, a backup room, a printed volunteer contact sheet?

If you collected session ratings, read them with the change in mind. A talk that moved rooms at the last minute may score lower for reasons that have nothing to do with the speaker. Ratings are advisory, so treat them as one signal among several.

The one-page playbook

  1. One person decides, after checking the new room, access and the speaker.
  2. Update the agenda once, in the Live changes console.
  3. Write a banner: kind of change, session name, new room and time, what stays the same.
  4. Preview, then publish.
  5. Put a sign with directions on the old door and a volunteer beside it.
  6. Message the speaker (and panelists) yourself and wait for a confirmation.
  7. Have the MC, the screens, the chat channel and the registration desk repeat the banner.
  8. Review it within a week and update your checklist.

Planning the schedule from scratch? Start withhow to build a conference schedule, which covers the buffers and room planning that make changes like these rarer.

Be ready before the projector fails

Publish your agenda with AgendaKit and push room changes to every open screen. Free, with no account or email.