Shift handover: transferring control of a running process between crews

A transfer of responsibility, not a friendly update

The outgoing team holds knowledge that exists nowhere else, and the point of handover is to move it, confirm it has been received and understood, and only then release the previous crew. Treating it as an informal conversation between two people leaving and arriving guarantees that what gets passed on is whatever the outgoing person happened to remember at the end of a long shift. Naming the moment when responsibility actually changes matters too: until the handover is complete, the outgoing supervisor still owns the plant, including any decision that has to be made while the briefing is happening.

The items that must cross the boundary every time

A workable list is short and non-negotiable: current state of each process and where it sits against plan; anything running abnormally or on a temporary arrangement; equipment out of service, isolated or under permit, with the permits physically handed over; batches or lots on quality hold; part-finished jobs and what the next crew must do with them; material or tooling shortages coming; expected events such as a delivery, a contractor arriving or a trial; and anything the previous shift failed to complete. Everything else is useful context. These are the items whose omission causes the incident.

Overlap time is the first thing cut and the last thing that should be

A handover done properly needs the two crews present together, which costs paid overlap on every shift change, every day. That cost is visible in the wage bill while the failures it prevents are not, so it gets trimmed the moment labour comes under pressure. Where overlap has been removed, the transfer degrades into a note left on a desk and a phone call. If the overlap genuinely cannot be afforded, the plant has to compensate deliberately — a structured written record completed before the outgoing crew leaves, and a defined read-and-confirm step by the incoming supervisor before they take control.

Written and verbal, in both directions

Written alone loses emphasis and nuance: a log entry saying the compressor is noisy does not convey that the outgoing engineer is worried about it. Verbal alone loses everything the moment either person misremembers, and leaves no record when a question is asked days later. The working combination is a written log completed during the shift rather than at the end, read by the incoming crew, then discussed face to face with the incoming person doing some of the talking — asking questions and summarising back is what proves the message was received rather than merely delivered.

Handovers that cross functions, not just shifts

Shift-to-shift is the obvious case; the neglected ones are just as dangerous. A maintenance job left half complete at the end of a shift needs a formal transfer to the next fitter, including what has been dismantled, what is loose, what is isolated and what has been reassembled. A contractor working across a shift change needs someone to take over supervising them. A quality decision left pending needs a named owner on the next shift rather than a hope that somebody picks it up. Each of these has caused a serious event somewhere because the item fell between two people who each assumed the other had it.

Frequently asked questions

Should handover happen in an office or out at the plant?

Both, in that order. Start with the written log and the structured items somewhere quiet enough to concentrate, then walk the area together for anything abnormal — the machine running oddly, the isolation in place, the batch on hold. Standing in front of the equipment removes the ambiguity a written description carries and lets the incoming crew ask the question they would never have thought of in an office. The walk is the part usually skipped and the part that catches misunderstandings.

How do we manage handover when shifts do not overlap at all?

Compensate with structure. Require the outgoing supervisor to complete the log before leaving, not from memory afterwards; require the incoming supervisor to read it and confirm receipt before taking control; make a phone call mandatory for anything abnormal rather than optional. Then look hard at whether the arrangement is genuinely sustainable on a plant running a hazardous or continuous process, because in that setting the absent overlap is a recognised weakness that inspectors will raise.

What should happen after a crew returns from days off?

Treat it as a longer handover. Someone coming back after a break has missed several shifts of change: a modification completed, a specification revised, a persistent fault, a new person on the team. A short catch-up covering what changed while they were away, delivered before they take up duty, prevents the common failure where an experienced operator confidently does the thing that was correct the previous week. The same applies after extended absence, holiday cover and any temporary reassignment.