SERVER OR FLOOR TEAM · SERVICE START
Server or floor team service start restaurant playbook
Direct answer
Connect table context, guest questions and order handoff without changing protected settings. During service start, move from readiness into controlled live service with one visible owner for each queue.
Example ownership
- Table identity checks
- Guest QR fallback
- Order-context clarification
- Floor exception reporting
Required evidence
- First-live-path check
- Active queue owner
- Access exception
- Corrective note
Shift-moment sequence
- Confirm the first live menu, reservation and order states match the shift plan.
- Verify staff are using individual access appropriate to their duties.
- Check the first real transaction or request through its full handoff.
- Correct ambiguity before volume increases.
Escalation and stop condition
Pause or narrow the affected workflow when the first live path cannot be reconciled.
Role boundary: Floor access should not silently include pricing, payment-gateway, role or site-wide settings.
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.