Repeat downtime usually starts at the shift change

A downtime ticket gets logged as a machine fault. The line restarts. Three weeks later the same fault trips on nights.

Nobody lied on the ticket. The night shift had no idea days had already flagged that sensor as intermittent, because the note was in a logbook nobody on nights had to read.

Most plants already write it down

The gap usually isn’t missing documentation. There’s a logbook. The trouble is that nothing makes the next shift read it in their first ten minutes, so a flagged issue fades before anyone who could escalate it sees it twice.

If you want to get to the root cause of repeat downtime, start there. Make the handoff a checkpoint, not a courtesy.

What a working handoff looks like

It’s a two-minute routine, not a new system.

Before the outgoing lead leaves, they go through every open flag with the incoming lead, out loud. Both confirm it, and the confirmation is logged with a time. If a flag has stayed open across two shifts with no fix, it goes to the maintenance supervisor automatically instead of quietly ageing.

The second shift now knows what the first shift knew. That’s the whole point.

Why it never gets prioritised

The cost of bad handoffs doesn’t show up as one dramatic number, which is why it gets put off for years. It shows up as small repeat failures. A bearing gets flagged, forgotten, and fails at the worst possible moment. A changeover note never reaches the next crew, and they lose an hour troubleshooting something that was already known.

Pull the repeat faults out of your unplanned downtime and count those hours separately. Don’t leave them buried in one big total. You’ll see how much of the problem is information that was written down and never handed over.

Handoffs also feed into a bigger trust problem with plant numbers, which we cover in why nobody on the shop floor believes the plant dashboard.