Streamed Discussion Planning Now Opens With a Moderator Brief

For these early autumn weeks I have reworked how the Streamed Discussion Planning module starts. Until now, learners opened with the guest list and built outward. The module now begins with a single page that we call the moderator brief, and everything else in the plan hangs from it.

The reasoning is simple. A streamed panel has more moving parts than a room-based one: a moderator, guests in the building, contributors joining remotely, and a technical team watching a different screen from the one the audience sees. When those groups read different documents, the discussion drifts. One brief that all of them can open removes most of that drift before rehearsal begins.

Learners still work from original sample rundowns, so nothing about the material they handle has changed. What has changed is the order in which they decide things, and that order now starts with the person holding the conversation together.

The module still carries the same summary it always had: preparing moderators, guests and remote contributors for a streamed panel with clear handover points. The brief is simply the first place those handover points are written down.

The brief fits on one page and is written for the moderator first, with the rest of the team reading over their shoulder. It states the programme length, the order of topics, who speaks first on each topic, and the exact words or signal that pass the discussion to the next voice.

We ask learners to write it in plain sentences rather than shorthand. A moderator who reads it twenty minutes before going live should not need to decode abbreviations or ask what a note means. If a line cannot be understood on a first read, it is rewritten until it can.

The brief also names who covers each gap. If a remote contributor loses their connection, the moderator needs to know in advance whether to move to the next guest, repeat the question, or fill with a prepared prompt. Writing that down in calm conditions is far easier than improvising it live.

Learners are often surprised by how much of the work is deciding what the moderator should do when something goes slightly wrong, rather than describing the ideal run.

• Programme length and topic order
• First speaker on each topic
• The wording that passes the floor
• Fallback if a contributor drops out

A handover point is the moment one speaker finishes and another begins, and in a streamed panel it is the place where most awkward silences happen. The module now spends a full session on writing these moments deliberately, one at a time, rather than leaving them to the moderator's instinct.

Each handover names the person speaking, the person next, and the cue that links them. For a remote contributor the cue is usually the moderator saying their first name along with the question, so the contributor can unmute and begin without guessing. For a guest in the room, the cue may be a glance and a short phrase agreed at rehearsal.

Learners practise this on a sample rundown with six voices, two of them remote. They mark each handover, then read the sheet aloud as though presenting it to the technical team. Anything that sounds unclear when spoken gets rewritten.

The exercise teaches a habit more than a format: if you cannot say how the conversation moves from one person to the next, the plan is not finished yet.

Remote contributors are the group most often left out of rehearsal, and the module treats that as a planning error rather than a scheduling inconvenience. A short check call, even ten minutes, lets a contributor test their audio, learn where to look, and hear the moderator's voice before the programme begins.

Learners build this call into their rehearsal schedule as a named block with a start time and an owner. They also decide what the contributor receives beforehand: the brief extract that concerns them, the order of questions, and a plain note on who to contact if the connection fails.

We keep the instructions to contributors short. A guest joining from an office or a spare room does not want a technical manual; they want to know when to speak, when to stay quiet and what to do if something stops working.

This is also where learners meet the limits of planning. A rehearsal reduces surprises but does not remove them, so the plan always carries a quiet fallback.

By the end of the module each learner has a complete plan for one streamed discussion: the moderator brief, a segment order with timings, a list of handover points, a rehearsal block for remote contributors, and a short note for the technical team. It is built from a rough agenda we supply, not from a real client's material.

Realistically, this prepares someone to contribute usefully to the planning of a streamed panel as a junior coordinator or assistant, working alongside more experienced producers. It does not make anyone a finished producer, and we say so plainly. What it gives is a method that can be repeated.

Prerequisites are modest. Learners should be comfortable reading a schedule, writing short clear sentences and working to a time limit. No technical equipment training is assumed, since the focus stays on the plan rather than the hardware.

Marcus and Elena review the sample plans alongside me, and each learner receives written comments on where the sheet could be read more easily by someone who has never met the speakers.

• Moderator brief
• Timed segment order
• Handover list
• Remote rehearsal block

Since we moved the brief to the start, the plans learners hand in have become easier to follow. Fewer of them bury the handovers in the final pages, and more of them show the moderator as the person the whole document serves.

I think the reason is that the brief forces an early decision about how the conversation moves. Once that is settled, timings, rehearsal and technical notes have something firm to attach to. Before, learners often polished timings for a discussion whose shape was still unclear.

It also keeps the tone of the work calm. A plan that starts from one readable page feels manageable, and learners who were nervous about live programmes tend to relax once they see that the first task is simply to write down who speaks next.

That calm is part of what scenepulse tries to teach: preparation done early, in plain words, so that the live moment asks very little of anyone.