Shift handover: how good teams pass the day without dropping it

Every shift-based business has the same fragile moment, two or three times a day: one group of people who know everything walks out the door, and another group who knows nothing walks in. Whatever crosses that line survives. Whatever doesn't – the 86'd short rib, the guest who asked not to be woken, the sensor that tripped twice – turns into tomorrow's apology.

The strange part is how little attention this moment gets. Teams will argue for a week about the schedule template and then hand over the actual day in a hallway sentence: "pretty quiet, the thing with the walk-in is still going on, Dana knows." Dana, of course, left at four.

This is a guide to doing it deliberately. None of it requires software – a printed page and ten minutes of discipline will get you most of the way. (We sell the software version, and there's exactly one section about it near the end, clearly labeled.)

Why handovers fail

Handovers don't fail because people are careless. They fail because the context of a shift lives in three unreliable places:

• People's heads. The 7 am lead knows the boiler guy promised to come back "after lunch." That fact exists nowhere else. If the 3 pm lead doesn't hear it spoken aloud, the boiler guy arrives at 2:30 to a desk that has never heard of him.
• The group chat. Group chats feel like a record but behave like weather. The note about the late check-in was real at 11:48 pm – by the 7 am scroll it's sixty messages up, behind two memes and a discussion about Saturday. Chat is where context goes to scroll away.
• The previous tool's exhaust. A POS report, a ticketing queue, a cleaning checklist. Each shows its own slice. None of them says what the next human on duty should do first.

And one more place, the most fragile of all: the overlap that doesn't exist. On paper the shifts touch – 3 pm to 3 pm. In practice the morning lead is doing a refund at 2:55, the afternoon lead is hanging a coat at 3:02, and the day changes hands in the seven seconds they pass each other. Anything not written down before that moment was never going to survive it.

There's a structural reason, too: a handover is the one task whose cost falls on someone other than the person doing it. Writing a good note takes the outgoing lead ten minutes at the worst moment of their shift – the end. Skipping it costs the incoming lead an hour of confusion. Without a fixed habit, rational tired people skip it every time.

So the fix isn't "try harder." The fix is to make the note cheap to write, impossible to miss, and always shaped the same way.

What a good handover contains

A handover note isn't a diary. The next shift doesn't need prose; they need to know what to do first, what not to redo, and what's about to happen. Three sections cover it, plus one that covers the schedule itself:

1. Open issues. What is unresolved right now, one line each, each with an owner. "Walk-in door sticking – repair booked Thursday, ref #4412." "Room 218 card reader intermittent – maintenance aware." If a line has no owner, the handover is where it gets one.

2. Done & verified. What was finished and checked this shift. This section exists so the next crew doesn't redo work – and so "I thought you did it" dies. "Pool chemicals balanced and logged, 9:40 pm." Done-and-verified is a different claim than done; make people write the stronger one.

3. Heads-up for next shift. The future, in time order. "Party of twelve at 7:30, back room." "Linen delivery 6–7 am, use the side door." "VIP in suite 9 leaves 8:30, car booked." The test for this section: if the incoming lead reads nothing else, do they avoid the worst surprise of the next eight hours?

4. Callouts & coverage changes. Who called out, what moved, who covers. Schedule changes made verbally at 9 pm are precisely the ones that produce an empty post at 6 am.

That's the whole structure. Write it in the last ten minutes of the shift, in the same place every time, and read it aloud at the overlap when you have one. Two disciplined teams can run this on paper for years.

Handover patterns by trade

The skeleton above is universal; the flesh differs by trade. Here's what the strong operators we've watched actually put in each section.

Restaurants: the 86 list and the room

The restaurant handover has two halves with different lifespans. The kitchen half is the 86 list and prep status – facts that expire by tomorrow's delivery. The floor half is the room: which reservations matter, who reserved the back room, what the GM said at line-up. The classic failure is the lunch-to-dinner seam on a split-shift day: the closer arrives at 4 pm to a dining room that "everyone" knew was rearranged for a party – everyone who worked lunch. Strong houses write the 86 list and the room changes down at the pass before the lunch crew breaks, not from memory at 5.

Hotels: the night is the test

A hotel handover happens three times a day, and the 11 pm one matters most, because the night auditor works alone – there is nobody to ask. Late check-ins with names and quirks ("arriving ~23:30, asked not to be disturbed before noon"), VIP departures with car times, anything broken in a room that's occupied. The morning note back to the day shift is shorter but saves the most face: what happened overnight that the 7 am guest will mention at the desk.

Clinics: structure beats heroics

Clinical teams formalized this decades before the rest of us – SBAR exists because "she seemed fine when I left" is not a medical record. Without giving clinical advice, the operational pattern translates: the overnight note leads with anything that needs action before a fixed time ("follow-up before 9"), states facts with timestamps rather than impressions, and the incoming shift acknowledges it explicitly – read and signed, not assumed. One more clinical habit worth stealing: the handover happens at a fixed overlap window that is scheduled, not squeezed in if the morning is calm.

Security: the log is the product

For a guard team the handover note is the deliverable a client may eventually read. Post by post: what tripped, what was checked, what was logged, plate numbers, times. The discipline that matters here is tagging by location – "fence sensor, dock 3, tripped 2:14 and 3:05, checked both, false alarm" is useful; "sensors acting up tonight" is noise. The day shift should start their patrol already knowing which camera to glance at first.

A simple template

If you want the structure without inventing the page, we made a free one: a shift handover template with exactly the four sections above – as a spreadsheet for a shared drive, or a one-page PDF you can print into a stack and keep at the desk. No email wall; take it.

Print twenty, put them on a clipboard, and declare the clipboard the single source of truth at shift change. That sentence – the clipboard is the truth – does more for handovers than most software purchases.

Making it stick

Habits survive on three properties: same place, same structure, every shift.

Same place. The note lives in one fixed location – the clipboard at the desk, the binder at the post, the pinned doc. The moment "where did they write it" is a question, the system is already dead.

Same structure. The four sections, always, even when a section is empty. "Open issues: none" is information; a blank page is a shrug. Structure is also what makes the note fast to write at the end of a long shift – nobody composes prose at 11 pm, but anyone can fill four labeled boxes.

One refinement once the basics hold: make the incoming shift acknowledge the note, not just have access to it. A signature line, initials, a thumbs-up on the pinned doc – the mechanism doesn't matter. What matters is that "I didn't see it" stops being an available sentence. In teams that add acknowledgement, the quality of the notes rises on its own, because writers finally know they're being read.

Every shift. Including the quiet ones. The Tuesday note that says "nothing open, truck at dawn" costs ninety seconds and keeps the habit alive for the Saturday that ends in chaos. The first skipped quiet day is the beginning of the end.

And the honest software paragraph, as promised: this entire structure is what Schedio's hand-off notes are – the same four-part note, attached to the actual shift on a live coverage dashboard, time-stamped, visible to the right people, impossible to leave in a jacket pocket. If the paper version sticks for your team, the digital one will too, and it costs $49 a month per location, plus applicable tax at checkout, with the rest of the product included. If the paper version is enough – genuinely fine. The point is that the day gets passed, not dropped.