Three days is not one day, three times. What changes on day two, how to staff the middle, and the small structural choices that keep a long programme coherent.
Day one of a conference runs on adrenaline and rehearsal. Day two runs on whatever systems you built. Day three runs on whatever is left of your staff. The events that feel coherent across three days are not the ones with the best opening — they are the ones that planned for the middle.
Attendance on day two is typically 10–20% below day one, and it is not a sign of failure — it is travel, work and fatigue. What matters is which sessions lose people. If your strongest content is all on day one, you have taught your audience that later days are optional, and next year they will book accordingly.
Put one thing people cannot miss on each day. Not necessarily the keynote — a workshop, a results announcement, a panel that only works live.
A crew that works 6am to 11pm on day one is a crew making mistakes by day two afternoon. Build two shifts from the start, with a real handover: a ten-minute standing meeting at the shift change, and a single written log of what broke and what was promised to whom.
The registration desk needs the most cover on day one morning and the least thereafter. Redeploy — do not leave four people at an empty desk while the session rooms have none. Our piece on how many people you need has the shape of a crew by event size.
Something will move: a speaker misses a flight, a room floods, a session overruns. The failure is not the change — it is three versions of the truth. One person owns the schedule; changes go into the platform, and the platform is what the signage, the app and the desk read. If your agenda lives in a document, you now have to remember every place it was copied to.
This is the most practical reason to keep the programme in one system. Gathervo's agenda is the same data the attendee sees, the session chair sees and the check-in desk sees — see building an agenda without clashes.
A single survey at the end of three days produces a verdict on day three. Ask about sessions while they are fresh — a two-question rating at the end of each session, and one short daily prompt. You also get the chance to fix something on day two that annoyed people on day one, which is the only feedback that helps this year. See session feedback and ratings.
Five minutes at the start of each day, from the stage: what changed, what people asked for, what is different today. It costs nothing and it is the single clearest signal that somebody is running the event rather than watching it happen.
Running something long and complicated? Set it up free on Gathervo and keep three days on one programme.
Continue the discussion around this blog post.
You must be logged in to participate in the discussion.
Login to CommentStart the conversation by leaving the first comment on this post.