Shifts
The roster next to what the room actually took.
A weekly square: who works, in which station, at what cost. Set against the revenue of those days. Copy last week. The payroll conversation starts from a picture, not a pile of papers.
Included in · Main & Chef’s Table
On a busy night
How Owner actually uses it.
01
You lay the week
Names, stations, hours. Or you copy last week and fix the exceptions.
02
The take sits beside it
Those days already have a revenue. The cost is no longer a feeling in the office.
03
The door knows who is on
The host is not texting to see if the commis landed. The grid is the answer.
01
A week you can see
Floor, kitchen, bar, office. Names on days, not a group chat that says “who can do Thursday”. Copy the week when the pattern holds.
02
Cost against the take
Hours × rate next to the revenue those shifts produced. You see a heavy Tuesday before you add another closer “just in case”.
03
The same people as the login
The roster is the team, not a parallel list. A kitchen shift is a kitchen shift. The door can see who is on.
What's inside
Everything you get with Shifts.
- Weekly grid by station
- Copy last week in one action
- Staff cost vs revenue of the days
- Roles: floor, kitchen, bar, office
- Visible to the people who run the door
- History you can open after a bad week
“We were overstaffing Thursdays because one Thursday in March was insane. The grid made the habit look expensive.”