Handover routines that stop work leaking between shifts

Trace a guest complaint back far enough and there is a reasonable chance it lands on a shift change. The maintenance request logged at four and not passed to the evening team. The allergy noted at check-in and not carried to dinner service. The late arrival flagged on the morning sheet and forgotten by the person who actually opened the door. The wider context of shift work helps explain why handovers are an operational control rather than a courtesy.

These are not attention failures. They are structural. A shift boundary is a point where information has to survive a transfer between two people who are, at that exact moment, both busy — one finishing, one starting.

Why informal handover fails predictably

The default handover is a conversation at the desk while the outgoing person puts their coat on. It fails in three specific ways, and all three are properties of the format rather than the people using it.

It is unordered, so what gets mentioned is what happens to be top of mind rather than what matters most. It is unrecorded, so there is no way to establish later what was passed on. And it is interruptible, so a guest arriving mid-handover truncates it, usually at the point where the important thing was about to be said.

A handover format that fits in four minutes

The goal is a routine short enough that nobody skips it under pressure. Four categories, in a fixed order, written down:

• In progress — anything started and not finished. A room being fixed, a delivery half-checked in, a complaint being resolved.
• Expected — what the incoming shift should be watching for. A late arrival, a group departure, a contractor due.
• Exceptions — anything that deviates from the standard state. A room out of order, a lift on a service call, a card terminal misbehaving.
• Carried — items handed over on the previous shift that are still open. This one catches the thing that has been handed over four times and done zero times.

The fourth category is the one that changes behaviour. An item that keeps reappearing in Carried becomes visibly embarrassing, which is exactly the pressure needed to get it closed.

Overlap is what makes it possible

A handover cannot happen if the shifts do not overlap. If the late shift starts at the minute the early shift ends, the handover is either rushed or unpaid, and both of those degrade it.

Fifteen minutes of paid overlap per boundary is the usual recommendation and it is a real cost — across three boundaries a day, seven days a week, it adds up to a meaningful fraction of a full-time position. It is nonetheless one of the better-value hours in a hotel's payroll, because the alternative cost is the compounding kind: repeated work, guest recovery, and the slow erosion of trust between departments who each believe the other drops things.

Written, but not long

The instinct when formalising a handover is to build a comprehensive form. Resist it. A handover document that takes twelve minutes to complete will be completed properly for about two weeks.

Constrain the format deliberately. One side of a page, or one screen. If an item needs more detail than fits, that detail belongs in the maintenance system or the guest profile, and the handover carries a pointer to it rather than the content itself.

The read-back

Borrowed from aviation and worth the mild awkwardness: the incoming person summarises back the two or three items they consider most important. It takes thirty seconds and it converts the handover from a broadcast into a confirmed transfer.

It also surfaces disagreement about priority, which is useful information. If the outgoing shift thought the contractor visit was the headline and the incoming shift read past it, that is worth catching at the boundary rather than at two in the afternoon when the contractor is standing in reception.