Every event on the venue’s record.
Events, bookings and ticketing planned against the spaces, the roster and the guests the rest of the operation already runs on.
Events, bookings and tickets, as one plan.
An event is a space, a headcount, a brigade and a guest list. All four already exist on the model.
Capacity planned against the space
Events and bookings sit on the same spaces and times, so a room is never sold twice and a service is never squeezed by a party nobody told the kitchen about.
Staffing called against the roster
The people an event needs are requested from the roster Workforce already solves, inside the same hours and qualification rules.
Tickets and reminders that reconcile
Ticketing, reminders and the guest list on one record, reconciled to what the event actually consumed once it closes.
What it writes to the model, and what Launchpad does with it.
A booking is written against the venue, the shift and the guest, so the roster, the kitchen and the front desk see the event without being told.
- Reads & writes
- events, bookings, tickets, spaces, staffing
- Launchpad
- Plans capacity. Calls staffing against the roster. Reminds and reconciles.
- Autonomy
- Set per capability, from off to unattended, and movable back
- Works with
- Workforce, Recipes, Messaging