The Shift Handover: The Five-Minute Ritual and the Note

Thursday, 14:55, at Harbourview Clinic. Ben is putting his jacket on. The desk runs two shifts, 07:00 to 15:00 and 11:00 to 19:00. So for four hours a day there are two people in. Aisha has been in since eleven with a queue of her own. "Anything I need to know?" she asks. "Nothing much. It's all in the queue." At 16:10 the pharmacist phones to ask why nobody called her back at half past three. Aisha finds the ticket. Status Open, owner Ben, last internal note at 13:40: "will call back after the sync runs". The sync ran at 15:15. Ben was on the bus.

A shift handover is the handoff that happens along the clock: the moment one person's responsibility for the live queue ends and another's begins. Every desk with more than one person's working hours in it has one. A desk with one shift has one too, between today and tomorrow, with a night in the middle. "It's all in the queue" is the sentence most handovers consist of, and it is true. It is not a handover, because the queue holds tickets and a handover carries promises. This article is part of our Handoffs & Coverage Transitions series, and it is about the five minutes that turn the one into the other.

It covers why the queue is not the handover, and the four things a handover has to carry. Then come the handover note, where it lives and what goes in it, and the five-minute ritual, in order. It covers the open-items list that the ritual walks through, and the handover when the shifts do not overlap. Next are the handover when the next person is not in yet, and the end-of-day handover on a single-shift desk. It ends with a short war story and the handover note to copy, in that order.

"It's All in the Queue" Is Not a Handover

The queue is a list of tickets, and a handover is a transfer of obligations, and the two overlap less than they look. Everything Ben owned was in the queue, with a status, a priority and a last-update time, and Aisha could have read all of it. What she could not have read was that Ben had told the pharmacist "half past three". That sentence was said on the phone and written nowhere. The note that came closest, "will call back after the sync runs", had no time in it. It was true for the rest of the afternoon and most of the next day.

The queue is also sorted for the wrong question. A queue sorted by priority or age answers "what should the desk work on", which is the right question at 09:00 and the wrong one at 15:00. The question at a shift change is "what did the last person set in motion that will fall over without them". No standard sort answers it, because the tool does not know which tickets have a promise attached. It knows which have a due date, if your tool has due dates and your desk fills them in, and that is not the same list.

So the handover exists to carry the things the queue cannot. It is a small, deliberate act, five minutes at a fixed time. The only reason desks skip it is that the queue looks complete. It is complete. It is just not the handover. (A filing cabinet is complete too, and nobody has ever been briefed by one.)

What a Handover Has to Carry

A handover carries four things, and a handover that carries all four leaves no gap. The first is promises: anything the outgoing person told a requester would happen by a time, whether or not the ticket records it. "I'll call you back at 15:30." "Someone will be down before the end of the day." "You'll have the account by tomorrow morning." These are the items a shift change drops, and they are the ones with a person watching the clock on the other end.

The second is in flight: anything the outgoing person started that is part-way through and needs a hand on it. A script running that will need checking at 16:00. A restart that was agreed with the finance team for 17:30. A part that the courier will deliver to reception this afternoon and that someone must sign for. In flight is not the same as open; a desk has fifty open tickets and three in flight, and the three are the handover.

The third is watch: anything that is fine now and may not stay fine. The file server that threw a disk warning at lunch and cleared. The user who has phoned twice and been polite both times. The directory sync that ran late yesterday. Nothing is owed on these yet, but the incoming person should know where to look first if the afternoon goes wrong. "I had a feeling about that server" is only useful before the fact.

The fourth is outside the queue: facts the next person needs that are not in any ticket. The engineer who is coming for the lift at four and will need the comms-room key. The managing director's visitor who will want the guest wireless. The printer on the second floor that has been fixed, and the sign on it that says it has not. Every desk has three or four of these a day. They are the things the incoming person is asked about at 15:20 and cannot answer.

What Goes in the Handover Note

The handover note is the four things written down, by the outgoing person, before they leave, in a place the incoming person reads first. Written, not spoken. Spoken handovers are a conversation, and conversations are remembered in proportion to how interesting they were, which for a handover is not very. The note is the record. The conversation, if there is one, is a walk through the note.

Where it lives matters more than what it is written in. The note needs a fixed home that the incoming person opens without being told to, the same place every day. Most desks use one of three. One is a standing ticket in the tool called "Handover", with each day's note added as an internal note. Another is a pinned message in the team's chat channel, replaced daily. Or it is a page in the knowledge base, overwritten each shift. Any of the three works. A note in the outgoing person's personal inbox, or on a sticky note on the monitor, does not. The first is unreadable by anyone else. The second is unreadable by anyone after the cleaner has been.

Keep it short and keep it structured. Four headings, the four things, and under each one a line per item: ticket number, what, by when, who was told. Three lines is a good note on a quiet day. A note that runs to a page is a note that has been padded with the queue. The incoming person will stop reading it by Thursday. Write for a reader who was not there and has thirty seconds. The table below shows what belongs under each heading and what a usable line looks like.

Leave the queue itself out of the note. The incoming person can read the queue; what they cannot read is the note. A note that lists every open ticket has buried the four lines that matter under forty that do not. If a ticket is open and nothing has been promised, started, or worried about, it is not in the note. That is not neglect. That is the note doing its job.

The Five-Minute Ritual

The ritual is the note read aloud, by the outgoing person to the incoming one, at the same time every day, standing up. Standing up is not a joke. A handover done sitting at a desk becomes a conversation. A conversation becomes a chat about the pharmacist, and the chat ends when a phone rings. Five minutes standing by the incoming person's screen, in the order of the headings, and then the outgoing person leaves. The length is the point. A handover that takes twenty minutes is a handover that is being padded with things the queue already says.

The order is promises first, because they have clocks on them; in flight second, because something is moving; watch third; outside the queue last. For each line the outgoing person says what it is and what they would do next. The incoming person says it back in their own words. "So Sunita at 15:30, with the sync result, and if the sync fails I tell her that and give her tomorrow 09:00." That sentence is the handover. Until it has been said, the ticket is still Ben's, jacket or no jacket.

Make the time fixed, and make it earlier than the shift end. Ben leaves at 15:00; the handover is at 14:45. A handover at the shift boundary is done in a coat and skipped on the first busy day. A ritual that is skipped on busy days is a ritual for quiet days, which is when it is least needed. Hold it fifteen minutes before the end, every day, including the days when the note says "nothing promised, nothing in flight". Those are the days the incoming person learns to trust it.

Both people carry the open-items list to the ritual. The incoming person asks one question at the end that is not on the note: "Anything you said to anyone that isn't written down?" The answer is usually "no". About once a week it is "oh, I did tell the warehouse I'd ring them", and that one is the reason the question exists.

The Open-Items List

The open-items list is the view the ritual walks through: the outgoing person's active tickets, sorted so that the ones with a promise on them come first. It is not the whole queue. It is one person's tickets, excluding anything waiting on somebody else with a date in the future. That leaves the handful that the next few hours could change. Most tools can produce it with two filters, owner and status, and a sort. The difficulty is the sort, because the thing you want to sort by is "promised time", and most tools have no such field.

Where the tool has a due-date or follow-up field, use it for the promise, every time a promise is made, and sort by it. Where it does not, the convention that works in any tool is a prefix on the first line of an internal note: "PROMISED 15:30 callback to Sunita re sync". The prefix is searchable. It is visible in the ticket list in most tools that show the last note, and it survives the ticket changing hands. Writing it is a habit of about ten seconds, formed in about two weeks. It is the single change on this page that pays back fastest. The promise moves from the technician's head to the ticket, where the next person can see it.

Check one thing before you rely on internal notes for any of this: that the requester cannot see them. Most tools separate internal notes from replies and show only replies to the requester; some show both in the portal; a few send everything. Test with a ticket raised from a personal address and read what arrives. Until you have, write every internal note as though the requester will read it, which is a good habit anyway and a surprising one to need.

The list belongs to the person, but the lead reads all of them. Once a day, usually at the second handover, the lead scans every open-items list for promises that fall due after the person who made them has gone home. Those are the items the next section is about. They are easier to find at 14:45 than at 16:10 with the pharmacist on the line.

When the Shifts Do Not Overlap

Many desks have no overlap at all. The early person leaves at 15:00 and the late person started at 15:00, or there is a gap of an hour with nobody in. The ritual then has no two people in the room, and the note has to do the whole job. It can, if two things are true. It must be written in the fixed place before the outgoing person leaves. And reading it must be the incoming person's first act, before the queue, before e-mail, before the phone that is already ringing.

Make the first act visible. The incoming person adds one line under the note, "Read 15:05, taking all four, Sunita first". That line is the confirmation that closes the handoff. Without it, the outgoing person has no way of knowing whether the note was read. The incoming person then has no moment at which the obligations became theirs. With it, the handover is a written exchange with a timestamp. For a desk that cannot be in the same room at the same time, that is the best available version of standing up.

If the gap is long, an hour or more, the note gets one extra heading: "Falls due in the gap". Anything promised for a time when nobody is in goes there. The outgoing person deals with it before leaving by one of the three means in the next section. A promise that falls due in an empty room has already been broken, and the only question is who tells the requester.

When the Next Person Is Not In Yet

Some promises fall due before anyone is in to keep them. The callback at 17:30 when the desk closes at 17:00. The "first thing tomorrow" when the first thing tomorrow is a 08:00 start and the person who promised it is off on Fridays. The Friday afternoon "by Monday" that nobody on Monday has heard of. These are the handover's hardest items, because the handoff is not to a person but to a gap. A gap does not say things back in its own words.

There are three honest things the outgoing person can do, and they should pick one before they leave. Do it now: the callback at 17:30 becomes a callback at 14:50 with what is known so far, and a new, kept promise for tomorrow. Re-promise: send a reply to the requester, in the ticket, that moves the time to one somebody will be in for. For example, the reply can say "I said 17:30 and I will not be here; Aisha will ring you by 09:30 tomorrow". Obtain Aisha's agreement first. Or hand it to the team: the ticket goes to the team queue, unassigned, with a note that starts "PROMISED 09:30 callback". The first person in tomorrow then owns the team queue's promises as part of opening the desk. The one thing not to do is leave it assigned to yourself with the time intact. That ticket will be read at 16:10 by someone with the requester on the phone.

The first person in each morning has a job, then, and it needs to be written down. Open the team queue, open the handover note, and work anything marked promised before touching anything else. On most desks this takes ten minutes and most days it finds nothing. On the days it finds something, it finds it before the requester does. That is the entire difference between a desk that keeps its promises and a desk that keeps most of them.

The End-of-Day Handover to Tomorrow

A single-shift desk hands over to itself, and the handover is the same note with a night in it. At 17:15 the person going home writes the four headings for whoever opens the desk tomorrow, which is often them. In the morning they read it as though a stranger wrote it. The stranger did. The person who arrives at 08:00 remembers Thursday's promises as a general warmth and not as a list. The list is what the pharmacist is expecting.

On a one-person desk the note is also the only handover that can ever happen on unplanned absence. If the one person is ill tomorrow, the manager who opens the desk in their place has exactly one source for what was promised. It is the note, if there is one. Three lines at 17:15, in a place the manager knows about, makes the difference when the manager phones three requesters. One version is "sorry, I don't know what you were told". The other is "you were told 09:30 and I am ringing to say it will be Thursday". The solo desk has other defences against the empty chair, and they are in Documentation as Your Second Person. The handover note is the cheapest of them and the first to write.

The note at the end of the day is also where the promise interval gets kept honest. If a desk's rule is that every waiting ticket gets a follow-up within two working days, the follow-ups that fall due tomorrow are tomorrow's promises. The note is where those promises are listed. The cadence itself, how often to chase and what to say, belongs to Follow-Up Cadences That Keep Tickets Moving. The handover is where the cadence survives the night.

A Short War Story: The Scanner Gateway at Bellweather Logistics

Bellweather Logistics ran a two-shift desk for a warehouse that worked around the clock. One Tuesday the day-shift technician, Rosa, told the night shift manager that the scanner gateway on dock three would be restarted. The time was "after the last outbound wave, about 22:00". She then went home at 18:00 with the ticket assigned to herself and the time written nowhere but in her memory. The night technician, Kwame, read the queue, saw an open ticket about a gateway, saw no promise, and worked the queue in priority order. At 22:00 the dock three team stopped scanning and waited, as they had been told to. At 23:10 the shift manager phoned the desk. At 23:40 the gateway was restarted. By then, two outbound trailers had missed their slots and a customer's penalty clause had been invoked for the first time that year. Rosa had done the work and made the promise, and both were good. What she had not done was hand them over. Bellweather started a 17:45 standing handover the following week with a four-heading note in a pinned message. The night shift's first act became reading it. A promise that leaves the building with the person who made it is not a promise the desk made. It is a promise the desk will break.

The Handover Note

The note below is the four headings on one page, with the confirmation line for desks whose shifts do not overlap. It also has the "falls due in the gap" section for desks with an empty hour. Copy it into whatever fixed place your desk chooses, fill in only the lines that apply, and leave the rest blank. A blank heading is information: it tells the incoming person that nothing was promised, and that is worth knowing.

SHIFT HANDOVER — ONE PAGE
Desk: ______________   From: ____________   To: ____________   Written at: ____:____

PROMISED (anything a requester was told to expect, with a time)
  [ ] #______  ______________________  told ____________  by ____:____
  [ ] #______  ______________________  told ____________  by ____:____
  [ ] #______  ______________________  told ____________  by ____:____

IN FLIGHT (started, part-way through, needs a hand)
  [ ] #______  ______________________  next step: ______________  at ____:____
  [ ] #______  ______________________  next step: ______________  at ____:____

WATCH (fine now, may not stay fine; where to look first)
  [ ] ______________________________  look at: ______________________
  [ ] ______________________________  look at: ______________________

OUTSIDE THE QUEUE (facts no ticket records)
  [ ] ______________________________________________________________
  [ ] ______________________________________________________________

FALLS DUE IN THE GAP (nobody in when it is due)
  [ ] #______  due ____:____   dealt with by:  [ ] done now  [ ] re-promised to ____:____  [ ] team queue

Anything said to anyone that is not written above?   [ ] no   [ ] yes: ______________

CONFIRMATION (incoming person)
  Read at ____:____ by ____________   Taking all items: [ ]   First action: ______________

The confirmation line is the one most desks leave off and the one that makes the sheet a handover rather than a diary. Until the incoming person has written their name under it, the outgoing person still owns everything above it. The clearest sign of a handover that has gone wrong is a week of notes with the top half filled in and the bottom line blank. The wider picture, of which the shift end is one of five moments where tickets stop, is in Where Tickets Fall Between the Cracks. The shift end is the narrowest of the five and the one that recurs every single day, which is why it is worth five minutes.

Aisha rang the pharmacist at 16:15 with the sync result and an apology, and the pharmacist was fine about it, because people mostly are. The following Monday the desk started a 14:45 handover, standing, with the four headings in a pinned message. Ben's first note had one line under Promised and nothing else. Aisha read it back to him in her own words, and he put his jacket on. It took ninety seconds. The pharmacist has not needed to phone since.

Frequently Asked Questions