Event Side Event Coordination

You decide what happens when somebody who is not you runs an event inside your event's dates or venue orbit: whether you approve it, whether you list it, what they may call it, when it may run, and what you say you are not responsible for.

The default answer is often nothing at all. Most community events never formalise this and are right not to. Decide deliberately once, rather than at T-2 weeks when a poster carrying your logo turns up in a bar.

What you own, and what is already decided

You own the relationship with an event you do not run. Four questions, and only these four: approval, calendar, name, liability.

• The evening you run yourself is not yours. samber/dev-event-organizer-skills@event-hospitality decides whether the event has a mixer, a dinner or no organised programme, and it already deletes the do-nothing rung it calls "everyone will end up at a bar somewhere" for having nobody responsible. Your subject starts one step out: an event somebody else is responsible for. That skill's evening is what you provide; yours is what you permit.
• The policy's reach is not yours. samber/dev-event-organizer-skills@event-code-of-conduct decides whether its scope clause covers a satellite event, a jurisdiction question, and never the approval process. Its own interview asks who is bound "beyond ticket-holders", naming satellite and attendee-run fringe events among them. Hand it the confirmed list of approved satellites so its scope clause can name them; take from it the adoption requirement your criteria set enforces.
• The peer swap is not yours. samber/dev-event-organizer-skills@cross-event-promotion brokers reciprocal visibility between two independently-run events. Nobody hosts anybody and nobody approves anybody. A counterparty asking you to promote their event, rather than to run something inside your dates, belongs to that skill.
• The grid is not yours. samber/dev-event-organizer-skills@event-schedule-design owns the published session grid you deconflict against. Never move a session to make room for somebody else's party.
• The main venue is not yours. samber/dev-event-organizer-skills@event-venue-sourcing secures it. Note the name collision: that skill's "satellite sites" means extra venues for your own event, never a third party's separate one.
• Selling a side-event slot is not yours. samber/dev-event-organizer-skills@event-format-selection already lists side events among the inventory a sponsor may buy, and samber/dev-event-organizer-skills@event-sponsor-fulfillment delivers what was sold. You decide the terms a bought slot runs under, exactly as you decide them for any other satellite.

Interview