Skip to content
CHRONOMANCER

Bid-based rostering software for casual shift crews

Publish the work for your next period and your crew requests the named shifts they want from a single link. There's nothing to install and no password to remember. You allocate, keep a standby pool and confirm. On the night, attendance and hours are recorded on a phone.

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
Notch gauge11 of 18
Lit · allocatedHalf · reserveGhost · still open
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.

First deployment An entertainment venue in New Zealand

Running live weekend rosters today

The four parts of a roster

The rest of Chronomancer is built around them.

Staff choose their work

You publish nights, areas and named positions, each with a capacity. Staff open a signed link and request the work they want on each night, so you know who wants what before you place anyone.

  1. You keep the decision

    A request doesn't place anyone by itself. You see the requesters sorted by priority tier and reliability score, place people yourself, and keep a ranked standby list for each night.

  2. Nights run from a phone

    When you confirm the roster, everyone placed hears by SMS and email. On the night you record attendance and hours on a phone or tablet, and moving someone to cover a gap doesn't send out another round of messages.

  3. Reliability adds up

    When a period is completed, each person's attendance rate and hours fulfilment feed into a reliability score. Recent periods count for more, and the score shows as a green, amber or red band.

Publish the work before you place anyone

A roster starts as a list of available work. You open the nights and choose which areas and named positions are on offer, and each person gets a private link to request what they'd like. When requests close, one board lines up the requests against the positions, sorted by priority tier and reliability, so you can see the whole night while you place people.

  • Named positions, each with a fixed capacity
  • A unique link for each person each period, with no app or password
  • Requests sorted by priority tier and reliability score
  • A ranked standby list for each night, ready before anyone drops out
Notch gauge11 of 18 · standby held
Lit · allocatedHalf · reserveGhost · still open
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

When someone drops out, the seat goes to standby

A person can withdraw through their own link, or you can mark them ill, unavailable or gone on the night. Either way, the empty seat is offered to the night's ranked standby pool with a one-time claim link. The first person to make a valid claim gets the seat, and anyone later is told it's filled. The live board updates on each device that has it open, so two supervisors on a busy night are looking at the same roster.

  • The first valid claim takes the seat, with no ringing round
  • The standby pool is ranked before the seat opens
  • The live board stays in sync across devices on the night
  • Withdrawals, cover and reassignments are all logged

Wind your next roster forward

Tell us about your venue and your crew, and we'll show you how requests would work for your next period.