A virtual roundtable should feel like a focused conversation between peers, not a webinar with extra faces on screen. The participants need a reason to contribute, the moderator needs enough structure to keep the discussion useful, and everyone needs to understand what will happen to their words after the session.
This playbook gives you an operating pack for making those decisions. It covers the format, participant mix, one-page brief, trust and recording agreement, prompt-led agenda, working roles, live facilitation, and follow-up. It also explains when an audience-facing broadcast works well and when a closed meeting is the better choice.
What a virtual roundtable is, and what it is not
A virtual roundtable is a moderated online discussion built around a focused problem and active contribution from a small group of peers. The defining feature is not the number of people on screen. It is the expectation that participants will exchange perspectives, respond to each other, and help the group examine a useful question.
That makes the format different from several adjacent event types:
| Format | Who carries the conversation? | Separate audience? | Typical privacy model | Best fit |
|---|---|---|---|---|
| Closed peer roundtable | Invited participants | No | Private by default, with sharing rules agreed in advance | Candid peer exchange, advisory discussion, customer council |
| Audience-facing roundtable | Invited participants, guided by a moderator | Yes | Participants are public; audience interaction and reuse rules are explicit | Expert discussion, customer conversation, market education |
| Panel | A selected group of speakers | Usually | Commonly on the record | Contrasting expert views for an audience |
| Webinar | One or more presenters | Yes | Commonly recorded and replayed | Teaching, demonstrations, launches, structured presentations |
| Focus group | Selected research participants | No | Research protocol and data handling are defined | Learning about attitudes, language, or product reactions |
| Ordinary meeting | Everyone invited | No | Determined by the organisation | Coordination, decisions, project work |
If most attendees are expected to listen, you are probably planning a webinar or panel. If the purpose is structured research, you may need a focus-group method. If the conversation depends on privacy and every attendee needs to speak freely, a closed meeting tool may be more appropriate than a broadcast platform.
Choose the format before you choose the platform. That prevents a familiar tool from quietly deciding how the session works.
Start with a one-page roundtable brief
The brief is the contract between the organiser, moderator, participants, and production team. It should be short enough to use during planning and specific enough to resolve disagreements before invitations go out.
Copy this structure:
Roundtable purpose: The problem this conversation will examine.
Participant value: What each person should learn, test, compare, or take away.
Desired outcome: A decision, set of insights, unresolved questions, next action, or simply a better shared understanding.
In scope: The two or three areas the moderator should explore.
Out of scope: Topics that would dilute the conversation or create avoidable risk.
Format: Closed peer discussion or audience-facing broadcast.
Trust agreement: On the record, under the Chatham House Rule, or off the record.
Recording and reuse: Whether recording, transcription, quotation, summarisation, replay, or content reuse is allowed.
Follow-up promise: What participants and audience members will receive, and how their information may be used.
Owner: The person accountable for the session and its follow-up.
Write the desired outcome as something the group can actually influence. “Generate pipeline” is not a useful roundtable outcome. “Identify the three operational obstacles teams hit when moving from one-off webinars to a recurring programme” gives the moderator a real job.
Choose participants using conversation math
There is no universal ideal group size. The right participant count depends on how many active voices you want, how much time is available, how many prompts you plan to explore, and how much depth each contribution needs.
Think in turns rather than seats. If eight people each need an opening contribution, a response to two prompts, and a chance to add a closing thought, the agenda must create room for at least 32 meaningful turns before follow-up questions, moderator summaries, and transitions. That may be perfectly workable in one format and impossibly rushed in another.
Use four filters when building the room:
- Relevance: Each participant has direct experience of the stated problem.
- Perspective: The group includes useful differences in role, company stage, market, approach, or experience.
- Contribution: Invite people who are willing to exchange ideas, not only deliver a polished talking point.
- Safety: Avoid combinations that make candid participation unlikely or create an undisclosed commercial conflict.
Ask invitees to confirm that they are comfortable with the format and sharing rules, not just the date. For a closed peer session, do not overbook heavily in anticipation of dropouts: an unexpectedly crowded room changes the experience for everyone who accepted the invitation.
If you have a separate audience, define the boundary between participants and viewers. Decide whether audience members can submit questions, vote in polls, request to join, or only watch. Those are design choices, not settings to improvise while live.
Agree trust, confidentiality, and recording before the invitation
People cannot make an informed choice about joining if the organiser has not decided what may be attributed, recorded, or reused.
Three common trust models are:
| Model | Participants may use what they hear | Names or affiliations may be revealed | Recording or publication |
|---|---|---|---|
| On the record | Yes | Yes, subject to the agreed scope | Possible when clearly disclosed |
| Chatham House Rule | Yes | No attribution to a speaker or participant | A separate decision; the Rule does not grant recording permission |
| Off the record | Only within the agreed boundary | No | Normally disabled unless a separate explicit agreement says otherwise |
Chatham House’s explanation of the Chatham House Rule says participants may use the information received, but must not reveal the identity or affiliation of the person who shared it. The Rule is not legally binding, does not automatically make an entire meeting confidential, and does not decide whether you may record or publish the conversation.
Treat recording as its own decision. The Information Commissioner’s Office guidance on recording online events advises organisers to define and document a valid purpose and lawful basis, tell people why the recording is being made and how long it will be kept, and make any intended online publication clear. It also recommends giving people practical privacy choices. Exact obligations vary by jurisdiction and circumstances, so this is an operating prompt rather than legal advice.
Before inviting anyone, answer:
- Will the session be recorded, transcribed, summarised, or quoted?
- Will a replay or edited clip be published?
- May anonymised themes be shared?
- May attributed quotations be used, and how will approval work?
- Who can access the raw recording or transcript?
- How long will those files be retained?
- Can someone participate with their camera off or a shortened display name?
- Will participant information be shared with partners, sponsors, or sales teams?
“We will decide after the session” is not a neutral answer. It transfers uncertainty to participants after they have already spoken.
Build a prompt-led agenda
A roundtable needs structure, but a rigid script can suffocate the exchange. Plan a sequence of open prompts and give the moderator permission to spend longer where the room has something useful to unpack.
Here is an adaptable 55-minute example:
- 0–5 minutes: Welcome and trust agreement. Restate the purpose, format, attribution rule, recording choice, and how audience questions will work.
- 5–12 minutes: Topic-linked introductions. Ask each participant for their name, role, and one short observation that connects directly to the problem.
- 12–25 minutes: Context prompt. Explore what participants are seeing now and where approaches differ.
- 25–40 minutes: Tension prompt. Examine the hardest trade-off, failure point, or disagreement.
- 40–49 minutes: Practical response. Ask what participants would change, test, or advise another team to do.
- 49–55 minutes: Synthesis and close. Summarise themes, note unresolved questions, confirm any next actions, and repeat what may be shared.
Adjust the timings to the active-voice count and desired depth. A small closed discussion may spend most of its time on one prompt. An audience-facing session may need a defined Q&A window and a producer who filters questions while the moderator stays present in the conversation.
Send the theme and opening prompt before the session. Avoid sending a long questionnaire that encourages rehearsed mini-presentations. The goal is preparation without turning the room into a sequence of speeches.
Assign roles before the session
Roundtables become fragile when the moderator is also expected to troubleshoot audio, manage a speaker queue, watch chat, take notes, approve recording, and decide follow-up in real time.
Use a compact role matrix:
| Role | Before the session | During the session | After the session |
|---|---|---|---|
| Organiser | Owns purpose, invitations, trust agreement, and participant fit | Protects the intended format | Owns outcome and stakeholder handoff |
| Moderator | Prepares prompts, names, context, and redirects | Opens, balances voices, probes, synthesises, and closes | Reviews themes and participant commitments |
| Producer | Runs technical rehearsal and contingency plan | Manages room, media, timing, and technical recovery | Secures or deletes production assets as agreed |
| Audience interaction owner | Plans Q&A and poll rules | Filters and routes audience input | Exports only the agreed signals |
| Note and privacy owner | Defines note, recording, and attribution boundaries | Captures only what is permitted | Applies retention, approval, and sharing rules |
| Follow-up owner | Plans participant and audience journeys separately | Records agreed next steps | Sends the right message to each group |
For deeper live prompts, handoffs, Q&A triage, and issue cues, use a dedicated webinar moderator script rather than asking the moderator to invent language under pressure.
Prepare the room and the people
Preparation should make contribution easier, not make the session feel over-produced. Send participants a concise brief containing:
- The purpose and participant value.
- The format and expected level of contribution.
- The opening prompt and broad discussion themes.
- The trust, attribution, recording, and reuse agreement.
- The moderator’s name and a backup contact.
- The technical join instructions and rehearsal time.
- Accessibility options and a way to request support.
- What will happen after the session.
A peer-reviewed Microsoft Research study of remote meetings analysed 3,290 filtered survey responses from one large technology company. It found that agendas, pre-meeting communication, post-meeting summaries, meeting size, and audio and video reliability were among the factors correlated with perceived effectiveness and inclusiveness. The study is correlational rather than proof of cause, but it reinforces a practical point: the quality of the meeting system matters alongside the discussion topic.
Run a short technical rehearsal with the moderator and production team. Confirm names and pronunciation, role permissions, microphones, cameras, screen sharing, the waiting-room path, participant ordering, the backup contact, and what happens if someone drops out. If the roundtable includes an audience, also test the webinar registration page, watch page, Q&A, polls, any agreed CTA, and replay state.
Do not rehearse every participant answer. The facilitator should know the route through the conversation; the room should still be able to surprise you.
Facilitate without turning the roundtable into a panel
Open by naming the contract of the room. State the topic, the expected style of participation, the attribution rule, the recording status, and how you will handle time and audience input. Then ask an easy but relevant opening question so every participant contributes early.
During the discussion, the moderator can use five moves:
- Invite: “Maya, how does that compare with what you are seeing?”
- Probe: “What made that difficult in practice?”
- Connect: “That seems to challenge Aaron’s earlier point. Aaron, does it change your view?”
- Redirect: “I want to pause the product example and return to the operating decision underneath it.”
- Synthesise: “We have two approaches here: central control and local ownership. The unresolved question is where the handoff sits.”
When one voice dominates, interrupt the pattern rather than criticising the person: summarise their point, thank them, and deliberately bring in someone who has not spoken. When the room goes quiet, narrow the question or offer two concrete starting positions. When a participant turns the session into a sales pitch, redirect to the shared problem and the experience behind the claim.
If a technical issue affects one participant, the producer should handle recovery privately while the moderator continues where possible. If the issue affects the trust agreement, recording, or the whole room’s ability to participate, pause. Protecting the format matters more than filling every scheduled minute.
For an audience-facing roundtable, treat chat, questions, and polls as optional inputs. A question, poll answer, CTA click, or watch-time signal may add context, but it does not prove purchase intent or lead quality.
Close and follow up without breaking the room’s trust
The close should tell people what happened and what happens next. Summarise the main themes without forcing artificial agreement. Name unresolved questions, repeat any commitments, and restate what may be attributed or shared.
Keep participant and audience follow-up separate:
- Participants: Send a personal thank-you, the agreed summary, promised resources, and any quotation or content approval request.
- Audience members: Send the replay only if one was promised and permitted. Offer relevant resources and a next step that matches the public session.
- Internal team: Share only the notes, signals, and personal data covered by the stated purpose and permissions.
- Future content: Use anonymised or attributed insights only within the agreement. Ask again when the planned use is materially different.
For audience-facing sessions, audience intelligence can bring registration, attendance, clicks, and replay activity into one audience record. Webinar follow-up automation can then help teams segment messages using that context. Keep the interpretation modest: signals can guide a more relevant follow-up, but they are not a verdict on someone’s intent.
Where HeyStream fits
HeyStream is a good fit when the roundtable has an audience-facing broadcast layer. Teams can use branded registration and watch pages, assign a Moderator role, manage presenters and a waiting room, run chat, Q&A and polls, offer live or replay CTAs, keep audience records, and organise behaviour-based follow-up.
That does not make every roundtable a broadcast. A highly confidential peer discussion where every attendee needs an open microphone and recording must remain disabled may be better served by a closed meeting setup. The useful product decision follows the trust and participation model, not the other way around.
If the session is one part of a broader webinar programme, connect it to the B2B webinar growth engine: a clear topic and registration path before the event, a well-run live experience, useful audience context, and respectful follow-up after it.
The practical test is simple. Participants should know why they are there, what kind of contribution is expected, how their words may be used, and what happens next. When those answers are clear, the moderator can focus on the conversation instead of repairing the format while everyone is watching.
