A good conference schedule is almost invisible: people find the talk they wanted, get there on time and still have a minute for coffee. A bad one shows up as empty seats in one room, a queue out the door of another, and a speaker booked into two places at once. This guide walks through building a one- or two-day program the way experienced volunteer organizers do it — from the shape of the day down to the last buffer — with a sample schedule you can adapt.
Start with the fixed points
Before you place a single talk, write down what you can't move: when the venue opens and when you must be out, when catering arrives, which rooms you have and how many people each one seats, and any promises already made to a keynote speaker or sponsor. Those fixed points are the frame. Everything else is a puzzle inside it.
Next, sketch the day as blocks rather than individual sessions. Here is a common shape for a one-day event with two tracks and about 300 people, using our fictional Harbourline Dev Day:
| Time | Block | Why it's there |
|---|---|---|
| 08:30–09:15 | Registration and coffee | 45 minutes lets the queue clear before anything starts. |
| 09:15–10:00 | Opening keynote (single track) | Everyone in one room, nothing running against it. |
| 10:00–10:15 | Changeover | Time to walk, find a seat and plug in. |
| 10:15–12:00 | Morning block: two talk slots per track, one 90-minute workshop | Talks start together in every room. |
| 12:00–13:00 | Lunch | An hour, because 300 people take a while to get through a buffet. |
| 13:00–14:45 | Afternoon block: two talk slots per track, one 90-minute workshop | Lively sessions first; it's the hardest slot of the day. |
| 14:45–15:00 | Changeover | Rooms reset for the close. |
| 15:00–17:00 | Closing social | Ends the day on conversation rather than an empty hall. |
Only once the blocks feel right should you start dropping talks into slots.
Tracks are topics, rooms are places
Mixing these up is the most common cause of a confusing agenda. A track is a thread of related sessions — “Frontend”, “Platform”, “Community” — that helps attendees decide what to see. Aroom is a physical space with a capacity, a screen and a door.
- Keep each track in one room where you can, so its followers don't have to move every hour — but don't force it when a talk needs a bigger space.
- Name rooms the way the venue's own signs do. If the door says “Room B”, so should your agenda.
- Assign rooms by expected audience, not by how well-known the speaker is. A popular beginner topic often outdraws a famous name.
- Track colors help people scan, but some of your audience won't be able to tell them apart. Always pair a color with the track's name.
In AgendaKit, a session can belong to more than one track — handy for a keynote that everyone should see — and track colors always appear next to a text label.
Pick session lengths and keep a shared grid
Choose a small set of lengths and stick to them. A typical set:
- 20–25 minutes for short, focused talks, or a block of lightning talks sharing one slot;
- 40–45 minutes for a standard talk with questions;
- 45–60 minutes for a panel;
- 90 minutes for a hands-on workshop, filling two talk slots.
The rule that matters most: start times line up across rooms. If Room B starts on the hour and the Main Hall at quarter past, anyone switching rooms misses the start of every other talk. Workshops can span two slots, as long as they begin and end on the shared grid.
Build in buffers and breaks
- 10–15 minutes between sessions. People need to walk and speakers need to plug in. Use the longer end when rooms are on different floors.
- A break every 90–120 minutes. Attention fades, and everyone needs coffee and a restroom.
- A real lunch. For a few hundred people, plan an hour; anything shorter turns into a queue.
- Turnaround time for the room crew. A workshop that needs tables rearranged needs a gap before it.
- Extra time for access. Step-free routes and lifts take longer than the stairs, and a quiet room is only useful if there's time to get to it.
Put breaks in the agenda as sessions of their own. Attendees see when the next coffee is, and nobody accidentally schedules a talk over lunch.
Avoid speaker and room clashes
Room clashes
Two sessions in the same room at overlapping times are easy to create when you move one talk late at night.AgendaKit flags same-room overlaps in the editor and warns about them in the import preview, so you can fix them before anything is published.
Speaker clashes
The same person in two places at once is harder to spot, and panels are the usual culprit: it's easy to forget that the moderator of the 14:00 panel also gives the 13:00 talk two floors up. Do one pass per person: list every session each speaker appears in — including as moderator or host — and check the times and the walk between rooms. Ask about constraints in your call for papers too: a late flight, a school run or an access need is simpler to plan around before the grid is full.
Place keynotes deliberately
- Start the opening keynote after registration has had time to clear, not at doors-open, or the people still in the queue miss it.
- Run nothing against a keynote. It's the one moment the whole event shares.
- The slot straight after lunch is the hardest of the day. Give it to a lively panel or a demo, not your densest technical talk.
- Attendance thins late in the afternoon, especially before people travel home. If you have a closing keynote, keep it short and follow it with something social.
Label times and accessibility clearly
- Always show the time zone, especially if any speakers or viewers are remote. AgendaKit shows times in the event's time zone, labelled, with a “your time” toggle for people elsewhere.
- Use one clock format throughout. The 24-hour clock avoids AM/PM mistakes.
- Put access details where people make decisions: step-free routes, captioning, reserved seating.
- Add capacity notes such as “24 seats, first come” to workshops, and say when to bring a laptop.
- Mark session types — talk, workshop, panel, break — so people know what they're walking into.
Publish early, then iterate
Publish a first version as soon as the program is mostly settled. Sending an unlisted link to your speakers is the fastest way to catch misspelled names, wrong titles and talks in rooms that are too small. In AgendaKit, an Unlisted agenda opens for anyone with the link but asks search engines not to index it; switch it to Public when you're ready to promote it.
Each publish creates a new version, so publish as often as the program changes. On the day itself, use live changes instead: our guide to last-minute room changescovers that. Afterwards, session ratings help you plan next year — read them as a signal, not a verdict.
A pre-publish checklist
- Every session has a title, date, start and end time, and a room.
- No two sessions overlap in the same room.
- No speaker, moderator or host is booked in two places at once.
- There are 10–15 minutes between sessions, more between floors.
- Breaks and lunch are in the agenda.
- Every track has a clear name, and colors are never the only label.
- The event's time zone is set and correct.
- Speaker names are spelled the way the speakers spell them, and you have permission to publish their photos and bios.
- Workshops with limited seats carry a capacity note.
- Someone who didn't build the schedule has checked it on a phone.
How AgendaKit fits in
You can do all of the planning above in a spreadsheet, then bring it into AgendaKit with theCSV agenda template or straight from your call for papers with theSessionize import. The import preview lists new, changed and removed sessions and warns about same-room overlaps. Afterwards, the rooms × time grid lets you drag a session to another slot (with a keyboard and button alternative), and overlaps stay flagged as you work. When it looks right, publish and share one link.
Turn your grid into a mobile agenda
Free, no account, no email. Import your schedule and publish an unlisted version for your speakers today.