EventsSessions and the cockpit
Build the program, then run the day. Tracks, rooms, capacities and RSVPs beforehand, and the cockpit: one screen on the day that knows what is on now and what is on next.
The people and places behind the program. Directories, not fields you retype each year.
Speakers
A directory with your own profile fields and roles, reused between events instead of retyped each year.
Rooms and venues
Venues are a directory too: the room a session is in comes from somewhere real, and the map on the site follows.
Partners
Credited against the sessions they support, with your own label for what that relationship is called.
Lay out the program. Tracks, rooms and days.
A session carries its own room, track and capacity. Publish it, and the schedule page on your event site follows without being typed twice.
- Tracks and rooms across as many days as the event runs
- Per-session capacity, and its own timezone where that matters
- Draft until you publish it; the schedule page follows
- Internal sessions your attendees never see
- Partners credited on the sessions they support
Let people choose. Per ticket, not per order.
That’s why a group booking can split across streams: each RSVP belongs to its ticket, not the order that bought it.
- Require an RSVP where the room has a limit
- RSVP per ticket, not per order, for group bookings
- Show spots remaining, or keep the number to yourself
- A declined RSVP is recorded as declined, not as silence
- Lock selections once you need to print a room list
One screen for the day
What is on now and what is on next, how many people are in, how fast they are arriving, and what is waiting for somebody to deal with. All of it on the day, in one place, on whatever you are holding.
Yes, and the ticket types know about it: you can sell a day-one ticket, a day-two ticket and a full-event ticket on the same event, and the cockpit switches between days on the day.
Give the session a capacity and require an RSVP. You can show the spots remaining, or keep the number private if you would rather not advertise a half-empty room.
Not unless they want to. RSVPs are per ticket, so a group of four can split across four different streams and each person’s scan lands against their own session.
Scan them in at the door of the room. Anyone accepted without an RSVP is recorded as a walk-in at the moment of the scan, so the room count and the RSVP list stay separate numbers.
Yes. Send them a link and they get one part of that screen (the door, say) without an account and without access to anything else. What they do is still recorded against them.