Shift handover: where the day's truth goes to die.
Every site loses knowledge at 6am and 6pm. This guide covers what a handover has to carry, why it usually doesn't, and what it looks like when the handover lives on the board.
A shift handover is the structured transfer of operational knowledge from the outgoing to the incoming shift. A complete handover records line state, open downtime with what was found and what to watch, carried actions with priorities and deadlines, the schedule position, and the author's name and time — in writing, attached to the assets and boards the incoming shift actually uses.
Why handover is the weakest link
A manufacturing site is a relay race run three times a day. Everything the outgoing shift learned — the bearing that ran hot, the workaround holding line 3 together, the changeover that overran and why — either crosses the handover or it doesn't. When it doesn't, the incoming shift rediscovers it the expensive way: a repeat breakdown, a quality escape, an hour of "what's the story with BS01?"
The cost is invisible in any single handover and enormous in aggregate, because handover losses masquerade as other problems. The repeat failure gets logged as a maintenance issue. The slow start gets logged as a performance issue. Neither log says "the night shift knew this and the information died in the corridor".
What a good handover contains
- Line state: what's running, what's down, what's degraded and being nursed — with the workaround spelled out.
- Open downtime and its story: not just "BS01 down 119 minutes" but what was found, what was swapped, and what to watch. A repair without its watch-items is half a handover.
- Carried actions: the specific things the incoming shift must do, each with a priority and a deadline — "root cause due 14:00", "recheck BS04 seal wear".
- The plan delta: where the schedule stands against plan, and what was traded to get there.
- Who wrote it: a name and a time. Accountability is what separates a record from a rumour.
The three ways handover fails
Verbal folklore. The handover happens in the corridor in four minutes. It works right up until the one day it matters — the incident investigation that finds the critical warning was spoken, not written, to someone who'd already clocked off.
The notebook. A written log exists, but it's one book on one desk. Nothing links it to the asset, so last month's identical failure is invisible; the engineer who needs it on Saturday night has never seen the book.
The re-typed pack. Someone transcribes the shift's events into a handover template at 5:40am. It's slow, it drops detail, and it creates a second version of the truth that never quite matches the historian or the CMMS.
Handover on the board
In Lumen, the handover isn't a separate document — it's carried on the same board the next shift runs the day on. The note travels with its shift ("Night → A"), signed and timestamped, alongside the downtime events it explains. Carried items land as prioritised actions on the work board, so "recheck BS04 seal wear" is an owned task with a due time, not a hope. And because the note lives on the asset's timeline, the third hot-running bearing this year is visible as the third — evidence for the RCPS case, not a fresh surprise.
What should a shift handover include?
Should handover be written, verbal, or both?
How long should a handover take?
Why not just use the CMMS or logbook for handover?
See it on a running site.
Let us show you what Lumen would look like in your facility.