event-run-of-show

Start from the published grid and its disruption priority order, assign every day-of role by name, then build a cue sheet with one row per segment and per transition covering owner, tech owner, spoken lines, and escalation target. Present it section by section for validation before printing and briefing.

Each row carries the clock window, room, a named owner, a tech owner with material collected in advance, what is said out loud, what physically moves, and who to escalate to if the row fails. The attendee-facing schedule lacks all of these and should not be used as the staff document.

No. The MC orchestrates the whole event's flow while a separate speaker introducer handles each session, and collapsing the two is a named failure mode. Splitting hosting across multiple people is legitimate practice, and the introducer role can rotate freely.

The room lead names the problem and starts the clock, anything above their authority routes to the organizer on duty, and the decision follows the schedule's published disruption priority order rather than a fresh judgment. The revised grid is then locked for the block and announced in the room and on the channel.

Radios are promoted when mobile coverage fails, the footprint spans floors or buildings, staff have their hands full, or message volume outpaces reading. Radio leaves no written log, so pair it with a written channel, and check band licensing and any venue net you must join.

It never reopens the published session grid, rewrites the emergency plan, engineers AV redundancy, or designs the speaker green room; those belong to schedule design, risk management, production, and speaker experience respectively. It executes those plans and owns what staff do when they fail.