How to write a shift handover

A shift handover is the note one manager leaves so the next one walks in knowing what happened, what's still open and what to do first. Done well, it takes five minutes to write and saves the next shift an hour of guessing.

Done badly, or not at all, it's how a leaking walk-in door turns into a thrown-out delivery, or one guest complaint gets two different answers from two different managers. This guide covers what to include, a structure you can copy, examples of vague and useful notes, when to write it, how the incoming manager should read it and what to leave out.

Why handovers fail

Most handovers don't fail because managers don't care. They fail for a handful of predictable reasons:

What to include

Not every shift needs every heading, but every heading should be considered. If there's nothing to say, "nothing to report" is useful too: it tells the next manager you checked.

The numbers

Net sales, covers or guests, labor % and comps and voids. For a hotel front desk: occupancy, arrivals, departures and rooms out of order. Add one line when a number looks odd: "Labor 34%: sent one server home at 20:30, but it went quiet after the game." The number tells the GM something happened; the line tells them what.

86'd items and low stock

What ran out, at what time, and whether it's back on the next delivery or needs ordering. Running low is just as useful: the opening manager can fix "two bottles of house red left" before service and can't fix "out of house red" during it.

Staff and call-outs

Who called out, who covered, early cuts, and any gap on the next shift's rota. Keep it operational: "Bar back called out; covered by Jordan until 22:00" is all the log needs. The reason someone was absent isn't the next manager's business (more on that below).

Guests and complaints

What happened, when, what you did and whether it's resolved. If you promised anything (a callback, a comp on the next visit, a refund decision by Friday), write down exactly what you promised. Broken promises from a manager who didn't know about them do more damage than the original complaint.

Maintenance

What broke, when you noticed, who you called, what they said and when they're coming. "Ice machine not making ice since 18:00. Called the service company at 18:20; tech booked tomorrow 09:00–11:00. Using bagged ice." Add who needs to let the technician in.

Incidents

Facts only: what happened, when and where, who was involved (by role where possible), what was done, and whether a formal report was filed and where. Use the minimum personal information the next manager needs. If your jurisdiction or employer requires a formal incident or injury report, file it there; the handover points to it, it doesn't replace it.

Follow-ups with an owner and a due shift

Every open item needs a name and a deadline, and the deadline should be a shift, not "ASAP": "Sam, Saturday open". A shift is something the next manager can check. When the follow-up is done, close it with a short note ("Booked Tue 10:00") so the next person doesn't chase it again.

A simple structure you can copy

Use the same order every shift. Readers learn where to look, and writers stop forgetting headings.

Date, shift, manager on duty, location

  1. First things first: the two or three things the next manager must know before service.
  2. Numbers: sales, covers or guests, labor %, comps and voids (or occupancy and arrivals), plus a line on anything odd.
  3. 86'd and low stock: item, time, back when.
  4. Staff: call-outs, cover, cuts, gaps on the next shift.
  5. Guests: complaints, what was done, promises made.
  6. Maintenance: what, who was called, when they're coming, who lets them in.
  7. Incidents: facts only; report filed, and where.
  8. Follow-ups: task, owner, due shift.

Handed over to ________ at __:__

The printable manager log book lays this out on one page for restaurants, bars and hotel front desks, in US Letter and A4.

Vague notes versus useful ones

The test for any line: could the next manager act on it without calling you?

Examples of vague and useful handover notes
VagueUseful
Dish machine acting up again.Dish machine leaking at the door seal since 21:00. Called the repair company at 21:15; visit booked Tue 10:00. Towels down; check the floor at open.
Ran out of some stuff.86'd salmon at 19:40 and house red by the glass at 21:15. Salmon is on tomorrow's delivery. Red needs ordering: Sam, by Thu open.
Difficult guest on 12.Table 12, 20:10: steak sent back twice. Comped the main and offered dessert; the guest left happy. Nothing to follow up.
Room 214 complained.Room 214, 22:40: noise from the corridor. Moved to 318 at 23:05 with new key cards. Housekeeping to check 214 in the morning.
Staff issue tonight.Line cook called out at 15:30; prep cook covered until 22:00. Tomorrow's close is one short. GM to decide cover by Wed open.
Till was off.Till 2 short $20 at close. Recounted twice with a second manager; drop made as counted. GM to check the till report at open.

Notice what the useful notes share: a time, a specific item or place, what was done, and who does what next.

When to write it

How the next manager should read it

A handover is only half done until it's read. The incoming manager should:

  1. Read it before the shift starts, not in the middle of service. Ten minutes early is enough.
  2. Start with open follow-ups: accept them, reassign them, or ask about them.
  3. Check what's 86'd and low, and take it into the pre-shift huddle.
  4. Confirm maintenance visits: who's letting the technician in, and when?
  5. Mark it as read, with initials on paper or a read receipt in an app, so the writer knows it landed.
  6. Ask the outgoing manager about anything unclear while they're still in the building.

Privacy: what to leave out

A shift log is read by every manager and often by department heads. Write it as if the person you're writing about will read it, because one day they might.

In ShiftLogKit, incident entries are readable only by owners, admins and their author, are deleted after24 months by default, and are left out of exports unless an owner or admin chooses to include them. ShiftLogKit is an operations logbook; keep any legally required incident or HR records in the systems your jurisdiction requires.

Shift handover checklist

On paper or in an app

Paper works if the binder lives somewhere everyone passes and someone copies open follow-ups forward every shift. Start with the printable manager log book and theopening and closing checklist.

ShiftLogKit does the copying for you: open follow-ups stay at the top of every next shift's log until someone closes them with a note, "Since your last shift" shows the incoming manager exactly what they haven't read, and the owner gets one digest per location per day. It's free, with no accounts and no email.Create a free workspace and try it on your next close.