For organizers running one day for two audiences
Hybrid GridThe remote audience's half of a hybrid event, promised once and delivered session by session.
Enter what the remote audience was promised, the published grid with which rooms can carry a feed, each session's recording consent and the last date a session can join the stream, and get - free in your browser, in the order the skill sets - the promise in one sentence, remote eligibility marked on the grid as a column, the parity depth, a named remote person per streamed session and the two-audience gap in the disruption order closed; then the stream's cue track for the run of show and the remote advocate brief. This skill is deliberately narrow: the format decision must already be closed (if hybrid is still being weighed, it routes you to event-format-selection), production coverage tiers belong to event-production, consent records to event-speaker-experience, the run of show to event-run-of-show and the budget to event-budget - it hands off and never decides for them. It never names a streaming platform as a recommendation or a price, never specifies equipment, never moves a session on the grid, and labels every number of its own self-set.
The event free
For example UTC+1 or UTC-5 - an offset, never a zone name.
UTC offsets, comma-separated.
Blank means today.
The interview free
The skill's ten questions, word for word
- What was the remote audience actually promised, and to whom? A paid virtual ticket, a sponsor deliverable naming the stream, an access commitment to people who cannot travel, or nothing written down. It reorders every menu below, and the rest of the day gets argued against it.
- How many rooms run at once, and how many of them can physically carry a feed? A room the production sibling cannot instrument deletes rungs rather than reordering them.
- Where is the remote audience relative to the room: the same working day, or a spread wide enough that part of your programme lands in the middle of their night?
- What is the recording and publication consent posture per session, and who holds that record? Does the in-room audience appear on the outgoing feed during Q&A?
- Does anything constrain which platform may carry the feed, or where attendee data may sit: an employer's procurement, a sponsor's contract, an umbrella organization's rules?
- Has the schedule document arrived with a disruption priority order, and does it say anything about the remote side? Silence there is a gap you close in advance (see § The cue track the stream needs).
- What is the last date a session can still join or leave the remote programme? These menus are ranked against that deadline, not against the event date.
- One-off edition or a recurring event? A recurring event promotes every rung whose payoff lands after this edition: a briefed advocate, a cue template carrying both audiences, a consent form that already asks the right question.
- What is the effort ceiling: how many people can work the remote side alone during a session, rather than also covering something in the room?
- What already exists that should re-rank these defaults: a room already wired, an organizer who has streamed before, last edition's remote complaints, a community that already lives in a chat space?
Q2 is answered by the rooms table in card 3, Q4 per session on the grid, Q6 with the disruption order in card 4.
Copy it from the ticket page, the contract or the commitment - keep it short.
Comma-separated, for example Main Hall, B2, B5. A room name takes every session in it.
Handed to event-production as a constraint - the page recommends no platform and prices none.
The published grid and the rooms free
The grid as event-schedule-design published it - the page adds a column and never moves a session.
The crew and the disruption order free
A name per streamed session, never a function. A room lead is never the remote advocate.
The hybrid design, worked out free
What the page flags
The promise - every later choice is measured against it
The published grid with the remote eligibility column
Eligibility and parity depth - re-ranked, deleted rungs struck
The crew split and the remote advocate - a name per streamed session
The stream's cue track - one more column on the run of show
The two-audience gap and the hand-offs
The files free
The grid with its eligibility column, the cue track (as a table and as a calendar), the crew sheet, what the remote audience is told, and everything the page worked out.
The design metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
The page's check of this reply
Saved hybrid designs
How it works - and what is sourced
The order is the skill's: confirm the format decision is closed (if hybrid is still being weighed, route to event-format-selection and stop); write down what the remote audience was promised, in one sentence; mark remote eligibility on the published grid as a column, never a separate list (Menu 1); choose the parity depth and what it looks like minute to minute (Menu 2); hand the eligible-session list to event-production and check the consent record with event-speaker-experience before the grid is marked; staff the remote side by name per streamed session (Menu 3); add the stream's cue column to the run of show and hand it to event-run-of-show; close the two-audience gap in the disruption priority order in writing and say who decided; report the staffing consequence to event-budget, split by what a lean tier can drop.
Sourced from the skill and its references: the ten questions, the three menus with their rankings, defaults, promotions and deletions (a room that cannot carry a feed deletes every-session and opt-in; publishing the recordings afterwards, an open channel nobody reads and the room lead doubling as the advocate are struck), what each parity rung looks like inside a session, what the cue column carries, the gap rows, the documented disruption defaults and the two open questions. The page's own, said wherever used: the promise sentence's template, the reading that a promise of live Q&A puts reserved floor time first and that a remote night promotes the written return path, and these self-set lines - the pre-roll at -5 min, the Q&A handover and relay 10 min before the end, a remote night from 00:00 to 06:00, a join/leave deadline under 14 days is soon, a room missing from the rooms table cannot carry a feed, audience questions off camera until settled, at most 40 sessions and 60 cues sent to the run, a 40-word summary and at most 5 caveats. Never stated at all: a streaming platform as a recommendation or a price, a piece of equipment, a parity threshold, a staffing ratio, a share of Q&A owed to remote or a tolerable stream delay.