Order expeditor pre-opening restaurant playbook
Direct answer
Reconcile digital order context, kitchen completion and the correct pickup, table or delivery handoff. During pre-opening, prove the assigned channel and station are ready before guests or orders depend on them.
Example ownership
- New-order receipt
- Ticket-to-handoff matching
- Duplicate or missing-order checks
- Ready and handed-off status
Required evidence
- Readiness check
- Test-path result
- Exception owner
- Fallback confirmation
Shift-moment sequence
- Review the current shift assignment and enabled Wobistro modules.
- Test the role’s critical menu, order, reservation, table or ticket path.
- Record unavailable items, access gaps and unresolved exceptions.
- Confirm the fallback and named escalation contact before opening.
Escalation and stop condition
Do not open an affected channel when its accountable owner, required control or tested fallback is missing.
Role boundary: The expeditor must not guess when payment, identity, allergen, delivery or duplicate-order evidence conflicts.
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.