A webinar run of show
with a time against every line.

Storyflow covers the whole of this: six columns on one board for start time, length, block name, speaker, what is on screen and the cue line, with the slides, the demo beats and the six-line backup plan beside them. A guest speaker reads it from a link with no account. Streaming the session, taking registrations and counting attendance is still a job for your webinar platform.

Six columns: start time, length, block name, who is speaking, what is on screen, and the cue line that hands over. Add the tech check and the holding slide before minute zero, and put the backup plan on Storyflow's board beside it. Anything the producer has to remember rather than read is the thing that gets forgotten.

A working split: two minutes of welcome, three on why they are here, two to introduce the guest, twenty two for the talk, eight for the demo, fifteen for questions, four for the offer and next step, and two minutes of slack so it ends at fifty eight. Adjust the talk and the demo; protect the questions.

Four others if you can: a host to open, link and close, a producer watching the clock and the polls, a chat moderator answering in writing, and a tech backup on a second machine with the deck already open. One person can hold two roles, but never the presenter, who should only be talking.

Holds the clock, sends private nudges at the five minute warnings, opens and closes polls, starts and checks the recording, and takes over the screen share if the presenter's fails. They are the only person allowed to interrupt, which is why the cue times live in their row on Storyflow's board.

Read the one you wrote in advance. Put a real question on Storyflow's board before the day and have the host open with it. Collecting questions on the sign-up form also helps: sort them into themes beforehand and half the Q and A is already written.

Written down, not improvised. The host keeps talking, the tech backup shares the deck from their machine, and the presenter rejoins on a phone if they have to. Write the same kind of line for a broken demo, a failed screen share, an audio echo and a lost recording. Six lines cover almost every live failure.

Forty five minutes before the doors open, with everyone who will speak. Sound, camera, screen share and the demo, in that order. Open the room fifteen minutes early with a holding slide so people who arrive early see something calm instead of an empty screen.

Storyflow builds and holds the running order, next to the slides and the demo steps it describes. It does not run the webinar. Streaming the session, taking registrations, sending reminder emails, recording and counting attendance all happen in your webinar platform, promoting it with paid posts in the ad platforms themselves, and editing the recording afterwards in a review tool such as Frame.io, Filestage or Ziflow.

Yes. Storyflow's view-only link opens in any browser with no account, which is what you want when the speaker is from another company and will use it once. If they want to leave a note on their block they sign in to comment, and anyone a paid member invites to a board joins free.

Yes, as a draft. Attach the deck outline and last month's board and ask Storyflow's AI for a sixty minute run of show. It proposes the blocks, the lengths and the cue lines. You decide what the demo really takes and where the talk is too long, because it is the part only you have watched go wrong before.

Storyflow's table holds one row per block with its start time, length, speaker and cue line, and the length column takes a Sum footer so the total tells you straight away when the hour no longer fits. It cannot sort a table: rows stay in the order you drag them into. For a running order that is what you want, because the order is the show.