A programme is the schedule that decides whether people learn something or just sit through slots.

A programme built to fill slots and a programme built around what attendees came to learn look similar on paper: same number of sessions, same room, same clock. The difference only becomes visible once you read the agenda as an outcome, and it is visible almost immediately. One version answers the question "who offered to speak, and where do we put them?" The other answers "what does someone in that seat need to be able to do by four o'clock, and what sequence of sessions gets them there?" Those two questions produce different programmes even when they draw on the same pool of speakers.

Why speaker-first programming drifts toward a vendor showcase

Start from who is offering to speak, and the loudest offers usually come from people with something to sell: a vendor demonstrating a product, a sponsor exercising a slot written into their contract, a consultant pitching a case study that is really an advert. None of that is dishonest on its own, but a programme assembled by accepting the offers as they arrive drifts toward those interests without anyone deciding it should. The call for papers (CFP) makes this worse if it runs without a brief: an open call with no stated audience need selects for whoever pitches hardest.

Starting from what attendees came for

The alternative is to write down, before a single speaker is approached, what someone attending should be able to explain, decide or do differently by the end of the day. That sentence becomes the filter. A session pitch, a sponsor slot or a CFP submission gets tested against it: does this session move someone toward that outcome, or does it just fill fifty minutes? Working this way means speakers are found to fill a brief, and it is the single clearest way to keep a curated programme from reading as a sponsor showcase even when sponsorship is funding part of the event.

Where the audience's needs shape the format itself

The outcome sentence should also say who is in the room, because that determines what a session can reasonably ask of them. An audience with a wide range of access needs changes which formats are workable long before the running order is finalised: a panel with no captioning (CART) plan, or a workshop that assumes everyone can stand for ninety minutes, has already excluded part of the room the outcome sentence was written for. That decision belongs at the point the programme is shaped. See Accessibility and Codes of Conduct for what a reasonable adjustment looks like in practice, and Finding, Choosing and Looking After Speakers for how the same audience-first brief is used to select speakers.

A session format sets the ceiling on how much material a slot can carry, but pacing decides whether the audience is still with you when it gets there. Most programme designers work on the assumption that a single speaker holds a room for around 30 to 45 minutes before attention starts to drift, whatever the subject, and they design blocks around that limit. A 60-minute keynote with no structural break in it usually serves the speaker's ego more than the audience's retention.

Why breaks are a programme decision

A break is not the gap between the parts of the programme that matter. It is where people process what they just heard, decide whether the next session is worth their time, and have the corridor conversations that most attendees rate as the most useful part of the day. Cutting break length to fit in one more session is a trade: you gain fifteen minutes of content and lose the thing attendees came back for. That trade-off deserves to be made deliberately.

Break placement also carries an accessibility duty that belongs in the programme design stage. Under the Equality Act 2010, organisers have a duty to make reasonable adjustments, and for some attendees that means a genuine rest break. Live captioners (CART) working a full day need scheduled breaks to maintain accuracy, and a wheelchair user moving between rooms on different floors needs more transition time than the ten minutes built into a typical changeover. Build the break length around the slowest reasonable transition.

What a schedule that runs too tight actually costs

A programme with no slack fails at the first delay, and every conference has at least one. The usual sequence is predictable:

• A morning session overruns by ten minutes because the Q&A ran long.
• The break is cut to protect the next start time, so nobody actually gets to the toilet queue, let alone a conversation.
• The next session starts late anyway, because a room full of people takes longer to resettle than five minutes.
• By mid-afternoon the whole day is running behind, and the final session, often the one attendees were most looking forward to, gets shortened or cut.

The fix is not tighter timekeeping. It is building buffer into the schedule from the start: a genuinely unscheduled 10 to 15 minutes somewhere in the morning and afternoon that can absorb overrun without touching the breaks that were already the minimum. A sample timeline showing where that buffer sits is worked through in the worked examples and templates section. Where the accessibility and conduct decisions around breaks need more detail than fits here, they are covered in full in accessibility and codes of conduct.

Ask someone what they remember from a conference and the answer is rarely a slide. It's the conversation in the queue for coffee, the argument that carried on from a panel into the corridor, or the dinner conversation that turned into a job lead six months later. None of that sits on the printed agenda, and that is why organisers plan it least: it looks like dead time between the real content, when for a lot of attendees it is the real content.

The corridor is not dead time

A break has to do two jobs at once: let the room clear for the next session, and give people the minutes they need to finish the conversation the last session started. If the second job never gets scheduled time, it happens anyway, only later, eating into the start of whatever comes next. A programme with no room for it is not more efficient, it just moves the same conversations into the sessions they were supposed to precede.

The lunch queue as a design decision

Lunch is a scheduling decision as much as a catering one. A buffet queue for a couple of hundred people does not clear in five minutes, so if the lunch break is 45 minutes and 20 of those go on queuing, the actual break people get is 25. Boxed lunches, staggered release by badge or track, or food stations spread round the room all shorten the queue, and each carries a different cost: Venues, Catering and the Costs Nobody Budgets For covers how catering style moves the budget.

Seating matters as much as the queue. Long shared tables push people who don't know each other into conversation; small tables let existing groups stay closed. Neither is wrong, but the layout should be chosen on purpose.

Naming the corridor track

Some programmes block this time out explicitly, calling it a corridor track: a slot on the printed agenda with no session attached, set aside for the version of the conference that happens between the scheduled ones. Naming it does something a silent gap doesn't. It tells attendees the time is intended, and it stops a programme committee filling it with one more session because the slot was sitting empty.

The evening event: purpose and cost

An evening event extends the networking the corridor and lunch queue started, and how much value it delivers depends on decisions made well before the night itself. A drinks reception with no seating and background noise loud enough to block conversation gets the cost without the benefit; a dinner with assigned tables and a clear finish time usually gets more benefit for a similar spend. Attendance should be clearly optional and signposted as such, particularly for anyone travelling in for the day who needs to catch a last train.

Making the space workable for everyone in the room

The same evening event needs a quiet space attendees can find without having to ask, and a code of conduct that applies at the bar as much as in the panel discussion. Alcohol and informal settings are where conduct issues most often surface. Accessibility and Codes of Conduct sets out what a workable policy looks like and where it needs to be visible, including in the parts of the programme that never appear on the agenda.

Why programmes end up mixing the two

A call for papers (CFP), an open invitation for anyone to submit a session proposal, brings in ideas the organiser would not have thought to look for and signals that the programme is open. But CFP submissions alone rarely produce a strong programme: they skew towards people with the time and confidence to write a proposal, they say nothing about someone's ability to hold a room, and no CFP process reliably surfaces the person who happens to have built the thing everyone is talking about this year. Curation, the organiser actively inviting people, fixes both problems but reintroduces a different risk: the invite list becomes a list of favours, the loudest sponsor, last year's speakers, whoever asked first.

Where sponsor influence actually gets in

Pay-to-speak, a slot sold or bundled into a sponsorship package, is the risk that does the most damage to a programme's credibility and the one that is easiest to hide. It rarely appears as an explicit line item. It turns up as a clause in the sponsorship prospectus, agreed before the CFP even opens, giving the platinum sponsor a twenty-minute slot regardless of what else is submitted. Attendees notice. A sponsor talk placed in the same session format as the invited experts, with nothing in the agenda to say which is which, reads as compromised the moment someone points it out. The answer is not to refuse sponsor content but to separate it: its own track, its own labelled slot, named in the agenda as what it is.

Running both processes under one editorial line

Keep the CFP and the invited list under a single reviewing decision.

• Set the ratio before submissions open, roughly two-thirds curated to one-third open call is a common starting point, so invited names are not squeezed out by volume and the CFP is not just window dressing.
• Review CFP submissions blind where the format allows it, stripping names and employer before scoring, so a familiar name from a large company does not take a slot a stronger unknown proposal deserved.
• Score against the same criteria you would use for an invited speaker: relevance to what attendees actually asked for, and evidence they can hold a room, a recording or a track record.
• Publish roughly how many slots are open and who is deciding. A CFP that never says how many places actually exist is asking for submissions it has no intention of using.

What it looks like from the agenda

A programme built to fill slots is not the same as a programme built around what attendees came to learn, and the difference is visible in the agenda itself rather than in anything the organiser says about it. Look at who fills the best slots, whether every session format on the day is the same hour of slides regardless of the speaker, and whether sponsor sessions are distinguishable from editorial ones without checking the small print. None of that shows up in a mission statement. It shows up in the running order.

Speakers weighing up whether a particular CFP is a genuine open process can check Speaking at a Conference: Getting Selected and Being Good. Organisers building the invited side of the list, and deciding what to ask of speakers once selected, can consult Finding, Choosing and Looking After Speakers.