Shift Handover Done Right: Process, Checklist & Pitfalls
Every shift change is a controlled handover of an operation between two people who will barely overlap — and investigations across healthcare, aviation and heavy industry keep reaching the same finding: things go wrong at the seams. The handover is where a 24/7 operation is most fragile, and the fix is process, not heroics.
What a real handover transfers
Not 'how it went' — the state of the system: what is currently abnormal, what is in progress and who owns it, what is likely to happen next, and what the incoming shift must do first. The outgoing shift holds context that exists nowhere else; the handover's job is to move it across the boundary before it walks out the door.
The structure that works
Written + verbal + walked. A written log the incoming shift can re-read at 3am (structured fields beat free text; SBAR — Situation, Background, Assessment, Recommendation — is the healthcare standard worth stealing). A verbal briefing for the questions a form can't anticipate. And for physical operations, a walk of the floor — the anomaly you point at is the anomaly that gets owned. All three need paid, scheduled time: that's the case for overlapping shifts, and 15-30 structured minutes is cheap against one cross-shift incident.
The classic failure modes
The hallway handover (interrupted, unrecorded); the asymmetric handover (outgoing exhausted and minimising — end-of-block fatigue is exactly when detail drops); the assumed handover ('nothing happened' meaning 'nothing I remember'); and the broken-chain weekend, where Friday's context dies before Monday. Structure defeats all four: mandatory fields force the 'nothing happened' shift to assert specifics, and the log preserves the chain across gaps.
A checklist worth copying
| 1. Safety & abnormal states | Anything not normal right now — alarms, workarounds, isolation, patients/situations of concern |
|---|---|
| 2. Open work | In-progress tasks, owner, expected completion, what done looks like |
| 3. Coming up | Expected events this shift: deliveries, discharges, maintenance windows, weather |
| 4. People | Who's on, who's absent, cover arrangements, relief in place |
| 5. First actions | The incoming shift's first 60 minutes, agreed explicitly |
Build this schedule in Tommy
Set the rotation once and Tommy fills the weeks ahead — shift swaps, leave and coverage gaps handled in one place, with your team always seeing the latest version.



