Server or floor team closing reconciliation restaurant playbook
Direct answer
Connect table context, guest questions and order handoff without changing protected settings. During closing reconciliation, close the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.
Example ownership
- Table identity checks
- Guest QR fallback
- Order-context clarification
- Floor exception reporting
Required evidence
- Closed queue
- Variance record
- Carry-forward owner
- Access or device confirmation
Shift-moment sequence
- Resolve or explicitly carry forward every assigned open item.
- Compare expected status with observable orders, reservations or handoffs.
- Record variances, unavailable items and corrective follow-up.
- Secure role access and submit the closing evidence to the shift lead.
Escalation and stop condition
Do not silently clear a status, payment or operational variance merely to close the shift.
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.