Host or reservation lead peak service restaurant playbook
Direct answer
Keep reservation status, capacity context and guest communication aligned through the shift. During peak service, protect queue ownership and exception visibility when volume makes informal coordination unreliable.
Example ownership
- Pending reservation review
- Accepted and rejected status
- Arrival and seating notes
- Guest-facing reservation updates
Required evidence
- Queue status
- Aged exception list
- Handoff confirmation
- Capacity escalation
Shift-moment sequence
- Watch the role’s assigned queue and aging exceptions.
- Keep status changes tied to observable handoffs.
- Separate urgent blockers from work that can wait.
- Notify the shift lead before capacity or failure creates unsupported promises.
Escalation and stop condition
Escalate when demand exceeds the tested workflow, staff capacity or safe operating limit.
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.