Guide
How to write a shift handover the next lead will actually use
Why handovers go wrong
Most handovers fail in one of two ways. Either they are too long, a retelling of the whole shift that the next lead skims, or they are too thin, a line saying “all fine” written on the way out of the door. Both leave the incoming lead to rediscover problems for themselves, usually in the middle of service.
Underneath both is the same mistake: the handover note is the only place unfinished work lives. When the note is short, rushed or never written, the work disappears with it. The fridge that was running warm, the engineer who was supposed to call back, the dish that is off until Thursday: if they were only in the note, they are now only in someone’s memory.
Keep the work separate from the message
It helps to think of two different things. An issue is a piece of work, such as “the walk-in fridge is running warm”. It needs one owner and a next action, and it stays open for as many shifts as it takes until it is fixed. A handover is a message from one shift to the next: what changed and what to watch. It points to the open issues; it does not own them.
Kept apart, a forgotten handover note never means a forgotten job. The incoming lead can always see every open issue for their department, with who owns it and what happens next, and the handover adds the context.
What to put in a shift handover
- What changed during this shift. New problems, problems that got worse, and anything that was fixed but might come back.
- What the next lead must know before service. Closed areas, unavailable dishes, large bookings, anything that changes how they run the shift.
- Which blocked items need a decision. Work that is stuck until someone with the authority says yes or no.
- Whether the next shift is short of anyone, and what has been arranged to cover it.
That is the whole list. Our shift handover template asks exactly these questions and nothing else.
What to leave out
- A copy of every open job. Point to the issue list instead; copies go out of date the moment someone updates the original.
- Guest names, contact details or health information. Describe the situation, such as “table of eight at 7.30, two nut allergies”, and keep personal details in the system built for them.
- Blame. A handover is read by the whole team; facts travel better than opinions.
- Things that are finished and need no follow-up.
Write it before you leave
A handover is due before the earlier of the end of your shift and the start of the next one. Written the next morning, it is written from memory and arrives after the person who needed it has already started. If you are late, record the time it was actually written rather than backdating it; a late handover that says it is late is still useful.
Reading a handover is not taking on the work
Ask the incoming lead to confirm they have read the handover, and to confirm the specific version. If the outgoing lead adds something afterwards, the incoming lead needs to read the new version, not assume they already know.
Confirming you have read a handover is not the same as accepting every job in it. Ownership of each issue should be accepted on its own, by the person who will do it. That keeps “I read it” from quietly becoming “so it is yours now”.
When nobody writes a handover
Sometimes the outgoing lead forgets, or leaves in a hurry. The incoming shift should still see every open issue, because the list does not depend on the note. The missing handover is then a gap in context, not a gap in the work, and it can be flagged and caught up.
What changed: Walk-in fridge reading 7°C since 4pm. Food moved to the reach-in fridges and engineer booked for 9am. Issue #142, owned by the head chef.
Before service: Terrace closed tonight because of the heater fault (issue #139). Two large bookings at 7.30; sections agreed.
Needs a decision: The quote for the glasswasher part is over the repair limit. Manager to approve or decline.
Short of anyone: No.