How to use the Event Run of Show Generator.
A run of show is an operational cue sheet. Include time, duration, owner, location and transition cues, and distinguish doors opening from the first program segment.
Make the workflow fit your task.
Translate the program into timed operational cues, including setup, doors, transitions and teardown. Assign an owner and location to each cue and distinguish public timing from crew timing. Review overlaps with the people running the event.
- What you provide
- Confirmed segments, speakers and timings.
- What you get
- Detailed show sequence with owner and transition notes.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Doors open at 09:00; welcome at 09:30 for 10 minutes; demo follows for 20 minutes.
Completed example
09:00 Doors open — registration lead. 09:30–09:40 Welcome — host. 09:40–10:00 Demo — presenter, AV operator ready at 09:38. Confirm transition and contingency cues with the crew.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a run of show include only the audience-facing agenda?
Include crew actions too, such as microphone handoffs and slide readiness, because those make the public sequence possible.
Why does the event run late despite sessions fitting the schedule?
Transitions, questions or room resets may have no allocated time. Add those intervals explicitly.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑