Rostering software for events and venues with uneven demand
Each event brings its own rush. Publish it as a period and your casual pool requests the named work on offer. You allocate with a standby pool ready for no-shows at the gate, and a supervisor runs the event from their phone.
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
No request window is open on this page; the chronometer is shown without a time.
Instruments drawn on an example night. This site carries no customer data.
Publish each event as a period
A stadium gate, a festival weekend or a function room that turns over three times a night can each be a period, with named positions and fixed capacities: gate one, bar three, the VIP zone. Open the positions the event needs and your casual pool sees what's on offer for that date and nothing else.
- Named positions with fixed capacities for each event
- A site, zone and position hierarchy in your own terms
- Priority-ranked positions for a smaller event day
- Skills decide who can see and request a position
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
No request window is open on this page; the chronometer is shown without a time.
Requests instead of a phone tree
Chasing a casual pool through a group chat or a call list gets hard past a few events a month. Each worker gets one signed link per period and requests the positions they want at the events they can work. Reminders go to the people who haven't answered, so you don't have to make the calls.
- A link per person per period, with nothing to install
- Requests for named positions at particular events
- Automatic reminders to non-responders before requests close
- Link opens logged for security review
Standby cover at the gate, supervisor mode on the night
Some no-shows on event day are a given: someone's sick, someone's stuck in traffic. Each event night can carry a ranked standby list, and an empty seat is offered to it with a claim link. The first to claim it gets it, so cover at the gate doesn't wait on a phone call. On the day, your supervisor on site runs a live view of attendance, hours and moves, without config access or the rest of the admin console.
- A ranked standby list for each event night
- An empty seat goes to the first valid claim
- A supervisor-only live mode for event-day staff
- Hours recorded on the day, ready for payroll
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- Completed
Allocating. Requests are in and seats are being filled. Every roster sits at exactly one station, and each station names the one thing left to do.
Questions from events & venues
We only staff a handful of events a month. Is this too much for us?
No. Each event is its own period, published and completed on its own, so there's no standing roster to keep up between events.
Can casual staff work events across several venues we run?
Yes. Your venues sit in one hierarchy under your organisation, and each event's roster opens the positions it needs. A contact's request history and reliability score go with them to all your events.
How do we cover a no-show right at gate time?
Mark the seat (or tap Recover slot) and it's offered to the night's ranked standby list with a one-time link. Whoever claims it first is placed, and nobody has to redial down a list.
Who runs the event on the day if our office team isn't there?
Someone with the supervisor role. They see Live only, with attendance, hours and moves for the event, and have no access to configuration or other admin functions.
Do we get hours data for payroll after the event?
Yes. Expected and actual hours are recorded against each position and roll up into reporting for payroll and reliability scoring.
Talk to us before your next event
Tell us what a typical event day looks like for your staff. We'll show you how the next one would run on requests.