The system state at handoff must be fully briefed

What it is

A window that contains only “please take over” still leaves the person dark. Complete state briefing requires the handoff instant to hand over a current picture: which step, which object it is stuck on, which acts have already taken effect, which have not, and why the machine thinks it must give the work back.

Miss one piece and the person fills it with a guess. The guess becomes an act on the first beat of takeover.

Why it happens

Level-one SA is perceiving the elements. An agent’s elements are not on a windscreen; they sit in the seams of tool calls, drafts, permissions and the outside world. The person was not in those seams, so the elements have to be listed, not assumed from “one look at the UI.” Aviation shift handovers read altitude, heading, fuel, failed items out loud — not ritual, but turning invisible state into a scannable list.

Complete does not mean dumping the whole log. Complete means covering the state variables a decision needs, each with a current value. The causal story — how we got here — is a different packet; a state brief does not replace it, and must not be crowded out by it.

Studying it

Give briefs of different completeness before takeover: alarm only, current step, step plus object plus acts already in effect. Dependent variables: first-beat correctness, whether people can recast key state in a probe, steps needed to correct after takeover. Independent variables: whether the brief includes acts already in effect, whether it includes “not yet done,” whether it includes the machine’s reason for handing over.

Use a freeze probe: stop the handoff screen and ask “which mail has already gone.” If they cannot answer, state did not reach the perception layer.

Where it stops holding

If state is already continuously visible (the person has been watching the same gauges), an extra brief adds little, but the fact of “control just passed” still needs marking. If state keeps moving fast after the pass, the brief has a shelf life and must keep refreshing; a static screenshot will not do. This entry does not discuss how long the window must stay open, nor sudden transfer.

Applying it

• Fix four blocks on the handoff UI: current step, concrete object, in-effect / not-yet, reason for handing over. Missing one block, do not pass control.
• Group acts already in effect on their own, with more visual weight than the planned next step — the first thing a person needs is what has already changed in the world.
• Check: on the handoff screen, cover the brand copy and ask the person on shift “which things have already happened outward.” If they cannot finish the list, the brief is not yet complete state.

Related

• Same group: L4.04.1 Handoff needs enough time to rebuild the situation · L4.04.3 Sudden handoff is the most dangerous form · L4.04.4 Handoff quality depends on whether the giver explains how the situation was reached · L4.04.5 Time to rebuild the situation is a hard constraint and cannot be squeezed to zero · L4.04.6 The system hands off when it loses its grip, which is when the situation is most complex · L4.04.7 Responsibility transfers immediately after handoff; the transfer must be confirmed by the taker, not assumed · L4.04.8 Reverse handoff needs design too; when a person hands back, they must say what they changed
• Nearby: L4.08 Visibility of Task Progress · L4.13 Agent Failure Reporting and Escalation · L1.05 Human in the Loop
• Search terms: handoff briefing · situation awareness · takeover