How to Write a Shift Handover (With Examples)

A shift handover is only useful if the next shift can act on it without asking follow-up questions. Most handovers fail not because nothing was written down, but because what was written down isn't organized around what the incoming shift actually needs to do.

Why shift handovers fail

• Everything is one long paragraph. Priority alerts get buried next to routine notes, so the incoming shift has to read the whole thing to find what matters.
• Open issues silently drop. An issue mentioned yesterday isn't repeated today, so it quietly falls off the record even though it's still unresolved.
• There's no acknowledgment. The outgoing shift assumes the handover was read; the incoming shift assumes they'll be told if anything was urgent. Neither is guaranteed.
• It's written from memory at the very end. Details get generalized or lost when the handover is reconstructed in the last five minutes of a shift.

The 5 things every shift handover needs

1. Priority alerts — anything that needs attention before routine work, listed first, not buried in paragraph three.
2. Open issues, with an owner and a status — not just "there's an issue with X," but who owns it and where it currently stands.
3. Follow-ups the next shift must complete — specific, assigned actions, not vague context.
4. Low-priority FYI notes — kept separate from anything requiring action, so they don't compete for attention.
5. An acknowledgment — a signature, initials, or an in-app confirmation that the incoming shift actually read it before the outgoing shift leaves.

A simple shift handover example

Notice what this format does not do: it doesn't narrate everything that happened during the shift. It only surfaces what the next shift needs to know and act on.

Common mistakes to avoid

• Writing the handover at the very end instead of updating it as things happen.
• Treating every note as equally important — if everything is flagged, nothing is actually prioritized.
• Letting an open issue disappear from the handover once it's no longer "new" — carry it forward until it's resolved, not until it's old news.
• Accepting a handover was "probably read" instead of confirming it was.

Where a template stops being enough

A written template solves the format problem — it doesn't solve search, carry-forward tracking, or acknowledgment across a whole team over weeks and months. That's the gap structured tools like CrewSignals are built to close: the same fields, kept as a searchable record with acknowledgment tracked automatically.