Skip to content

Restaurant role playbooks

  • Home
  • /
  • Role playbooks
7 ROLES · 6 SHIFT MOMENTS · 42 PLAYBOOKS

Make restaurant shift ownership visible

Choose a role and shift moment to define the task, evidence, handoff and escalation. These are responsibility templates; configure Wobistro staff permissions to match your venue rather than treating job titles as universal access rules.

Restaurant role

Owner-operator

Set commercial, access and escalation rules without becoming the silent owner of every shift task.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

General manager

Translate venue policy into assigned workflows, current records and accountable shift leadership.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

Shift lead

Coordinate the live service, assign exceptions and preserve a usable handover for the next accountable lead.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

Host or reservation lead

Keep reservation status, capacity context and guest communication aligned through the shift.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

Server or floor team

Connect table context, guest questions and order handoff without changing protected settings.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

Kitchen lead

Turn accepted orders into an accountable production queue and surface unavailable or unclear items.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Restaurant role

Order expeditor

Reconcile digital order context, kitchen completion and the correct pickup, table or delivery handoff.

Pre-openingProve the assigned channel and station are ready before guests or orders depend on them.Open playbook →
Service startMove from readiness into controlled live service with one visible owner for each queue.Open playbook →
Peak serviceProtect queue ownership and exception visibility when volume makes informal coordination unreliable.Open playbook →
Exception responseContain a failed, conflicting or unsafe workflow without hiding the evidence needed to resolve it.Open playbook →
Shift handoffTransfer open work, exceptions and access responsibility without forcing the next role to reconstruct the shift.Open playbook →
Closing reconciliationClose the role’s queue, preserve variances and leave tomorrow’s setup based on records rather than memory.Open playbook →
Your experience on this site will be improved by allowing cookies.