virtual-event-production

Rank five postures from a single one-way feed up to a managed virtual-venue platform against ops effort, procurement cost, reach, interaction, and compliance. The default is a public one-way feed plus your existing chat space; a managed platform is only promoted by concurrent tracks, sponsor deliverables, or a procurement constraint.

Moderation scales with concurrent sessions, not attendance: one named moderator per stream live at the same time. An open chat with nobody on duty is a code-of-conduct obligation with no responder, so close the interaction surface on any track you cannot staff.

Send a written home-setup note with the join link, run a tech check on the actual event platform, and for high-risk talks add an instructed local backup recording. A local recording saves the talk but does nothing for the audience in the minute the feed dies.

Publish a one-sentence fallback line before the day naming where the audience should go, then rehearse the sequence: notice, say it immediately, point somewhere, recover or reschedule, close the loop. Speed matters more than accuracy because every attendee first assumes the problem is on their end.

No. A presenting speaker cannot enforce a code of conduct against their own audience while talking, so this option is deleted rather than treated as a cheaper rung. A moderator must still hold conduct in the space even if the speaker reads their own questions.

Do not use it when a physical room exists: capture and the signal path for any room belong to the event-production skill, and serving a room and a remote audience at once belongs to hybrid-event-design. The format decision itself belongs to event-format-selection and is never re-argued here.