Shift handover without losing information: the note gets written too late.

The night engineer at an office building restarts the same pump twice before four in the morning. It comes back both times. So it never makes the handover note, the note says the night was quiet, and at ten past eight the pump stops for good while the day engineer spends the first hour of the shift finding out what one sentence from nights would have told them. That night is made up. Most people who have run shifts could swap in one of their own.

What a handover note leaves out

Most advice on shift handover comes down to a template and a few minutes of overlap so both shifts can talk. Both help. The trouble is when the note gets written. It gets filled in during the last twenty minutes of a shift by someone who has been awake all night, from memory, and memory keeps what felt like news at the time. A pump that recovered does not. Neither does a tenant who rang twice about the heating and was told somebody would look in the morning.

So what crosses the changeover is the outgoing person's sense of what mattered, which is right on most nights. In one building with the same engineers for years, the rest gets sorted out in the corridor at seven. Across a portfolio with relief staff on weekends and three changeovers a day, the corridor conversation stops happening, and the gap it used to close stays open.

Write it down while it happens

The handover gets better when it is already written by the time the shift changes. Every restart and every promise made to a tenant lands on one record for the site when it happens, with the time and the name beside it. That is the shape behind an operations system: one record that every step writes into, so whoever picks the work up next starts from what already happened.

At the changeover, the system does the part people are worst at by seven in the morning. Open items come first, meaning what was promised to whom and by when, and anything that happened more than once overnight. Closed items stay out of the way.

The trade order desk OCTYN designed for a trading company is drawn around the same morning question. Its operations view shows the team the orders at risk first, and why. It is only a design so far. A building asks the same question at seven every morning, about pumps and tenants where the desk asks about orders.

What stays with the people on shift

The day engineer still decides whether the pump needs the service company now or can wait for the planned visit, and the record makes none of that call. What it takes away is the hour spent finding out the question existed. People keep the judgement calls and stop finding problems a shift late.

It is worth counting before anything gets built. Say a site changes shift three times a day, every day, and each incoming person spends twenty minutes rebuilding the last shift before they can act on anything. That comes to seven hours a week per site of people reading backwards. Your own numbers will be different, and the page on what a system gives back runs the sum with them. There is also a comparison of doing it by hand against a system.

The night will still go down as quiet, which, to be fair to the night engineer, it mostly was.