Make the handoff clear

A working agreement for kitchen, expediting, and service teams

Fictional example: Cedar Table is a sample restaurant used to illustrate the handoff. During service, the kitchen or expediter communicates an order’s ready status or an exception; the receiving service role acknowledges it and checks the shared order record when details are unclear.

This page is about communication at the food-service interface, not end-of-shift handover. Follow your property’s approved procedures for safety-critical, regulated, or guest-sensitive decisions.

Make the handoff two-way

A handoff is complete when the sender states the relevant status and the receiving role acknowledges it. If either side is unsure, clarify rather than infer.

Kitchen or expediter

Identify the order, state its current status, and direct the message to the agreed receiving role.

  • Use the property’s agreed handoff signal.
  • Name an exception and the affected order.
  • Wait for acknowledgment when the message affects the next service action.

Service role

Acknowledge the message, check the order record if needed, and clarify any mismatch before acting on assumptions.

  • Repeat back a detail when it is unclear.
  • Confirm who owns the next communication.
  • Use the locally approved process for guest-facing decisions.

Use one shared order record

The property’s approved order system is the shared record for order details and changes. Use that approved source when checking the order before a handoff.

If a spoken handoff and the order record do not match, pause the coordination conversation: check the record, identify the responsible kitchen or expediting role, and confirm the current detail through the locally agreed channel. Do not treat an assumption or an unrecorded message as a confirmed change.

Useful handoff cues

A static communication aid for a clear exchange. These cues are not interactive checkboxes, certification, attestation, or a safety procedure.

  • Order identified: both roles know which order the message concerns.
  • Status stated: the sender gives the current status or names the exception.
  • Receiving role acknowledged: the intended recipient confirms they heard the handoff.
  • Next owner clear: the roles know who will take the next communication step.

Routine handoff or exception?

Use the same shared-record discipline in both situations. The example shows communication and ownership, not a decision about food safety or what may be offered to a guest.

Routine: ready for pickup

At Cedar Table, the expediter says, “Order 42 is ready at the pass.” The service role replies, “Acknowledged—order 42.” Both roles have identified the order and confirmed the handoff.

  • The sender names the order and status.
  • The recipient acknowledges the same order.
  • The approved order system remains the shared record.

Exception: requested item unavailable

The kitchen or expediter flags the affected order in the approved system and tells the service role which order needs attention. The service role confirms the next guest-facing step through the property’s locally approved process.

  • Identify the affected order without guessing at a replacement.
  • Keep the record and verbal message aligned.
  • Refer decisions outside the handoff agreement to the designated local role.

Close the feedback loop

When a handoff is repeatedly unclear, raise it with the shift lead or designated local operational owner. Describe the handoff point, what information was unclear, and how it affected coordination; use the organization’s approved channel and avoid including unnecessary guest details.

Review this working agreement when roles, the approved order system, or the service flow changes. Hospitality Operations owns the agreement in the Cedar Table example. The shift lead passes recurring handoff problems to that team and communicates an approved correction to kitchen, expediting, and service colleagues.