A Fixed Structure for Handover Between Shifts
A look at how restaurants can build handovers as a structure that carries the day forward - with fixed categories for upcoming bookings, table status, groups and issues, and a clear person responsible for each open point until the next shift takes over.
Why a One-Time Handover Isn't Enough
Many restaurants have some form of handover, but it's worth asking how much of it happens verbally, right before the shift begins. If the information only exists in the memory of the person going off duty, it quickly disappears once the evening gets hectic. The next shift then starts without a clear picture of what has already been settled, and has to ask the same questions all over again.
A better solution is to build the handover as a structure that carries the day forward, not just a point that ends when shifts change. The structure should show what has been settled, what is still open, and who is responsible going forward. This turns the handover into an extension of operations, rather than a separate routine that gets set aside afterward.
Four Categories That Should Stay Together, in the Same Order Every Time
The structure should be divided into four fixed categories: upcoming bookings, table status, groups, and issues. Upcoming bookings show what will happen for the rest of the day, while table status shows which tables are free, cleared, or currently being served. When the categories always appear in the same order, staff quickly know where to find the answer without searching through loose notes.
The dashboard in TableBooking shows bookings, guests, and the table map together, making it easier to pull up upcoming bookings and table status without switching between multiple sources. Tables can also have a reference photo, so the next shift can find the right table quickly even if they don't know the venue well. This information should still be placed within the fixed order, not just displayed as a general overview.
Groups and Issues Need a Named Follow-Up Person, Not Just a Description
Groups shouldn't just be noted as a number of guests and a time. The structure should show what has been agreed with the group - table placement, any pre-ordered menu, or arrival time - and what remains open. Without this distinction, groups can easily be treated as a regular booking, even when questions remain that should have been resolved before service starts.
Issues, such as a complaint, a booking error, or a guest who had to be moved, should be logged with one responsible person and a status: resolved, in progress, or awaiting response. Without a named follow-up person, issues can easily be left for the next shift to discover again, often in a more pressured situation than the one that originally caused the issue.
How the Structure Gets Closed Out by the Next Shift
When the next shift goes through the structure, they should start with what's marked as open, rather than reading the entire overview from the top each time. A brief verbal review of these points - not all the content - makes the handover shorter and more precise, while the written structure remains available if something needs to be double-checked later in the shift.
Points that get resolved along the way should be marked as closed with a short comment on what was done, rather than simply removed from the list. This gives the next shift a chance to see what worked, and makes it easier to spot if the same type of issue reappears over several days, without anyone having to remember it from memory.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free