Carry unfinished guest requests across a shift change

The decision this workflow supports

A request received near the end of a shift can become everybody’s responsibility and nobody’s task. The handoff should describe what has already happened and the next action, rather than forwarding an entire conversation without context.

Put the review process in place

Before leaving, the outgoing reviewer identifies open requests and records their status. The incoming reviewer acknowledges ownership through the restaurant’s chosen process. Keep any guest-facing response commitment visible, and do not reset the clock simply because a new shift has taken over.

Worked example for your team

A fictional catering inquiry arrives near the end of lunch service. The outgoing reviewer has checked the basic details but has not reached the catering manager. The handoff should state that completed check, the outstanding decision and who is taking responsibility next. Ask the incoming reviewer to acknowledge the task and identify any guest-requested deadline. A forwarded transcript alone is insufficient if nobody knows whether someone already replied. The shift change should preserve the request’s history and expectations rather than restarting the inquiry as though it had just arrived.

Sample wording to approve

“Staff handoff example: this catering inquiry is awaiting a feasibility check. The organizer asked to hear back tomorrow morning. Please acknowledge ownership and confirm the response plan before closing the handoff.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need request reference, completed actions, outstanding decision, guest expectation, and incoming owner. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The incoming reviewer acknowledges the task. The guest’s original timing request remains visible. Completed actions are not repeated unnecessarily. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides