CHRONOMANCER
The score

Staff reliability scoring built from attendance, not opinion

Every completed period recomputes a reliability score per person, from what actually happened: did they show, did they work the hours expected, and did any no-shows go unexplained. It's the number that quietly makes your next allocation easier.

SATURDAY NIGHTFILLED 0/14
DEMAND 14 · RESERVE 3FILLING…
Built in Auckland, New Zealand
Running live weekend rosters today
Proven at a leading NZ haunted attraction
Recomputed automatically on every period completion

One formula, computed automatically

When you complete a period, Chronomancer recalculates each attending person's score from attendance rate and hours fulfilment, capped and combined, then subtracts a no-show penalty. No-shows are penalised harder than a cancellation made with notice — the system distinguishes 'something came up and they told us' from 'they just didn't turn up'.

score = 100 x attendance rate x hours fulfilment (capped) minus no-show penalty
Cancellations with notice are treated more leniently than silent no-shows
Recent periods are weighted more heavily via exponential decay
The score and its history are cached per contact for fast lookup
Draft
Bidding
Allocating
Scheduled
Live
Completed
BIDS CLOSE IN41:12:0934/41 RESPONDED

A band you can read at a glance

The raw score is backed by a simple green, amber or red band, so allocating doesn't mean reading a spreadsheet. When you're sorting bids at allocation time, or ranking who sits where in the standby pool, the band and the percentage are right there next to the person's name.

Green, amber or red band alongside the underlying percentage
Feeds bid sort order at allocation, alongside priority tier
Also ranks who sits where in a position's standby pool
Full history retained per contact for the reliability report

Visibility is a setting, not a given

Reliability and priority are sensitive information, so they're hidden from Org Managers by default — managers can run rosters, allocate bids and message staff without ever seeing who's rated where. An Org Admin can grant that visibility deliberately, per organisation, rather than it being switched on for every role automatically.

Hidden from Org Manager by default, even though managers allocate
Org Admin can grant visibility deliberately, per organisation
Never delegable to Supervisor or Support roles
A dedicated reliability report tab for admins who need the trend
SATURDAY NIGHTFILLED 0/14
DEMAND 14 · RESERVE 3FILLING…
Auto
RECOMPUTED ON EVERY PERIOD COMPLETION
3 signals
ATTENDANCE, HOURS FULFILMENT, NO-SHOWS
Recency-weighted
RECENT PERIODS COUNT FOR MORE
Hidden by default
MANAGERS DON'T SEE IT UNLESS GRANTED

Questions about reliability scoring

How is the reliability score actually calculated?

It's 100 times attendance rate times a capped hours-fulfilment factor, minus a no-show penalty, with recent periods weighted more heavily than older ones through exponential decay.

Does a cancellation count the same as a no-show?

No. A cancellation made with notice is penalised more lightly than a silent no-show — the formula treats the two differently on purpose.

Where does the score actually get used?

At allocation, bids are sorted by priority tier and then reliability score, and the same score ranks who sits where in a position's standby pool.

Can Org Managers see everyone's reliability score?

Not by default. Managers run rosters and allocate bids without seeing contact priority or reliability — an Org Admin has to deliberately grant that visibility per organisation.

Can we see how someone's score has changed over time?

Yes — history is retained per contact, and there's a dedicated reliability report tab (admin-only) showing each person's trend across periods.

See the score in context

Tell us about your venue and your crew — we'll show you how reliability scoring shapes your next allocation.