Rotas · Leave · Attendance

Rota, leave and attendance for shift-based teams.

RotaTree is where your managers build the rota, your staff see it on their phones, request leave and clock in on site. One workspace, every location.

Get a demo

Web app. Works on phone, tablet and desktop. Nothing to install.

What does it actually do?

Six things. Pick one and see the real screen.

RotaTree weekly rota grid showing published and draft shifts for each employee, with hours and cost per day

Weekly or monthly grid. Drag shifts, publish when ready.See rotas

Get a demo

Inside the workspace

  • 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

Who is it for?

Any employer that runs shifts, at one site or many. Managers plan the week, staff check it on their phones, and everyone clocks in at the workplace.

Rotas

How do shifts get planned?

Managers build the week in a grid and publish it. Staff see published shifts on their phones and can claim the open ones.

Drag and drop on a weekly or monthly grid

Move shifts between people and days. Role stripes show who is doing what. Hours and labour cost update per day, per employee and per week.

Weekly rota grid with open shifts in the first row and a row of shifts per employee

Draft first, then publish

Saving or editing a shift leaves it as a draft. Staff only see it once you publish, and they can acknowledge it.

Draft and published shift counts above a banner reading 22 draft shifts need publishing

Open shifts staff can claim

Leave a shift unassigned and employees can pick it up. Drop and swap requests need a manager’s approval.

Open shifts row showing three unassigned published shifts

Copy last week

Copy a week forward, then change what is different. Export any week to CSV.

Rota toolbar menu with the options Copy current week to next week and Export this rota

Overlaps, leave clashes and long weeks get flagged

A shift that overlaps another or lands on approved leave fails validation. Weekly-hours warnings show who is over their limit.

Team list showing each person's weekly hour limit and hours this week, with two people over their limit in red

See rotasGet a demo

Leave and availability

How does leave work?

Each person has an allowance. They request time off, the manager approves or denies it, and the rota is checked for clashes.

One ledger per person

Holiday, sickness, TOIL and additional leave, with monthly totals and what is left. Export to CSV when payroll asks.

Leave ledger with holiday allowance, used and remaining days per employee and a column per month

Request, approve or deny

Requests reach the manager as a pending notification. One decision, recorded against the ledger.

Add leave form on a phone with employee, dates, leave type and an Add leave request button

Availability, month by month

Employees mark themselves available or unavailable, all day or for set hours, and can repeat a weekday pattern. Managers see it while planning.

Availability calendar columns for Friday to Sunday, with Saturdays and Sundays marked unavailable, all day, repeating

Clashes are caught at approval

Leave cannot be approved over a scheduled shift. Move the shift first.

Conflict with a scheduled shiftFri 18 Sept · 09:00–17:00 · Riverside Café
Illustration

Staff do it from their phone

Employees open RotaTree in their phone’s browser to check shifts and request leave. There is nothing to install.

RotaTree dashboard on a phone with leave and attendance tiles

See leaveGet a demo

Attendance

How does clock-in stop buddy punching?

A tablet at the workplace shows a QR code that changes every 20 seconds. Staff scan it with their own phone, on the workplace Wi-Fi. The server records the time.

A QR code that expires every 20 seconds

The workplace terminal shows a code signed on the server. A photo of it sent to a friend is useless a few seconds later.

QR code inside a countdown ring with the seconds remaining and the note Refreshes automatically every 20 secondsClock-in screen on a phone showing the date, the time 08:56 and a Clock in button

20 s

A new code every 20 seconds, signed server-side.

Only on your workplace Wi-Fi

The phone has to be on your workplace Wi-Fi. A scan from anywhere else is refused.

Terminal instructions: connect to workplace Wi-Fi, scan the live QR, choose and confirm

Server time, not phone time

Timestamps come from the server. Late arrivals and breaks are recorded against the scheduled shift.

Timesheet rows with clock-in, clock-out and break times, the last one marked 4 minutes late

Corrections are marked as corrections

A manager can fix a missed clock-out. The record says it was adjusted by hand.

In 09:00QR verified
Out 17:02Manual adjustment
Illustration

A PIN terminal for sites without the QR check

The older terminal takes a six-digit PIN and locks after five failed attempts. Sites that enforce the Wi-Fi check use the QR code instead.

Once

Each QR code can be used once per person. A reused code is rejected.

A monthly sheet you approve and lock

Scheduled next to recorded, for every person. Approve the records, then lock the payroll period. Manual edits are blocked once the period is locked.

Monthly timesheet for one employee with scheduled and recorded times and an Approve 4 records button

Who is in, right now

The dashboard shows who is late, clocked in, on break and clocked out today.

Dashboard tiles for who is late, clocked in, on break and clocked out today

See attendanceGet a demo

Will it work with what we already use?

Yes. Export anything to CSV, or connect your own systems through the API.

Switching from RotaCloud?

We import your shifts, workers, locations and roles for you, with their IDs preserved. Create a new API key and point your integrations at api.rotatree.com.

How switching works

Get a demo

Is our data safe?

Every row belongs to one company, and the database enforces that, not just the app.

  • Each company’s data is separated in the database itself
  • Employees never see colleagues’ pay
  • Managers only see their own locations
  • Approvals and clock-ins are checked on our servers, not in the browser
  • API keys are stored hashed
  • HTTPS everywhere

Getting started

How fast can we be live?

Three steps. The only hardware is a tablet for the clock-in terminal.

    • Add locations and people, or we import them from RotaCloud for you
    • Set pay rates and weekly hour limits
    • We set up logins for your managers and staff
    • Build the week, copy it forward, publish
    • Staff see their shifts on their phones and claim open ones
    • Leave requests arrive in the app, not by text
    • A tablet on the wall shows the 20-second QR code
    • The first monthly attendance sheet is approved and locked
    • Hours and cost reports by location and role
Day 1: people and locations in.

Get a demo

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