Rosters that match the rush, not the register
Build weekly rosters per outlet, let staff request leave and swaps on their phone, and see who actually turned up for each shift.
What it replaces
The paper, calls and spreadsheets this takes off your team's plate.
How it works
Rosters shaped by sales
See expected covers by hour next to the roster, so you add staff for the dinner rush and don't overstaff a quiet afternoon.
- Templates per outlet
- Split shifts
- Labour cost of the roster before publishing
Leave and swaps without the chase
Staff request leave or swap shifts with a colleague on the app. Managers approve with one tap and the roster updates.
- Leave balances visible to staff
- Swap approval rules
- Holiday calendars per state
Attendance that proves itself
Check-ins come from face recognition on outlet cameras or a shared device. Late arrivals and missed shifts show against the roster.
- Late and early-exit marks
- Missed check-out handling
- Attendance regularisation with approval
Getting started
The order we set it up in.
Template
Set shifts per outlet.
Publish
Staff see the week on the app.
Check in
Face check-in at the outlet.
Close
Attendance feeds payroll.
What changes
What teams using Shifts and Attendance should expect to see.
- Labour matched to expected covers
- Fewer no-shows discovered at service time
- Attendance data payroll can rely on
Questions
Can staff check in from their own phone?
You can allow it with location limits, but most restaurants prefer face check-in at the outlet.
Does it handle staff shared between outlets?
Yes. A person can be rostered at different outlets on different days.
Can we see labour cost per shift?
Yes. The roster shows planned labour cost, and actual cost follows from attendance.
See DeepRestaurantAI with your own outlets
We'll connect a sample of your POS data and walk you through sales, purchasing, food cost and DeepObserve.ai camera AI for your format.