A handover where an item cannot quietly go missing HANDOVER

Everything about handover is stacked against the item that matters

It is five minutes at the end of a shift, given by somebody who has been awake for eleven hours to somebody who has been awake for ten minutes. The person handing over is working from memory and wants to go home. The person receiving is orienting and has not yet got a sense of what is normal.

And the item that matters is almost never the dramatic one. The dramatic one gets handed over properly, because it is on everybody's mind. The dangerous one is the small thing that has been passed on four times, that everyone has now stopped hearing, and that is about to become somebody's inquiry. Every public report into a failure of this kind describes the same object: a known issue, mentioned repeatedly, that nobody owned.

So the one thing a notebook cannot do is count

Every item here carries the number of handovers it has survived. An item on its fifth is shown as what it actually is: not a live issue any more, but a thing the organisation has decided not to deal with.

Saying that on the screen is the entire point, because it is the only way it gets dealt with. As long as the item reads the same on its fifth handover as on its first, it can be repeated indefinitely at no cost to anybody. Once the count is visible, repeating it is a decision somebody is seen to be making, and the item either gets an owner and a date or gets closed honestly as accepted.

That is also the number worth looking at across a month. A handover log where several items regularly reach four or five is not telling you about those items; it is telling you the shift has no route for escalating anything, and that is a management finding rather than an operational one.

The rest is ordinary discipline

Items are closed rather than deleted, so the record of what was live when is still there afterwards. That matters when somebody asks, six months later, whether the problem was known: a log that only shows what is open now cannot answer, and an item that was quietly removed looks exactly like an item that was never raised.

Write for the person receiving, not for yourself. “Bay 3 still playing up” means nothing to somebody who was not there when it started. What is wrong, what has been tried, who was told, what happens next and when. If you cannot say what happens next, write that down too: an item with no next step is the one that reaches its fifth handover.

Everything stays in this browser on this device, which means the export is the record and the page is not. Export at the end of each shift and keep it with the rest of the shift's paperwork. Nearby: ONCALL works out who is on, DEBRIEF runs the conversation after the event, CHAIN records custody of anything physical, and CHECKLIST keeps the proof that a routine was actually run.