Building a Conference Agenda Without Clashes

You have forty accepted sessions, four rooms and two days. Every arrangement is possible and most of them are bad. The difference is in a few rules applied before you start dragging things around.

Design tracks around the audience, not the topic

A track exists so that a person can stay in one room all afternoon and have a coherent experience. Organise by who the sessions are for — practitioners, leaders, newcomers — rather than by subject taxonomy. Subject tracks feel tidy in a spreadsheet and send the same person across the building four times.

Size rooms by expected demand, not by track fairness

Every track does not deserve an equal room. Estimate demand from submission themes, last year's attendance, and the registration data you already have — if people chose sessions at registration, you have the answer. Put the two sessions you expect to be busiest in the largest rooms, and do not put them opposite each other.

The clashes people actually resent

1. Two sessions for the same audience at the same time. The unavoidable one — minimise it, and be visible about having tried.
2. A speaker scheduled in two places. Unforgivable and entirely preventable; a platform should refuse it.
3. The same room booked twice. Same.
4. A session that finishes as the next one starts across the building. Ten minutes of transfer time is a minimum; fifteen if there are stairs.

Rules one to three should be enforced by the system, not by proofreading. Gathervo blocks double-booking of rooms and speakers as you build the schedule, which removes the most common late-night error.

Build in the buffers

• Ten to fifteen minutes between sessions. Not five.
• A longer mid-afternoon break — see networking that works.
• Slack after the keynote. Keynotes overrun; a tight follow-on breaks the whole morning.

Publish early, change carefully

Publish as soon as it is 80% right. Attendees plan travel around the agenda, and a late programme costs you attendance far more than an imperfect one costs you credibility.

When something moves — and it will — change it in one place and let every surface read from it: the site, the app, the signage, the session chairs' sheets. The failure is never the change itself; it is the four stale copies. This is the practical argument for the agenda living in your platform rather than in a document.

Sanity-check with a walk-through

Read the agenda as one attendee type, hour by hour, and ask whether their day is sensible: do they eat, do they have to cross the building twice, is there an hour with nothing for them? Do it for three different personas and you will find most of the remaining problems.

Build your agenda free on Gathervo, and see session chairs and moderators for who keeps it to time on the day.