An event agenda page people can follow from the corridor
An agenda is read twice: once at a desk while deciding whether to attend, and dozens of times on a phone in a corridor, between sessions, with patchy signal. Design for the second reading. List sessions in time order, put the room next to every title, make changes in one place, and say when the schedule was last updated.
What every session line needs
Attendees scan an agenda for one answer: where do I need to be next? Give each session the same fields in the same order so the eye learns where to look.
| Field | Notes |
|---|---|
| Start and end time | 24-hour or am/pm, but consistent; the time zone stated once at the top |
| Title | Plain and specific; a pun with no subtitle helps nobody choose |
| Room or stage | Next to the title, not on a separate map page |
| Track | As a short label, with the same name everywhere |
| Speakers | Names, with a link to a speaker page if you have one |
| Format | Talk, panel, workshop, break; workshops may need a sign-up |
| One-line summary | Enough to choose between parallel sessions |
Tracks on a small screen
A grid with rooms across the top and times down the side looks good on a projector and fails on a phone, where it shrinks to unreadable or scrolls sideways. The pattern that holds up is a single column in time order, with sessions that run at the same time grouped under one time heading and each one labelled with its room. A day heading at the top of each day, and a jump link per day, is enough navigation.
If you have more than three or four parallel tracks, consider a short page per track as well as the full list, so a person following one theme isn't wading through the others.
Late changes without chaos
Something always moves: a speaker's flight is late, a room is too small, a panel loses a member. The rules that stop that becoming confusion:
- Change one source. If the agenda lives in three places (site, PDF, slide), one of them will be wrong. Make the site the source and drop the PDF.
- Mark changes visibly: "Moved to Room B" or "Now 14:30" beside the session for the rest of the day, rather than silently editing.
- Show a last-updated time at the top.
- Announce big changes in the room as well. Nobody refreshes an agenda they think they already know.
Keeping sessions in a CMS collection
On Anticode, keep the sessions in a CMS collection with typed fields for day, start, end, room, track, title, speakers and summary. You edit entries in the dashboard, so moving a session to another room on the day is a one-field change rather than a rebuild. Each session also gets its own page at /<collection>/<slug>, which is handy for linking a talk from social posts, and the collection page lists them. Ask for the agenda when you describe the event site, for example "a two-day conference site with an agenda collection grouped by day and time, room shown on every session". The update an event schedule workflow covers the day-of routine.
Because a phone is where the agenda is read, the publish checks matter here. Anticode's design gate blocks publishing a page without a phone viewport, visible keyboard focus, reduced-motion support, alt text or a declared language. Pages from the design engine also ship with no scripts, so there's less to download on weak venue Wi-Fi. Readers can also install the site to their home screen, and it has an offline fallback.
Limits
- No personal schedule builder where attendees star sessions. An app build could do it in the visitor's own browser, separately from the site.
- No live refresh. People reload to see changes, which is one more reason to mark them clearly.
- No calendar files per session, and no sync to attendees' calendars.
- No workshop seat limits. If a session needs sign-up, link to your ticketing tool; Anticode's booking calendar only offers six fixed daily times, so it rarely matches a conference programme.
- No embedded venue maps: published pages can't embed them. Upload a floor plan image or link to a map.
Questions people ask
Should the agenda be on its own page?
Yes, for anything longer than half a day. People bookmark it, so give it a short, memorable address.
How do I handle an online event across time zones?
State the event's time zone once at the top, in words and as an offset, and link to a time zone converter for everyone else.
When should the agenda go live?
As soon as you have a credible outline, marked as provisional. It helps sell tickets; confirm details as speakers sign.