01
Separate the decision from the background
Start with the particular decision the recipient needs to make. In the packaging example, the studio might ask which information hierarchy to develop, rather than requesting general feedback on every visible detail. Then identify the draft version and explain which constraints shaped it. Keep background references available, but distinguish them from the material that needs attention now. This gives the client a defined task and helps the studio recognise whether the reply resolves it. A handoff should not rely on someone remembering an earlier conversation or discovering the question inside an attachment.
02
Name the next action and its owner
Record who will respond, what form the response should take and what happens after it arrives. The example studio could ask the client lead to consolidate comments in one place before the next revision begins. Any date should be an agreed project date rather than a decorative urgency label. If the recipient cannot decide yet, provide a way to identify the missing information. This turns a delay into a visible dependency. The note can remain short, but it should be clear enough that another team member could understand the next step without reconstructing the entire email chain.
03
Preserve the reason for the choice
Once a decision is made, keep a brief record beside the relevant version: what was chosen, who confirmed it and which constraint mattered. In the example, the client might prefer one information hierarchy because it leaves room for a required product detail. Recording that reason helps later contributors distinguish an intentional choice from an accidental layout. It also reduces the temptation to reopen the same question without new evidence. The handoff record is a working aid, not proof that a project succeeded; its value is in making subsequent work easier to understand.