How to plan and moderate a panel discussion people will pay to hear

You've booked respected speakers for your conference, put their faces on the event page, and given them an hour on stage. Now you need that hour to be worth attending. If everyone answers the same broad questions with the same advice, the audience has paid to hear a conversation they could have predicted.

A good panel discussion lets people examine a real decision through different kinds of experience. Plan the question before the invitations, choose speakers who can explain their decisions, and appoint a moderator who will ask follow-ups and interrupt when necessary. The preparation should help the conversation go somewhere useful while leaving room for answers you didn't expect.

This guide covers how to build that session, brief the panelists, prepare questions, manage the time and handle the awkward moments. We'll use a fictional panel about whether a paid conference should add a second day. Its people, examples and timings are planning choices, not findings from a real event.

Decide what the audience is paying to understand

A panel discussion is a moderated conversation between invited speakers in front of an audience. Its advantage is that the audience can hear people challenge and qualify each other's answers. That makes it useful when a decision depends on circumstances, experience or competing priorities. You need more than several speakers who happen to work in the same industry.

Take our example. "The future of conferences" could produce an hour of agreeable predictions. "Should your annual conference add a second day?" creates a decision that someone in the audience might face. One speaker can explain why they expanded. Another can explain why their buyers resisted. A producer can examine what changes operationally when the programme grows.

The useful outcome is an audience member understanding which conditions would justify expansion for their own event. You aren't promising that every operator should add a day, or that the panel will settle the issue for everyone. You're promising a clearer way to judge demand, additional costs and the experience buyers would receive.

Write the programme description around that outcome. Tell prospective attendees whose experience they'll hear, what question the moderator will test and how audience questions enter the discussion. A buyer should understand the session without knowing the speakers personally. Their names can build confidence once the description explains why the conversation matters.

Check whether a panel is the right format before announcing it. If the answer requires someone to demonstrate a budgeting method, a workshop may serve the audience better. If the value comes from delegates comparing their own cases, consider a conference roundtable discussion. Choose a panel when the exchange between your invited speakers is the reason to attend.

Build a panel with useful differences

Start with the experience you need, then look for the people who have it. For the second-day discussion, we'd invite a conference organizer who has expanded, a person responsible for approving delegate travel and a producer who understands delivery costs. Each can challenge something the others might take for granted. Their roles explain why they're on the stage.

These are illustrative roles, not a required combination for every panel. You might need a practitioner and a researcher, or an operator working at a different scale. Look for differences that change the answer. Several executives from similar businesses can still bring distinct views, but you need to establish those differences before you write their introductions.

Ask a prospective panelist about a specific decision in a short conversation. "When did an extra day stop making sense for your buyers?" tells you more than "Would you speak about conference growth?" Listen for whether they explain circumstances, answer the actual question and respond when you ask for clarification. A polished speech clip won't show all of that.

Don't recruit disagreement as entertainment. Someone can disagree with expansion because their delegates face travel restrictions, while another supports it because their audience needs practical training. That's useful. Booking a person solely to make an inflammatory claim creates a different programme, and your audience deserves to know if that's what you're selling.

Consider whose relevant experience is missing from your usual contact list. Broaden the search across backgrounds, organizations and career stages without asking anyone to represent an entire group. Invite each person for what they can contribute to this question. Explain that contribution in your outreach so they can decide whether they're a good fit.

Confirm preparation, availability and commercial terms before using a name in promotion. Your conference speaker booking process should cover the actual session role, including the preparation call. A speaker who agrees to a short interview hasn't necessarily agreed to moderate a panel or provide a separate presentation.

Budget for the work behind the conversation

A panel can look inexpensive because nobody is preparing a full presentation. You still need to cost the moderator's preparation, speaker arrangements, production support and the room. Put those costs in your event budget before treating the format as an easy way to fill an hour. Unpaid preparation still uses somebody's working time.

For a standalone ticketed panel, check what else buyers receive. Is the programme only the discussion, or does it include a hosted reception and access to follow-up material? Describe the actual offer and budget for each promise. Don't add a networking reception to the sales description until someone owns its staffing, space and delivery costs.

For a panel within a larger conference, avoid pretending you can attribute the full ticket price to that hour. Judge its contribution against the programme you promised and the resources it requires. A session can justify its place through useful learning even when it doesn't generate a separate payment. The commercial question is whether the programme supports an event people value enough to buy again.

Make speaker obligations explicit when discussing fees. The preparation call, live session and any later interview are different commitments. If your budget cannot support everything, reduce the request before confirmation. Asking for additional work after a speaker has accepted creates a problem that a friendly reminder won't solve.

Give the moderator authority before the event

The moderator needs to understand the subject well enough to recognise a vague answer, a contradiction or a claim that needs evidence. They also need to listen while managing the room. A strong presenter may enjoy explaining their own ideas so much that they struggle to leave space for other people. Ask how they'd handle that responsibility.

For our example, the moderator should understand how programme length affects costs and buying decisions. They don't need to know more than every panelist. They do need to notice when someone claims extra sessions automatically justify a higher ticket price, then ask what buyers actually valued and how the organizer checked that assumption.

Toastmasters' panel moderation guidance puts the audience's understanding ahead of panelists' personal agendas and recommends probing questions. That's the standard to agree with your moderator. Their role includes asking an awkward follow-up when it helps the audience understand the answer, even if a speaker would prefer to move on.

Tell every panelist that the moderator can interrupt, redirect a question and invite another speaker into the conversation. Agree how the timekeeper will signal changes. If the organizer privately promises a sponsor uninterrupted speaking time, the moderator needs to know before accepting the brief. You can't ask them to manage rules that somebody else has already waived.

Agree who handles conduct problems and production failures. A moderator can stop a personal attack and return the discussion to the question. They shouldn't also have to leave the stage to find the event manager. Name the person who can respond when the situation needs action beyond the conversation itself.

Prepare the conversation without writing the answers

Speak to panelists individually before bringing everyone together. Ask what they can explain from direct experience, where their knowledge ends and what they can't discuss publicly. A useful limitation might concern a client agreement, an unpublished result or identifying details. Knowing that beforehand lets the moderator ask a fair question without ambushing someone into a disclosure.

Then hold a joint preparation conversation. Introduce the audience, the central question and the differences you hope to examine. Explain the running order, audience questions, recording arrangements and the moderator's authority. Ask panelists which assumptions in the proposed discussion need correcting. This is your chance to discover that a promising question rests on something none of them believes.

The University of Iowa's career panel toolkit recommends confirming logistics and sharing discussion questions with speakers in advance. Its setting is student career events. The preparation principle also helps a paid conference, where panelists need enough context to bring relevant examples and understand what the audience has been promised.

Share the themes and likely opening questions, but don't require rehearsed answers to every possible prompt. A speaker should know that you'll discuss buyer demand and additional delivery costs. They don't need to know the follow-up you'll ask after another panelist challenges their example. Listening to that exchange is part of what makes the session valuable.

Ask each speaker to prepare a case they can discuss accurately. For our panel, that might be a decision to add practical training on another day, the evidence used and what remained uncertain. If they mention a result, ask what it measured and whether they can substantiate it. You don't need an impressive number if the decision itself is instructive.

Send a short written brief after the call. Keep the essentials easy to find, including arrival time, session location, contact person, pronunciation, access arrangements and any agreed limits. Your conference speaker briefing can hold those logistics. The moderator's separate notes should focus on questions and follow-ups rather than reproducing the entire production plan.

Write questions that produce explanations

Start with a question that gives the audience something concrete. "What decision made you consider a second day?" is easier to answer usefully than "What are your thoughts on growth?" Direct it to the person with the relevant experience. You don't have to ask every speaker for an opening opinion before anyone can examine the first answer.

Follow the sequence of the decision. Ask what changed, what information the team had, which alternative they considered and why they chose their approach. Then bring in a different perspective. The person approving delegate travel might explain why the same programme would be difficult to justify for their team. Now the audience can hear where the reasoning differs.

Useful follow-up questions include these:

• "What did buyers tell you before you committed to the extra day?"

• "Which additional cost did you underestimate?"

• "What would have changed your decision?"

• "Would that still work for delegates paying for their own travel?"

• "Which part of that example would you avoid generalising?"

Those questions are prompts for our fictional subject, not a script for every panel. Adapt them to the actual decision and the speakers' experience. The important part is the request for an explanation. "Tell us more" may help occasionally, but it doesn't tell a speaker which part of their answer needs development.

Prepare a challenge to the attractive answer. Suppose everyone agrees that a longer conference offers more networking. Ask how they'd distinguish useful additional meetings from another evening away from work. Someone may explain that their delegates wanted structured appointments. Another may say buyers preferred a shorter event. The moderator should identify that difference rather than summarising both as enthusiasm for networking.

Keep factual disagreement separate from a difference in preference. If a speaker cites research, ask which study and what it measured. If they describe their own event, make that scope clear. You can challenge an unsupported generalisation without turning the panel into a surprise examination. Tell speakers during preparation that the audience will need that context.

Try a brief rehearsal using conflicting answers. In our fictional panel, the organizer says buyers asked for more time together. The travel buyer replies that another day away would make approval harder. The moderator could ask, "Are buyers asking for a longer programme, or more opportunities to meet within the existing day?" That question checks whether the speakers are discussing the same need.

Then ask each person what information would resolve it. The organizer might need to separate requests for training from requests for meetings. The buyer might explain which activities their team could justify attending. Those are possible rehearsal answers, not claims about delegate behaviour. The point is to practise following a disagreement far enough to make it useful, instead of immediately asking the next person whether they agree. Listen for the important missing assumption first.

Plan the hour before adding another speaker

For this example, we'd use three panelists and a moderator in a sixty minute session. That gives enough people to examine different perspectives while allowing follow-ups. It isn't a universal panel size. Work backwards from the time and the conversation you want before accepting another invitation or promising a sponsor another place on stage.

Here's our suggested allocation. Four minutes cover the welcome, question, short introductions and participation instructions. Eight minutes establish the speakers' relevant cases. Twenty-four minutes examine the main decision and test differences. Nineteen minutes go to audience questions, and five minutes remain for conclusions and the handover. Together they total sixty minutes.

These timings are our planning example, not an industry benchmark. The chart makes the allocation visible so you can change it deliberately. If your subject requires longer case explanations, take that time from somewhere specific. Don't quietly reduce audience questions after promoting the session as a chance to question the speakers.

Now test the temptation to add more panelists. If five speakers each answer an opening question for two minutes, those answers alone take ten minutes. That's before introductions or follow-ups. This is simple illustrative arithmetic, but it exposes the tradeoff. More speakers may broaden the programme while leaving each person less time to explain anything properly.

Protect a shorter version if the previous session overruns. Agree which question the moderator can remove and the minimum audience participation you can still deliver. Keep the closing handover clear so delegates know where to go next. Don't expect the moderator to recover lost time by speaking faster or asking panelists to rush through every prepared answer.

Make the opening brief and useful

The moderator can open our example with a direct explanation. "Today we're asking when a second conference day is worth the additional cost for organizers and buyers. You'll hear different experiences, and we'll test the conditions behind them. Send questions throughout the conversation using the route on your session information. We'll start taking them after the moderated discussion."

Then introduce each speaker through their relevance to the question. Mention that one has expanded a conference, another approves delegate travel and another produces multi-day programmes. Use their names and agreed descriptions. Their full career history can remain in the programme. The introduction should help the audience understand the perspective behind the next answer.

State the recording and sharing arrangements before inviting sensitive examples. If the session will be publicly available, speakers and audience members need to know. Explain what happens when somebody asks a question on microphone. Match the opening to the permissions and information you supplied before the event, rather than introducing a new condition once people are seated.

Don't describe a public recorded panel as confidential because you hope people will speak frankly. Chatham House's explanation of its Rule permits use of information while protecting participants' identities and affiliations. If you're considering that arrangement, check that promotion, recording and sharing plans genuinely support it. Most public panels should simply state their actual terms.

Moderate the answer you're hearing

The moderator needs a prepared route through the subject and permission to change it. If the first answer reveals that buyers wanted a shorter event, examine that before moving to a prepared question about adding evening activities. Ask what those buyers were trying to accomplish and which parts of the existing programme weren't helping them.

Invite responses with a reason. "You approve travel for a team. Would that additional programme justify another night away?" gives the next speaker something specific to examine. Going along the row for reactions to every answer can produce repetition. Ask the person whose experience can explain a missing condition or challenge the recommendation.

Interrupt a long answer before the audience has forgotten the question. "I'm going to pause there because I want to understand the decision before the launch. What evidence did you have at that point?" This acknowledges the topic and narrows the request. You aren't humiliating the speaker. You're helping them deliver the answer the audience needs.

When someone hasn't contributed, invite them through their expertise. "We haven't examined the production changes yet. Which cost would you check first?" That is easier to answer than announcing that they've been quiet. Let them decline a question outside their knowledge. Balance comes from useful opportunities to contribute, rather than identical speaking time measured for its own sake.

When people disagree, slow down enough to establish what each person means. One speaker may be talking about a residential conference while another assumes daily commuting. Ask them to name those conditions. If a disagreement remains, describe it accurately and move on when the audience understands the choice. You don't need to manufacture agreement to end the session.

If an answer becomes a sales pitch, return to the audience's problem. "What should an organizer check before choosing that approach?" If the speaker continues, remind them of the agreed boundary and move to another perspective. Apply the same standard to everyone, including a sponsor. A moderator can't protect the discussion through hints nobody has agreed to respect.

Agree what sponsorship buys

A sponsor may fund the session, contribute relevant expertise or receive a separately identified presentation. Decide which arrangement you're offering before discussing names. A logo beside a panel title doesn't explain whether the sponsor selected the speakers, controls the questions or has a representative on stage. Your programme description and agreement should make the relevant relationship clear.

If a sponsor representative joins our second-day discussion, invite them because they can explain a relevant decision. A venue operator might understand how another day changes staffing and room use. Brief them to discuss those conditions, including when expansion wouldn't suit the organizer. If they can only describe their own offer, a clearly labelled demonstration may be the more honest format.

Keep the moderator involved when commercial promises affect the session. They need to know about an agreed acknowledgement or closing announcement, and the sponsor needs to understand that speaking on the panel includes follow-up questions. Resolve objections before selling the package. An event producer shouldn't discover backstage that a promised discussion has become an uninterrupted product presentation.

Run audience questions as part of the programme

Decide how people will submit questions before doors open. A roving microphone can work when staff can reach people safely and everyone can hear the question. Written questions can help people who prefer time to compose their thoughts. If you use a digital route, offer another way to contribute for someone who can't use it.

Explain how the moderator selects questions. Group repeated questions and prioritise ones that help the wider audience understand the session's decision. Don't promise to answer everything if the allocation won't allow it. Someone should monitor submissions while the moderator listens to the panel. Otherwise you'll ask one person to follow competing conversations and choose questions at the same time.

Urban Institute's moderator guidance identifies familiar problems, including audience members offering their own views instead of asking a question. Prepare a polite intervention. "I understand your concern. What's the question you'd like the panel to address?" If it remains a speech, thank them and take the next question under the rules you announced.

Give the first audience question to the speaker best placed to answer, then invite a contrasting view when it adds something. Avoid requiring everyone to respond automatically. For a specific private case, ask whether the speaker can explain the general principle. Don't let a detailed consultation use the whole question period while other delegates wait.

Keep a relevant reserve question in case nobody volunteers immediately. Give the room time to think before using it. You might ask what evidence would justify cancelling an expansion plan after initial enthusiasm. Label it as the moderator's question. Inventing an audience submission creates a false impression and is unnecessary when the question itself is useful.

Check that people can hear and participate

Walk through the actual room with the production team. Test microphones in the seats where panelists will speak and check the audience question route. A speaker turning towards another panelist still needs to be audible. Make sure the moderator can see the timekeeper without repeatedly looking away from the conversation.

W3C's accessible events checklist recommends microphones for audience contributions and repeating a question into the sound system when it wasn't audible there. It also advises arranging access support and asking about requirements. Plan those arrangements with the people providing them so participation doesn't depend on somebody improvising a workaround during the session.

For a hybrid panel, assign someone to represent remote questions and test the complete sound path. A room that hears its own speakers clearly may still send poor audio to remote attendees. Rehearse a remote question, a stage answer and the moderator's response. Agree what happens if a remote panelist disconnects rather than waiting for the failure to make that decision.

Keep the stage usable for the actual speakers. Check access, seating needs, sightlines and where water will go. Ask privately about requirements during preparation. A furniture choice that looks attractive can still make the conversation uncomfortable or exclude someone. The production check should confirm that people can use the setup throughout the session.

Prepare for a cancellation or a lost connection

A cancellation changes the discussion most when it removes a perspective the audience was promised. If our travel buyer drops out, the organizer and producer can still talk, but they cannot speak for the person approving delegate travel. Check whether a suitable replacement can prepare properly. Filling the chair matters less than preserving the experience you advertised.

If you continue with fewer speakers, revise the moderator's questions and tell the audience about the change. Don't read the absent person's published comments as if they had answered today's questions. You can identify a relevant published position accurately, but it doesn't replace someone who can explain their circumstances and respond to challenge.

For a connection failure, decide how long production will attempt recovery while the conversation continues. Give the moderator a clear signal when the speaker can rejoin. They can summarise the relevant exchange before inviting a response, instead of expecting the returning person to know what happened while they were disconnected. Preserve the finish time unless the programme team authorizes a change.

Rehearse the handoff between moderator and producer as well as the microphones. Ask a colleague to simulate an unavailable speaker, then check who contacts them, who updates the running order and who explains the change. This short exercise can reveal that everyone assumed somebody else was watching the connection. Fix the responsibility while there's still time to brief the team.

Close with the decision the audience can now make

Use the closing minutes to ask what would change each speaker's recommendation. In our example, the organizer might require evidence of demand for additional training, while the travel buyer might need a stronger reason for another overnight stay. These are hypothetical responses. Your real closing should reflect the distinctions your speakers actually established.

The moderator can then state the remaining disagreement and the information an operator would need before deciding. Avoid a final round of general advice if it repeats the previous hour. Thank the panelists and audience, explain where any agreed follow-up will appear, and hand over on time. Don't promise answers or materials that nobody has agreed to provide.

Afterwards, review whether the session delivered what buyers saw in the programme. Ask which answer helped them make a decision and what remained unclear. Your post-event survey questions can distinguish useful content feedback from a speaker popularity score. A confident performance and an informative conversation aren't always the same thing.

Read the feedback alongside your moderator's notes. Did the cases reveal different conditions, or did everyone repeat the same recommendation? Did audience questions receive enough time? Use those answers when deciding whether to repeat the panel, change its question or choose another format. Begin the next invitation with the experience that was missing from this conversation.