What is an agenda builder?

The agenda builder is where the organizer’s time actually goes. Demos show the attendee view; the console is where somebody spends three days entering forty sessions, sixty speakers and a room plan.

In practice at an event

The work is: create sessions with title, description, day, time, room and track; attach speakers; set capacity where it applies; and then change all of it as the programme firms up. A conference programme is not stable until roughly two weeks out, and the changes between draft and freeze number in the dozens.

Bulk entry is the difference between days and hours. So is duplication — creating next year’s event from last year’s rather than from nothing.

What to look for

Ask whether sessions can be imported in bulk rather than only created one at a time, and what the import format is.

Ask what happens when a session is edited after attendees have saved it, because that is the case that matters during the event and the one demos skip.

And ask whether the organizer can make a change live without vendor involvement. If the answer involves a support ticket, that is a real operational cost landing at the worst moment of your event.

One more thing to check, because it is the difference between three days of work and one: whether the console can duplicate a previous event. Most of a returning conference’s programme structure is unchanged year to year, and re-entering it from nothing is the single largest avoidable cost in setting an app up.

How event67 handles it

Sessions, tracks, rooms, speakers and sponsors are created and edited in the console, with the schedule live to attendees. Attendee lists import from CSV. Changes to a session reach the attendees who saved it, through a notification that deep-links to that session.