The Handover Note Before You Log Off

Subject: Handover — Support Desk — Tue 21 July, EU shift Overall: 🟢 Quiet shift, one open item Done on my shift: - Cleared the overnight queue (18 tickets); nothing escalated - Shipped the pricing-page fix; monitoring looks clean Open / needs you: - Ticket #4412 (Meridian Bank) — customer waiting on a refund decision. Finance replies around 09:00 your time; please chase if nothing by 11:00. Context you may need: - The billing API was flaky between 02:00 and 03:00 UTC. If reports spike this morning, that is the likely cause. Pinged: @dan (finance), @lena (on call)

That is the whole note, and it should take you six minutes to write. A handover is not a diary of your shift; it is a set of instructions for the next person, written by someone who will be asleep when they need it. Keep the same five headings every day. When the shape never changes, your colleague can find the one line that matters without reading the rest.

Open with a one-line verdict. "Quiet shift, one open item" tells the incoming person how alert to be before they read a single detail. If things are on fire, say so in the first six words, not in paragraph three. A colleague who reads a green light and then discovers a live incident will never fully trust your notes again.

Under "Done on my shift", write only what changes the next person's decisions. Nobody needs your ticket count for its own sake, but they do need to know that the queue is empty and nothing was escalated. Skip the routine, name the exceptions. A good test: if a line would not change what your colleague does next, delete it.

The "Open / needs you" section is the one that earns your reputation. For every open item, give four things: what it is, who is waiting, what happens next, and when to chase. "Ticket #4412 — customer waiting on a refund decision; finance replies around 09:00; chase if nothing by 11:00" leaves no room for a shrug.

Add context only where it saves someone a search. The flaky billing API between 02:00 and 03:00 is worth a line, because it explains reports that would otherwise look like a brand-new bug. This is the difference between a handover and a log: you are not recording history, you are pre-answering the questions your colleague is about to ask.

Two small habits prevent most handover accidents. Write times with a zone — 02:00 UTC, not "early this morning" — because "this morning" means three different things across a follow-the-sun team. And name people, not roles: @dan is reachable, "finance" is not. Ping them in the thread so the next person can chase without hunting for a contact.

Finally, post it in the shared channel, not in a direct message, and post it before you log off rather than the next morning. A handover that lives in someone's inbox helps one person; a handover in the channel helps whoever actually picks up the shift. Do this for a month and the phrase "sorry, nobody handed that to me" quietly disappears from your team.