How to write a handoff note
A handoff note is successful when nobody needs to ask you what you meant. It should transfer state, not just information.
The receiver needs to know where the work stands, what can break, and what to do first.
What does a weak handoff look like?
I added the latest files to the folder and talked to Marketing. Most things are ready, but a few bits still need checking.
This sounds helpful, but it hides almost everything: which files, what state, which bits, who owns them?
What does a stronger handoff look like?
Context: launch email for the June 20 release.
Current state: copy approved; design exported; audience list still pending.
Owner: Ana owns audience list, due Thursday noon.
Risk: if the list slips, send to beta users only.
Files: final copy, Figma export, CRM draft.
Next action: confirm Ana’s list by Thursday 12:00.
This handoff gives the next person a map.
The six-part structure
- Context. What is this work and why does it exist?
- Current state. What is done, open, or blocked?
- Owners. Who owns each open item?
- Risks. What can go wrong?
- Links and files. Where is the source of truth?
- Next action. What should happen first?
What if the handoff is urgent?
Put the deadline at the top.
Urgent: confirm the audience list by Thursday 12:00 or the launch email misses the Friday send window.
Then give the rest of the handoff.
Save this as a playbook
Handoffs are perfect for playbooks because the structure rarely changes. ILURA can store your handoff format and help turn rough notes into a clean transfer of state.
Turn this message into an agent rule
Do not treat the answer as a one-off rewrite. Save the repeatable behavior behind it so your ILURA agent can apply the same judgment next time.
- What situation triggered the message?
- What tone, boundary or decision should repeat?
- What should the agent avoid doing again?
Problems this guide helps with
The same rule appears in real user searches.
Do it now
Draft this in ILURA right now.
Open ILURA, paste your message, and get help with "write handoff note" — in your voice, on device, free. It quietly saves the rule (Context, state, owners, risks, files, next action.), so the next time is one tap.
Free to start · No account · Data Not CollectedQuick answers
- What is the most important part of a handoff note?
- The next action. Context matters, but the receiver needs to know what to do first and what would go wrong if they miss it.
- How long should a handoff note be?
- Long enough to remove hidden knowledge, short enough to scan. Bullets are usually better than paragraphs.
- Should I include links?
- Yes. Include the source docs, files, tickets, decisions, and people involved. A handoff without links creates follow-up work.