How Do You Prepare a Remote Guest for a Streamed Panel?

When learners ask how to prepare a remote guest, they usually mean something narrower: what do I send, and when? A guest who joins from a spare room has none of the cues a studio provides. There is no floor manager waving a hand, no monitor showing the running order, no colleague nearby to whisper that the segment is about to start.

So preparation has to carry what the room normally carries. In my own work I treat the guest brief as a small production document. It says what the programme is, who else is on the panel, how long the guest will speak, and who will bring them in. A guest who knows those four things walks in calm, and a calm guest sounds better than one who has been coached for hours.

The rest of this note follows the order I use: the first message, the technical check, the handover points, and what to do when something slips.

The first message should fit on one screen. Open with the date, the start time in the guest's own time zone, and the length of their part. Then name the moderator and say what the opening question will be. Guests relax when they can see the first thirty seconds in advance, because the hardest moment on a stream is the silence before the first answer.

Add the practical details next: which link to use, which device, and a contact for the day itself. Keep one person as the single point of contact. If a guest has to choose between two phone numbers while the countdown is running, the message has failed.

Avoid long background reading. A guest does not need the full agenda for the day, only their own slot and the segments on either side of it, so they know who speaks before and after them.

• Date, start time and their local time zone
• Length of their part and the opening question
• Moderator's name and one contact for the day
• Link, device and a quiet-room reminder

Book a check at least a day before, and keep it to fifteen minutes. The aim is not to perfect the picture but to find the three things that cause most trouble: a weak connection, a microphone that picks up the room, and a camera angle that cuts the guest off at the forehead. Fix those and most of the risk is gone.

Ask the guest to use headphones, sit facing a window or lamp, and close other applications that might grab bandwidth. Have them say their name and the opening line of their answer so the sound technician can set levels on a real voice, not a count to ten.

Write the result into the production notes: connection type, device, any workaround agreed. On the day, whoever runs the technical desk can read that line instead of guessing, and a problem seen at the check is a problem with a known fix.

• Wired connection if possible, otherwise sit near the router
• Headphones on, other applications closed
• Level check on the guest's actual opening line

A handover point is the exact moment control passes from one voice to another. For a remote guest it must be audible or visible, because they cannot read the room. I agree a spoken cue with the moderator: a name and a short question, for example, rather than a vague turn towards the camera. The guest then knows precisely when to start speaking.

Write each handover into the cue sheet with the words that trigger it and the person who gives it. If the guest is to hand back to the moderator, give them a closing phrase to listen for and one to say, such as a thank-you and the name of the next speaker.

Rehearse the first handover and the last one in the check call. Those two carry the most risk: the first because nerves are highest, the last because the programme tends to be running behind by then.

Plan for a dropped guest before it happens. Decide in advance how long the team waits before moving on, and write that number beside the segment. A common choice is a short fixed wait, then the moderator takes the next question and the guest rejoins when the line returns. Nobody should be improvising the rule while the stream is live.

Keep a fallback ready: a phone number for audio only, or a short pre-agreed statement the moderator can read. Tell the guest about the fallback during the check, so a failed picture feels like a normal step in the plan and not an emergency.

After the programme, add a line to the handover notes about what happened. The next team will know which guests needed the wired connection and which cue worked.

• A fixed wait time written beside the segment
• A phone number for audio-only rejoining

You can hear the difference within the first answer. A prepared guest speaks at an even pace, answers the question that was asked, and does not apologise for the setup. That is rarely talent. It comes from knowing the order of events, having tested the equipment once, and trusting that someone else is watching the clock.

The moderator benefits as well. With clear handover points, they spend less energy managing the guest and more on listening, which is where good panel questions come from.

If you take one habit from this note, make it the one-screen first message. Everything else grows from a guest who knows what is expected and when.