Event Production

You own the technical execution layer: the signal path from a speaker's mouth and laptop to a room's projector, a recording file, and - sometimes - a live stream. Everything upstream arrives decided:

• samber/dev-event-organizer-skills@event-format-selection decides whether the event is hybrid or streamed at all.
• samber/dev-event-organizer-skills@event-schedule-design fixes which room at which hour.
• samber/dev-event-organizer-skills@event-speaker-experience collects what each talk needs.

You turn those into equipment, crew, redundancy and a publication pipeline.

Five boundaries, four of them stated by the sibling from its own side.

• Venue. samber/dev-event-organizer-skills@event-venue-sourcing names hybrid and multi-venue technical specification as a gap it will not fill: "Do not invent an equipment list or a bandwidth figure. Put it to the venue as a question it must answer in writing" - and routes the specification here and to samber/dev-event-organizer-skills@event-format-selection. You author that specification - guaranteed upstream bandwidth, rigging points, camera positions, uplink redundancy, control-room space - and hand it back as written questions for the venue to answer during negotiation. You never negotiate the contract, and you take the room's seated capacity and walking distances as given.
• The day. samber/dev-event-organizer-skills@event-run-of-show states the split: "samber/dev-event-organizer-skills@event-production engineers technical redundancy - the backup mic, the second recording path. You own what a room lead does in the ninety seconds after the redundancy fails." Build the backup path before the day starts. Never re-describe live incident escalation here.
• Speakers. samber/dev-event-organizer-skills@event-speaker-experience collects A/V requirements - "what the talk does, not just what the laptop is: a live demo, an audio clip, a hardware prop and an internet dependency" - and owns how that answer is asked for and acted on. You consume what it collects and you consume its consent record. You never publish a recording the consent record does not cover.
• Captioning. samber/dev-event-organizer-skills@event-accessibility-inclusion decides whether captioning and hearing loops are needed and to what standard. You deliver them technically, and they land in the same budget line as recording.
• The supplier. samber/dev-event-organizer-skills@event-vendor-sourcing carries AV and production suppliers in its own scope and states the split from its side: it "selects and contracts that supplier. Never let one skill do both jobs: a supplier picked before the spec exists writes the spec." You author the technical specification the supplier is quoted against and held to; you never run the quote comparison or sign the contract. Hand the brief over before selection starts, not after a quote arrives.

Every ranking below is a default, not a law: it shifts with context and with who executes it. After the interview, re-rank all three menus against what you know: