The Conference and Summit Playbook: Plan the Programme Around the Audience

Define what the conference is there to change

A conference can inform, convene, teach, debate or help people make decisions. These purposes often appear together in a brief, but they do not require the same programme. Start by choosing a primary objective and identifying the audience groups it serves. Ask what those guests should understand or be able to do afterwards, and what would make the time worthwhile from their perspective.

Translate the objective into programme tests. If discussion matters, the agenda needs time and a credible method for it. If guests must compare options, they need relevant information before the comparison. If relationships matter, networking should have a purpose, a setting and enough space in the programme to happen. A large speaker list is not evidence that these needs have been met.

The client sponsor approves the objective. A programme owner then maintains an agenda brief describing audience needs, session purposes and constraints. The event lead connects this brief to the venue, hospitality and delivery plan. Make the first approval gate a decision about purpose and audience, before design begins. This prevents the number of available presentation slots from becoming the organising principle of the event. Use Build an Event Brief That Makes Decisions Easier to record the choices and unresolved assumptions.

Build an agenda with a visible argument

Treat the agenda as a sequence of ideas and actions. What context do guests need first? Which questions follow naturally? Where should they hear different perspectives, discuss a problem or reflect? Name the purpose of each session in a sentence. If two sessions do the same work, combine them or explain the distinction. If an important objective has no session, the programme has a gap even when every minute is occupied.

Give each session a content owner, intended audience, format and required output. A panel may surface different views; a workshop may produce a set of proposals; a keynote may establish a shared frame. These are intended outputs, not promised outcomes. Ask the owner how guests participate and what preparation the format requires.

Review the day from the guest's seat. Allow realistic movement, breaks and orientation between different activities. No universal session length guarantees attention. Programme duration should reflect audience needs, content complexity, participation and the practical setting. The agenda approval gate should therefore test the whole journey, not just individual speaker availability. Keep a visible distinction between confirmed sessions, provisional placeholders and optional additions so a late request does not silently consume the time intended for breaks or discussion.

Use the 90-day window to sequence decisions

This is an illustrative 90-day framework, not a prescribed lead time. An event with complex travel, procurement or content development may need more time, while another may have different constraints. Begin by identifying fixed dates and the approvals that release dependent work.

In the first part of the window, agree the objective, audience, budget assumptions, venue requirements and programme architecture. During the middle period, confirm session owners, speaker invitations, registration approach and room allocations. As the event approaches, turn the agenda into a detailed running order, gather content, close guest-information deadlines and test room transitions. The final period is for coordinated checks, briefings and resolved exceptions rather than discovering that a panel has no moderator.

The event lead maintains the integrated schedule; the programme owner maintains content readiness. The venue and production leads confirm what must be decided before layouts, checks and rehearsals can proceed. Each milestone needs an approver and a consequence if missed. For example, a breakout format decision may determine room furniture and technical requirements. A date in a spreadsheet is not enough: record what can proceed after approval and what remains blocked. Link this plan to The Event Critical Path: What Can Delay an Entire Production? when reviewing delayed dependencies.

Choose the room layout from the session needs

Describe the work the room must support before choosing a stage style. Will guests mostly watch, take notes, discuss in groups, move between stations or alternate between these modes? The answer affects seating, sightlines, stage relationships and circulation. A visually impressive stage may reduce space needed for audience activity or place speakers too far from a discussion setting.

At client level, the stage brief should identify the number and type of presenters, moderated conversations, presentation content, speaker movement and accessibility needs. Ask the venue and production specialists to translate these requirements into an assessed layout and appropriate technical proposal. This guide does not prescribe stage dimensions, screen sizes or safe capacities. Those decisions require the actual room, content and responsible specialist review.

Walk the proposed layout from several guest positions, including less favourable ones. Check the experience of seeing the speaker, following content, joining a conversation and reaching exits and support areas. Identify where production control, cameras if used and guest routes interact. The layout gate needs a versioned plan, venue confirmation and agreement that the programme can operate within it. Use How to Evaluate a Venue Before Signing the Contract for the room and access review, and the production guide for technical decisions.

Make speaker management a content and movement plan

A speaker register should include the session purpose, contact owner, arrival requirements, presentation status, rehearsal needs and the next action. Separate a speaker's acceptance from their readiness. A confirmed calendar invitation does not establish that content has been approved, travel is settled or the speaker understands the session format.

Send a concise brief that explains the audience, purpose, available time, format and submission process. Ask for the information needed to introduce the speaker accurately and to support their participation. Confirm who approves biography, name pronunciation and any public description. Collect practical requirements through the agreed route rather than allowing separate supplier conversations to create unrecorded commitments.

Assign a speaker liaison to track arrival, preparation and handover to the programme lead. The liaison should know where the speaker waits and how they reach the stage, but should not independently change the agenda. If a speaker is late, establish the facts and take the decision through the programme owner and event lead. The speaker gate combines content readiness, practical arrangements and a confirmed handover. For late-file decisions, use The CEO Changes Their Presentation Five Minutes Before Stage; for arrival and holding arrangements, use Travel, VIPs and Departure: Connect Every Guest Handover.

Design panels so conversation has a structure

A panel needs a question worth discussing, not merely several people available at the same time. Give the moderator a brief with the purpose, audience context, themes, boundaries and intended close. Ask what each participant contributes and where their views may differ. Repetition often starts with an unclear brief rather than an insufficiently energetic moderator.

Decide how audience questions enter the discussion. A staffed microphone, written prompts or a digital channel each has practical consequences. The method needs an owner who gathers and routes questions, a moderator who selects or groups them and a clear explanation to guests. Do not promise that every submitted question will be answered during a limited session. Agree a route for appropriate unanswered questions where follow-up is part of the scope.

Brief participants on introductions, the discussion sequence and the moderator's role in keeping time. Plan the closing question before the session begins so the conversation can reach a useful end. The panel readiness gate checks moderator preparation, participant availability, question handling and the handover to the next session. Technology can carry questions, but it cannot decide the editorial priorities of the conversation. The client programme owner must approve those priorities and any sensitive-topic boundaries.

Give breakouts their own operating brief

Breakouts are separate experiences linked to the main programme. Each needs a clear audience, purpose, host, room, timing and output. Decide whether guests choose freely, register in advance or are assigned to groups. Explain that choice before people reach a corridor with several doors. If a session has limited availability, the event team needs a confirmed approach for allocating places and handling alternatives.

Prepare a short room brief covering layout, content, facilitation, guest support and reset. The venue confirms the approved use and capacity of each layout; relevant suppliers confirm requirements. A breakout cannot be treated as a smaller main room if it uses a different format. Group work may need materials, a facilitator and a way to capture outputs rather than a presentation setup alone.

Map movement between sessions and back to the plenary. Ask how late arrivals find the right room and what happens if one breakout overruns. Name the person who signals closing and who can approve a timing change. The breakout gate should confirm room readiness, host briefing, guest communication and output ownership. Without a recipient for the discussion notes, a promised workshop output can disappear into an uncollected sheet at the end of the session.

Plan registration from arrival patterns, not totals

Registration demand depends on when guests arrive, what each interaction requires and how exceptions are handled. A total of 500 registrations does not tell you whether arrivals are spread across an hour or concentrated after a shared transfer. Ask the guest lead to model the likely pattern using the actual invitation, transport and programme arrangements.

Define the normal transaction and the exception route. A guest with a confirmed record should not wait behind a lengthy name correction if a separate help process is available. Test the intended system with realistic tasks, including an unreadable confirmation, a missing record and a late change. Ask the responsible provider to assess equipment, connectivity and fallback arrangements; do not assume that a QR code removes the need for guest support.

The registration plan should identify the queue area, information points, onward route and the person monitoring conditions. The venue must review the physical arrangement. Never promise queue-free arrival or prescribe a universal desk ratio. Instead, agree how the team will observe demand, communicate delays and activate a reviewed alternative. Invitation timing and clear pre-arrival information are part of the same plan. See From Invitation to Registration: Plan the Arrival Before the Queue for the hypothetical simultaneous-arrival scenario and an editable test sheet.

Protect attention through transitions and hospitality

The programme includes the moments between sessions. Guests need to understand where to go, whether they have enough time and what will happen when they return. Build these instructions into host scripts, signage and staff briefings. A break should not require guests to choose between refreshments, toilets and reaching the next room without knowing the expected return time.

Coordinate coffee and meal service with the venue's banquet lead. Confirm where guests approach, collect and move away, and how service staff replenish and clear without conflicting with guest routes. Ask the programme lead to communicate likely changes early enough for hospitality to respond. The venue should assess the layout and service arrangement; the event team connects it to the running order.

If a conference becomes dinner, treat the change as a designed transition. Identify the receiving space, any room reset, seating information and where guests can wait if readiness changes. Do not announce movement before the receiving lead confirms it can begin. A hypothetical 500-guest transfer deserves a coordinated release and reception plan, not an assumption that everyone will find the next room. Detailed attention, networking and transition decisions are developed in Networking, Attention and the Spaces Between Sessions.

Understand what changes at different audience scales

The following counts are illustrative scenarios, not venue capacities, service rates or staffing prescriptions. A 100-person conference may still have complex content and access needs; a larger audience does not automatically require a more elaborate programme. Start with what the audience must do and ask how scale changes the dependencies.

For a hypothetical 100 guests, direct discussion may be practical to explore, with clear facilitation and support. At 500, simultaneous registration, room changes and break demand may become important to test. At 1,000, parallel sessions and multiple guest groups can create additional version, signage and communication decisions. At 5,000, the planning team may need to evaluate distinct audience zones, distributed support and coordinated transport arrangements with the venue and relevant specialists.

Use each scenario to ask different questions, not to select a fixed staffing table. What information must reach everyone? Which decisions can be delegated locally? How will the event lead know that a receiving area is ready? If the guest count changes, obtain renewed review of the layout, hospitality, registration, technical scope and emergency arrangements from their responsible owners. The client approves the revised scope only after those consequences are visible. A larger invitation list is not just an additional meal order.

Prepare for a keynote or agenda change

Imagine a keynote speaker reporting a travel delay shortly before their session. This is hypothetical. The risk is that guests and delivery teams continue preparing for an appearance that is no longer feasible at the planned time. A common failure is to fill the gap with unbriefed content or to move sessions independently without checking speakers, hospitality and room commitments.

The speaker liaison confirms the best available arrival information without turning an estimate into a promise. The programme owner identifies approved alternatives, while the event lead checks their effects on the running order. A moderator-led discussion, an available session moved earlier or a revised break may be considered only when the relevant people and receiving services can support it. The client approver decides where required.

The programme lead issues one updated sequence to the host and affected leads. Give guests a concise explanation of the confirmed change, not a speculative arrival time. Set a next decision point if the delay remains uncertain. The contingency is an approved programme path that remains useful; the intended outcome is coherent communication and a workable day. The production operations scenario library covers the detailed delayed-keynote recovery interface, while this playbook keeps the programme decision visible.

Control content versions across the programme

Create a presentation register linking each file to a speaker, session, approver and checked version. Include supporting videos, holding visuals and any material used in breakouts. Distinguish content approval from technical checking: a file can be approved to say something and still require assessment in the actual presentation setup.

Agree a normal submission route and a late-change route. The programme owner and content approver establish what the message must be; the presentation owner coordinates receipt and checking; the show caller or programme lead confirms when it is used. In small teams these responsibilities may overlap, but a last-minute replacement should still produce one clear instruction.

Use rehearsal to check transitions between speakers, panels and room states as well as individual files. Record exceptions and fallbacks. An earlier deck is a valid fallback only if its content remains approved; it should not be used automatically when the change corrects a material error. After the event, mark the version actually presented and seek approval for any distribution. A conference resource pack should not accidentally include an abandoned draft because it was the easiest file to find. See The CEO Changes Their Presentation Five Minutes Before Stage for the exception process.

Measure the programme against the brief

Decide what evidence is useful before the event, then keep collection proportionate. Session attendance, relevant guest questions, requested follow-up and specific feedback may each illuminate part of the objective. None independently proves that the conference achieved a business result. Agree who collects the evidence, when it is reviewed and what its limitations are.

A workshop intended to produce priorities needs a recipient for its output and a decision about what happens next. A conference intended to inform needs questions that test whether the content was useful, not only whether the room was comfortable. Operational observations should also be captured: where guests asked for directions, which transitions caused confusion and where the plan depended on an unresolved assumption.

The post-event owner consolidates an evidence record and an action list. Separate verified facts from interpretations and from proposed improvements. Assign unanswered questions, promised materials and commercial follow-ups to named owners. A debrief is complete when decisions for the next brief are visible, not merely when photographs have been distributed. Use Make the Post-Event Review Useful for the Next Brief and Gifting and Post-Event Communication: Finish the Guest Promise to connect reporting with the guest commitments made during the programme.

Questions before you approve the conference

How long should a session be? There is no universal duration. Set the time from its purpose, format, content and audience needs, then test the complete agenda with movement and breaks included. More content does not automatically justify a longer session.

Should every conference have breakouts? Only if they serve the audience and can be supported with clear room, host and output plans. A breakout without a useful task adds movement without necessarily adding value.

Can registration be guaranteed to have no queues? No planning claim should assume that. Test arrival patterns and transactions, assess space with the venue and agree how conditions will be monitored and handled.

What belongs in the approval pack? The objective, agenda brief, current programme, room layouts, speaker register, content register, guest plan, hospitality timings, operating responsibilities and open exceptions. Confirm which decisions are still provisional and who may change them. Start with the agenda purpose worksheet before requesting isolated quotations, so suppliers can respond to a connected requirement. Discuss your conference at hello@threesixzero.live.