You could be running the rota with a lot less chasing.
Most shift teams run on a spreadsheet, a group chat and a paper sign-in sheet. Each one does part of the job and none of them agree. RotaTree puts them in one workspace.
How do we get a demo?
Tell us how big the team is. We will show you RotaTree set up for a team like yours.
- Weekly rota
- Monthly rota
- Open shifts
- Copy week
- Draft to publish
- Labour cost per day
- Leave ledger
- Sickness and TOIL
- Availability patterns
- 20-second QR clock-in
- Monthly attendance sheet
- Payroll lock
- Scheduled vs actual
- CSV export
- API
- Signed webhooks
- Multi-location
- Pay rates
- Weekly-hour limits
The real problems you are dealing with
One workspace instead of five tools that do not talk to each other.
Before
The rota lives in a spreadsheet
Someone edits it, exports a picture and posts it. Two versions later nobody knows which one is current.
After
- One rota grid, published to phones
- Drafts stay hidden until you publish
Before
Swaps happen in a group chat
Messages get buried. The manager finds out on the day.
After
- Drop and swap requests that a manager approves
- Open shifts staff can claim
Before
Leave is an email thread
Nobody is sure how many days are left, or whether the rota was checked first.
After
- An allowance ledger per person
- No approval over a scheduled shift
Before
Clock-in is a paper sheet
Times are rounded, written in later, or signed by a friend.
After
- A 20-second QR code on site, server-stamped
- Manual corrections flagged
Before
Payroll is a reconciliation job
Hours are typed from paper into a spreadsheet at the end of every month.
After
- A monthly sheet you approve and lock
- CSV export and an API
Built for the way shift teams work
No add-ons to make it useful.
-
Import, do not re-type
Coming from RotaCloud, we import your shifts, workers, locations and roles for you, with their IDs.
How switching works -
See it with your own set-up
Tell us your team size and sites. We will walk you through RotaTree configured that way.
Get a demo -
Managers see their sites, staff see their shifts
Every row is scoped to your company. Employees never see colleagues’ pay.
Read about security
FAQs
What makes RotaTree different from a spreadsheet rota?
The rota, leave and attendance share the same data. Leave cannot be approved over a scheduled shift, and recorded hours sit next to scheduled hours.
Is switching from RotaCloud difficult?
The RotaTree team imports your shifts, workers, locations and roles with their IDs preserved. API integrations need a new base URL and a new key.
How long does it take to get going?
Day 1 is set-up or import. The first rota can go out in the first week. On-site clock-in needs a tablet for the terminal.
Is there a mobile app?
No native app. RotaTree is a web app that works on phone, tablet and desktop.
Where is our data held?
On Supabase (PostgreSQL) and a VPS. Ask us for the region and we will confirm it in writing.