Put a whole season's roster out in one go
Opening weekends, holiday periods and event runs can all go in front of your crew together, and the pool requests from the lot.
- 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 the whole period at once
Seasonal work comes as a block of nights that all need filling. Build the period once, with its nights, areas, named positions and capacities, and open it to your whole pool in a single publish. You aren't chasing single shifts as the season gets busier.
- One period covers each night in the run
- Capacity is set once for each position, so nobody re-types it every night
- Requests open and close on a schedule you control
See where demand lands
At the start of a season, everyone wants the same few nights. Requests show you which nights and positions are contested and which are thin before you allocate anyone, so you can tell which weekends need a recruiting push.
- See demand for each night before you allocate
- Spot thin nights early enough to do something about them
- Extra requesters on popular nights go to the reserve
A season, start to finish
Build the period
Lay out the nights in the run, the areas open on each, and the named positions with their capacities.
Publish once
Everyone in the pool gets a signed link by SMS and email, with nothing to install or log in to. They request the nights and positions they want.
Watch the requests arrive
Requests come in against all the nights at once, so you see the shape of the season before you allocate.
Allocate with standby cover
Place requesters by priority tier and reliability, and keep a ranked reserve for each night, including the quiet ones.
Confirm and run
Confirmations go out for the whole run. Attendance and hours are recorded night by night as the season goes on.
Score on completion
When the period is completed, reliability scores update for everyone who worked it, in time for next season's allocation.
Questions about seasonal rosters
Can we publish a whole season at once, or does it have to be night by night?
A period can hold as many nights as your season needs, whether that's a run of weekends, a holiday stretch or a festival week. You build it once and publish it all together.
What happens when a night is more popular than we have positions for?
Requesters are placed by priority tier and reliability score, and everyone else who asked can be held on that night's ranked reserve. The people at the top are told they're on standby, and the rest wait as a silent reserve.
Does capacity change if we add extra areas partway through the season?
Yes. Capacity is set per position, and you can open more areas on later nights as demand becomes clear, without rebuilding nights you've already published.
How do we handle a burst of new casuals joining right before the season opens?
Add them as contacts before you publish and they get the same signed link as everyone else. There's no separate onboarding step and no app to install.
Get your next season's roster moving
Send us your season dates and crew size, and we'll show you how the whole run would work in Chronomancer.