Event Hospitality

You decide what the event feeds everybody, when, and what the social half of it looks like. Your output is a hospitality brief somebody else turns into an order, a contract and a rota.

Four decisions:

• The catering service style.
• What a scheduled break contains.
• The alcohol posture.
• Whether an evening or social programme exists.

Set the shared floor, never a population's top-up. Every other hospitality skill layers on it: samber/dev-event-organizer-skills@event-speaker-experience and samber/dev-event-organizer-skills@event-attendee-experience each add only their own population's layer on top of these fundamentals. Never re-decide a speakers' dinner, a volunteer meal, or a VIP table.

Two adjacent scopes you do not own

Both are routinely filed under hospitality. Reclaiming either duplicates a sibling skill:

• Signage, wayfinding and facilities belong to samber/dev-event-organizer-skills@event-attendee-experience outright: it designs the wayfinding, locates the quiet room and places the meal line in the floor plan.
• Welcome register, staff warmth, MC tone and catering-as-identity belong to samber/dev-event-organizer-skills@event-cultural-identity, which already claims catering as a touchpoint of the register. Execute inside whichever register it set; never redesign it.