CHRONOMANCER
Use case

Wind up a season's roster in one publish

Opening weekends, holiday periods, event runs — put the whole period's work in front of your crew at once, and let the pool bid for it.

SATURDAY NIGHTFILLED 0/14
DEMAND 14 · RESERVE 3FILLING…

Publish the whole period, not one night at a time

Seasonal work doesn't arrive one shift at a time — it arrives as a block of nights that all need filling together. Build the period once: the nights, the areas, the named positions and their capacities. Then open it to your whole pool in a single publish, instead of chasing individual shifts as the season ramps up.

One period covers every night in the run
Capacity is set once per position, not re-typed nightly
Bidding opens and closes on a schedule you control

Let demand find its own level

When a season opens, everyone wants the same handful of prime nights. Bidding surfaces that automatically — you see exactly which nights and positions are contested and which are thin, before you allocate a single seat. No more guessing which weekends need a recruiting push.

See demand per night before you allocate
Spot thin nights early enough to act
Reserve pool absorbs the nights everyone wants

A season, start to finish

STEP 01

Build the period

Lay out every night in the run, the areas open each night, and the named positions with their capacities.

STEP 02

Publish once

Everyone in the pool gets a signed link by SMS and email — no app, no login. They bid for the specific nights and positions they want.

STEP 03

Watch demand land

Bids come in against every night at once, so you can see the whole season's shape before allocating anything.

STEP 04

Allocate with standby cover

Place bidders by priority tier and reliability, and hold a ranked reserve for every night — not just the contested ones.

STEP 05

Confirm and run

Confirmations go out for the whole run. Attendance and hours are tracked night by night as the season plays out.

STEP 06

Score on completion

When the period closes, reliability scores update for everyone who worked it — ready for the next season's allocation.

1 publish
COVERS AN ENTIRE PERIOD OF NIGHTS
Zero logins
FOR EVERY CASUAL ON THE ROSTER
2-way SMS
REMINDERS AND RESPONSES, BOTH DIRECTIONS
The mechanics that make a full season manageable from one dashboard.

Common questions

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 — a full run of weekends, a holiday stretch, a festival week. You build it once and publish the lot together.

What happens when a night is more popular than we have positions for?

Bidders are allocated by priority tier and reliability score, and everyone else who bid goes into a ranked reserve for that night — the top standbys are notified, the rest sit silently ready.

Does capacity change if we add extra areas partway through the season?

Yes — capacity is set per position and you can open additional areas for later nights as demand becomes clear, without rebuilding the nights 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 receive the same signed link as everyone else — no separate onboarding step, no app to install.

Get your next season's roster moving

Tell us about your peak period and your crew size — we'll show you how a full season would look under bidding.