Scheduled vs actual vs arbitrated times
A shift carries three sets of times — what the rota scheduled, what book-on and book-off recorded, and what an Admin or Manager arbitrated for pay. Screens that answer what time the shift actually ran read the first of those that exists, taking arbitrated before actual before scheduled, which is how a correction made for payroll reaches the employee's own schedule.
Which times does a screen show?
Four values, checked in this order. The first one that has been recorded wins.
| Times | Where they come from |
|---|---|
| Arbitrated | An Admin or Manager set them on Arbitration |
| Actual | Book-on and book-off |
| Expected | The scheduled times, copied onto the pay record the moment arbitration first ran for that shift |
| Scheduled | The shift as it stands on the roster |
So a shift nobody has arbitrated shows its actual times; a shift nobody booked on to shows its scheduled times.
Expected and Scheduled are the same value in the ordinary case, and separate only because expected is a snapshot. It is copied from the shift when the pay record is written and is not rewritten if the roster is edited afterwards.
Where do actual times come from?
From the person on shift pressing Book On and Book Off on their Check Calls screen. The time recorded is the moment the button is pressed, not the time the shift was due to start.
Two side effects follow. Booking on moves the shift to In Progress and booking off moves it to Completed. And if somebody makes a check call without having booked on first, the platform books them on at that moment and notes it as Auto booked on via check call.
Actual hours are book-off minus book-on, minus any break recorded between them.
An agency officer's times come the same way, from the officer's own Book On and Book Off in the phone app. That also moves the organisation's shift on the roster to In Progress and then Completed, and the position the app sends (with the current version of the app) is kept. If a manager instead marks an officer's shift In progress or Completed on the roster, the officer is booked on or off at the scheduled times, and those become the shift's recorded times. Officer shifts are not arbitrated for pay by default: the agency pays its officers.
One pair of times is thrown away rather than trusted: a book-on and book-off less than 60 seconds apart is treated as a shift closed off from the roster rather than worked, and the shift is read as having no actual times at all.
Booking off before the scheduled end asks why: Emergency, Unwell, Released by the client, Relieved early, Site closed or Other (which needs a note). The reason travels with the shift into arbitration.
There is one book-off nobody presses. A shift pattern with Automatic book off switched on books off anyone still booked on once the shift's end has passed, at the scheduled end time, and records the reason as No book-off received. Those times are the system's guess, not an observation, and arbitration treats them that way (below).
What does running arbitration do?
Arbitration sits under Scheduling and is open to Admin and Manager. Run Arbitration offers Use Actual Times or Use Expected Times, and writes one pay record per shift across the date range on screen. What it writes depends on the state of the shift:
| The shift | What arbitration writes |
|---|---|
| Booked on and booked off, both within 15 minutes of the scheduled times, and the worked hours within 30 minutes of the scheduled hours | Auto Arbitrated |
| Booked on and booked off, either one more than 15 minutes out | Manual Advised, flagged Time variance: with which end, by how many minutes, and whether early or late — plus the book-off reason on an early finish |
| Worked hours more than 30 minutes from the scheduled hours, however close the start and end look | Manual Advised, flagged Worked …h against …h scheduled. A book-off a day late is caught this way |
| No pay rate anywhere | Manual Advised, flagged No pay rate set — priced at £0 |
| Booked off by Automatic book off | Manual Advised, flagged no book-off received — auto-closed at scheduled end, however close to schedule the times look |
| Never booked on, its end time passed, and the employee declined it | Dropped |
| Never booked on and its end time passed, with no decline | Auto Arbitrated on the expected times, flagged No actual times recorded |
| Not finished — booked on but not booked off, or still to come | Nothing. It is skipped and picked up on a later run |
A shift that has been cancelled, or marked as a no-show, is not considered at all: those two are filtered out before any of the above is decided, so no pay record is written for them.
Every Manual Advised row is held out of payroll, invoicing and holiday accrual until a manager decides it: approving it, using expected or actual times, or editing it releases it.
Fifteen minutes is the tolerance for the whole shift, applied to the start and the end separately; the larger of the two is what is recorded as the variance.
Hours on a bank holiday are paid at twice the rate, and the record is flagged Includes …h Bank Holiday pay at 2x rate. This applies to employees only. An employee's payroll record can exclude them from bank-holiday pay, but no screen sets that today, so in practice every employee gets it.
How are breaks paid?
The arbitrated hours are the whole span from start to end. A recorded break comes off pay once, and only when the employee's Break Payment Settings have Unpaid Breaks on and Paid Breaks off. With no setting, with neither switch, with Paid Breaks only, or with both on, the break is paid. The client is charged the contracted hours either way. The answer is fixed on the record when it is first written, so changing the setting later does not alter records that already exist.
Running arbitration again does not overwrite a record that already exists. The one exception is a record whose pay rate, total pay or arbitrated hours never computed — that one is recalculated from the current rates.
Does arbitration run by itself?
Only if the organisation switches on Run arbitration automatically every night in Settings → Organisation. Off by default. When on, it runs at midnight over the last 7 days of finished shifts and is stricter than the button: a shift with no book-on, or a book-on with no book-off 12 hours after the end, is never paid at its scheduled times. It is left as Manual Advised for a manager. The Run Arbitration button still pays a shift nobody booked on to at its scheduled times.
What happens when the clocks change?
Hours are real elapsed time. A 22:00–06:00 shift on the night the clocks go back is 9 hours, and on the night they go forward it is 7, on timesheets, schedules and working-time checks, and in pay. Shifts stored before this was fixed keep the hours they were saved with.
What can be changed after the fact?
The edit dialog shows four rows of times: Expected (fixed), Actual, Payroll and Charge. The payroll times are the arbitrated times — the ones that become pay and the ones every other screen then reads. The charge times are held separately, so correcting what someone is paid does not silently move what a client is billed; they follow the payroll row only when Use Payroll Length For Charging is switched on.
The row menu offers Use Expected Times, Use Actual Times, Drop Shift, Confirm Drop, Mark Paid and Mark Invoiced, showing only the ones the record's current status allows, and the tick beside it accepts the record as it stands. Accepting, using expected times and using actual times all leave the record at Manual Complete and clear its flag.
To get to a record from the roster, right-click a completed shift and choose Arbitrate shift. Arbitration opens on the week that shift is in, with its edit dialog already open. If arbitration has not been run for that shift yet there is no record to edit, and the page says so. The action is greyed out for anyone who is not an Admin or Manager, and the right-click menu on a completed shift also has View employee, which opens the employee's profile.
Two people editing the same record cannot both win. Every save carries the version it was read at, and a save against a stale version is refused with Record was modified by another user.
What happens once a record is marked paid or invoiced?
It locks. Paid, Invoiced and Paid & Invoiced all refuse further edits, accepts, time changes and drops with Record is locked. The system can override the lock with a written reason of at least five characters, kept in the audit trail, but no screen offers that today.
Marking a record paid and then invoiced (or the reverse) leaves it at Paid & Invoiced rather than replacing one with the other.
Each of those three events — marked paid, marked invoiced, and any override of a locked record — also writes an immutable snapshot of the whole record: the times, the hours, the rates, the totals, and the employee and site names as they read at that moment. Snapshots are never updated, so a later correction cannot rewrite what a closed pay run said.
What does the employee see?
Their own My Schedule. A shift they booked on to reads Booked on: 07:02 – Off: 19:05. A shift they never booked on to, but which an administrator has since given times, reads Adjusted to instead. Either way, if the times on display came from arbitration rather than from their own book-on, the line ends with · adjusted.
Does any of this cover agency officers?
Only where a deployment has switched it on. Generating pay records for agency officers is behind the ENABLE_OFFICER_ARBITRATION setting and is off by default. With it off, a run reads no agency roster shifts and writes no officer records, so a pay run — and any invoice built from those records — covers employee work only.
Related
Last updated 2026-11-17