Time tracking
Shift rota and scheduling software, with the clocked hours under the plan
One row per person, one column per day, and both things in every cell: what was owed on top and what was clocked underneath. Because the question anyone asks of a rota is never one of the two on its own — it is whether they match.
The pattern and the exception are different things
A schedule is a named weekly pattern: "Split-shift office", "Afternoon shift", "Summer hours". You write it once, with two slots per day, and put fifteen people on it in one go. It is the stable part: touched twice a year.
A shift is what happens on one particular day when it is not the usual: the Saturday you open, the day someone starts at eleven, the cover for someone off sick. Touched every Friday.
Mixing the two is what turns a rota into a mess: you end up with half the staff on a personal schedule called "Ana". Here the shift beats the pattern on that day and only that day, and removing it hands the cell back to the schedule — so if the pattern changes tomorrow, that day changes with it.
Next week, in one click
Next week is almost always this week with two changes. Filling in seven days by twelve people by hand is eighty-four cells every Friday, and that is exactly why rotas end up in a spreadsheet only the person who built it understands.
The copy button sets next week up as it stands, and you change whatever changed on top of that.
And the rota checks itself against reality
Under each shift sits what that person actually clocked that day, and the cell is marked when it falls short. Nothing to export and no two systems to reconcile: the rota and the clock are the same database. How clocking works.
Anyone who forgot to clock shows up as "not clocked" under their shift the same day, not at the month-end close.
With a work centre, when the shift has one
A shift can carry its own centre: the person covering the town-centre shop today and the retail-park one tomorrow. That is what gets checked when they clock, and what shows on their entry afterwards. Clocking by location.
Frequently asked questions
Does it handle rotating morning, afternoon and night shifts?
Yes. You write three schedules — one per shift — and rotate on the grid, changing each person's shift on the week it falls to them, or reassigning the schedule if the rotation is a long one. Night shifts that cross midnight are counted whole: the day is booked against the date it started.
Can the team see their own rota?
Each person sees their week on the Clock screen, with scheduled and clocked side by side, day by day. The whole-team grid is seen by whoever holds the schedules permission, which is handed out role by role like everything else.
Can a day be marked off even though the schedule says otherwise?
Yes, and that is how you plan a bank holiday without touching anyone's schedule. The day is marked as off, counts as nothing scheduled and therefore raises no "not clocked".
What about approved leave?
Anyone on approved leave does not get the "you did not clock yesterday" email, because they were not supposed to clock. Leave and time tracking are the same database, so there is nothing to remember to cross-check.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.