In this article
Any restaurant running more than one shift a day has this problem, and almost none of them have organised anything around it: the crew that's leaving knows things the crew that's arriving doesn't, and that knowledge usually travels as half a sentence on the way to the coat rack.
It plays out somewhere between two shifts, every single day. The lunch crew has just spent four hours on the floor — they know the salmon is nearly gone, that table 6 complained about a cold soup, that this afternoon's delivery only showed up half-full — and at 3:30pm everyone hangs up their apron and goes home. At 6pm the dinner crew walks in, opens the walk-in, and discovers the salmon situation for themselves. Table 6's complaint comes back as an angry review three days later. The missing half of the delivery only gets noticed once it's almost time to plate the sauce.
That's not a general communication problem — it's a very specific one, and it's different from what this blog already covers. A pre-shift briefing is forward-looking and can be run by one person alone: whoever's on duty tells the floor what tonight looks like. A shift handover is backward-looking and structurally can't be run solo — the information sits with the crew that's leaving, and they're usually in the same room as the crew arriving for about ninety seconds, somewhere between pulling off one shirt and putting on the next.
That's also why "just communicate better" never works as a fix. Two people who barely cross paths don't suddenly start talking more thoroughly because you ask them to. What does work is exactly what every other shift-based, high-stakes profession figured out a long time ago: a fixed, short structure that doesn't depend on whoever happens to have a spare minute to mention something. Hospitals call it a structured handoff at a nursing shift change — not because it needs to be complicated, but because it's too important to leave to whoever remembers.
This article translates that idea into restaurant language, not hospital jargon: a four-box method that takes two minutes to fill in, a calculator for what a dropped handover is already costing you, and a plan for rolling it out without it becoming one more task nobody does.
Why a handover isn't a briefing, and isn't a checklist either
A briefing covers what needs to happen NOW, told by whoever's here now. An opening or closing checklist covers the state of the BUILDING — heaters on or off, till counted, doors locked. A shift handover covers something neither of those does: what happened during the shift that just ended that the next one needs to know, and that isn't written down anywhere else.
That makes it an information problem with two owners instead of one. A briefing has one person responsible for saying something. A checklist has one list to tick off. A handover needs the departing crew to remember exactly what's worth mentioning, at the exact moment their head is already halfway home — and the arriving crew has to retain it too, while they're busy starting their own shift.
That's exactly why it usually breaks down without anyone recognising it as a system failure. Nobody was careless — the nearly-gone salmon just stops being anyone's priority once they're already outside, and the dinner crew has no reason to suspect there was anything to be told. The problem isn't the people. It's the absence of a fixed place that information lands in, whoever happens to be on shift.
An unstructured handover is one sentence on the way out the door. A complete one needs four different kinds of information — and they rarely all fit in that one sentence.
What usually gets said
"Have a good one — oh, and the fryer was acting up this afternoon. See you tomorrow!"
What actually needs to cross over
This isn't a criticism of the people saying that sentence — it's exactly the problem a fixed structure solves: not remembering WHAT to say, just filling in four boxes.
Click a box to see what belongs in it. Four categories, in the order a handover actually needs them.
Out & Low
Everything the kitchen or bar used up or nearly used up during this shift — not a full stock count, just what's different NOW from how the shift started.
For example: "salmon is down to about 8 portions, no time to reorder today."
Still Open
Anything that started during this shift but isn't finished — a complaint that still needs a follow-up, a piece of equipment that was acting strange, a table that's still being watched.
For example: "table 6 got a free dessert for a cold soup — keep an eye on whether they leave happy."
Heads Up
What's different about tonight compared to a normal service — a booking that needs extra attention, a new hire who still needs support, a delivery arriving later than planned.
For example: "a table of 8 for a birthday at 8pm — they've already asked three times about the dessert with a candle."
Do This First
The ONE action that comes before all the others — not a summary of the other three boxes, but the call on what needs to happen the moment the new crew walks in.
For example: "call the supplier about the missed delivery first — everything else can wait until after mise en place."
These aren't four separate forms — it's one sheet with four boxes, filled in during the last five minutes of the shift. An empty box is fine; a forgotten one isn't.
1. Out & Low
This is the easiest box to fill in and the one most often skipped, precisely because it seems so obvious — "they'll see the salmon is low when they open the walk-in." The problem is timing: the dinner crew usually discovers it once a guest has already ordered it, not five minutes before service when there's still time to adjust the specials board or warn a guest a choice isn't available.
This isn't a full shopping list — that's what stock control is for. It's about what's changed SINCE this shift began, and what the next crew will run into within the first hour if nobody mentions it.
2. Still Open
This box exists because some problems don't end within one shift. A complaint smoothed over at 2pm with a gesture, while the guest is still sitting at the table when the crew changes, is a problem that survives — and a new crew that doesn't know something already happened risks compensating the guest a second time, or doing nothing at exactly the moment it was still needed.
The same goes for equipment: a fryer that was "acting strange" but still working, a walk-in that felt a touch warmer than usual. Nobody calls a technician over that at 2pm — but if it fails outright at 7pm, the difference between "we knew this was coming" and "this came completely out of nowhere" is exactly this box.
3. Heads Up
This is the only box that looks forward instead of back, and it exists for a simple reason: the lunch crew often knows things about the evening that the dinner crew doesn't know yet, purely because the phone rang during the day and the bookings came in over lunch. A group booking confirmed at 11am shouldn't get lost by 6pm.
A new hire belongs here too: if the lunch crew noticed a trainee struggling at a particular station, that's exactly the kind of thing that helps the dinner crew avoid putting someone on the same spot without support.
4. Do This First
The first three boxes are a list. This box is a choice, and that choice is exactly what an unranked list doesn't offer. A new crew arriving with four equally-weighted points on a sheet will work through them in whatever order feels convenient — often too late for the one that was actually the most urgent.
This box forces the departing crew to set that priority themselves, at the moment they have the best overview of what genuinely can't wait. It costs one sentence, and it's the difference between a sheet that gets read and a sheet that gets ignored because nothing on it looks urgent.
Where this matters most
Not every restaurant benefits equally from a fixed handover. A place with one steady crew running the whole service from open to close barely has this problem — the same people who watched the salmon dwindle are still there at 7pm. The risk grows with every fault line between who has the information and who needs it.
A split shift — lunch and dinner staffed differently — is the clearest fault line, but not the only one. A restaurant that leans heavily on seasonal or student staff sees the same handover happen every week with different people on both sides, which makes a fixed structure matter even more than it would for a settled team that knows each other well. And an owner who isn't present for both services — the most common situation of all — is themselves permanently dependent on what does and doesn't get passed along between the people who were actually there.
The more of those fault lines stack up — split shifts, rotating staff, an owner who isn't always around — the more likely something gets stranded between two shifts, and the more a five-minute sheet is worth against what it costs not to have one.
What a dropped handover costs you
The arithmetic is simple once you write it down: how many times a week you change crews, how often something gets lost in that changeover, and what a missed handover typically costs — a redone dish, a gesture to a guest, wasted prep. Multiply that out and you get a number most owners have never actually worked out.
Enter your own estimate. Nobody tracks this precisely — it's a realistic guess, not a bookkeeping figure.
Calculate what a dropped handover costs you
Enter your own numbers — the result updates as you type.
—
This is an estimate based on your own judgement, not a measured industry statistic — enter the figures that fit your own restaurant.
The number this calculator can't guess is your own: how often does something actually get lost? Just track it for two weeks — every time someone says "if only I'd known that" — and you'll have a real percentage instead of an estimate.
And keep in mind: this figure only counts the visible misses — the redone dishes, the gestures that were needed. The invisible cost — a guest who never comes back a second time because nobody knew about last time's complaint — isn't even in it.
Your handover rollout plan
Turn this into three moments: the sheet itself, the first two weeks, and how you make it stick.
Build the sheet
- One sheet of paper, or a fixed spot on the whiteboard by the time clock, with four headings: Out & Low, Still Open, Heads Up, Do This First.
- Put it exactly where the departing crew already passes by — near the time clock, by the door, never somewhere that needs a separate stop.
- Make it a habit of the LAST ten minutes of the shift, not the first ten of the next one — the information is still fresh then.
The first two weeks
- Ask the departing shift lead to fill it in, not everyone individually — otherwise nobody does it, because everyone assumes someone else already has.
- Have the arriving crew read it out loud at the start of their shift, the same way a pre-shift briefing starts — two minutes, no discussion needed.
- Throw the sheet away every day. It isn't an archive — it's a bridge between two shifts that's worth nothing the next morning.
Making it stick
- If a box stays empty every time, it's probably not that there's nothing to report — ask explicitly until it becomes a reflex.
- If "Do This First" is the one that keeps staying blank, that's the signal the departing crew is filling in the other three but not prioritising — exactly the part that saves the most time.
- Don't skip it on the shifts that were already chaotic. Those are the nights it matters most, not the ones to let slide.
Conclusion: it's not extra work, it's a missing link
A shift handover can't be fixed by asking people to communicate better — two crews who cross paths for ninety seconds simply don't have the time for that. It's fixed with a short, fixed structure that doesn't depend on who happens to have a spare minute: four boxes, five minutes, every shift.
The four-box method isn't new admin stacked on top of what you already do — it's making explicit what a good shift lead already half-does in their head today, but rarely writes down anywhere. Out & Low, Still Open, Heads Up, Do This First: four questions that together cover exactly what gets lost between two shifts.
Start small: one sheet of paper, one week, and simply count how often someone says "if only I'd known that." That number, not this calculator, is the real proof of whether it works for your restaurant.