Host or reservation lead shift handoff restaurant playbook
Direct answer
Keep reservation status, capacity context and guest communication aligned through the shift. During shift handoff, transfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.
Example ownership
- Pending reservation review
- Accepted and rejected status
- Arrival and seating notes
- Guest-facing reservation updates
Required evidence
- Open-item list
- Status snapshot
- Next owner
- Receiver confirmation
Shift-moment sequence
- List open orders, reservations, unavailable items and unresolved incidents.
- Match each item to a current status and next owner.
- Transfer only the access, device or physical material the procedure requires.
- Have the receiving role confirm the handoff and its priorities.
Escalation and stop condition
A shift is not handed over when a material exception has no accepting owner.
Role boundary: A request or special note is not a confirmed promise until an authorized restaurant workflow accepts it.
Wobistro access boundary
Use individual staff accounts and grant the smallest useful module set. Wobistro permissions support the workflow when enabled; they do not define training, legal authority, food-safety responsibility or emergency command.
Verify allowed and restricted paths with a non-owner test account after changing the active plan, modules or role.