Shift lead exception response restaurant playbook
Direct answer
Coordinate the live service, assign exceptions and preserve a usable handover for the next accountable lead. During exception response, contain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.
Example ownership
- Shift readiness
- Live order and reservation exceptions
- Fallback activation
- Handover completeness
Required evidence
- Incident time
- Affected records
- Fallback action
- Named follow-up owner
Shift-moment sequence
- Identify the exact affected channel, record and first known time.
- Stop duplicate actions or new promises where evidence is unreliable.
- Activate the approved fallback within the role’s authority.
- Record facts, notify the accountable lead and assign reconciliation.
Escalation and stop condition
Emergency, safety, security, suspected data exposure and unresolved payment events override routine software steps.
Role boundary: A shift lead must escalate safety, payment, security and policy decisions outside assigned authority.
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.