The Conference Q&A Playbook: Pre-Event, Live, Post-Event
Conference Q&A playbook covering pre-event collection, live moderation, handling controversial questions, post-event summaries, and a sample run-of-show.
Hushwork Team
A conference Q&A goes well or badly in the first three minutes. If the audience starts asking real questions, the room engages and the speaker has something to work with. If the first question is a long ramble or an off-topic complaint, energy collapses and the next 40 minutes are uphill.
Most of what determines those first three minutes happens before the event starts. Here's the full playbook: pre-event, live, post-event.
Pre-event (week before)
Collect questions in advance
Share an AnswerLink with registered attendees a week ahead. "Drop questions for our speaker here." Hush AI clusters them by topic so the speaker walks in already knowing what the audience cares about.
Why it works:
- Speakers come prepared with answers, not improvised ones
- The first question of the live Q&A is one you've already seen
- The audience that asked in advance feels heard before they show up
Send the speaker the cluster
48 hours before the event, send the speaker:
- The top 5 question themes (Hush AI summary)
- The single most-asked specific question
- Any sensitive or controversial questions you'll handle in moderation, not on stage
This briefing changes the speaker's prep. Most will adjust their talk to address the most-asked theme.
Test the live setup
Run a 5-minute dry run of the moderator screen the day before. Confirm:
- The QR code projects clearly from the back of the room
- The moderator dashboard auto-refreshes
- Hush AI ranking and grouping are on
- Spam and harm filters are configured
Two minutes of testing prevents 20 minutes of stage panic.
Live (during the event)
The opening 30 seconds
The host opens the Q&A by:
- Showing the QR code on a slide
- "We're taking questions anonymously. Drop them here as we go."
- Repeating in 5 minutes if needed
The repetition matters. Latecomers and people who weren't paying attention need a second prompt.
Live moderation patterns
The moderator's job is filtering, not editing. Three patterns:
The cluster: Hush AI shows you "8 questions about pricing." You read the strongest version, the speaker addresses the cluster. One answer, eight questions resolved.
The single sharp question: A specific, well-formed question with high upvotes. You read it as written. The speaker has time to actually answer.
The off-topic question: about the venue, the WiFi, an unrelated topic. Hide it. Don't read it.
Handling controversial questions
Some events have controversial questions. Three options:
Read it as written. When the question is sharp, fair, and not personally attacking, read it. The audience respects a Q&A that doesn't dodge.
Reframe to the underlying question. "There's a question about our recent decision on X. The deeper question is whether we're still committed to Y. Can you address that?" You acknowledge the controversy without amplifying any single phrasing.
Decline with a reason. "There are a few questions about something I won't get into here, but happy to take it offline." Don't pretend the questions weren't there. The audience saw them in the queue.
What not to do: read every controversial question, ignore them all silently, or get into a back-and-forth on stage.
Pacing
A 45-minute Q&A typically lands 8-12 substantive answers. That means most questions don't get covered. That's fine; the queue is the signal, not the read-out.
Aim for:
- 90 seconds per answer maximum
- Brief follow-up if needed, then move on
- 2-minute warning at 40 minutes
- Hard stop at 45 minutes
Going long is the most common pacing mistake. You always feel like there's one more question worth taking. Stop on time. Send the unanswered ones to AnswerLink for follow-up.
Post-event (within a week)
Send a follow-up to attendees
24 hours after the event, send:
- The speaker's response to the top 3 unanswered questions (written, short)
- A 5-question post-event survey
- The AnswerLink URL for any further questions
This three-part follow-up converts a one-off event into ongoing engagement. People who couldn't ask live, who thought of the question afterwards, or who want to follow up on something specific have a channel.
Run a 5-question post-event survey
Hush AI drafts this in 30 seconds. Sample:
- Overall, how would you rate this event? (Likert 1-5)
- What was the most useful part?
- What was the least useful part?
- What would you want at the next one?
- Would you recommend this event to a colleague? (Likert 1-5)
Hush AI summaries cut your reading from a full afternoon to ten minutes.
Brief the speaker
A few days after, send the speaker:
- The post-event survey themes
- Specific quotes about their talk (from the post-event open text)
- The unanswered questions worth a follow-up post or social thread
Most speakers appreciate the post-event briefing more than the day-of briefing. They've come down from the adrenaline; the feedback is actionable.
A sample run-of-show
Here's a typical 45-minute Q&A as it plays:
| Time | What's happening |
|---|---|
| -7 days | AnswerLink shared with registered attendees |
| -2 days | Speaker briefed on top 5 question themes |
| -1 day | Moderator dry run of the live dashboard |
| Min 0 | Host shows QR code, "drop questions here" |
| Min 0-5 | Speaker introduces, audience starts dropping questions |
| Min 5-40 | Q&A live; moderator picks from Hush AI ranked queue |
| Min 40 | 2-minute warning; "we'll take two more" |
| Min 45 | Hard stop; "thanks, we'll follow up on AnswerLink" |
| +24h | Follow-up email with answers to top unanswered questions |
| +48h | Post-event survey opens |
| +7 days | Survey closes; themes summarised; speaker briefed |
What goes wrong (and how to recover)
The dashboard doesn't show questions. Refresh. If still broken, bring up backup view on a phone. Don't apologise on stage; just keep going.
The first 5 minutes have no questions. Have one or two pre-loaded questions ready (from the pre-event collection). The host reads one to break the seal. Audiences need to see the format work before they participate.
Someone keeps submitting variations of the same question. Hush AI dedupes most of this. If one slips through, address the cluster once and move on.
A controversial question goes viral in the queue. If it has 50+ upvotes and you're not addressing it, the audience notices. Better to acknowledge briefly ("there are a lot of questions about X; we'll come back to that") than to ignore.
Get started
Sign in to Hushwork, set up an AnswerLink for your next event, share the QR. Free for any audience size.
Related reading:
