A shift handover report template for manufacturing teams
The riskiest five minutes of the day is the shift change. The outgoing crew is tired and already thinking about the drive home, the incoming crew walks in cold, and the handover is a quick word by the time clock — "press 2 was acting up, oh and we're low on the blue stock." Half of it is forgotten by the time the new shift reaches the floor. The die change that was due, the line running at reduced speed, the quality hold nobody closed — they fall through the gap between shifts and become the next shift's surprise. A written handover report closes that gap. This guide gives you a one-page template you can copy today, a worked example from a stamping line, and a way to make the open items carry themselves across shifts instead of living in one person's memory.
Why shift handovers fail
A verbal handover fails for the same reason shouting across the floor fails: it depends on one person remembering everything that matters and another person retaining it, at the worst possible moment of the day. Watch a real shift change and you see the same failure modes every time.
All three are the same root cause: the handover is treated as a separate task bolted onto the end of a shift, done from memory, under time pressure. A template fixes the memory problem. Structured data fixes the pattern problem. You want both.
- The outgoing shift under-reports. They mention the dramatic failure and forget the slow leak — the line that has quietly run 10% under rate all afternoon, the sensor that faults every hour and gets cleared each time. Those don't feel like news, so they never get passed on.
- The open items have no owner. "Maintenance is looking at it" is not a handover. Is it still open? Who on the next shift follows up? Without a name and a next step, an open problem becomes nobody's problem the moment the person who knew about it clocks out.
- Nothing is written down, so nothing compounds. The same jam, the same material substitution, the same overdue PM shows up shift after shift, and because each handover is a conversation and not a record, no one ever sees that it is a pattern.
What a good handover report captures
A handover report is not a shift summary for management. It is a to-do list and a warning list for the person taking over the floor. It should answer four questions in under a minute of reading: What is broken or degraded right now? What is still open and who owns it? What is the next shift's priority? And is there anything about to bite — a material about to run out, a PM coming due, a customer order with a deadline?
Keep it to one page. A handover report that takes fifteen minutes to write at the end of a shift will be skipped on the busy days, which are exactly the days it matters most. The goal is a form that the outgoing lead can fill in three minutes because most of it is already captured as the shift ran.
The shift handover report template
Copy this into a shared doc, a printed form by the time clock, or a tablet on the floor. Fill it from the top as the shift ends, and read it top to bottom at the start of the next one.
Two rules make it work. First, pull the facts from your logs, not your memory — the downtime and open-issue rows should come straight off whatever you already use to track stops, so the handover is a read-out, not a reconstruction. Second, the incoming lead acknowledges in writing. An unread handover is the same as no handover, and the initials line is what turns "I told them" into "they confirmed they know."
A worked example: day-to-second-shift handover on a stamping line
Here is the template filled in for a typical shift change. A stamping shop runs Press 2, a 400-ton press line, on two 8-hour shifts with a target of 9,600 parts per shift, one part per hit. The day lead hands over to second shift at 2:30 p.m.
Now trace the cost of not writing this down. If the second-shift lead walks in blind, the Press 2 feed roller does not get replaced early; it fails outright around 7 p.m. and takes the line down hard for 40 minutes mid-shift. The staged blue coil runs out at 4:30 because nobody loaded it, costing another 25 minutes. And die D-218 blows past its 500k PM interval unnoticed, risking a cracked part and a scrap batch.
That is about 65 minutes of unplanned downtime on a line that was already behind, plus a quality risk. A written handover does not make all of it vanish: replacing the roller and loading the coil still take time. It turns two surprise stops into short planned ones at a moment the lead chooses, and that is the difference a three-minute form buys.
How to run the two-minute handover
The form is only half of it. The handoff itself should be a short, standing conversation with the report open between you, not a form left on a desk. The outgoing lead reads the open downtime and the next-shift priority out loud, the incoming lead asks their one or two questions, and they initial the acknowledged line. Two minutes, face to face, every shift change.
Tie the handover to your daily data and it gets sharper still. If you already run a start-of-shift huddle on real numbers — the longest stops, the recurring reason codes, what is still open — the handover report is just the bridge between last shift's data and this shift's plan. For the reporting layout that feeds both, see a production downtime report example.
Common mistakes that make a handover report useless
- Writing a diary instead of a to-do list. "Busy shift, ran three jobs" tells the next lead nothing. They need what is open, what is at risk, and what to do first — not a narrative of the day.
- Leaving owners and next steps blank. "Press 2 is down" with no owner and no next step just transfers a problem without transferring responsibility. Every open item needs a name and a next action.
- No link back to the data. If the handover lives only on paper, the same recurring item gets re-reported every shift and never becomes a tracked pattern. The handover should point at your log, not replace it.
Where HelpFab fits
The hardest rows to fill are open downtime and open issues, because memory is where things get dropped. Downtime tracking fills them as a by-product. When operators log every stop with a tap on a phone or tablet at the machine, the habit covered in how to improve shop floor communication, each stop is already a timed record with a machine and a reason. In HelpFab's downtime tracking, reasons are called issue types, and a stop that is still running shows as a live timer on its button on the Log downtime page. At handover, the "machines down right now" row is a list you can read, not a memory test.
Two limits are worth knowing. HelpFab has no shift setting, so you review stops by date, not by shift, and the reports count a stop only after someone stops its timer. It also doesn't track part counts, so the "output vs. plan" row still comes from your production count. A machine that is running but degraded, like Press 2 in the example, isn't a running timer either. Write it in by hand.
Open follow-ups carry across the shift boundary the same way. On the Follow-ups page, you create a task against an issue type with a title, an owner, and a due date. It stays on the list until someone selects Mark complete, and it shows as overdue once the due date passes. Nothing resets at 2:30 p.m., so the incoming lead sees the same open list the outgoing lead left.
If you turn on Andon for an issue type, the Andon board shows each open call with its machine and its state: raised, acknowledged, or escalated. It runs in any signed-in browser and has a board mode for a wall screen; see an andon system for a small shop for how that works. And because every timed stop is logged under an issue type, the items you keep handing over show up in the Downtime Pareto on the Reports page, so the pattern gets attacked instead of passed along one more shift.
None of that replaces the two-minute conversation or the acknowledgment. If you are still on paper, start with a structured downtime tracking spreadsheet so the open items at least live in a log you can read at handover, then move it off Excel when the shifts outgrow it.
Copy this and run one tonight
Print the template, put it by the time clock, and have the outgoing lead fill it in three minutes before the next crew arrives. Read the open downtime and the top priority out loud, get the initials, and keep the filled-in sheets for a week. On Friday, flip through them: the item that shows up on three nights running is not a handover problem — it is a maintenance or process problem you can now see and fix. A one-page form that takes three minutes is cheap insurance against a shift like the one in the example.