You build the rota in a spreadsheet, the staff work something slightly different, and on Sunday night you reconcile the two from memory and a WhatsApp group.
Then somebody queries their hours and you have no way to prove anything.
What it does
- Build it once, copy it forwardMost venues run a shape, not a fresh puzzle every week. Get one week right and roll it.
- Clock in with a PIN, offline-proofStaff clock in with a PIN the system issued, not one they chose. The time is stamped at the tap, so an outage never moves anyone's start.
- The wage bill, live as you buildDaily and weekly totals update as you drag a shift. Cut an hour and see the saving before the week is booked.
- Timesheets that show the differenceClocked against rostered, with your break rules applied. Someone who clocked in 40 minutes early is a question, not paid as a fact.
- Break rules, SSP and entitlements, worked outYour break rules, statutory sick pay, holiday pay and bank-holiday entitlements calculated automatically, built to what a WRC inspection asks for.
- Exports straight into BrightPayHand it to whoever runs your payroll. BrightPay is built in; send a sample of whatever else you run and we match it.
Better with the rest
Everything shares one staff list. Add a module and it already knows your people — there is no second setup.
- With Holidays — approved leave is already blocked out, so you can't roster someone who's in Spain.
- With HR — the pay rate and start date you typed once drive the timesheet and the entitlement.
Running the daily rota, clock-in and timesheet across a working multi-venue group — in service, not in a demo.
What it costs
Free for small venues. Paid per venue above that — never per head, because charging per person is a fine for hiring.
Figures go on the pricing page before anyone is asked to pay one. Export is free on every plan, always — including on the way out.
Want to see how it actually works before you sign up? Read the guide — it's public, no login.