Why publish an online agenda for delegates?
An online agenda changes when the programme changes, which a printed one cannot. What it gives delegates, what it gives you, the honest version of the environmental case, and what you should still print anyway.
The short answer
Publish the agenda online so that when the programme changes, the version delegates are holding changes with it. A printed programme is correct on the day it goes to print and wrong from the first swapped speaker. Online, the same programme can be searched, filtered by day or track, saved as a personal schedule and exported to a calendar — and it never needs reprinting when the running order moves.
The rest of this guide is the four things that follow from that: what delegates get, what you get, what the environmental argument honestly is, and what you should still print.
What does it give delegates?
Most delegates read an agenda for a minute or two at a time, standing up, on a phone, deciding where to go next. Everything below is judged against that moment rather than against a desktop.
- The current version
- The one thing paper cannot do. Somebody checking at 14:20 sees what is happening at 14:30, not what was true when the programme went to the printer three weeks ago.
- Search and filters
- By day, by track, by format, by speaker. A twelve-track programme is unreadable as a list and perfectly readable as a filter.
- A personal schedule
- Save the sessions you are going to. What most delegates actually want is not the whole programme. It is their six sessions, in order, with the rooms.
- Calendar export
- The sessions in the calendar they already look at, with the room in the location field. Nobody has to retype anything, and nobody misses a session because they retyped it wrong.
- The room, attached to the session
- Building, floor, room. Wayfinding belongs with the session rather than on a separate map that also went to print in February.
- It works on a phone
- Which is where it will be read: in a foyer, in bright light, on a connection that is doing its best.
What does it give you?
The organiser case is simpler than the delegate case: one version, and no reprint cycle.
A printed programme sets the running order in concrete at the moment it goes to print, which is always earlier than the moment the running order stops moving. Everything after that is managed by erratum slip, by announcement, by a sheet of A4 taped to a door, or by nothing at all.
The second thing is the link. A programme that lives at a URL can go in the joining instructions, in the confirmation email, on the signage, on a slide and in the follow-up, and every one of those stays correct without anybody reissuing it.
And it removes a specific job from the week before the event: proofing, printing, checking the delivery, and finding out on the Monday that the Thursday keynote has changed.
What about the climate case?
There is a real environmental argument here and a dishonest one, and they are easy to confuse.
The dishonest version says digital is green. It is not free. A published agenda runs on servers and is read on devices that were manufactured and have to be charged. Anyone offering you a figure for how much carbon your event saved by not printing a programme is offering you an estimate with a great many assumptions inside it, and you are entitled to ask to see them.
The honest version is narrower and more useful. A printed delegate programme is a print run sized to the whole audience, produced from a document that is guaranteed to change, and thrown away within days. The waste is not really the paper. It is the certainty that some of it is wrong before it is handed out, and the reprints that follow.
Reprints are the part worth attacking. A single print run is a decision made once and budgeted for. A reprint is the same run again, at short notice, at a worse rate, usually because one speaker moved. An online agenda removes the reprint completely, because there is nothing to reissue.
The rest of the case is smaller and should be stated as such: less freight to the venue, fewer boxes to store and distribute, and no skip full of Tuesday's running order on Wednesday morning. These are real and they are modest, and describing them as modest is what makes them believable.
What an online agenda does not touch is the largest part of an event's footprint, which is people travelling to it. If sustainability is a genuine objective, the decisions that matter are about where the event is, what format it takes, and whether everyone needs to be in that city. Publishing the programme online is a cheap, honest improvement. It is not a climate strategy, and any supplier who presents it as one — including this one — has earned your scepticism.
What should you still print?
Going online is not the same as going paperless, and events that treat it as the same make themselves worse. Print the things that are true regardless of the running order, and the things people need when there is no signal.
- Badges
- Nobody has replaced these, and your event is not the place to try.
- A large-print run, on request
- Some delegates need paper and some need it larger. A programme that exists only on a phone is less accessible, not more. A short run costs almost nothing and is the difference between including somebody and not.
- Crew department views
- Production still prints. Every department view should print with its version and its timestamp on it, because venue wifi is what it is and a printed cue sheet has never once failed to load.
- One day-at-a-glance page
- If you print anything at all for delegates, print the smallest thing least likely to change: the shape of the day, the room names, the break times, and where the live programme lives.
How EventBlok approaches this
Everything above applies whatever you publish with. This section is what EventBlok specifically does.
The attendee portal is the event's public home: the full programme, speaker biographies and headshots, and venue, floor, room and online-space information. Delegates search and filter by day, track or format, save sessions as a personal agenda and export it to their calendar as ICS. It is mobile-first, keyboard navigable and screen-reader friendly, and it is legible on a phone in a bright foyer.
It reads the event rather than holding a copy of it. Change the agenda and the portal is already right — there is no republish step — and during the event it shows the current state of the day rather than the plan from this morning. Cues, comms and staging notes live on the same session and never reach the public page. The programme can also be embedded on your own site, where it stays in step with the event behind it.
EventBlok publishes no environmental impact figures and makes no sustainability claim. What it removes is the reprint.
The related reading is what makes a good attendee portal and managing live agenda changes.
Common questions
Is an online agenda better for the environment than a printed programme?
It removes a print run that was going to be reprinted, along with the freight, storage and disposal that went with it. It does not make an event low-carbon: the largest part of an event footprint is people travelling to it, and a published web page has an impact of its own. Treat it as a real but modest improvement, and be sceptical of anyone quoting a saving figure without showing their assumptions.
What should an online event agenda include?
The full programme by day and track, session titles with times and durations, the room in enough detail to find it, the speakers with their biographies, and a way to filter the programme and save sessions. During the event it should show the current state of the day rather than the plan from that morning.
Can delegates add sessions to their own calendar?
They should be able to. The EventBlok attendee portal exports a saved agenda to a calendar as ICS, which is the format every mainstream calendar application reads.
What if the venue wifi is poor?
Assume it will be. Publish the agenda online as the current version, and print one page unlikely to change: the shape of the day, the room names, the break times and where the live programme lives. Put the running order on signage inside the building, driven from the same record. Do not rely on delegates having a connection at the moment they need to know where to go.
Do we still need a printed programme at all?
Not the forty-page one. Keep badges, keep a short large-print run for delegates who need paper, keep the crew department views that production prints with a version and timestamp on them, and consider a single day-at-a-glance page. Print what stays true regardless of the running order.
Does publishing the agenda online mean it can change during the event?
That is the point of it. The value is not that it is a web page. It is that when a session moves, everyone reading it sees the move. If your online agenda needs a manual republish, you have a printed programme that happens to be on a screen.
Plan the event. Publish the programme. Run the show.
One event spine, many views. Build the programme once, then give every person the right live view of it.