A handover should pass along interpretation and open hypotheses, not just the current readings
Aliases: Situation-aware shift handover · industrial human factors
What it is
A situation-aware handover carries recent changes, the outgoing operator's interpretation, open hypotheses, emerging risk, and the triggers the next shift should watch for — not only the current readings. Under Endsley's three-level model of situation awareness, a numbers-only snapshot covers at most level 1, perception of present values; it leaves out level 2, comprehension of what those values mean, and level 3, projection of where the process is heading. Without the latter two, the incoming operator inherits an outcome without the chain of reasoning that produced it.
Why it happens
The incoming operator did not take part in building the outgoing team's mental model — the path from action to interpretation to judgment was lived by one side and left only its endpoint, a number, for the other. Narrating that path as event, interpretation, action, response externalizes reasoning the incoming operator would otherwise have to reconstruct from scratch, saving exactly the inference work a snapshot forces onto them.
This breaks down under time pressure. When the handover window is compressed — a rushed shift change, an outgoing operator eager to leave after overtime, an early call-in — the narrative is the first thing dropped, leaving only values, which is precisely when the process is still evolving and the explanatory chain has not closed. Conversely, when the process has been at steady state for a long stretch with no developing event, level 2 and 3 situation awareness carry little marginal value, and skipping the narrative costs little. Whether a full narrative is worth doing turns on this condition, not on treating every handover as equally demanding.
A numbers-only snapshot has a more specific blind spot: the same reading could be trending up or trending down, and a snapshot cannot tell which — yet it is exactly that direction and rate of change that determines whether the value will cross a limit before the next handover. Conveying the trend line is one of the core things level 2 and 3 awareness are for; it is not the same as reading the current display value aloud a second time.
Studying it
Free-form, structured, and data-only handovers can be compared using post-handover situation probes that test whether level 2 and 3 awareness actually transferred, rather than whether the incoming operator can recite values. One approach borrows the freeze-probe logic of the Situation Awareness Global Assessment Technique (SAGAT): pause the task after handover, blank the display, and ask about the cause of the current state and its likely trajectory. A subjective scale such as the Situation Awareness Rating Technique (SART) can be collected alongside, so self-reported confidence can be compared against actual accuracy — a large gap signals false confidence. The scenario must include an event still in progress; a scenario already at steady state will not discriminate between handover formats at all.
Where it stops holding
Verbal narrative can carry the outgoing team's confirmation bias forward: the incoming operator tends to adopt an existing interpretation rather than treat it as a hypothesis to verify, which matters most when the state keeps changing during the handover itself. Structured templates reduce omissions but can turn into mechanical box-filling — completing every field is not the same as conveying the situation. Handover duration is itself an organizational constraint: if scheduling compresses the window to just enough for values, no interface or template can recover the narrative — that limit sits outside what interaction design can fix.
This claim also applies unevenly across roles: a field operator typically walks the plant after taking over, which functions as a built-in real-time check, so a missing narrative costs relatively little. A control-room-only role has no such natural check — once the narrative is missing, the incoming operator can only passively accept whatever interpretation the outgoing team handed over, which concentrates the risk on that role in particular.
Applying it
Organize the handover screen as perception, then comprehension, then projection: current values first, followed by the outgoing operator's interpretation and the evidence behind it, ending with the trends and trigger conditions the next shift should watch, alongside a live-data view so narrative never substitutes for verification. Require the incoming operator to read back key judgments and ask questions rather than sign off passively. To check it worked, ask two or three open questions right after handover — what is most likely to happen next, which signal will you watch — and treat a blank answer as failure regardless of how much the record contains; a follow-up test that injects a developing scenario shortly after handover can confirm whether response time and judgment actually hold up.