# Action Map — The Handover

> Kit 25 · The Handover · deliverable · designed and built by I Wayan Usada · fictional case

## The goal

In this fictional brief: handover documents that a colleague in another time zone can run without asking, with conditions written as conditions and times given in both zones. Proposed measures are on the case page; nothing has been measured.

## What people do instead

Writers either describe everything at the same depth (a wall of text) or write a few bullets and "ask me if unclear", which the reader cannot do at 22:00 IST.

## The actions that close the gap

| # | Behaviour | What it looks like | Where the build practises it |
|---|---|---|---|
| 1 | **Match structure to the element's failure mode** | conditions as IF-THEN, procedures as a worked example, facts as one line | card choice per element, scored 2 / 1 / 0 |
| 2 | **Prioritise inside a budget** | expensive structures only where the clicks are | 15-point budget equal to the best answer's cost |
| 3 | **Write times in both zones** | 20:00 CET = 00:30 IST (winter) / 23:30 IST (summer) | feedback on deadline and batch window; replay clock |
| 4 | **Never leave the gate steps out** | deadline, exceptions, verification always answered | critical-gap rule |
| 5 | **Test the doc as the reader** | replay, find the guess, rebuild | rebuild-and-replay loop |

## What this training will not do

It cannot give the reader someone to call. A weekend duty contact is an organisational decision (see the case page).