How to read a conference programme and plan your days

Plenty of European conferences still print "programme", the British spelling, on their websites and in their apps. We use the American "program" below, but the document is the same, and it is usually the most read and least studied page of any event. People skim it for famous names, star a few sessions in the event app, and then spend two days walking between rooms they picked in thirty seconds.

A programme rewards a slower read. Its structure shows how the organizers expect the days to flow, where the crowds will be, which sessions will be on video next month and which only exist in the room. This guide walks through reading one properly in three passes and turning it into a plan you can follow on the day. For the work before and after the event (setting goals, keeping notes, reporting back), see our conference value checklist.

Contains affiliate links. As an Amazon Associate I earn from qualifying purchases.

First pass: read the structure, not the sessions

Before you look at a single title, look at the shape. Open the full grid rather than the filtered "for you" view in the event app, and note:

• How many days there are, and whether the last one is shorter. Many events wind down by mid-afternoon on the final day, which changes your travel plans.
• How many tracks run in parallel. With three, you see a third of the program at most. With eight, you see very little live and should plan around recordings.
• Whether tracks are themes ("Android", "Design", "Growth") or levels ("Foundations", "Deep dive"). Themed tracks often keep one room all day; level-based tracks mix topics.
• Session lengths. A grid of 40-minute talks with 10-minute changeovers feels very different from 25-minute talks back to back.
• Where the breaks are and how long they last. Fifteen minutes is a toilet and a coffee. Thirty minutes is a conversation.
• The room list and, if published, the room sizes and the venue map.

That last point catches people every time. A popular topic in a small room fills before the previous session ends, and in a large venue the walk between halls can take most of a short changeover.

Second pass: decode each listing

Session listings follow a pattern, and every part of one carries information.

An abstract that names a specific problem ("cutting cold start time on low-memory Android phones, with a team of four") usually signals a talk built on real work. One made of general nouns ("the future of mobile experiences") usually signals a talk built on slides. Neither is a guarantee, but the pattern holds more often than not.

Third pass: place the fixed points

Some sessions decide the rest of your plan, so place them before anything else.

Workshops come first. They usually need separate booking, sometimes through a different form or at a different moment from the main registration, and seats are limited. When you book, read the prerequisites closely. A workshop that expects a recent Xcode, or Android Studio with particular emulator images, means downloads of many gigabytes. Do them at home, not on conference Wi-Fi the morning of the session. Bring a charger and find out whether the room has sockets at the tables.

Next come the sessions that only make sense live: panels where you want to ask a question, small-room talks unlikely to be filmed, labs or office hours with a platform team, and any session whose speaker you hope to talk to afterward. Keynotes count as fixed points too, for a different reason: everyone will be discussing them at lunch.

Recordings change the math

Find out what the event records before you plan around talks. If there is a video channel from the previous edition, look at it. Common patterns: main-stage and large-room talks are filmed, workshops and small rooms often aren't, panels vary. Videos may appear within days, after several weeks, or only for people who attended.

A talk that will be recorded becomes a candidate for your watch-later list, and its slot opens up for something that won't exist afterward. Keep that list honest, though. A recording you never watch is worth less than a talk you half heard live. Put the list in your calendar for the two weeks after the event, one talk per lunch break, and it will actually get watched.

Leave buffers on purpose

A plan with every slot filled fails by mid-morning on day one. Sessions overrun, rooms fill, a conversation goes somewhere good. Build in slack:

1. Leave one slot empty in each half-day for overruns, conversations and urgent email.
2. Keep the first slot after lunch light; it is the hardest one to concentrate in.
3. On multi-day events, plan day two on the evening of day one, using what you have learned about the rooms and the crowds.
4. Don't schedule anything demanding for the final afternoon if you have a train or flight to catch. You will be watching the clock.
5. Check the event app each morning for room changes and cancellations, and switch on its notifications.

The hallway track belongs inside this plan, not outside it. An empty slot near the coffee, right after a session on a topic you care about, is when the speaker and the people who asked questions are still standing around. If there is someone specific you want to meet, that is the moment to find them.

Put it on one page

Once the three passes are done, compress the result onto one page or one note per day: time, room, session, and a few words on why you chose it. Mark booked workshops and must-see sessions so they stand out, note an alternative for the slots most likely to fill, and add the watch-later list at the bottom.

That page is what you check between sessions, not the full grid. When a room is full or a talk disappoints, the decision is already made: go to the alternative, or take the buffer early. For the practical side of getting there (travel, badges, Wi-Fi and power), our event info guide covers the logistics, and the mobile event schedule shows when the big recurring events usually fall.

Questions

How many sessions should I plan per day?

Fewer than the grid allows. With a buffer in each half-day and a proper lunch, four to six sessions on a full day is a realistic plan, and you will remember more of them than of ten.

Is the event app enough to plan with?

It is good for live changes, reminders and room maps, but its personalized views hide the structure. Read the full grid first, then use the app's favorites to mirror your one-page plan.

What if the session I picked is full?

Go to the alternative you marked, or treat it as an early buffer. Some events stream big sessions to an overflow room or allow standing at the back, so ask a volunteer at the door before you give up.

Should I skip the keynote to avoid the crowd?

Usually not. Keynotes are almost always recorded, but they set the topics people talk about for the rest of the event, and having seen it live gives you an easy opening at every lunch table.