CHRONOMANCER
Use case

Allocation your crew can see is fair

Staff choose the named work they actually want. Managers keep the final decision. Order is earned through reliability, not who asked first or knows someone.

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

Bid for the named work, not just a time slot

A time slot tells someone when to show up. A named position tells them what they'll actually be doing. Staff bid for specific positions — a particular area, a particular role — within the min and max limits you set per night, so the roster reflects what people actually want to work, not just when they're available.

Bids are for named positions, not generic shifts
Min/max bids per night keep the pool honest
Bidders can be gated by skill, so unqualified requests never clash

Managers decide, reliability earns the order

Bidding never removes the manager's judgment — allocation is still a deliberate decision, seat by seat. What changes is the input: bidders are sorted by priority tier and a reliability score computed from their own attendance history, so the person who reliably shows up rises above the one who doesn't, automatically and the same way every time.

Reliability score: attendance × hours fulfilment − no-show penalty
Recency-weighted, so people can rebuild a reputation
Managers place every seat; the system never auto-allocates behind their back

From open bidding to an audited roster

STEP 01

Positions go up

Named positions are published for the period, each with its own capacity.

STEP 02

Everyone bids

Staff pick the specific nights and positions they want, within their min/max limits.

STEP 03

Priority and reliability sort the field

Contested positions are ranked by priority tier, then by each bidder's reliability score.

STEP 04

A manager allocates

The sorted list informs the decision, but a person places every seat — nothing allocates itself.

STEP 05

Reserve holds the rest

Everyone not placed goes into a ranked standby pool, ready if a seat opens.

STEP 06

Every move is logged

Who was placed, who was moved, and who allocated it — all written to an audit trail.

Named positions
BID FOR THE WORK, NOT JUST THE HOUR
Full audit trail
EVERY ALLOCATION MOVE IS LOGGED
Recency-weighted
RELIABILITY SCORE, NOT A PERMANENT MARK
The mechanics that keep allocation decisions visible and defensible.

Common questions

Does bidding mean the system allocates automatically?

No — a manager places every seat. Bidding and reliability scoring sort and inform the decision; the final allocation is always a deliberate human call.

How is the reliability score calculated?

It's computed on period completion from attendance rate and hours fulfilment, with a no-show penalty and recent periods weighted more heavily than old ones — so a rough patch doesn't follow someone forever.

Can staff request specific roles, not just any shift?

Yes — bidding is for named positions with their own capacity, and can be gated by skill so someone only sees and requests work they're qualified for.

Is there a record of who allocated what, in case someone disputes it?

Every allocation, move, and revision writes to an audit log — actor, action, and before/after state — so any decision can be reviewed after the fact.

Make allocation something your crew trusts

Tell us how you allocate shifts today — we'll show you what earned, audited allocation looks like.