The shift schedule your team actually sees

Open shifts

Somebody’s ill? Send the shift to everyone who’s free and holds the position. First to tap gets it. Double-booking can’t happen — the database guarantees it.

• —Until it’s taken, the shift sits on the schedule as its own row
• —It can be claimed from a phone, without opening a computer

Nothing to install

An employee opens a link from their email — or Telegram, if they have it — and is in the system seconds later. It installs to the home screen like an app; there is no app store and no password.

• —Shifts, open shifts, swaps, clock-in and profile — in one window
• —Works on any phone, in the language the person chose

Swaps and time off

A request instead of a thread. Each one has a status, a history and a trail in the activity log: who asked, who agreed, who approved.

• —A swap doesn’t happen without the other side’s consent
• —An undecided request expires after 48 hours

Hours and labour cost

Hours per person and the cost of the week are right there on the schedule — while you’re building it, not after.

• —Overtime and too-short rest are visible before you publish
• —Export to Excel — for the accountant and payroll

English, Russian and Uzbek

The manager reads in one language, the employee in another. One schedule, and every notification arrives in the reader’s own language.

• —Dates, money and the clock follow the business’s country — “5 PM” in Ohio, “17:00” in Leeds
• —Everyone picks their own language in their profile

Your country’s calendar

Public holidays for twenty countries, the week starting on Sunday where it does, overtime flagged after your working week, and pay counted in your currency.

• —Holiday and night premiums where the law sets them, and off where it doesn’t
• —A paid-leave balance per person, counted the way your country counts it

The time clock

Staff clock in from their phone, or on a tablet by the door with a PIN. The timesheet shows where they were, how long they took for lunch, and — if you switch it on — a picture at each punch.

• —Clock in on site only, per venue, when you want it enforced
• —Breaks punched, not assumed; a long lunch costs what it took
• —A nudge to whoever forgot to clock in, and to whoever forgot to clock out

Reports, and the Monday email

Hours, overtime, labour cost against budget, who was late, who left early, who didn’t show — by person, position and day. And every Monday morning, last week in one message.

• —Any date range; export for the accountant
• —Absences on a month grid, with the leave balance beside each name

Chat and announcements

One message to everyone that you want read, held until morning unless it’s urgent. And a chat next to the rota — a room per venue — so “who can cover Saturday?” gets an answer, not forty messages.

• —Read counts on announcements
• —Quiet hours: nothing buzzes between 23:00 and 8:00 unless you say so

01

Two-step verification

An authenticator code after the password, for every manager. A stolen password alone opens nothing.

02

Your data in the EU

Stored in a data centre in the European Union, encrypted in transit and at rest with AES-256.

03

Every business sealed off

Access rules live in the database itself and are checked on every request — not in the app, where a bug could forget. One customer’s data is never in another’s query.

04

As little as possible

A clock-in keeps the distance to the venue, never the coordinates. Terminal photos live 30 days in private storage. Any person’s data can be exported in one press.

05

Nobody marks their own homework

No one approves their own request or confirms their own hours. Every change — who published, who approved, who corrected which hours — is in the activity log for two years.

06

GDPR, UK GDPR, and a DPA

A Data Processing Agreement with the EU Standard Contractual Clauses is part of the terms; the sub-processors are listed. Nothing to sign, nothing to chase.