Skip to content
CHRONOMANCER
Use case

Allocation your crew can see is fair

Staff choose the named work they want and managers make the final decision. The order people are considered in comes from their reliability, rather than from who asked first or who knows whom.

Notch gauge11 of 18 · standby held
Lit · allocatedHalf · reserveGhost · still open
Roster lifecycleCurrent · Allocating
  1. Draft
  2. Requesting
  3. Allocating
  4. Scheduled
  5. Revise
  6. Live
  7. 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.

Seven states · one verb at a timeRevise loops back from Scheduled and Live
ChronometerStanding by

No request window is open on this page; the chronometer is shown without a time.

Countdown and absolute time,in the tenant's own timezone

Instruments drawn on an example night. This site carries no customer data.

Request the job as well as the time

A time slot tells someone when to turn up. A named position also tells them what they'll be doing. Staff request particular positions in particular areas, within the minimum and maximum you set per night, so the roster shows what people want to work as well as when they're free.

  • Requests are for named positions
  • Minimum and maximum requests per night keep things in proportion
  • Positions can require a skill, so unqualified people can't request them

Managers decide, and reliability sets the order

Requests don't take the decision away from the manager. Allocation is still made seat by seat. What changes is the list in front of them: requesters sorted by priority tier and by a reliability score from their own attendance history. Someone who turns up consistently sits above someone who doesn't, by the same rule each time.

  • Reliability score: attendance × hours fulfilment − no-show penalty
  • Recency-weighted, so people can rebuild a reputation
  • Managers place each seat, and nothing is allocated without them

From open requests to an audited roster

STEP 01

Positions go up

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

STEP 02

Everyone requests

Staff pick the nights and positions they want, within the limits you set.

STEP 03

Priority and reliability sort the field

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

STEP 04

A manager allocates

The sorted list informs the decision, but a person places each seat.

STEP 05

Reserve holds the rest

The people not placed can be held on a ranked standby list, ready if a seat opens.

STEP 06

Each move is logged

Who was placed, who was moved and who made the change all go into an audit trail.

Named positions
PEOPLE REQUEST THE JOB AND THE NIGHT
Audit trail
EACH ALLOCATION MOVE IS LOGGED
Recency-weighted
OLD RESULTS FADE FROM THE SCORE
Allocation decisions you can explain afterwards.

Questions about fair allocation

Do requests mean the system allocates automatically?

No. Requests and reliability scores sort the list and inform the decision. Nobody is placed until a manager places them.

How is the reliability score calculated?

It's calculated when a period completes, from attendance rate and hours fulfilment less a no-show penalty. Recent periods weigh more than old ones, so a rough patch fades over time.

Can staff request specific roles rather than any shift?

Yes. Requests are for named positions, each with its own capacity. A position can require a skill, and then only people who hold it can see and request it.

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

Yes. Each allocation, move and revision goes into an audit log with who made it, what they did, and the state before and after, so any decision can be checked later.

Show your crew how allocation is decided

Get in touch for a look at the allocation board and the audit trail behind it.