A useful handoff answers three questions: what is true now, what happens next, and what should make the next person stop and ask.
It also identifies what the next person has actually accepted. Sending someone a document does not prove they have taken ownership.
Try this structure for a recurring administrative task:
Current status and the date it was checked.
Next action and the evidence needed to complete it.
Proposed owner and acceptance status.
Deadline, if agreed.
Location of the source material.
Escalation condition and contact role.
For a fictional delivery coordination task: the order is confirmed, the delivery window is not. The next action is to obtain the window from the supplier. Receiving the goods is not yet the immediate task.
Use this prompt:
Draft a handoff using only the supplied facts. Separate confirmed status from pending information. Distinguish the proposed owner from an owner who has accepted. Include the next action, completion evidence, agreed deadline, source location, and stop/escalation condition. Mark missing information. Do not treat a sent message as acceptance.
Before relying on it, ask the recipient to restate the next action and flag what is missing. That response tests the handoff more directly than asking whether the document looks good.
A good handoff gives the next person enough clarity to move and enough context to know when they should not.
Try a free sample
Want a reusable starting point? Open the Handoff Pack and copy the free worksheet at the top. The paid section adds guidance and worked examples to help you use it.
Become a paid reader for the complete pack archive and two new implementation packs each month.
—Future Proof

