The worst handover in hospitality is not an empty one.
It is “all good”.
Two words that tell the next shift nothing about the fridge that ran warm, the guest who is expecting a call, the casual who is still learning the till, the delivery that has not arrived or the booking that needs a quieter table.
Then the next team finds out the hard way and everyone acts surprised.
A handover is not a diary entry
The purpose is not to record every event. It is to protect the next shift from surprises.
The best handovers are short, specific and action-led. They answer three questions: what changed, what matters next, and who owns it?
If a note does not change the next shift’s decision, it probably does not belong in the handover.
Use five headings every time
Keep the format identical across every shift:
Trade: what happened versus expectation, briefly.
Guests: unresolved complaints, VIP or accessibility notes, follow-up commitments.
People: absences, training gaps, welfare or conduct issues that the next manager must know.
Product and equipment: stock-outs, quality concerns, maintenance and deliveries.
Next action: one named owner and a due time for each unfinished item.
That last line is what separates a handover from a complaint board.
“Ice machine noisy” is not useful. “Ice machine noisy. Jamie to call technician by 10am. Use backup ice bins for lunch” is useful.
Make it a management habit, not extra paperwork
The handover should take around 15 minutes at the end of a shift. Ten to write it properly, five to speak through the important points with the incoming manager.
Do not make a manager rewrite the entire service. Use checkboxes for routine conditions and a short free-text field for exceptions.
The next manager should be able to read it while walking the floor, then know exactly where to start.
Review the repeats on Monday
Once a week, scan the handovers for anything that appears more than twice. Repeated stock-outs may be a par issue. Repeated guest complaints may be a service-standard issue. Repeated “short staffed” notes may be a roster problem.
The handover is a detector. It tells you where the operating system is failing, without waiting for a monthly meeting.
Handover control
| Handover item | What belongs in it | Named owner |
|---|---|---|
| Covers and pacing | Arrival peaks, VIP or special notes | Duty manager |
| Product constraints | 86s, allergy and substitutions | Kitchen lead |
| Labour coverage | breaks, gaps, priority zones | Floor manager |
| Carryover actions | outstanding recovery or supplier issue | Shift lead |
Illustrative handover checklist. Replace with verified venue inputs.
Further reading
[Restaurant Industry Award](https://awards.fairwork.gov.au/MA000009.html
The standard to aim for
At 4pm, the incoming manager should be able to answer: what is happening tonight, what could go wrong, and what do I need to do first?
If they cannot, the prior shift has handed them a room, not a handover.
Write for the person who was not there
A useful handover should make sense to someone who did not watch the shift unfold. “Busy night” does not help the morning manager understand why a table is unhappy, which batch needs using first or why a team member needs support. Replace general labels with the minimum detail needed for the next person to act.
For example: “Table 14 waited for mains after a docket delay. Manager spoke with them, offered dessert, they may return on Friday. Check booking note.” That is specific without becoming a diary. It tells the next shift what happened, what has already been done and what still needs attention.
Keep confidential personnel matters out of a shared shift log. If a matter needs a private conversation, record only the operational implication the next manager must know, then use the appropriate private channel. The handover protects service, not gossip.
Make the five headings easy to use under pressure
The best handover is not the most detailed one. It is the one the team can complete when the room is closing, the till is being balanced and everyone wants to go home. Use the same short headings every time: guests, people, product, systems and tomorrow.
Under each heading, ask only for information that changes the next shift. Guest issues, staffing gaps, product shortages, equipment problems and booking or event notes are enough. If a heading is consistently blank, remove it. If the same note keeps appearing, turn it into a checklist, maintenance request or pre-service prompt.
Give the handover a home that the right people can reach. A shared document, purpose-built log or printed close sheet can all work. What matters is that the next manager knows where to look and the outgoing manager knows the note has been read when it matters.
Audit the handover after seven days
At the end of the first week, read the handovers in one sitting. You are not looking for beautifully written notes. You are looking for whether the same five headings were used, whether unfinished actions had a name and time, and whether the next shift could understand the note without calling the previous manager.
Circle any phrase that appears repeatedly: “short staffed”, “ran out”, “guest unhappy”, “machine issue”, “busy”. Then ask one more question: what would have prevented this from appearing again? The answer may be a roster adjustment, a par level, a maintenance action, a brief or a training conversation. The handover has done its job when it produces a better system, not more writing.
Managers should also be able to say when nothing unusual happened. A short, clean note is a good result. The objective is not a growing file. It is fewer surprises and faster starts for the next team.
Make the handover part of the shift rhythm
Set a fixed moment for the outgoing and incoming leaders to read the exceptions together. It might be before the first briefing, at the manager overlap or as the final close task. The time matters because it makes reading the handover an operating responsibility, rather than something people hope happens. When a note needs a decision, agree the owner before the conversation ends.
Keep the record easy to find for the people who need it and protected from people who do not. A handover is useful when it is current, clear and reviewed. It is not useful when it becomes a long archive nobody opens until there is a problem.
If management handovers are mostly WhatsApp messages and memory, start by standardising the five headings. It is one of the quickest ways to make a team feel less reactive.
Saved to Open Context
