Glossary
Session vs track
A session is a single scheduled item on your agenda — one talk, panel, workshop, or keynote — while a track is a themed grouping of sessions (like "AI track" or "Beginner track") that often run in parallel across different rooms.
What a session is
A session is the atomic unit of your program: one scheduled thing an attendee can sit in. It has a title, a type (keynote, talk, panel, workshop, lightning talk), a start and end time, a room, and one or more speakers attached to it. Everything else on the agenda is built out of sessions. When you drag a card on the agenda builder, when a speaker confirms, when a registrant decides where to be at 2pm — the object in play is a session. In AgendaForge a session carries its speakers, its track, and its room as relationships, so the same talk shows up correctly wherever it's referenced: the public event page, the speaker's portal, and the JSON embed feed on your own website.
What a track is, and how it differs from a room
A track is a curated theme that groups sessions together — an editorial label, not a place. "AI track", "Beginner track", "Product track": each is a through-line an attendee can follow across the day. A room is the opposite kind of thing — it's a physical or virtual location with a capacity, like Hall A or Workshop Room 2. The distinction trips people up because at many events a track happens to live in one room all day, so the two feel synonymous. They aren't. A track answers "what is this about?"; a room answers "where is it?". One track can move between rooms; one room can host sessions from several tracks. AgendaForge models tracks (with colors) and rooms (with capacity) as separate things precisely so you can mix them freely as you build the schedule.
Why multi-track events need conflict checking
The moment you run more than one track at the same time — parallel sessions — two failure modes appear. First, a room collision: two sessions scheduled into the same room in the same time slot. Second, a speaker collision: the same speaker booked to be in two places at once, which is impossible and embarrassing. Single-track events rarely hit either, because everything is sequential. Multi-track agendas hit both constantly, and they're easy to miss when you're dragging dozens of cards around. AgendaForge's Agenda AI watches for exactly these double-bookings while you build, flagging room and speaker conflicts and suggesting open slots so you can resolve them one at a time. One honest caveat: this is an authoring-time aid that surfaces problems as you schedule — it is not a continuously-enforced server guarantee, so a final read-through before you publish is still on you.
Key points
- A session is one scheduled item (talk, panel, workshop, keynote); a track is a themed group of sessions.
- A track is an editorial theme; a room is a physical or virtual location with capacity — they are not the same thing.
- One track can span multiple rooms, and one room can host sessions from several tracks.
- Parallel multi-track agendas create room and speaker double-bookings that single-track events rarely hit.
- Agenda AI flags room and speaker conflicts while you build, but it's an authoring-time aid, not an enforced guarantee.
See how AgendaForge handles this in practice:
Agenda building →Common questions
Q.01 Is a track the same as a room?
Q.02 Can one session belong to more than one track?
Related terms
Run the whole program in one place.
Invite-only while we onboard early partners. Tell us about your event and we'll bring you in — white-glove, no training course required.