Build the week's rota, let staff clock in from their phone, and get hours and overtime worked out for you — with holiday counted against the days that person actually works. Built for teams that don't run Monday to Friday.
The demo is a real workspace with sample staff — no sign-up, no card, nothing to install. Or read through every screen first.
Jonah's rota gives him the 24th off anyway — charging him for it is the mistake that starts the argument. Rotasmith knows his pattern, so it charges what he actually works.
Most teams pay for one tool for holiday, another for the rota and a third for clocking in — then reconcile them by hand. These belong together, because each one only makes sense in light of the others.
Generate the week from everyone's usual pattern, then edit it — move a shift to someone else, drop it, change the times. Leave is blocked out so nobody gets rostered on a day they're off, and night shifts are counted properly.
One button, a running timer, no app to install and no terminal to queue at. Clocking in on a day they weren't rostered still works — it just shows as extra hours.
Nobody types an overtime figure. Clock out at 18:30 on a 09:00–17:00 shift and the hours appear on the timesheet by themselves, with grace and rounding rules so three minutes over isn't overtime.
Because we hold the schedule, holiday is charged against the days someone was really down to work. A shift worker booking a week off is charged shifts, not days.
See every screen with real numbers — no sign-up needed.
Built for teams that run on rotas
Invite by email, put them in teams, and set each person's pattern: standard Mon–Fri, part-time days, or a rota cycle with the date it starts.
The calendar shows their own working days. As they pick dates they see exactly what it costs, their balance after, and warnings if the team would be short.
Approvers get an email with the full context and can approve or decline straight from it — no login. Every decision is logged, with a 10-second undo.
Set a minimum staffing level per team. Rotasmith counts who is actually scheduled that day — not headcount — and warns you before the rota breaks.
Nothing is hand-typed. Every balance is derived from entitlement and real requests, and any employee can open the full sum. Fewer disputes, cleaner audits.
Rotasmith finds the dates where someone's remaining days stretch furthest — "book 4, be away 9" — so people take proper breaks without denting cover.
Sick leave is special-category data under UK GDPR. It routes to HR only — line managers never see the nature of it. That's enforced in the code, not a policy note.
Managers who never log into HR systems still approve in two seconds, from the email, on their phone.
One click exports everything your organisation holds as a file you own. Erase an individual's personal data when they ask.
Everything included. No setup fee, no per-feature upsell, and half what the leave-only tools charge for a fraction of this.
Free while we're in private beta. We'll always ask before charging you.
Yes — that's the reason Rotasmith exists. You set the cycle (days on, days off, and the date it starts) and leave is charged in shifts against that pattern. Shift workers keep working through bank holidays; fixed-pattern staff get them off. Both are handled without anyone doing mental arithmetic.
Tick the days they work. A Mon–Thu employee is never charged for a Friday, and their entitlement is theirs to set — no pro-rata spreadsheet needed.
Not really. They get an email with the request and its context, and can approve or decline from it without logging in. The full inbox is there when they want it.
Any time, in one click, as a complete JSON export. You can also erase an individual's personal data on request. It's your data.
Each organisation's data is isolated at the database layer and that isolation is covered by automated tests. Sickness data is restricted to HR. Everything runs over HTTPS on UK/EU infrastructure.
Open the demo and book a shift worker's week off — you'll see the difference on the first request.