Staff reliability scoring based on attendance records
Each time a period is completed, every person's reliability score is recalculated from the record: whether they turned up, whether they worked the hours expected, and whether they missed shifts without notice. At the next allocation, the result sits beside their name.
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- 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.
No request window is open on this page; the chronometer is shown without a time.
Instruments drawn on an example night. This site carries no customer data.
One formula, calculated for you
When you complete a period, Chronomancer recalculates the score of each person who worked in it. It multiplies attendance rate by hours fulfilment (capped), then takes off a no-show penalty. A no-show costs more than a cancellation made with notice, because "something came up and they told us" and "they didn't turn up" are different things.
- score = 100 x attendance rate x hours fulfilment (capped) minus no-show penalty
- Cancellations with notice cost less than no-shows
- Recent periods are weighted more heavily through exponential decay
- Each contact's score and history are stored for quick lookup
- Draft
- Requesting
- Allocating
- Scheduled
- Revise
- Live
- 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.
No request window is open on this page; the chronometer is shown without a time.
A band you can read at a glance
Behind each score is a green, amber or red band, so allocating doesn't mean reading a spreadsheet. When you sort requests at allocation, or decide the order of a night's standby list, the band and the percentage are shown next to the person's name.
- A green, amber or red band beside the percentage
- Sets request order at allocation, after priority tier
- Also sets the order of a night's standby list
- Each contact's history is kept for the reliability report
Who sees it is up to you
Reliability and priority are sensitive, so Org Managers don't see them by default. A manager can run rosters, allocate requests and message staff without seeing anyone's rating. An Org Admin can choose to grant that visibility for their organisation; it isn't switched on for every role.
- Hidden from Org Managers by default, even though they allocate
- An Org Admin can grant visibility for their organisation
- The reliability report is a separate permission, granted per role
- Admins who need the trend have a reliability report tab
Questions about reliability scoring
How is the reliability score calculated?
It's 100 times the attendance rate times a capped hours-fulfilment factor, minus a no-show penalty. Recent periods are 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 less than a no-show. The formula treats them differently on purpose.
Where is the score used?
At allocation, requests are sorted by priority tier and then by reliability score. The same score sets the order of a night's standby list.
Can Org Managers see everyone's reliability score?
Not by default. Managers run rosters and allocate requests without seeing contact priority or reliability. An Org Admin has to grant that visibility for the organisation.
Can we see how someone's score has changed over time?
Yes. History is kept for each contact, and the reliability report tab shows each person's trend across periods. It's admin-only unless you grant it to another role.
See where the score fits
Tell us how you allocate shifts now, and we'll show you where the score would fit in.