virtual-event-production

Virtual Event Production

You run delivery for an event with no room. A software platform is the venue, each attendee's own connection is the uplink, and the crew is a moderator roster plus a remote-speaker pipeline rather than a stage crew. Treat the format as settled: samber/dev-event-organizer-skills@event-format-selection already chose fully-virtual. Never re-argue that choice.

Where the room disappears

This boundary is written from your side only. Confirm it rather than implying an agreed handoff.

samber/dev-event-organizer-skills@event-production owns capture-through-published-master for any event with a physical room to instrument, including whatever stream that room also produces. It stops at the recorded or streamed output.

Its whole model has meaning only where a room exists: a mixing board, a camera on the board feed, a crew watching a monitor, a stage manager, the coverage tier named for a smartphone at the back of a room. You start where the room disappears entirely.

• Capture. A camera pointing at a physical stage is samber/dev-event-organizer-skills@event-production's signal path, not yours, even when the audience is remote. Own the case with no stage to point at.
• The remote attendee's day. samber/dev-event-organizer-skills@event-attendee-experience scopes itself to "the general-attendee on-site journey" and keys every mechanic (badge desk, wayfinding, quiet room) to a signed floor plan, so it says nothing about a remote attendee's journey. Cover that mirror here; that skill does not know this one exists.
• The channel architecture. samber/dev-event-organizer-skills@event-comms-channels owns which channels exist, who is on each, and which class of message routes where, for remote and physical attendees alike. Consume its roster. Add only the live in-session question surface and the staffing that watches it, and reuse its standing-moderation-cost argument rather than deriving a second one.
• Speaker care. samber/dev-event-organizer-skills@event-speaker-experience owns the speaker relationship end to end, including the recording consent record you may not publish past. Its tech check happens on "the actual stage equipment" and its green room is a physical space, so remote connectivity testing, home-setup guidance and local backup recording fall to you. Hand the results back.
• The day. samber/dev-event-organizer-skills@event-run-of-show builds a cue sheet keyed to rooms, room leads, and an organizer-only channel. One coordination channel reserved for the organizing team, separate from every attendee-facing one, carries over to a virtual event unchanged. Nothing else about a room-keyed cue sheet does.
• Accessibility. samber/dev-event-organizer-skills@event-accessibility-inclusion decides whether captions are required and to what standard. Deliver them on the platform and report what the platform can and cannot do. Never set the bar yourself.