The shift handover note that stops things being dropped

Where work actually gets lost

Not in the middle of a shift. At the seam between two of them. Someone was halfway through chasing a carrier, the shift ended, and the next person had no idea it was in flight. The customer finds out first.

Verbal handovers fail because the outgoing person is tired and the incoming person is not yet oriented. Written handovers fail when there is no format, because then they are a paragraph and the important line is in the middle of it.

The five lines

Same order, every time. The order matters more than the wording: consistency is what lets someone scan it in twenty seconds.

1. What changed. Anything that is different from the last time this person worked. New promo live, a product pulled, a courier issue.
2. What is outstanding. Things in flight with your name on them. Include the state, not just the topic: “chased DPD about #1042, waiting on a reply, ref 88213”.
3. What to watch. Things that are fine now and might not stay fine. Stock getting thin, a customer who is getting impatient.
4. Who is on next. Names and times, so nobody guesses.
5. What I would do first. The single highest-value opinion in the note. It transfers judgement, not just facts.

Copy this

HANDOVER - [date] [shift]

CHANGED:
OUTSTANDING:
WATCH:
NEXT ON:
DO FIRST:

Empty headings are deliberate. A blank line under OUTSTANDING is information: it says nothing is in flight, which is different from having forgotten to mention it.

Three rules that keep it working

• Post it in the room, not in a DM. The next person might not be who you expect.
• Write it before you are finished, not after. Ten minutes before the end, while you still remember the detail.
• Anything under OUTSTANDING gets an owner. A handover that lists work without assigning it just moves the ambiguity along.

A good handover is not a summary of your shift. It is a briefing for the next one.

If your outstanding items are already tasks with a name and a due time, this note gets much shorter, because the work is tracked rather than described. That is the argument in turning messages into tasks.

The five lines

Same order every time. The order matters as much as the content, because a note read in ninety seconds is scanned rather than read, and scanning depends on knowing where to look.

1. Anything on fire. Problems live and unresolved right now. Usually empty, and it goes first precisely so that an empty line is instantly visible.

2. Waiting on someone. Things that are stalled pending a customer, a supplier or a courier. This is the line most often missing and the one that causes the most silent delay, because nothing prompts you about something you are waiting for.

3. Unfinished, with owners. What did not get done and who picks it up. Unfinished work with no name is dropped work with a delay.

4. Different about today or tomorrow. A promotion starting, a collection time moved, someone in late, a delivery expected.

5. Anything odd. The catch-all. A product that keeps coming back, a customer who has emailed three times, a bin emptier than the system says. Not yet a problem, and the line where problems get caught early.

Why written beats spoken

Verbal handovers feel faster and lose most of their content within the hour.

They depend on both people overlapping, which shift patterns often prevent. They cannot be checked later, so a disagreement about what was said is unresolvable. And they encode nothing: the same problem recurring three weeks running is invisible when each handover exists only in someone's memory.

Written notes take slightly longer and produce a record that can be searched, which is what turns a handover from a courtesy into an operational asset.

Keeping it to ninety seconds

Handover notes die from growing. Three rules keep them short.

Only what the next person needs. Not a shift diary. If it does not change what they do, leave it out.

Empty lines stay. Write the heading with nothing under it rather than deleting it. An explicit "nothing on fire" is information; a missing line is ambiguous between nothing to report and nobody checked.

No prose. Fragments are fine. This is a checklist, not a report, and treating it as writing is what makes people avoid it.

Where it should live

Somewhere both shifts already look, which in practice means the tool the team uses rather than a notebook by the till or a document nobody has bookmarked.

A paper notebook works until someone is off-site, and it cannot be searched. A note posted where the team already talks is visible to whoever arrives next without them needing to remember it exists, and it accumulates into a record you can look back through when trying to work out when something started going wrong.

If it fits your setup, having items from the note become tasks with owners closes the loop, so that unfinished work does not depend on the next person remembering to re-read line three.

Reading the note, not just writing it

Handovers fail on the receiving end at least as often as the sending end. A note written carefully and skimmed carelessly has achieved nothing.

Two habits fix most of it. Read it before starting anything, not twenty minutes in when you have already begun something else. And respond to it, even with a single word, so the person who wrote it knows it landed. Without acknowledgement, writers gradually stop putting effort in, because it feels like posting into a void.

If something in the note is unclear, ask while the previous shift is still reachable. The window for that is short, and a question asked at handover costs a minute where the same question asked the next day costs considerably more.

Using the notes as a record

The individual note serves tomorrow. The accumulated notes serve the quarter, and this is the part most teams never use.

Read back through a month of them and the patterns are obvious in a way they never are day to day. The same product appearing under "anything odd" four times. A courier collection that has been late repeatedly. A question that keeps arriving because nothing is documented.

None of those are visible in any single handover. Fifteen minutes reading a month of them is one of the cheapest diagnostic exercises available to a small team, and it is only possible if the notes are written down somewhere searchable.

Adapting it to your store

Five lines is a starting point rather than a specification. Two adjustments are common.

Stores with a physical location often add a line for anything about the premises: a delivery expected, something broken, a key held by someone unusual. Stores that are entirely online rarely need it.

Teams with high seasonal turnover sometimes add a line for anything a new person got wrong, which sounds harsh and is not: it surfaces training gaps within days rather than at the end of the season, when the same gap has been repeated fifty times.

What should not change is the order or the length. Both are what make the note scannable rather than something people skip.

Starting the habit

Handover notes fail at introduction more often than in use, usually because they are announced as a new requirement and nobody writes the first one.

Write it yourself for a week. Not as a demonstration, just do it. People copy what they see far more reliably than they follow what they are asked, and a week of examples establishes the format better than any explanation.

Then hand it over by asking rather than instructing: "can you do the handover tonight?" A single specific request is easier to accept than a standing policy, and once someone has written two or three it stops being a thing they have to remember.

Why this one is worth the effort

Of everything a small store can standardise, the handover note has the best return, because it targets the exact moment when information is most likely to be lost and least likely to be recoverable.

Ninety seconds, five lines, at the point where one shift's knowledge would otherwise walk out of the door.

Common questions