Back to Blog

Corporate Event Livestream Run of Show: UK Checklist

WeTrends8 min read

Build a clear corporate event livestream run of show with speaker cues, camera plans, audio checks, rehearsal steps, remote audience support and fallback actions.

Editorial illustration of a hybrid corporate event production desk with a run of show, camera feeds and speaker cues

A corporate event livestream run of show is the shared minute-by-minute plan for the room, broadcast, speakers and technical team. For a live or hybrid event, it should show what happens, who owns it, which cue is required and how the remote audience experiences each moment.

What should a corporate event livestream run of show include?

A useful run of show combines the event schedule with production instructions, ownership and contingency notes.

  • Time and duration: include the planned start time, end time and length of every segment.
  • Segment: describe what the audience sees, such as a keynote, panel, product film, audience question or break.
  • Speaker and owner: name the presenter, host, stage manager, producer or technician responsible for the next action.
  • Room cue: specify lighting, stage movement, lectern use, confidence monitor content and audience instructions.
  • Broadcast cue: identify the camera shot, graphic, video, remote guest layout, screen share or holding slide required in the stream.
  • Audio cue: state which microphone is live, whether room sound is required and whether a video or remote contributor needs a separate feed.
  • Fallback: record what happens if a speaker is late, a video fails, a remote guest drops out or the stream needs to pause.

A run of show is more effective when the whole core team reviews and rehearses it before it is locked and distributed. The Events.com run of show guide also recommends reviewing the draft with the team to find gaps, overlaps and unclear responsibilities.

How should you structure the document for a hybrid event?

Structure the document so the show caller can read it quickly while the room and broadcast teams can find their own cues without ambiguity.

Use one master version rather than separate schedules that can drift apart. A practical sequence of columns is:

  • Time
  • Duration
  • Segment or action
  • Speaker or contributor
  • Room cue
  • Stream and camera cue
  • Audio cue
  • Owner
  • Notes and contingency

Keep the operational language short. “Stand by keynote camera two, confidence slide 04, CEO lav mic, lower-third graphic” is more useful during a live transmission than a paragraph explaining the intention of the segment.

For a corporate event livestream in the UK, also record the time zone, platform, stream privacy settings, planned holding content and who has authority to stop or restart the broadcast. If the event includes a remote panel, list each contributor’s connection method, joining time and backup contact.

Which technical cues need checking before the broadcast?

The technical production plan must test the complete path from speaker or presentation source to the room and the remote viewer.

  • Audio: test lectern, handheld, lavalier and remote-speaker microphones separately, then check the room PA and stream mix as distinct listening experiences.
  • Video: confirm wide, mid and close camera positions, camera movement, framing and any restrictions caused by the venue or audience.
  • Presentation: check slide playback, screen sharing, embedded video, aspect ratio, presenter view and confidence monitors.
  • Graphics: prepare and test name straps, holding slides, chapter cards, sponsor acknowledgements and any on-screen instructions.
  • Lighting: check the speaker’s face on the broadcast feed rather than relying only on how the stage looks in the room.
  • Connectivity: test the encoder-to-platform chain, network stability and the intended stream destination.
  • Redundancy: keep spare batteries, cables, adapters and critical playback files available, and identify a backup route for essential content.

Hybrid event AV requires two audio checks: one for people in the venue and one for the remote audience. Firefly AV’s technical guide for UK planners recommends testing both paths with a speaker at the lectern and a remote listener monitoring the stream output.

When should speakers and technicians rehearse?

Run a full technical rehearsal one or two days before the event, followed by a shorter day-of check before the broadcast opens.

The full rehearsal should use the intended equipment, platform, graphics, microphones and presentation files. Ask every speaker to deliver the relevant section rather than simply confirming that they will attend. Time each segment, test camera framing, check screen shares and watch the output on a separate device as a remote viewer would.

Use the rehearsal to settle practical questions:

  • Where does each speaker wait before going live?
  • Who introduces a remote guest if the connection is late?
  • Does the host repeat audience questions for the stream?
  • Which camera covers the stage while a presenter changes position?
  • What does the audience see if a video or presentation cannot play?
  • Who calls the next cue and who can override it?

On event day, complete a final check at least an hour before broadcast where the schedule allows. Confirm equipment, microphones, network, platform settings, stream privacy, graphics, playback and remote contributors. A short test stream can expose problems that a local preview will not.

What does a practical hybrid event run of show look like?

A practical schedule makes each transition explicit instead of assuming that the room and stream will change at the same time.

For example, a 09:00 leadership webcast from a UK venue could use the following sequence:

  • 08:30–09:00, doors and pre-show: room music plays; the broadcast shows a branded holding loop; the producer checks the platform health and the host confirms the opening notes.
  • 09:00–09:05, welcome: the host microphone goes live; the room lights rise; camera one takes a medium shot; the opening graphic is replaced by the event title.
  • 09:05–09:25, keynote: the presenter uses the lectern microphone and confidence monitor; camera two takes the speaker; the presentation source is ready for the planned slide sequence.
  • 09:25–09:28, product film: the producer confirms the file and audio; the room dims; the stream switches to the film; the host waits off-stage for the return cue.
  • 09:28–09:53, panel: four microphones are checked live; the broadcast uses a wide opening shot and cuts to individual speakers; the moderator repeats questions from the room.
  • 09:53–10:00, remote questions: the host takes questions from the platform; the remote producer confirms each contributor before they appear; a holding slide covers any delay.

This example gives every team a shared reference. It also exposes dependencies: the panel cannot begin until microphones and chairs are ready, and the product film needs a tested playback source and audio path.

How should you manage remote speakers and audience interaction?

Manage remote contributors as planned broadcast elements, not as guests who can simply join at the last minute.

Send each remote speaker a joining time, technical requirements, contact number and clear briefing on camera position, lighting, headphones, background and presentation sharing. Test their microphone, camera, screen share and return audio before the event. Keep them in a private waiting area until the show caller confirms that they are ready.

Decide how remote questions reach the host. Options include moderated chat, a producer-selected question list or a dedicated moderator. Add the method to the run of show, including who removes unsuitable questions, who reads names and what happens if the queue runs empty.

Do not overlook accessibility and audience clarity. Plan captions where required, describe how questions will be handled, keep important information on screen long enough to read and avoid asking remote viewers to depend on room-only announcements.

What should happen after the livestream?

Close the run of show with a documented handover for recording, clips, data and follow-up actions.

  • Confirm when the stream ends and what viewers see afterwards.
  • Record whether the programme was captured locally and on the platform.
  • Note any missing files, audio issues or sections that need editorial review.
  • Assign ownership for the recording, captions, highlights and internal distribution.
  • Save the final run of show with the event files so future teams can understand what happened.

If you need support planning the room, broadcast cues and audience experience, see WeTrends’ event production service. Share the event format, venue status, platform and required outputs early so the production plan can be built around the real show rather than added after the agenda is fixed.

Frequently asked questions

What should a corporate event livestream run of show include?

Include timings, segment descriptions, speaker and owner details, room cues, broadcast and camera cues, audio requirements, and fallback actions for common problems.

When should speakers and technicians rehearse for a hybrid event?

Run a full technical rehearsal one or two days before the event, followed by a shorter day-of check covering equipment, platform settings, graphics, playback, microphones and remote contributors.

How do you manage remote speakers during a livestream?

Give contributors a joining time, technical briefing and backup contact, test their camera, microphone and screen share, and keep them in a private waiting area until the show caller confirms they are ready.

Need a hand with this?

Event photography and film

Plan coverage around the room, the moments and the content you need afterwards.

Explore the Service

Tags

corporate event livestream UKevent livestream production Londonhybrid event run of showcorporate event technical productionevent broadcast checklist
Share:

WeTrends

Building uncopyable brands for small businesses. No jargon, no fake urgency — just the truth, told properly.