Rotas, clock-in and the hours that come out of them

Most platforms list staffing as one line

Here it is the rota, the clock-in, the hours into payroll, the tronc split, the leave request and the labour cost against the sales that paid for it. The depth is the product.

What it actually does

instead of Planday

Build the week against a budget

Set what the labour should cost and watch the number move as you drag shifts. You find out you have over-rostered Saturday on Wednesday, not on the payroll run.

Clock in on the phone they already carry

No terminal on the wall and nothing to buy. The clock-in is tied to the site, and the difference between the shift and the actual is there to be approved.

Hours become gross pay and tronc

The hours worked carry straight through to pay and to the tronc split, per person, per site. Nothing is re-typed into a second system, which is where the errors live.

Labour against sales, per day

The percentage, on the day it happened, per site. Not a month later in a spreadsheet somebody built once and nobody maintains.

Leave and availability in the same place

Someone asks for the Saturday off in the app they clock in with, and it is on the rota you are building rather than in a message you have scrolled past.

What it doesn’t do

—It does not calculate PAYE or National Insurance, and it does not file RTI with HMRC. That needs HMRC-recognised software, and this is not it.

—It does not pay anybody. It produces the numbers your payroll runs on.

The rest of it

This one is worth having on its own. It is worth more beside these.

See this part on your own setup

Pick two times and say what you run. We build the demo around that rather than showing you a restaurant that is not yours.

Request a demo