A restaurant handover should transfer decisions and unresolved issues, not create a diary of everything that happened. The next shift needs to know what could affect service, what has already been done and what still needs an owner. A short, structured handover can reduce repeated checking while keeping important details from disappearing during a busy change of staff.
Lead with what can affect the next service
Put time-sensitive operational information first. That can include unusual booking requirements already recorded through the restaurant's normal process, unavailable menu items, stock shortages, equipment issues and work that has not been completed. Routine information that the incoming team can see elsewhere does not need to be copied into every handover.
Separate facts from actions still required
A note such as 'fridge issue' leaves too much interpretation. Record what was observed, what action has already been taken and what remains outstanding. Where a matter requires a manager, maintenance provider or other competent person, identify the escalation rather than implying that a brief handover note is itself a diagnosis or repair instruction.
Give customer follow-ups enough context
If a customer matter needs further attention, the next responsible person should understand the issue and the promised next step without reading a long narrative. Record information through the restaurant's approved system and avoid copying unnecessary personal data into informal notebooks or messages. The handover should help complete the service response, not create a second uncontrolled customer database.
Make stock exceptions specific
'Low stock' is less useful than identifying the affected item and the operational consequence. The incoming shift needs to know whether an ingredient is unavailable, whether a substitute has been approved through the restaurant's process, or whether a delivery is expected. Where allergen or ingredient information could change, staff should rely on maintained source information rather than treating a handover comment as definitive product guidance.
Record equipment problems without normalising them
Repeatedly carrying the same fault from shift to shift can make a genuine problem seem routine. Give unresolved equipment issues an owner and escalation route, and distinguish equipment that has been taken out of use from equipment that remains available under an authorised procedure. Safety-critical questions belong with the restaurant's established procedures and competent advice, not improvisation in a handover book.
Close completed items instead of copying them forward
A handover becomes difficult to trust if old issues remain visible after resolution. Mark actions complete and remove them from the active list according to the restaurant's record-keeping method. This keeps attention on the genuinely open work and prevents staff wasting time investigating something another shift has already solved.
Keep the format stable but the content selective
A consistent set of headings helps staff remember what to consider, but it should not force them to write something under every heading. Review the format when recurring gaps appear. If important information repeatedly arrives through informal chats instead of the handover, the structure or staff routine may need changing. The measure of a good handover is whether the next shift can act confidently without having to reconstruct the previous service.