Event moderator briefing builder
A moderator will run a panel with several voices, and needs a pack that never puts words in a panellist's mouth.
…
The short answer
The builder assembles a moderator pack from the objective, panellist roles, boundaries, timings and questions you enter. It produces a running order with clock times, a transition between each approved question, and escalation prompts for a panellist who overruns, a boundary topic or a technical problem.
Only questions you tick as approved enter the running order. A statement is attributed to a panellist only when you typed it and ticked that the panellist approved it. The tool writes no questions, answers or quotes of its own.
What to enter
- The session: title, objective, start time, total length, and minutes for the opening, audience questions and closing.
- Boundaries: the topics to stay away from, as agreed with the organiser and panellists, in your own words.
- Panellists by role. Add a name only if it is confirmed. Add a statement only if the panellist supplied it, and tick Approved when they agreed to its use.
- Questions in running order, each with its approved wording, who it is directed to, the time for it and an Approved tick.
Approved questions and approved statements
A question that is not ticked as approved is listed separately and left out of the running order. A statement that is typed but not approved is left out of the pack and flagged, so it is not read out as someone's position.
If a tick is present but no statement was typed, nothing is used. The moderator is also reminded to ask panellists to state positions in their own words.
Timing and transitions
Segments are placed one after another from the start time. A blank time is unknown, not zero, so clock times stop after it and the tool says so. The total is compared with the session length, and any unallocated or extra minutes are shown.
Transitions are procedural: thank the previous responder, check the time, ask the next approved question as written, directed to the role you named. Each pack ends by returning to the objective and handing back to the organiser.
Escalation prompts
The pack lists what the moderator does if a panellist overruns, if the discussion moves into a boundary topic, if an unapproved statement is put to a panellist, or if a technical or room problem stops the session. Each prompt names the role to signal, which you enter.
Safety matters go to the venue and the organiser, not the moderator. If you leave the role blank it is printed as open.
Limits
The pack is a draft for the organiser and moderator to edit. It does not check that questions are fair or accurate, and it does not predict what panellists will say. For the speakers' own briefs use the speaker briefing generator, and for the day's cues use the stage cue sheet builder.
Worked example · Fictional example
A fictional association panel
Fictional session, roles and figures, to show what the pack contains.
A fictional panel runs for 60 minutes from 11:00 with three panellist roles. Three questions are approved (10, 12 and 8 minutes) and a fourth is not approved. The regulator liaison role has a typed statement that is not ticked as approved.
The running order places the opening at 11:00 to 11:05, then the three approved questions, audience questions at 11:35 and the closing at 11:50, using 55 of 60 minutes. The tool shows 5 minutes unallocated, lists the fourth question as not approved, and leaves the unapproved statement out of the pack.
| Time | Minutes | Segment |
|---|---|---|
| 11:00 | 5 | Opening and introductions |
| 11:05 | 10 | Q1: first decision members will be asked to take |
| 11:15 | 12 | Q2: how members prepare their own records |
| 11:27 | 8 | Q4: which step is most often missed |
Use this yourself
Moderator briefing sheet
Fill in each line from facts the organiser and panellists have confirmed. Leave anything unknown open.
| Line | What to write | Confirmed (yes or open) |
|---|---|---|
| Session title and objective | ||
| Boundaries agreed with panellists | ||
| Panellist roles, and names only if confirmed | ||
| Opening, audience questions and closing (minutes) | ||
| Approved questions in order, who each is for, minutes each | ||
| Statements approved by the panellist for use | ||
| Role the moderator signals if something goes wrong | ||
| Total minutes against the session length |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One panel, a moderator who knows the topic and an organiser who approves every question.
- Boundaries and timing have been agreed with the panellists.
Outside planning help earns its fee when
- Several panels run in a day and the packs must be consistent with each other and with the programme.
- Questions, boundaries and statements keep changing and approvals must be tracked.
- Panellists and sponsors each want a say and someone must hold the decisions.
Need panel briefings coordinated with the programme?
A project lead can keep the moderator packs aligned with the programme, collect approvals from the people who must give them and keep the running order current as sessions change. Questions, statements and boundaries stay yours to decide.
Questions organisers ask
Can the tool suggest questions for the moderator?
No. It uses only the questions you enter, and only those ticked as approved enter the running order.
Why is a typed statement left out of the pack?
It is not ticked as approved by the panellist. Attributing it to them could put words in their mouth, so it is left out and flagged.
What if the minutes do not add up to the session length?
The tool shows how many minutes are unallocated or over. It does not change any time for you.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.