Running a shift handover that actually works
What belongs in a handover, why verbal-only handovers fail, and how to structure one so the next shift starts informed.
A shift handover is the transfer of responsibility and context from one team to the next. Most operational problems that surface mid-shift were knowable at the start of it, and were known by somebody who had gone home.
Why verbal handovers fail
They are not written down, so nothing survives past the person who heard it. They happen while both shifts are busy. And they are compressed to whatever the outgoing person remembers at the moment they are trying to leave.
The result is predictable: safety-critical items get passed on reliably, and the merely important ones: a supplier issue, an intermittent fault, a customer to expect, get dropped exactly as often as the outgoing shift is tired.
What belongs in one
| Category | Examples |
|---|---|
| Outstanding work | Anything started and not finished |
| Faults and workarounds | What is broken, what is being done, the temporary fix in use |
| Stock and supply | Shortages, deliveries expected, substitutions in use |
| People | Absences, cover, anyone new needing support |
| Anything unusual | Incidents, complaints, visits expected |
Attach it to the work, not to a notebook
The most common structure is a notebook by the till or a whiteboard in the back office. Both fail the same way: the note is separated from the thing it concerns, so a month later nobody can connect "the fryer was playing up" to the maintenance history of that fryer.
Recording the handover against the closing routine itself keeps them together. The note about the fryer sits on the record for the shift it happened on, next to the checks performed that night, which is where anyone reviewing it later will look.
Make it the end of the close
Handovers work best as the last step of an opening and closing routine rather than a separate task. It's already happening at the right moment, the person is already in the record, and one more prompt — anything the next shift needs to know?: costs seconds.
Teams that add this consistently report it as the part staff value most, because it's the only item on a closing checklist that makes the next person's job easier rather than documenting the last one.
Common questions
- What should be included in a shift handover?
- Outstanding work, faults and any temporary workarounds in use, stock and delivery issues, people matters such as absence or cover, and anything unusual like an incident or expected visit. Safety-critical items are passed on reliably; the merely important ones are what get dropped, so structure exists mainly to catch those.
- Why do verbal shift handovers fail?
- Nothing survives past the person who heard it, they happen while both shifts are busy, and they are compressed to whatever the outgoing person recalls while trying to leave. A written handover attached to the shift record keeps the context available to anyone reviewing it later, not only to whoever was standing there.
- Where should handover notes be recorded?
- Against the shift's own closing record, not in a separate notebook or whiteboard. Keeping the note with the checks performed that night means a recurring fault can later be connected to the shifts it appeared on, which a detached notebook makes impossible.
More on operations
Run these checks on a schedule
EasyBee turns recurring obligations into dated, attributable records.