The shift handover

The situation

06:55. The night lead has been awake thirteen hours and wants to be in a car. Handover happens standing up, at a desk, in four minutes: "Pump 4 was noisy, keep an eye on it. Line 2 tripped twice, we cleared it both times. The spare seal kit never came in. Oh, and the contractor's coming for the roof at nine."

The day lead nods and writes nothing down, because there is nothing here to write — it is four sentences of atmosphere with no request in it. Line 2 trips twice more that morning and gets cleared twice more. Nobody orders the seal kit, because nobody was asked to. Pump 4 is watched by no one in particular for two weeks and then fails on a Thursday.

The principle

A shift handover is a queue of open decisions, not a diary of what happened — the next crew needs what is unresolved, who owns it, and what would close it.

Nothing moves, nothing stops, no interlock is touched — the only thing that changes is what the next crew is handed, which is why this is where an industrial team can start without a safety case.

Most handovers fail because they are organised by time instead of by state. A diary tells you the order things occurred and leaves you to work out which ones are still live. A queue tells you the four things that are still open, who has each, and what evidence or action ends it. The three sentences that produced nothing above contain two unresolved decisions and one procurement action — they were simply never separated from the weather report.

That separation is mechanical, which is why a model does it well and a tired human does it badly at 06:55.

Worked example

Shown here in ChatGPT.

Job: Rewrite this raw night-shift log as a handover for the incoming lead.

Inputs: [pasted log lines, timestamps included, as typed]

Output: Three sections, in this order.
  OPEN DECISIONS — a table: item, owner, decide by, what closes it.
  WATCH ITEMS — one line each, with the specific condition that turns it
    into an open decision.
  CLOSED THIS SHIFT — one line each, no detail.

Standard: An item is open only if someone has to choose or do something.
Every open item names one person and one condition that closes it. If the
log does not say who owns it, write UNASSIGNED — never guess a name. Do
not smooth the language or add anything the log does not support.

From the four sentences above:

OPEN DECISIONS
  Line 2 repeat trips (2x)  | UNASSIGNED  | 12:00 today | Root cause found,
                                                          or escalate to
                                                          maintenance planner
  Spare seal kit not        | UNASSIGNED  | 10:00 today | PO raised and
    received                                             confirmed
WATCH ITEMS
  Pump 4 audible noise — becomes an open decision if noise persists on
    the next start, or vibration exceeds the alarm limit
CLOSED THIS SHIFT
  Roof contractor attending 09:00, access arranged

Two UNASSIGNED rows is the entire finding. The model did not know who owns them and, told not to guess, said so — which puts the naming decision in front of the person who can make it, in the ten seconds the handover has for it.

Underneath this sits the map you are building. For each recurring signal in your area, one row:

SIGNAL          | who sees it first | what it can mean | who can act
                | how long they have | what closes it
----------------------------------------------------------------------
Pump 4 noise    | night operator    | bearing wear /   | maintenance planner
  on start      | until next start  |   mounting /     | closed by: vibration
                |                   |   normal cold    |   reading at limit,
                |                   |   running        |   or clean restart

In your tool

A handover has to leave the chat and land somewhere the next crew reads. The capability to look for is a fixed-format output you can lift out whole.

Product surfaces checked 2026-08-04.

Try it

Take the last signal you personally handled — an alarm, an inspection note, an operator comment — and fill one row of the map: who sees it first, what it can mean, who can act, how long they have, what closes it.

You are done when the closing condition is a physical fact somebody could confirm, not a feeling. "Vibration back under 4.5 mm/s on two consecutive readings" closes. "Seems fine now" does not. One row is the exercise; the map for a whole process is this track's artifact.

Common failures

• The diary. Chronological retelling, complete and unreadable. It happens because writing what occurred is easier than deciding what is still open, and because the outgoing crew is rewarded for having covered themselves rather than for handing over cleanly.
• "Keep an eye on it." No owner, no threshold, no expiry. It passes down shift after shift, costing nothing each time, until the equipment settles the question itself.
• Pasting the log and asking for a summary. Summary length scales with input length, so the one unresolved decision gets the same weight as the contractor's arrival time. Ask for the state of each item, not for a shorter version of the log.