The Handoff
The machine hands over control on purpose: it signals early, says what's happening, and gives the operator time to get their bearings before they're responsible.
Alvia train at Santiago de Compostela Draft
July 24, 2013 · Santiago de Compostela, Spain
On the evening run from Madrid to Ferrol, an Alvia train approached Santiago de Compostela on a new high-speed line. That line was built with a European train control system that would have announced the end of the high-speed section, asked the driver to acknowledge it, and braked if he didn't. But a processing delay in the onboard equipment meant trains had been ordered to run on Spain's older ASFA system instead, which warns a driver but doesn't brake for him. A few kilometres before the city, the line passed from high-speed to conventional track, and slowing from about 200 km/h to the 80 km/h limit for the A Grandeira curve became entirely the driver's job, marked only by trackside signs. He was on a work call from the train's conductor as the train passed the point where he needed to start braking. It entered the curve at more than twice the limit and derailed. 79 people died and more than 140 were injured.8
Anti-pattern: The Unannounced Handoff Draft
The track handed speed control to the driver at a fixed point, at full speed, with nothing in the cab to say it had happened. The version that would have announced it, asked for an acknowledgement and braked if none came had been switched off.
The Handoff
Therefore: Hand over control early and on purpose: signal clearly, tell the operator what's happening, give them time to get their bearings, and release only when they confirm.
Simplified illustration.
Without
Motorway handoff
The car is driving. You are not.
With the pattern
Motorway handoff
The same transfer, announced before it happens.
The transfer is announced, explained and acknowledged. Responsibility moves only once the human is oriented.
The mechanism
machine leads → human leads
- 01Machine leadsAutonomy nominal
- 02TriggerApproaching the edge of its limits
- 03 · Key momentSignal + stateMode, intent, hazards, time left
- 04OrientHuman acknowledges, gets bearings
- 05Human leadsMachine confirms release
At 02: Hand off early and on purpose, at a designed boundary, not at the moment of failure.
At 04: The window is sized to how long a human needs to re-enter the task, not to when the machine runs out.
On this page
When to use
Use this whenever a machine can reach the edge of what it can safely do and an operator is expected to take over. It matters most at autonomy levels where the human isn't watching continuously, so they arrive cold.
Design considerations
- Never depend on someone you can't alert. If the design assumes a person will take over, the system needs a way to ask them, early.10
- Trigger at a designed boundary. Decide in advance which conditions start a handoff, and start it before the machine runs out of options. A handoff that begins at the moment of failure is already late.
- Size the window to the human. Planned takeovers vary widely in how long they take. Base the orientation window on operators who have been out of the loop, not on emergency takeover data.
- Brief all three levels. Tell the human what is happening, what it means, and what happens next. Raw state alone leaves them holding data instead of understanding.
- Clear the channel. Suspend unrelated displays and media once a handoff starts, so the briefing is the only thing competing for attention.
- Release only on acknowledgment. Responsibility moves when the human confirms, not when a timer expires. If nobody confirms, fall back to a safe stop rather than handing control to no one.
In the field Draft
■ Without it · Automotive: The system relied on the safety operator to brake in an emergency but wasn't designed to alert her.10 See Provenance Log for the full timeline.
● Applies the pattern · Rail: ETCS level transitions. The driver gets a text announcement, then a flashing prompt to acknowledge, and the train brakes if no acknowledgement comes within seconds.12
Observed · Automotive. UN R157 names this moment the transition demand, and requires non-driving displays to suspend once it starts.6
Observed · Aviation. Air France 447: the autopilot disconnected suddenly and the crew took over cold. The handoff arrived as a few lines of text on the message display.11
Related patterns
- Requires · 05Shared Mental ModelThe state briefing only works if the human's model of the situation is already current.
- Follows · 03Graceful DegradationWhen the ladder runs out of fallbacks, the system escalates by handing control back.
- Follows · 11Readiness CheckA takeover request assumes someone is ready to receive it. This is the check that assumption rests on, and the reason the escalation ends in a stop rather than a handover.
- Complements · 12Return of ControlThe Handoff covers the machine giving control up. This is the same transfer in the other direction, where the failure mode is not a cold takeover but a contest neither side acknowledges.
- Complements · 13Operator-to-Operator HandoverThe Handoff moves control between a machine and a human. This moves it between two humans, where the state has to survive a gap in which nobody is watching.
Sources
Timing is where this one usually goes wrong. A handoff triggered when the machine runs out of options is already too late, because the operator has been out of the loop and needs time to work out what's happening before they can act.5 Planned takeovers vary enormously in how long they take, so sizing the window from emergency data leaves people short.3
- Ironies of AutomationPaper
- “Take over!” How long does it take to get the driver back into the loop?Paper
- Takeover Time in Highly Automated Vehicles: Noncritical Transitions to and From Manual ControlPaper
- Designing for Situation AwarenessBook
- The Glass CageBook
- UN Regulation No. 157 — Automated Lane Keeping Systems (ALKS)Standard
- SAE J3016 — Taxonomy and Definitions for Terms Related to Driving Automation SystemsStandard
- Final report on the derailment of Alvia service 04155 at Santiago de Compostela, 24 July 2013Incident
- Court ruling on the Angrois derailment, 26 July 2024Incident
- NTSB HAR-19/03 — Collision Between Vehicle Controlled by Developmental Automated Driving System and Pedestrian, Tempe, ArizonaIncident
- BEA Final Report — Air France Flight AF447, Rio de Janeiro to ParisIncident
- ETCS a crucial factor in Santiago accident inquiryArticle