Move the service context, not just the table number
When a party moves, confirm the destination, open check, server ownership, and kitchen status before treating the transfer as complete. Changing a table label does not necessarily update every ticket already printed or every person involved. One employee should own the move and tell the host, server, and relevant production team what changed. Keep the original check traceable rather than closing it and rebuilding the meal as a new sale.
First establish who is moving. A whole party changing tables is different from one guest joining another party or two checks merging. Ask whether any items are already being prepared, whether seats have been assigned, and whether a payment step has started. Use the approved transfer function and manager authority where required. If the system cannot represent the intended change safely, pause and ask the responsible manager before improvising.
Check seats and pending food
For an illustrative example, four guests move from table 8 to table 14 after ordering appetizers. The server confirms the new location with the host and checks the open items. The kitchen still has the original table reference on an earlier ticket. A direct acknowledgment prevents a runner from searching table 8 with finished food. This is a service coordination problem even if the register successfully shows table 14.
Reconfirm seat assignments at the destination. Guests may change relative positions around a differently shaped table. Any preparation request associated with a diner needs to remain correctly assigned under your approved process. The course-firing guide covers timing between courses; a table move needs the additional check that production and delivery teams still agree where each course belongs. Never infer that an earlier printed ticket rewrites itself.
Use a five-point transfer check
Confirm destination availability; verify the correct open check; review guest and seat references; acknowledge the change with the relevant kitchen or runner; confirm who owns checkout. Record an exception if the move affects an existing payment or a separate guest check. Keep the procedure short enough for staff to use while maintaining the guest experience. It should guide attention to likely gaps rather than create a second unofficial transaction record.
Before payment, review the displayed items with the server responsible for the new location. Check that nothing was duplicated, accidentally closed, or left on the previous table. If guests request separate bills after moving, follow the split-check sequence instead of creating another ad hoc transfer. Where a gratuity, deposit, or authorization is involved, use your provider’s approved instructions and the manager’s policy rather than assuming it moves automatically.
Rehearse the difficult move
During a quiet training session, try a move before food is sent, after one course is sent, and after a guest separates from the party. Use demonstration data and confirm which roles can perform each action. Ask a runner to identify the destination using only the information they normally receive. If the correct table requires someone to remember a verbal conversation from earlier, document and improve that gap.
This article focuses on a party’s physical location, not the shift-change ownership addressed in the existing open-check guide. Keep both processes connected without treating them as identical. Use the Table Service solution page to discuss table transfers, seat mapping, and already-sent tickets in a walkthrough. Confirm current behavior and manual handoffs before deciding that a generic move button covers your dining room’s complete service routine.

