Shift handover checklist between operators: what has to be written down before the next person sits down

Shift handover checklist between operators: what has to be written before the next one sits down

A shift handover is not a message saying 'there are pending things'. It is a short, written document that the incoming operator can read in five minutes and start working without asking anyone anything. If the outgoing operator leaves and the incoming one has to reconstruct the state of every conversation by opening chats one by one, the handover did not exist: there was just a change of the person sitting there.

This page is a checklist. It is grouped by stage: before closing, at closing, at opening, and closing the cycle. Each item says what to review and how to know it is fine. It is not a guide to read straight through: it is material to copy, print, or leave posted next to the monitor.

Why handovers break (and it is not for lack of willingness)

Almost all handovers fail for the same reason: the outgoing operator tells what they know, not what the other person needs. 'So-and-so is waiting for a reply' is true and useless. What the incoming operator needs is what was promised, by when, what is missing, and who has it. The difference between the two sentences is the entire quality of the handover.

The second reason is that the handover is done at the end of the shift, when the operator is already tired and wants to leave. That is why the checklist has a 'before closing' stage: that is the one that prevents the handover from being written in a rush at the last minute. If the only stage that exists is the closing one, the handover will come out incomplete every time.

A concrete example from food service: a shop that receives orders via WhatsApp has two shifts, midday and night. If at 15:55 the midday operator writes 'there is a pending order' and leaves, the night operator opens the chat at 20:00 and discovers it was a cheese board to be picked up at 19:00. The order was lost and the customer has already called twice. If instead the handover said 'Order #312, cheese board, pickup 19:00, already paid, still need to confirm it is ready — kitchen has it', the night operator resolves it in two minutes.

Stage 1: before closing (30 to 45 minutes before the shift change)

This stage is not done at the end: it is done while the shift is still live. The goal is that, when the time comes, the handover is copy and paste, not writing from scratch.

• Close or move forward everything you can close. A conversation that can be resolved during the shift should not pass to the next one: every unnecessary handover is a cost that accumulates.
• Mark every open conversation with an explicit status. 'Pending' is not enough: use statuses that mean something to the person coming in, for example 'waiting for customer response', 'waiting for response from an internal area', 'waiting for payment' or 'requires decision'.
• Write down the next concrete action for each open conversation, not the summary of what happened. 'We need to confirm Thursday's shift for them' is a next action; 'we talked about the shift' is not.
• Record who has the ball. If the next step depends on an internal area (warehouse, billing, logistics) and not on the customer, that has to be written down, because the person coming in cannot resolve it alone.
• Leave a record of what was promised, with the words that were used. If you told them 'I'll confirm today', the person coming in has to know that this commitment exists and that it expires during their shift.
• Separate what is urgent from what is important. A conversation that can wait until tomorrow is not the same as one that expires in two hours. The person coming in needs the order, not the full list without hierarchy.

The most common mistake in this stage is leaving classification for the end. If you classify the conversations at 19:55, when you come in at 20:00, you will classify them wrong and the person coming in will start with the wrong conversation.

Stage 2: at closing (the handover document)

This is where the handover is written. The rule is simple: if the person coming in has to open the conversation to understand the item, the item is badly written. The document has to be self-sufficient.

A well-written handover generally has between five and fifteen lines per open conversation. Less than that and information is missing; much more and the person coming in won't read it. If a conversation needs three paragraphs, the next action is probably not clear: go back to step 1 and define it.

• Write the handover in a fixed place, not in a chat that will get lost among other messages. If the team uses an internal messaging tool, pin the message or use a channel dedicated to handovers.
• Always use the same format. If each operator writes the handover their own way, the person coming in has to interpret the format as well as the content.
• Don't mix what is a handover with what is a task for another area in the same document. If billing has to do something, it goes to the billing channel, not the handover.
• If there are no open conversations, write it anyway: 'no pending items.' Silence is not information; the person coming in doesn't know if there is nothing or if the other person forgot to write.

Step 3: at opening (the first 15 minutes of the incoming shift)

The person coming in doesn't start by replying: they start by reading and confirming. These items belong to the person arriving, not the person who left.

1. 1Read the entire handover before opening any conversation. If you start with the noisiest chat, you lose the order set up by the previous shift.
2. 2Confirm that you can access everything the handover mentions: conversations, contacts, templates, billing data. If something is out of your reach, that is the first thing to resolve.
3. 3Check the shift's deadlines: which commitments are due during your hours and which can wait. Organize your work by due date, not by order of arrival.
4. 4Check whether new messages arrived between the close and your opening. Those messages are not in the handover because it was written earlier: they are yours and must be incorporated.
5. 5If you find an ambiguous item, ask the person who left before replying to the customer. Asking a colleague costs a minute; replying badly costs a conversation.
6. 6Leave a mark that you read the handover. It can be a 'received' in the same channel or a checkmark in the document. It serves to know whether the handover arrived and so the person who left knows they can disconnect.
7. 7If the handover is missing or incomplete, don't improvise in silence: resolve what is urgent and leave a record that the handover was missing. That record is what later allows the process to be corrected.

The most underestimated point is the fourth. Between the operator who leaves writing the handover and the one who comes in reading it, minutes or hours can pass, and messages that no one saw come in during that gap. If the team serves customers through WhatsApp, those messages are the main source of complaints about delays, and they don't appear in any handover because the handover was written before they arrived.

The verification table: what to check and how to know it's OK

This is the table to check off. If an item can't be checked, the handover is not ready and the person coming in should not start without resolving it.

What to do when the handover fails

A handover fails in three different ways, and each one is fixed differently. Do not mix them up: if you treat everything as 'lack of commitment', you will insist with reminders and the problem will continue.

If after setting the format the handover still comes out incomplete, the problem is usually staffing, not discipline: an operator handling 60 conversations per shift does not have 45 minutes to classify. In that case the checklist is not relaxed: it is distributed. See the sizing section.

How to know if the handover is working (without asking anyone)

You don't need a survey. There are three signals you can measure with what you already have.

• Number of questions from the person coming in to the person going out. If it drops week by week, the handover is improving. If it stays high, the document isn't self-sufficient.
• Conversations that get answered twice or contradict each other. Every contradictory answer is a handover that didn't record what was promised.
• Messages from the period between shifts that went unanswered. It's the most expensive signal: the customer wrote and nobody saw it. If it shows up often, the review of new messages at the start of a shift isn't being done.

The handover when there are more than two shifts or more than one channel

With two shifts and one channel, the checklist above is enough. With three shifts, several channels, or more than one operator per shift, you need to add three rules.

• One document per shift, not one per operator. If two people leave at the same time, they write a joint handover; otherwise, the person coming in receives two versions of the same conversation.
• The channel of each conversation has to be explicit. A conversation that started on WhatsApp and continued on Instagram isn't the same conversation for the person coming in if it isn't noted.
• If there are auto-replies by schedule active, the handover has to say what automatic message the customer received. The person coming in needs to know what was automatically promised so they don't contradict it.
• If the team uses AI suggestions in the inbox, the handover doesn't change: the suggestion is an aid for replying, it doesn't replace the record of what was promised. What's written in the handover remains the source.

The general rule is that the handover is written per shift, not per person, and that each conversation has only one owner at a time. If two operators think a conversation is theirs, nobody answers it; if neither thinks it's theirs, the same thing happens.

What the handover should not include

What goes in is just as important as what doesn't. A handover loaded with information that isn't used stops being read.

• Don't repeat the entire conversation history. The person coming in can open it; what they can't reconstruct is what was promised and when it's due.
• Don't include conversations that are already closed. If it was resolved, it's not a handover: it's history.
• Don't mix the handover with the shift's metrics report. They are two different documents and they are read at different times.
• Don't use the handover to record a problem with a colleague. That goes to the appropriate channel, not to the document the other person has to read in order to work.
• Don't write 'see conversation' as the next action. That is exactly the item that forces the person coming in to reconstruct everything.

A well-done handover is read in five minutes and avoids half an hour of reconstruction. That's the whole calculation needed to justify it: if the team has ten open conversations at shift change and each one costs three minutes of reconstruction, the handover saves twenty minutes per shift change, every day.

A minimal template to copy

If the team doesn't have a format, this is the minimum that covers all the checklist items. It's copied and filled in per open conversation.

• Customer or number:
• Status: (waiting on customer / waiting on internal team / waiting on payment / requires decision)
• Next action: (verb + what + when)
• Owner: (person or team)
• Deadline: (time or 'can wait until tomorrow')
• Commitment made: (what was told to the customer, in the words used)
• Minimal context: (one line, only if needed to understand the next action)

At the end of the document, two fixed lines: 'No pending items: yes/no' and 'Handover received: yes/no'. With that, the checklist can be checked off completely without depending on anyone's memory.

Tools like Wando, which suggest replies on WhatsApp and let the team approve them, help reply faster, but they don't replace this document: the suggestion resolves the message, the handover resolves the shift.