When the Open Item Carries Itself Forward

You think your system works for you. Most shifts, you're working for it.

Every open item, every watch-point, every "don't forget" gets carried across the shift gap by someone re-writing it, re-saying it, remembering for it. And when that carrying fails, people die.

Fifteen did at the Texas City refinery in 2005. Everything needed to stop it was known — one shift before. A tower had been filling far past a safe level for hours, and the night crew watched it climb. But the handover was thin, the logbook vague, and a decision to hold the unit never crossed to the day shift. So they started up on a plant they could no longer see.

Source: U.S. Chemical Safety Board, final investigation report 2005-04-I-TX.

Different plants, different decades — Piper Alpha, Toledo — one root: the gap between two crews, where the important thing slips through.

Here's how an open item survives that gap today: someone re-writes it into the next log. Shift after shift. By hand. Drop it once — or delete it — and nothing flags. The item simply stops existing. And every re-written line looks fresh, so it can cross handovers for weeks without ever showing its age.

The fix isn't more discipline, louder reminders, or a fuller logbook. All three ask people to re-write harder — and re-writing is the failure mode.

What if the open item didn't depend on being re-written at all?

Raised once, the moment it's noticed. On every handover after that, by default. Open until someone closes it — not until someone forgets it. Carrying its own history with it.

Once an item shows its age, a rule becomes possible that no hand-carried logbook can enforce: anything that crosses two handovers isn't open anymore — it's stuck. Stop handing it over. Start replanning it.

That's not a product pitch — it's a design principle any operation can adopt: make the important thing survive by default, instead of by memory. "He'll remember to mention it" is not a safety system.

Today's technology is more than capable of closing this gap. So, honestly — is your system serving you, or are you serving the system?