The roster is a bet on how busy you will be. Stop placing it blind.
Rosters live in a group chat because that is the fastest thing available. The cost of that is invisible: an extra hand on a dead Tuesday, one short on a festival weekend, and no record of either when you look back.
Build a week by station, not just by headcount. Tandoor at lunch is a different requirement from tandoor at dinner, and the roster reflects that rather than averaging it.
Attendance on the terminal already there
Staff mark in and out on the counter or a station device with a personal code. No extra hardware to buy, break or forget to sync.
Swaps and leave with a trail
A swap request goes to the manager, gets approved or refused, and the roster updates for everyone. Nobody has to scroll a chat thread to find out who is actually coming in.
Labour cost against sales
Cost of hands on the floor beside revenue for the same hours, per outlet and per daypart. The hour where the two diverge is usually the one worth changing.
Overtime before it becomes a surprise
Hours accumulating past a threshold are flagged during the week rather than discovered at payroll, along with who approved the extra shift.
Suggested cover from the forecast
The demand forecast proposes how many hands each station needs, by hour. It is a suggestion on a draft roster. You approve every shift that gets published.
On the suggestion engine
We will not pretend a model knows your team.
A forecast can tell you that next Saturday between eight and ten will run roughly thirty percent heavier than an average Saturday. It cannot tell you that one of your cooks is faster than two of the others, or that a particular server handles a difficult table better than anyone else.
So the module proposes cover and explains the volume it is reacting to. The judgement stays where it belongs.
It suggests, on a draft. Nothing is published to staff until a manager approves it.
It shows its reason. Every suggestion states the forecast covers and the station load it came from.
It learns from your edits. If you consistently add a hand where it proposed none, that pattern is taken seriously.
It stays out of discipline. Dearrasa does not score, rank or rate your staff. Speed data belongs to the station, not to a performance file.
Practical questions
Payroll, part timers and privacy.
Does this run payroll?
No. It produces the attendance, hours, overtime and shift record that payroll needs, exportable in a form your accountant can work with. We would rather do the roster properly than do payroll badly.
We use a lot of part time and casual staff.
That is normal in this trade. Staff can be marked as regular or casual, with different rate structures, and casual shifts can be offered to a pool rather than assigned to one person.
Can staff see each other's hours or pay?
No. A staff member sees their own shifts, their own hours and the published roster for their station. Rates and cost figures are visible to managers and owners only.
Does it work across outlets?
Yes, including staff who cover more than one location. Hours are attributed to the outlet where they were actually worked, which matters when you are comparing outlet performance.
Next service
Bring last month's roster and last month's sales.
We will lay them against each other and show you the hours where your labour and your revenue were not in the same room.
