How does scriptwriting differ for live webinars versus pre-recorded tutorials?

WHAT THIS TESTS: This question probes whether you think in formats or just in information. A senior writer knows that a live webinar is a real-time performance with uncontrolled variables like audience attention decay, technical failure, and invisible feedback, while a pre-recorded tutorial is a retention product where the enemy is the back button. The interviewer wants to hear you map structure, pacing, and risk to the delivery mechanism itself.

A GOOD ANSWER COVERS: Four distinct dimensions in order. First, STRUCTURE: live scripts must be modular, with self-contained ten to fifteen minute chunks and clear re-entry points because attendees join late, leave, or multitask; recorded scripts should follow a tight narrative arc with progressive disclosure, since rewinding is possible but viewer patience is lower. Second, PACING: live delivery requires padding the script by twenty to thirty percent to absorb Q&A, polls, and technical delays without rushing; recorded pacing should be aggressive, aiming for one core concept per two to three minutes and a visual or tonal change every twenty to thirty seconds to prevent drop-off. Third, CONTINGENCY: live contingencies are audience-facing and operational, including pre-written chat responses, a co-host to manage questions while the presenter recovers, and fallback demos if the live screen share fails; recorded contingencies are production-oriented, such as alternate voice-over takes, script versioning for post-discovery errors, and B-roll to cover edit points. Fourth, ENGAGEMENT MECHANICS: live scripts rely on direct address, real-time calls to action, and social proof moments; recorded scripts use predicted friction points, pattern interrupts, and precise signposting because the viewer is alone.

COMMON WRONG ANSWERS: Treating the two formats as identical except for the presence of a chat window. Claiming that live content can be fixed in post, which reveals no understanding of broadcast risk. Ignoring the cognitive load on a live presenter who cannot pause to think. Asserting that recorded tutorials need no contingency planning, when in fact they need rigorous production backups to avoid expensive reshoots. Suggesting that a recorded script should leave room for improvisation, which usually creates edit room nightmares.

LIKELY FOLLOW-UPS: How would you repurpose a live webinar into an evergreen recorded course? What is your exact backup plan if a live demo breaks two minutes in? How do you script differently when you can see real-time drop-off analytics versus when you are flying blind? When is it better to pre-record a segment and play it during a live event?

ONE CONCRETE EXAMPLE: A strong candidate describes scripting a sixty-minute live product launch as three modular twelve-minute teaching blocks, each ending in a poll to re-engage stragglers, plus a hidden slide deck ready if the internet drops. For the recorded counterpart, they describe a five-minute onboarding tutorial where every sentence is timed to a screen transition, the script includes two alternate voice-over takes for the complex setup step so the editor has options without a reshoot, and the contingency is a pre-rendered video insert that plays if the live capture fails.