When one restaurant server takes over from another, the open check and the guest's unfinished service need attention together. A check can move to the correct operator while a request is still forgotten. Practise a handover that verifies both. Follow your restaurant's authorized process and permissions; this exercise is not a sequence of universal point-of-sale buttons.
Identify each open check separately
Use the check reference, table or service location, current operator and receiving operator. Confirm that the check is still open and that you have selected the intended record. Two parties at the same table, a split check or a recently closed bill can make a table number insufficient. Do not reopen or merge a check merely to make a handover list look tidy.
Record the service position beside the check: items already served, items accepted but not yet served, and requests still needing confirmation. Keep these categories separate. An item visible on a check is not by itself proof that the guest received it. Equally, a guest asking about dessert is not an accepted dessert order. Use the kitchen and service records available under your procedure.
A fictional two-check handover
At 18:00, Sara hands over two open checks to Ali. Check C84 belongs to table 6: the main courses have been served, and an accepted tea order is still pending. Check C85 belongs to table 9: the party asked whether dessert is available, but has not ordered it. A third reference, C83, is already closed and is outside this handover.
The authorized colleague completes the required operator transfer. Sara and Ali then verify C84 and C85 under the intended receiving operator, with the expected items and references. They do not combine the two parties' checks. Ali repeats the service actions: follow up the accepted tea for C84, and answer the dessert enquiry for C85 before entering any new order.
At 18:05, Ali confirms tea delivery and records the completed service under the local process. At 18:07, table 9 orders dessert after the availability discussion; that new order follows normal entry and kitchen communication. The earlier enquiry is not treated as an order sent at 18:00. Both changes belong to their own check and time.
What if the transfer does not match?
If C84 still shows the previous operator, the handover remains incomplete even if the guests have met Ali. Keep the service request visible, identify who is responsible meanwhile and ask the authorized supervisor to resolve the record. Do not repeat transactions blindly or share credentials. When the correction is confirmed, record the result so a later colleague does not attempt the same transfer again.
Oracle describes check transfer as changing check ownership; adding checks means combining them. Those are different operations. Its documented transfer function also has reporting limits, so do not promise that changing the operator reallocates every historical sales figure. Any reporting question belongs with the authorized supervisor and the restaurant's configured system.
Finish with a read-back
- The correct open references and receiving operator are verified.
- Closed and unrelated checks remain outside the handover.
- Served items, accepted pending items and enquiries are distinct.
- Each unfinished action has an agreed responsible colleague.
- Any unresolved system mismatch remains visible until confirmed.
Read Oracle's check-transfer explanation and O*NET's restaurant service duties. This scenario is original and fictional. Practise the read-back with a colleague, explore HCA restaurant service training and review current hospitality vacancies.
Explore HCA restaurant service training
