A photo in a group chat
- Write the rota
- Photograph it
- Argue about it
Two versions circulate. A double-booked server is found on the night. Hours are reconstructed from memory at month end, and nobody can say what labour actually cost last week.
Build next week on a 7-day grid, publish it so the team can see it, and watch who actually turns up. Clock-ins happen at a kiosk by PIN or face, and the hours become cost per person without anyone adding up a timesheet.
The week schedule, as it ships.
Most restaurants here plan the week in a notebook and send a photo to a group chat. It works until someone swaps a shift, and then nobody knows which photo is current.
Two versions circulate. A double-booked server is found on the night. Hours are reconstructed from memory at month end, and nobody can say what labour actually cost last week.
One rota everyone reads from the moment you publish it. The system warns you before you double-book someone, and the hours people actually worked come from the clock rather than from recollection.
You still decide who works when. You stop being the only person who knows what was decided.
Set-up is entering your team once. After that it is a few minutes a week.
Click a cell to add a shift: who, start, end, and the role they are working that day. The grid totals hours as you go.
Assigning someone who is already on shift at that time flags an overlap before you save it, not on the night.
Shifts start as drafts only you can see. Publishing the week shares it with the team, so there is one current version.
A spare tablet paired to your restaurant. They tap their name and enter a PIN, or look at the camera if you have enrolled faces.
A live list of everyone currently clocked in and how long they have been on, plus the recent clock-outs.
Someone forgets to clock out. Correct the entry from the dashboard — a reason is required, and the edit is recorded.
Hours per person for any date range, with the roles they worked and the number of shifts closed.
Give a staff member an hourly rate and the report estimates their cost for the period, and the total for the team.
Manual time-entry edits always carry a reason and land in the audit log with the name of whoever made them.
Two screens do most of the work: the labour report at the end of the week, and the clock-in check that decides whether an entry can be trusted.
Grouped by the job, not by which screen they live on.
The rota, in one place, with one current version.
What actually happened, rather than what was scheduled.
A spare tablet by the staff door, paired to your restaurant.
Optional, consented, and honest about how sure it is.
The number you need before payroll, not after it.
The point of a time clock is not that it records a time. It is that you can say how that time was recorded when someone disputes it.
A capture that is too far away, too dark or partly out of frame is rejected at the device. Nothing blurry ever reaches the matcher, so a bad photo cannot become a bad match.
The kiosk issues a challenge and requires evidence that the action actually happened. Holding up a picture of a colleague fails it.
Face, PIN, manager or code — recorded on the entry along with an assurance level. A medium-assurance clock-in is visible as such rather than looking identical to a strong one.
Editing a time entry needs a reason and is written to the audit log with the manager’s name. The record shows it was edited rather than quietly replacing the original.
Workforce is useful alone. It gets sharper when the rest of the restaurant is on the same system.
The same team records the rest of Tahlib uses, with the role-based access that decides who can edit a rota or correct a clock-out.
Estimated labour cost sits next to your other costs in a monthly P&L with a labour percentage.
Opening and closing checklists for the shift you just rostered, with acknowledgement per person.
Order volume by hour tells you when the floor is actually busy — the input you want before writing next week.
Who was on the till, and when, from the same staff records the clock uses.
Each branch keeps its own rota and its own kiosks, while the group compares hours and cost across locations.
Products are switched on individually — see the full catalogue and prices on the products page.
The rota is the same shape everywhere. The problem it solves is not.
Written around how restaurant teams here are actually staffed.
The dashboard runs in English and Arabic with proper right-to-left layout, so whoever writes the rota does it in the language they think in.
An hourly rate per staff member turns hours into an estimated cost for the period — the figure you want before payroll, in the currency you pay in.
Shifts carry their own start and end rather than fitting a fixed pattern, so a lunch-and-dinner double is one rota entry and one set of hours.
Face clock-in is optional. Consent is recorded before a template is stored, and a staff member’s face data can be permanently removed at any time.
Two ways to get it, and you are not forced into either. Add it to the paid plan you already have, or move to the plan that bundles it.
Start with a Tahlib plan, then add the products you need — or move to a plan that already includes them.
You build the week as drafts that only you can see, then publish it. Publishing shares those shifts with the team, so there is one current version rather than several photos of a whiteboard.
It warns you. Assigning a person to a shift that overlaps one they already have flags it while you are still editing, so the clash is caught before the rota goes out rather than on the night.
A kiosk — any spare tablet, paired to your restaurant from the dashboard with a one-time token. Staff tap their name and enter a 4–8 digit PIN, or look at the camera if you have enrolled their face.
No. PIN clock-in works on its own and needs no enrolment, which is usually the right choice for a new starter. Face is optional, per staff member, and consent is recorded before anything is stored.
The kiosk issues a liveness challenge and requires evidence the action actually happened, so a held-up photo fails. There is also a quality gate before that which rejects a capture that is too far, too dark or partly out of frame.
Correct the entry from the dashboard. A reason is required, the record shows it was edited, and the change is written to the audit log with the name of whoever made it.
Yes, permanently, at any time — per staff member from the attendance screen. The template is stored for attendance only.
It estimates it. Give a staff member an hourly rate and the labour report multiplies it by the hours from their closed time entries, per person and as a team total for any date range.
Not today. The report gives you hours and estimated cost; putting that against revenue is something the Expenses & P&L product does at a monthly level. If a live labour-to-revenue ratio matters to you, say so before you commit.
No. Tip pooling is not part of Workforce today — it schedules, tracks time and reports hours and cost. Worth knowing now rather than discovering it on payday.
You can read the report on screen for any date range, broken down per person. There is no CSV export yet, so today it is a screen you work from rather than a file you hand over.
Yes. The schedule, time clock, labour report and attendance screens all run in English and Arabic with proper right-to-left layout.
Two ways, and you choose. Add it to the paid plan you are already on at its own monthly price per branch, with a 14-day free trial — no upgrade required. Or move to the plan that bundles it with several other products. The pricing section above shows both with current figures.
Build next week on a grid, publish it once, and let the clock tell you what actually happened.
No card to start · nothing to install · cancel whenever