A webinar run of show is not a copy of the slide deck. For a virtual assistant, it is the minute-by-minute record of who speaks, what appears on screen, and what happens when a step fails. A live session with no run of show depends on the host's memory. The document makes the sequence visible to everyone who has a role.
Set the timeline from the rehearsal backward
Start with the rehearsal date and the time the room opens to speakers. Work backward to the slide deadline, the speaker briefing, and the final check. The assistant should record each date with an owner. A timeline without owners is a wish list.
Add a buffer before the live start for the last technical check. A microphone or a screen share can fail at the worst moment. The assistant should record the fallback for each tool. A buffer that is not scheduled will be taken from the presentation.
Confirm the time zone of every speaker and every invitation. A run of show that lists only the host's local time will confuse a remote guest. The assistant should write the zone beside each time. A repeated confirmation is cheaper than an empty panel.
Check the platform limits for the number of panelists and the recording length. A session that exceeds the plan may stop or lose the recording. The assistant should record the limit and the plan that applies. A limit discovered during the session cannot be fixed.
Assign each speaker a cue and a backup
Give every speaker a named cue for when to start and when to stop. A cue can be a spoken line, a slide change, or a message in the chat. The assistant should record who gives the cue. A speaker who cannot see the cue may talk over the next segment.
Name a backup for each role, including the host, the moderator, and the person who manages the recording. A backup who has never seen the run of show is not ready. The assistant should brief the backup before the rehearsal. A role with no backup is a single point of failure.
Write the exact handoff line for each transition between speakers. A vague instruction to move on often produces an awkward silence. The assistant should test the line during the rehearsal. A tested transition sounds natural and keeps the time.
Record the pronunciation of each speaker's name and organization. A mispronounced name is a small error that the audience remembers. The assistant should write a phonetic note beside each name. The note should be visible to the host during the session.
Prepare the slides, links, and polls
Number every slide and record the speaker and the planned time for each one. A deck without numbers is hard to navigate during a live session. The assistant should keep a copy that the host can open independently. A shared screen should never be the only copy.
Open every link in the deck and confirm that it reaches the intended page. A link that works in the editor may fail in the presentation view. The assistant should record the final address and the date it was checked. A broken link in a live session cannot be quietly repaired.
Test each poll and each chat prompt before the session. A poll that was not launched cannot be recovered once the moment passes. The assistant should record the question, the options, and the result view. A poll result that is hard to read wastes the audience's attention.
Prepare a plain slide for a technical failure. The slide should tell the audience what is happening and when to expect the next step. The assistant should record who will speak while it is shown. A calm message is better than silence.
Run the live sequence with a timekeeper
Assign one person to keep time and to signal the speaker when a segment is over. The host cannot do this well while also presenting. The assistant should record the signal and the margin. A timekeeper who waits for the exact minute is already late.
Keep the run of show open beside the chat and the recording controls. The assistant should mark each segment as it starts and ends. A live note of the actual time makes the debrief accurate. A memory of the session is not a record.
Watch the chat for a question that changes the planned order. A repeated question may justify a short detour, while a single comment can wait. The assistant should record the decision and who made it. A host who reads every comment will lose the timeline.
Record the exact time of the start, the end, and each major transition. These times help the editor find the right segment and help the next session plan. The assistant should note any interruption that affected the recording. A timeline with gaps is hard to reconstruct.
Capture the recording and the follow-up list
Confirm that the recording started before the first speaker begins. A late start loses the opening, which is often the most quoted part. The assistant should record the file name and the location. A recording that cannot be found is not a recording.
Check the quality of the audio and the shared screen before the file is released. A recording with a silent panelist or a hidden slide is not ready. The assistant should record the timecodes that need a fix. A quick review saves a later complaint.
Build the follow-up list from the registration and attendance reports. The assistant should separate registrants, attendees, and people who asked a question. A single list with no segments leads to a vague message. A clear segment makes the follow-up useful.
Send the recording and the promised resources to the people who attended. The message should say what is included and when the link expires. The assistant should record the send date and the list used. A follow-up that arrives a month later loses its value.
Debrief while the details are fresh
Hold a short debrief within a day of the session. Ask each role for one thing that worked and one that did not. The assistant should record the answers before they fade. A debrief a week later becomes a summary of impressions.
Compare the actual timeline to the planned timeline and mark the largest gap. The gap may point to a slide, a speaker, or a technical step. The assistant should record the cause rather than only the minutes. A cause that is named can be fixed.
Update the run of show with one change for the next session. A second change can wait until the change is tested. The assistant should record the date and the owner. A template that changes every time is hard to compare.
Store the run of show, the recording note, and the attendance report together. Label the folder with the session date and the title. The assistant should keep the debrief beside them. The next session starts from evidence rather than a blank page.
Key takeaways
Build the timeline backward from the rehearsal and give every date an owner. Confirm the time zone of every speaker and the platform limits. Schedule a buffer for the last technical check. A buffer that is not scheduled will be taken from the presentation.
Give every speaker a tested cue and a backup for every role. Write the exact handoff line for each transition. Record the pronunciation of each name where the host can see it. A role with no backup is a single point of failure.
Number every slide and test every link, poll, and chat prompt. Prepare a plain slide for a technical failure. Keep an independent copy of the deck beside the chat and the recording controls. A shared screen should never be the only copy.
Confirm the recording before the first speaker and review the file before release. Build the follow-up list in segments and send it while the session is still relevant. Debrief within a day and adopt one change. A cause that is named can be fixed.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Office of Personnel Management - Training and development describes how agencies plan and evaluate training and development activities.
Related reading
Build a newsletter production checklist for a virtual assistant
A production checklist that fixes the send date, gathers source material, checks links and claims, routes review to the right owner, and archives the sent issue.
Create a client offboarding checklist for a virtual assistant
A closeout checklist that fixes the last day, final deliverables, access removal, records transfer, and the confirmation the client receives.
Set a supplier sample tracking log for a virtual assistant
A tracking log that records each sample on arrival, links it to the request and supplier, follows the review decision, and closes the loop on returns and storage.
