A wordpress theme with event schedule templates will give you a handsome agenda on a 27-inch monitor and then quietly fall apart on the device four out of five delegates actually use. Multi-track agendas are the worst offenders, because the thing that makes them readable on a desktop — tracks as columns, time as rows — is exactly what cannot survive a 390-pixel screen. This guide covers why agenda pages break on phones, how single-track and multi-track layouts differ structurally, how to build the agenda in a theme that ships schedule templates, and the three things organisers consistently get wrong after launch: time zones, personal agendas and last-minute changes.

Why agenda pages fail on phones

Almost every failure comes from one decision: building the agenda as a wide grid and hoping responsive CSS will sort it out. A three-track, nine-hour conference day is a table roughly 1,100 pixels wide before padding. On a phone there are four ways that can resolve, and three of them are bad.

  • It shrinks. Session titles drop to seven-pixel type and nobody reads them.
  • It scrolls sideways. The reader can see Track 1 at 09:00 or Track 3 at 09:00, but never the choice they are trying to make, which is what is on at 09:00. Horizontal scrolling inside a page is also the pattern readers are least likely to discover.
  • Columns collapse into one long list with no label saying which track a session belongs to, so the agenda becomes 40 undifferentiated blocks.
  • It reflows properly — one time slot at a time, each showing every parallel session with its track labelled. This is the only version that works, and it has to be designed rather than inherited.

There is a standard worth designing against here. The WCAG 2.2 Reflow criterion asks that content be usable at 320 CSS pixels wide without two-dimensional scrolling, with data tables as a recognised exception. An agenda is genuinely tabular data, so you are allowed the exception — but “allowed” and “usable” are different standards, and the exception is not a reason to ship something nobody can read. The W3C tutorial on data tables is the right reference for marking the agenda up so a screen reader announces the time and track a session sits in, which is the same information a phone user needs visually.

The second failure is subtler and costs more: the agenda that exists only as an image or a PDF. It cannot be searched, linked to, read aloud, or updated without re-exporting, and every session in it is invisible to search engines. If your programme is a PDF, you have no agenda page at all — you have a download.

Single-track vs multi-track layouts

These are not two styles of the same page. They answer different reader questions and should be built differently.

Single-trackMulti-track
Reader’s question“What time should I arrive, and when is lunch?”“What are my options at 14:00, and which do I pick?”
Natural shapeA vertical timelineTime slots, each containing parallel sessions
Desktop layoutOne column, chronologicalTracks as columns, times as rows
Mobile layoutThe same column — nothing to doMust become slot-by-slot, with the track named on every session
Breaks whenSessions run in parallel after allA track is added or a session spans two slots

The rule that saves the most rework: model the session, not the grid. Give every session its own record with a start time, an end time, a track, a room and one or more speakers. The desktop grid, the mobile list and the per-speaker session list are then three views of the same data. Build the grid as the primary artefact instead, and adding a fourth track in week three means rebuilding the page by hand.

Two structural cases catch people out. A keynote has no track — it spans all of them, so your model needs an “all tracks” value rather than a fudged duplicate in each column. And a workshop that runs 14:00 to 16:30 against two 75-minute slots needs real start and end times, not a slot number, or it will render as a gap.

Building the agenda in YOY, a WordPress theme with event schedule templates

Be clear about what the theme supplies and what is your editorial work, because that boundary is where most agenda projects overrun. The YOY event and conference theme states on its product page that it includes event venues, speakers, sessions and sponsors, and that it ships Schedule templates, Venue, Clients and Speakers pages, eight home pages, WPBakery Page Builder and the Event Scheduler plugin — described on the page as a way to build schedules for conferences, conventions, festivals, meetings, training and exhibitions. What its page does not claim is automated multi-track logic, time-zone conversion or attendee favouriting. Those are the three things covered below, and in every case they are something you decide and implement, not a switch you find. That boundary is also the honest answer to the theme-or-plugin question: a standalone event schedule plugin WordPress organisers often start with gives you the data model, a theme that ships schedule templates gives you the presentation, and a working agenda needs both.

  1. Write the agenda in a spreadsheet first. One row per session: start, end, track, room, title, speaker, description. Sort by start time and read it through. Every clash, gap and unstaffed room shows up here, where fixing it is free.
  2. Install the theme, import the demo, then delete the demo sessions. One-click import gives you a working structure with placeholder content, not a finished programme — and the demo imagery is licensed for the demo only, so plan your own assets.
  3. Create the sessions as records with real times before you lay anything out. Use the HTML time element with a machine-readable datetime attribute wherever a time appears, so the page is parseable rather than just legible.
  4. Build the desktop view with the Schedule template, by day. One page per day beats one page carrying three days: shorter pages, cleaner links and far less to re-render when something moves.
  5. Design the mobile view deliberately. Collapse to one time slot at a time, print the track name on every session card, and keep the time sticky at the top of the slot so the reader always knows where they are in the day.
  6. Give every session a real URL. Not a modal, not an accordion that loses state — an addressable page or at minimum a stable anchor. Speakers share their session link, sponsors want theirs in a newsletter, and you will want to link to it from the speakers page.
  7. Mark it up as structured data. Use schema.org Event for the conference and for each session, with start time, end time, location and performer, so the programme is machine-readable.
  8. Test on a real phone on mobile data before you announce. Not a resized desktop window — an actual handset, held one-handed, on a slow connection.

Cross-linking sessions to speaker profiles is editorial work done by hand unless you build custom fields for it, so put it on a checklist per announcement wave rather than assuming the theme will do it. The same applies to selling from the agenda: the schedule is the page that persuades, so each slot wants a route to purchase — see our guide to running ticket sales on your own site for how that hooks up.

Time zones for hybrid events

A conference agenda page for an in-person event has one time zone and no problem. Add a stream and you have introduced the single most common support complaint in hybrid events: someone joined an hour late.

Three rules handle almost all of it.

  • Name the event’s zone everywhere a time appears — “14:00 CET”, not “14:00”. Put it in the page heading too, not only in a footnote.
  • Store times with a real zone identifier from the IANA time zone database — Europe/Berlin, not UTC+1. A fixed offset is wrong for half the year, and a spring conference scheduled in winter is exactly when daylight saving bites.
  • Convert in the browser, label clearly, and always keep the event’s own time visible. Showing a remote attendee their local time is helpful; replacing the official time with it is how two people in the same room end up disagreeing about when a session starts.

One more that costs nothing: offer a calendar file per session. An attendee who adds the session to their own calendar has delegated the conversion to software that already gets it right, and never asks you about it again.

Personal agenda and favouriting

“Let attendees build their own agenda” sounds like an obvious win and is often the wrong first investment. It is a genuine feature with real cost: it needs accounts or persistent local storage, a saved state that survives the programme changing underneath it, and a way to get the selection onto the phone the attendee carries on the day.

Judge it on scale. Below roughly three tracks, favouriting solves a problem nobody has — the whole day fits on one screen. Above five tracks it becomes genuinely useful, because the reader cannot hold the options in their head. In between, there is a cheaper version that captures most of the value: make every session individually linkable and addable to a calendar, and let the attendee’s own calendar be the personal agenda. No accounts, no saved state to corrupt, and it works offline in the venue.

If you do build it, decide one thing in advance: what the attendee sees when a favourited session is moved or cancelled. Silently dropping it is the failure that generates angry messages at 09:05.

Last-minute changes without breaking links

Programmes change in the final fortnight — a speaker drops out, two sessions swap rooms, a workshop moves to the afternoon. By then the agenda has been shared in newsletters, posted by speakers and indexed by search engines, so the test of a multi track schedule website is what it does to those links.

  • Never change a session URL. Edit the record in place. If a session genuinely becomes a different session, keep the old URL and redirect it — a 404 on a link a speaker posted is a cost you pay in their goodwill.
  • Put the change on the session, not only in a news post. A short dated note on the session page itself is what the person following an old link will actually see.
  • Date-stamp the agenda page with a visible “last updated” line. It tells a returning reader whether to re-read it, and tells you which version the complaint refers to.
  • Keep the structured data honest. If a session is cancelled, update its markup rather than deleting the page, so the cancellation is machine-readable too.
  • Leave the agenda up after the event. It is the strongest evidence of what you actually programmed, it is what next year’s speakers read before agreeing to appear, and it keeps earning search traffic long after the room has emptied.

Get the model right and the agenda stops being the page you dread editing. Start from the programme itself — our list of conference session ideas delegates actually remember is the input — and browse the events and conference themes for a build that ships the schedule templates rather than leaving you to invent them.