Shift Handover in Manufacturing: The Checklist That Stops Information Dying at the Gate

Key takeaways

• Most shift handovers fail in the same way: the outgoing shift reports what happened, and the incoming shift needs to know what is still open.
• A handover is a transfer of unfinished business, not a summary. Structure it around open items, not around a narrative of the last eight hours.
• Six fields cover almost every plant: machine state, open faults, temporary measures, quality holds, parts and materials, and the one thing to watch.
• Temporary measures are the highest risk item on the list. A bypassed sensor that nobody hands over becomes a permanent modification by accident.
• Write it down. A verbal handover between two tired people at 06:00 is not a record, and it cannot be reviewed after an incident.

Ask a plant manager where information is lost and you get answers about systems. Ask a technician and you get one answer: at the gate, between shifts, when the person who knows what is going on goes home.

This is a checklist you can use tomorrow, and the reasoning behind each line, because a checklist nobody understands gets filled in without being read.

Why handovers fail

Three failure modes account for most of it.

The narrative problem. People naturally report chronologically: first this happened, then we tried that. The incoming shift does not need the story. They need the state of the plant right now and the list of things that are not finished. Chronology buries the open items in the middle of a paragraph.

The optimism problem. Nobody wants to hand over a mess. "We sorted the labeller" often means the labeller ran for the last forty minutes of the shift. The incoming shift inherits a fix that has not been proven, without knowing it is on probation.

The temporary measure problem. A guard interlock is bridged to finish a batch, a setpoint is raised, a line is run in manual. These decisions are almost always reasonable at the time and almost never written down. Two shifts later, nobody remembers the machine is not in its normal state. This is the item that turns an operational shortcut into a safety and compliance problem, and it belongs on every handover form in a box of its own.

The checklist

Six sections. Aim for a form that a shift leader can complete honestly in five minutes.

1. Machine and line state

• Which lines are running, which are down, which are running with a restriction.
• Current product or format on each line, and what the next changeover is.
• Anything running at reduced speed, and why.

2. Open faults and work in progress

• Every fault that is not closed, with its work order number.
• What has been tried already, so the next shift does not repeat it.
• Who is waiting on whom: a part, a contractor, a decision, a permit.

3. Temporary measures in force

• Any bypass, override, jumper, manual mode or raised limit currently active.
• Who authorised it, when, and what has to happen before it is removed.
• If this section is not empty, it is the first thing the incoming leader reads.

4. Quality and safety

• Product on hold, blocked pallets, deviations raised.
• Incidents, near misses, anything reported to the safety function.
• Open permits and who holds them, including lockout or permit to work that spans the shift boundary.

5. Parts, materials and people

• Parts consumed that took the last one off the shelf.
• Parts ordered, expected, or missing and blocking a repair.
• Absences, contractors on site, anyone working alone.

6. The one thing to watch

• A single sentence. If the incoming shift reads nothing else, this is it.
• Forcing one line does more for attention than three pages of complete information.

What a good entry looks like

Same event, two handovers.

Weak: "Line 3 gave us trouble again with the labeller, we had a few stops, changed the sensor and it seems OK now. Quality came down about the codes."

Strong:

• State: Line 3 running, format 0.5L, reduced to 85 percent speed since 03:10.
• Open: WO 4471 labeller misfeeds. Replaced the label present sensor at 02:40. Ran clean for 90 minutes but was already replaced in June, so treat as unproven.
• Temporary measures: none.
• Quality: 2 pallets on hold from 01:00 to 01:40, code legibility, QA notified, awaiting release.
• Parts: last label sensor used. None on the shelf. Reorder raised.
• Watch: if Line 3 misfeeds again, stop and call engineering rather than swapping the sensor a third time.

The second version takes about the same time to write and answers the questions the incoming shift was going to ask anyway. It also leaves a trail: the sensor has now failed twice, which is the beginning of a root cause analysis rather than a third replacement.

Verbal plus written, not one or the other

The written form carries the facts. The five minute face to face conversation carries the judgement: what felt wrong, what the machine sounded like, which operator noticed it first. Neither replaces the other, and plants that drop the conversation to save time usually find the form degrades into ticked boxes within a month.

Overlap the shifts by ten to fifteen minutes and protect that window. A handover conducted while one person is walking to the car park is a handover in name only.

Making it stick

Three practical rules decide whether the checklist survives contact with a bad night.

Pre fill everything the system already knows. Nobody should type out which work orders are open, or which faults were logged, if that data already exists. When the handover form is generated from the work order list and the downtime reason codes of the last shift, the shift leader writes judgement rather than transcription, and the form gets filled in properly at 05:55.

Make it readable in ninety seconds. Open items at the top, closed items collapsed or omitted. If the incoming leader has to scroll to find what is broken, they will stop reading it.

Review it, occasionally, out loud. Once a week, take one handover and check it against what actually happened next. This is the only mechanism that keeps the optimism problem in check, and it takes ten minutes.

Plants that outgrow paper usually move to a structured digital form for the same three reasons: it can be pre filled, it is searchable when an incident has to be reconstructed, and it cannot be left in a drawer. Our comparison of shift handover software covers the options.

Common mistakes

• Reporting the shift instead of the open items. The incoming team inherits the future, not the past.
• Leaving temporary measures verbal. This is the one that ends up in an incident report.
• Marking a fix as closed when it is unproven. Say how long it has run clean, and let the next shift judge.
• Free text only. Without fields, two shift leaders write two different things, and nothing can be searched or counted later.
• No parts line. The stockout that stops tomorrow's repair was created by yesterday's repair and nobody wrote it down.
• Handover as a formality. If nobody ever acts on it, people stop investing in it, and they are right to.

What good handovers do to your numbers

A repair that stalls because the next shift restarts the diagnosis from zero shows up directly in MTTR, and repeated short stops that nobody connects across shifts are how a real failure pattern stays invisible for months. Handover quality is therefore not a soft topic. It is one of the cheapest available inputs to OEE, and unlike most improvements it costs a form and fifteen minutes of overlap. When the same information also lands in the machine history in your CMMS, the third occurrence of a fault is obvious instead of anecdotal.

Book a demo to see open work orders, faults and machine state on one screen at shift change.

Frequently asked questions

What should a shift handover include?

Machine and line state, open faults with their work order numbers and what has already been tried, any temporary measures such as bypasses or manual modes, quality holds and safety items including open permits, parts consumed or missing, and one sentence naming the thing the next shift must watch.

How long should a shift handover take?

Five minutes to complete the written form and ten to fifteen minutes of overlap for the conversation. If it takes longer, the form is asking for information the system should already supply.

Should shift handover be written or verbal?

Both. The written record carries facts that have to survive and be searchable after an incident. The conversation carries judgement and context that never fits in a field. Plants that keep only one of the two lose either the evidence or the nuance.

Why do temporary measures matter so much in a handover?

Because a bypass or an override changes the state of the machine, and if it is not handed over it becomes invisible. That is how a short term operational decision quietly turns into a permanent condition that nobody assessed, with safety and compliance consequences attached.

Can shift handover be part of a CMMS?

Yes, and it works better there, because the open work orders, logged faults and downtime reasons that make up most of the handover already live in the system. The shift leader then adds judgement rather than retyping data, and the handover becomes part of the machine history instead of a separate document.