Ask a plant manager where the day loses the most money and you'll usually get an answer about machines. Ask him where the day loses the most *time* and it's a different answer: the first forty minutes of every shift, spent working out what the last shift left behind.
What actually goes wrong at handover
Handover failures look technical and are almost never technical. The incoming supervisor doesn't lack skill — he lacks a specific piece of information that the outgoing one had and didn't pass on, usually because it didn't seem important at 2 PM and nobody was collecting it.
| What wasn't passed on | What happens next shift | Cost |
|---|---|---|
| Batch 3 was stopped for a quality check, not finished | Packing starts on unchecked stock | Rework, or a customer complaint |
| The vendor promised the replacement blade by 2 PM and didn't deliver | Nobody chases; the machine stays down | Half a shift of a line |
| Operator raised a bearing noise verbally | It gets worse for two more shifts | An unplanned stoppage |
| A rush order was verbally re-prioritised by the owner | The original sequence runs | A missed dispatch, an angry client |
Every row has the same structure. Somebody knew. It was said out loud, or typed in a group, and then it evaporated at the boundary between two shifts.
Why the two usual systems don't catch it
Almost every plant has one of two handover systems, and both have a specific blind spot rather than being simply bad.
The verbal handover is fast, rich and adaptive — a good supervisor conveys a lot in ninety seconds. Its blind spot is that it's lossy and unverifiable: whatever wasn't said is gone, and nobody can tell later whether it was said or just remembered as having been said. It also degrades exactly when it matters most, because the shifts that most need a careful handover are the chaotic ones where there's no time for one.
The paper log or register fixes the memory problem and introduces a subtler one: it records *what happened*, in the past tense. Production numbers, downtime, quantities. The incoming shift doesn't primarily need to know what happened — it needs to know what is still owed, by whom, and by when. That's a different question, and the log format doesn't have a column for it.
The log tells the next shift what the last shift did. It almost never tells them what the last shift promised.
The four questions
Strip a handover back to what genuinely has to cross the boundary and it's four questions. Not a form — four questions, which can be answered in a conversation.
- What's mid-run? Which jobs are partly done, at what stage, and is anything stopped rather than finished?
- What's waiting on somebody? A vendor, maintenance, QC, the office. Who, for what, and by when were they meant to deliver?
- What broke or is behaving oddly? Including the soft signals — a noise, a vibration, a temperature that isn't wrong yet.
- What did we promise? To the owner, to a client, to the next shift. This is the one that's almost never written down and the one that most often bites.
Question four is the interesting one. It's the only one that is naturally already in your chat — because promises get made in conversation throughout the shift, not at the end of it.
Capture during, not at the end
The structural reason handover documents fail is that they're written at the end of a shift, by someone who has just worked eight or twelve hours and wants to go home. Quality is worst exactly when the shift was hardest — which is when the handover matters most. It's the same trap as the end-of-day summary message: it works on quiet days and fails on the days it was built for.
The fix is to stop treating capture as a step at all. The commitments were already made, out loud, in the group, spread across the shift: “cutting done by 3:30”, “blade aa raha hai 2 baje”, “batch 3 QC ke baad pack karenge”. If those are being read as they're said, then at 6 PM the handover isn't a document anyone has to write. It's a list that already exists.
A version you can run from Monday
Independent of any software, this is worth doing and takes a week. Keep whatever log you already have — add nothing to it — and simply do this at each changeover:
- Outgoing supervisor names, out loud, the open commitments: anything promised that hasn't happened yet, including what's owed by vendors and other departments.
- Incoming supervisor repeats them back. Not a formality — this is where the mishearings surface.
- Anything neither can answer gets written in the group, so the question is visible rather than forgotten.
- At the end of the week, count the handover-related problems and compare against the week before.
Most plants find the number drops noticeably just from naming the open items deliberately. That's a useful result on its own — and it also tells you exactly how much value there is in never having to remember them by hand.
Written by Team Scoop, Founding team, Scoop. General guidance on running a team, not professional or legal advice for a specific situation.