The customer said he would come back at 5pm for his pickup. The supplier was supposed to call back about the replacement. The card terminal drops the line now and then and needs restarting in that one weird way. The morning person knows all this. The person starting at 2pm does not. And between the two there was a handover dispatched with retail's most dangerous phrase: "all good".
It is not bad faith. It is that the morning, while you are living it, feels self-evident. Only at 5pm, when the customer shows up and nobody knows anything, does the morning's information reveal its value.
The tomorrow-colleague rule
There is exactly one criterion for deciding what to write down, and it always works: if a brand-new person took my place tomorrow, what would they need to know about today to avoid embarrassment? Not everything: the three or four items whose tail stretches beyond my shift. Commitments made to customers, open questions with suppliers, technical quirks, things started and left half done.
Whoever asks themselves that question at the end of a shift almost always writes the right lines. Whoever asks "what happened today?" writes a diary, which helps nobody.
Written beats spoken, one place beats three
The spoken handover has a structural flaw: it only works if the two people actually cross paths, and it evaporates as soon as it is said. The robust version is written, in one place, always the same one. Which place matters less than its uniqueness: the notebook at the counter, a shared note, the tool you use for shifts. Disaster starts when handover notes live in three places (some in the chat, some in the notebook, some spoken) and everyone checks the wrong one.
A written note has one extra virtue nobody ever mentions: it protects whoever left it. "I wrote it down at 1:40pm" kills at birth every argument about who was supposed to tell what to whom.
The five minutes worth an hour
Where schedules allow it, a five-to-ten-minute overlap between the person leaving and the person arriving is the best cost-benefit investment of the entire week: enough time for one lap of the floor together, two questions, and the new shift starts warm instead of cold. But overlap does not happen by itself: either the rota provides for it, or it does not exist. A plan built on perfectly abutting changeovers (2:00pm out, 2:00pm in) is de facto declaring that handovers are not part of the job.
The person arriving has a duty to read
Last piece, often forgotten: the handover only works if reading it is the arriving person's first act, before taking their coat off. It sounds trivial, but if reading the notes is not as sacred a habit as writing them, the system dies within two weeks of mutual distrust: "nobody reads them anyway".
One single place where the team sees shifts, notes and changes is half the work of a good handover: Sked Solve is built around that idea, and you can see it on the site.