How to Serve Guests Arriving in Groups: Track Each New Round and Undelivered Items in Order

Whenever another group of guests arrives, staff should first check what has already been ordered and which items have not yet been served. Then confirm what is genuinely being added now and where it should be recorded. Don’t re-enter the whole table’s order based on the current number of guests, or combine bills just because the guests are together. Record arrivals and additions for this round in one place so the next staff member can continue serving the same table.

Update the record as guests arrive; don’t recreate the whole table’s order

• First guests are seated: Record the current table, original order, and items ordered and not yet served. First clarify how they intend to pay for what they have already ordered.
• Companions arrive later: First ask whether anyone in their party is already seated and where they would like to sit. Then ask what they want for themselves and to share this time, and clarify where it will be recorded. If the billing arrangement has not been agreed, keep the original record as it is for now.
• Clearly specified additions for this round: Repeat the options and quantities, check them against the earlier order, and confirm whether these are additions or a query about the previous round.
• Guests move to another spot: Check the original order and the new location, and notify the staff still preparing and delivering the items. Verify which actions are available in the system based on permissions and the current status.
• Someone leaves early: Check what they are responsible for, the payment actually received, and what remains owed. Don’t allocate future spending that hasn’t happened yet.

One record for each round, with six details staff can refer back to

• Current location and original order: Use an identifier staff can look up. Don’t identify a bill by someone’s appearance, clothing, or a complete list of their companions.
• Requests made this round: Record only the items, options, and quantities confirmed this time. Tell the kitchen which items are new this round and provide the order identifier. Use earlier items for reference; don’t resend the entire order.
• Already served and still outstanding: Distinguish items already delivered, still being prepared, ready but awaiting delivery, and still awaiting clarification.
• Payment arrangements: Record who is covering the additions and whether this is still to be discussed. Don’t infer the arrangement from the order in which people arrived.
• Staff member handling this round: Take responsibility for gathering new requests received by other colleagues, and name a replacement when handing over.
• Next step: Note whether to check the earlier order, submit this round’s additions, or wait for a response, specifying which staff role is expected to reply. The person taking over should confirm receipt of the handover.

If someone who arrived later wants to order another shared dish, staff should first check the preparation and delivery records from the previous round and explain what has already been ordered. Then ask whether they want to add another dish or are checking on the original one. Don’t cancel an item just because someone at the table says they think it was already ordered, and don’t interpret “another one” as an instruction to remake everything for the table. The person making the request should confirm the key options and quantities in person.

Guests at the same table may ask different staff members about the menu, request water, or order more food. You can designate one staff member to gather confirmed requests for that round while colleagues continue to respond as usual and pass new information back to the same place for checking. When that staff member leaves, name the person taking over and hand over any outstanding tasks. Guests can get help from any colleague, while the front-of-house team maintains one clear, up-to-date record of the current arrangements.

When guests move tables, update the table association; don’t place their order again

• Confirm what was entered for the original table, what has been served, and what is still waiting to be delivered, so the same items aren’t ordered again at the new table.
• Check the new location and its relationship to the current bill. A staff member with the appropriate permissions should handle any available action based on the current status. Don’t assume the move is complete just because the cups have been carried over.
• Clearly tell the host, preparation, and delivery staff where items should now go. Make sure someone follows up on drinks that have not yet been served; telling only the front-of-house team that the guests have moved is not enough.
• Have one staff member repeat the handover details. The person taking over should be able to find the record using its order identifier, rather than having to piece together what happened from memory.

If someone leaves early, settle only the spending that has been confirmed

A guest who leaves early may want to pay only for their own drinks, or may be willing to cover part of a shared dish. The cashier should first check the latest items, payments received, and outstanding amount, then confirm the payment arrangement with the guest. Guests who arrive later may still order more, so don’t divide spending that the table hasn’t incurred yet.

MenuSnap’s bill-splitting guide covers equal splits, splitting by item, and splitting by amount. Staff should check which options the current bill supports based on the agreed arrangement, then process and verify each payment separately.

• For each portion, verify the payment actually received and the amount still owed. A printed split bill or one person’s proof of payment does not mean the whole table is settled.
• For a standalone card terminal, first verify the transaction through the terminal or with the payment provider, then record it against the correct portion. MenuSnap does not automatically verify transactions made on a standalone terminal.
• If the result is unclear, check the original transaction first and don’t charge again until it has been resolved. If more items are ordered during payment, check the latest bill before continuing.

Online payments and cloud syncing depend on network connectivity. The offline availability of the native client depends on the official version and configuration; after connectivity is restored, check the order and payment. Arrival updates and round-by-round notes are staff aids, not substitutes for formal orders or proof that the system has automatic grouping or bill-combining capabilities.