What breaks at shift handover (and how to stop it)

It's 8:45 pm. The evening shift is wrapping up, the night shift is clocking in, and the entire handover fits into three sentences said standing next to the till: 204 is complaining about the air con, the beer supplier called, everything else is quiet. At 11:10 pm someone on the night shift calls the manager's mobile to ask whether they can move a guest, because nobody knows if 204 is still occupied or who signs off on a room change at that hour.

A shift handover works when it meets two conditions: what happened today gets written down in one fixed place, and what never changes never gets said out loud. Most businesses running shifts mix the two, which is why the handover ends up as an improvised summary that depends on who's giving it and how much energy they have left that evening. Pulling those two layers apart is most of the work.

The three gaps information slips through

When you trace a typical mistake backwards, one of these three gaps is almost always behind it:

• What was said and never written down. The supplier's heads-up, the guest complaint, the machine making a strange noise. If it lives in the head of the person heading home, it stops existing at 9:00 pm.
• What is written down but nobody can find. The closing procedure exists, sure: in a PDF from two years ago, in a WhatsApp group with 4,000 messages, or in a shared folder only the person who created it knows how to open.
• What nobody knows they're supposed to know. The worst case. Nobody asks because nobody imagines there's a rule. You find out when the customer complains or when the invoice lands.

Each one is fixed differently. The first needs somewhere to leave the handover note. The second needs searchable documentation. The third needs asking to be cheap and embarrassment-free.

Separate what changes from what never changes

Take the last handover you gave and sort it into two columns. On the left, today's facts: a breakdown, a big group tomorrow, an angry customer, a delivery that never arrived. On the right, procedure: how the till is cashed up, who approves a discount, what to do if the alarm goes off, how late cancellations are accepted free of charge.

The right-hand column should never be said out loud. It's exactly the kind of thing that needs writing down once and looking up a thousand times.

If a piece of information has to be repeated at every handover, it isn't news: it's a badly written procedure.

That one line saves you a lot of arguing. Every time someone says remember to remind them that, the answer isn't to remember better, it's to document it and put it where people look.

The handover note people actually fill in

Long handover notes don't get filled in. A fifteen-field form at eleven at night ends up blank or copy-pasted from yesterday. What survives is short and always the same:

1. Open issues. Only what's still live when you leave. Closed items don't get mentioned.
2. To-dos with a name and a time. Call the engineer after 9. With no name on it, nobody does it.
3. Heads-ups for tomorrow. Unusual bookings, deliveries, people coming to view the place.
4. Till and stock. Cash discrepancies, breakages, anything that's run out.

Four points, two minutes. And one rule: if something shows up on the note three weeks running, it isn't an incident, it's a procedural gap that belongs in the manual. That's the filter that turns the handover note into living documentation instead of a diary nobody rereads.

The cost of not knowing, in your own numbers

You don't need to take anyone else's statistics on faith. Do the maths with your own. If a business running two or three shifts loses, conservatively, twenty minutes a day to calls to the manager, work being redone and decisions parked until tomorrow, that's around ten hours a month. Multiply by the hourly cost of whoever fields those questions and you have a cautious estimate of what the disorder costs you. It's an estimate, not a figure: the useful exercise is running it with your hours and your wages.

Then there's the cost you don't see: the mistake made by the person who didn't know. A charge applied wrongly, an allergen described wrongly, a customer promised something you can't deliver. Behind every one of those is a sentence that lived in somebody's head instead of in a document.

What a tool does well here, and what it doesn't

Somewhere to ask questions mid-shift closes the second and third gaps, not the first: you still write the handover note yourself. Concierge answers using only the documents you upload, and cites the exact document and section, so whoever asked can check where the answer came from. When something isn't written down, it doesn't make it up: it emails that question to whoever you choose, and there's your free list of what still needs documenting.

That suits teams with turnover: the new starter asks a screen instead of interrupting the supervisor fifteen times, which is half the problem with onboarding in shift-based businesses. And if you have staff who don't speak Spanish, it answers in the language the question was asked in, even when the document is in another.

Where to start

Don't rewrite the whole manual. This week:

1. Note down for five days every question that reaches you outside your shift. No filtering. You'll get between ten and thirty, many of them repeats.
2. Flag the ones that are procedure rather than news. Those are your first pages of documentation.
3. Write one page per topic, short, with the answer up top. Closing, payments and approvals usually cover most of it.
4. Put the four-point handover note in the same place every day and insist on it for two straight weeks until it's habit.
5. Stop answering from memory. When someone asks you something that's already written down, reply with where it is. That's the only thing that gets people looking it up themselves.

If you want to try the lookup side before changing anything else, there are 14 days free with no card and you can cancel in one click. But the order matters: first the five questions you get asked most, then the tool. The other way round doesn't work.