Templates

Conference agenda template

Single-day and multi-track agenda layouts with the session fields most templates forget.

Abstract and speaker management on the program graph
Trusted by teams running Informa, FT Live, medical societies, and global enterprises
Informa
Clarion Events
Financial Times
Dynatrace
ACEP
AVIXA
NACD
ASHG
American Society of Anesthesiologists
Google
Docebo
NRECA
CyberRisk Alliance
AdventHealth
Questex
IAAPA Expo
NAEYC
Informa
Clarion Events
Financial Times
Dynatrace
ACEP
AVIXA
NACD
ASHG
American Society of Anesthesiologists
Google
Docebo
NRECA
CyberRisk Alliance
AdventHealth
Questex
IAAPA Expo
NAEYC

Quick answer

A working conference agenda needs more than time slots: each session carries a title, format, track, room, speakers, and buffer time, and the whole grid has to survive speaker cancellations and room changes. This template covers a single-day and a multi-track layout, the session-level fields most agendas forget, and the checks to run before you publish.

Single-day agenda layout

A one-room, one-track day. Copy the structure and swap in your sessions.

TimeSegmentSpeaker / ownerNotes
8:00 – 9:00Registration & coffeeOps teamBadge desk staffed by 7:30; walk-in list printed
9:00 – 9:15Welcome & housekeepingEvent chairWi-Fi, exits, app download, sponsor thank-you
9:15 – 10:00Opening keynoteKeynote speakerAV check 8:30; confidence monitor; recording on
10:00 – 10:20BreakOps teamRoom reset; keynote speaker to signing table
10:20 – 11:05Session 1Speaker + moderatorQ&A last 10 min; hand mic runner assigned
11:10 – 11:55Session 2Speaker + moderator5-min turnover buffer built in
12:00 – 1:00LunchVenue cateringDietary tickets at buffet; sponsor tables active
1:00 – 1:45Panel discussionModerator + 3 panelistsSeating order agreed in advance; timer visible
1:50 – 2:35Session 3SpeakerRecording on; slides collected day before
2:35 – 2:55BreakOps teamAfternoon energy: coffee refresh mandatory
2:55 – 3:40Session 4SpeakerLast content slot — protect it from overruns
3:45 – 4:15Closing + awardsEvent chairAward winners confirmed and present; photos staged
4:15 – 5:30ReceptionSponsor hostSponsor host announced from stage at closing

Multi-track grid (per time slot)

For parallel tracks, structure each slot as a row and each track as a column — and give every cell a full session record.

SlotTrack A — ClinicalTrack B — ResearchTrack C — Workshops
10:20 – 11:05Session title + speaker + Room 201Session title + speaker + Room 204Hands-on workshop + facilitator + Lab 1 (cap 30)
11:10 – 11:55Session title + speaker + Room 201Session title + speaker + Room 204Workshop continues (90-min block spans two slots)
1:00 – 1:45Panel + moderator + Room 201Rapid-fire abstracts (6 × 7 min) + Room 204Hands-on workshop repeat + Lab 1
1:50 – 2:35Session title + speaker + Room 201Poster spotlight + poster hallRoundtables (8 tables, host per table)

Session-level fields most agendas forget

A time and a title is not a session record. Each entry should carry:

  • Session format — talk, panel, workshop, rapid-fire, poster spotlight — because AV, seating, and timing differ per format
  • Track and audience level, so attendees self-select and marketing can promote by segment
  • Room and capacity, with a plan for who moves when a session outdraws its room
  • All speakers and moderators with confirmed bios and headshots — from one record, not re-keyed per document
  • Turnover buffer — 5 minutes minimum between sessions in the same room, 15+ for format changes
  • AV requirements per session: recording, confidence monitor, hand mics, demo connections
  • Owner for the slot — the one person who starts it on time and cuts overruns
  • Learning objectives and credit codes where CE or CME applies

Pre-publish checks

  1. Read the agenda as one speaker: no person in two rooms in one slot, and 10+ minutes between their sessions
  2. Read it as one room: every gap between sessions covers the turnover the formats need
  3. Read it as one attendee per track: no track dead-ends into an empty slot while others run
  4. Confirm every listed speaker has accepted — not invited, accepted — before anything prints
  5. Version the file and name an owner; an agenda that lives in six inboxes is six different agendas
  6. Plan the change path: when a speaker drops on day -2, know exactly which documents, screens, and app views must update

Frequently asked questions

Time slots with explicit buffers, and a full record per session: title, format, track, room, capacity, speakers and moderators, AV needs, an owner, and learning objectives where credits apply. Layouts vary; the fields are what make an agenda survive show day.

Grid it by time slot (rows) and track (columns), keep slot boundaries aligned across tracks so attendees can switch, and let long formats span two slots explicitly. Check the grid three ways — per speaker, per room, per track — before publishing.

Five minutes minimum for same-format turnover in the same room, fifteen or more when the format changes (panel to workshop, talk to reception), and a real gap after keynotes — the whole audience moves at once.

Publish a session-level agenda four to eight weeks out — registrations rise when people can see what they're buying — and treat it as living: speaker changes happen up to and through show day, so plan the update path, not a frozen PDF.

Speaker changes after print. A dropped presenter touches the agenda grid, the program book, the website, the mobile app, and signage. Templates in spreadsheets require re-editing each surface by hand; a program platform updates them from one session record.

Yes — build the agenda on the same system that holds sessions and speakers. Sessionboard publishes agenda views from the program record, so an accepted swap or room change updates every surface without a reprint cycle.

Build the agenda once — on the program record

Talk through your event workflow — abstracts, speakers, content, and marketing on one program graph.

Loading form…