How to write handoff notes someone can act on

Handoff notes should help the next person continue the work without guessing what “almost finished” means. Write for someone who has the role's basic knowledge but has not been present for every conversation.

Start with status, not history

For each workstream, state what is complete, what remains, and what happens next. Include the relevant deadline and the person responsible for the next action. A long narrative of how the project began can be less useful than a short description of the current decision. Use links to authoritative documents rather than attaching several competing versions. Label drafts clearly. Do not put passwords, private keys, or sensitive personal data into a general handoff document; use the organization's approved access process.

A handoff template

The “last checked” field makes it easier to recognize notes that may have become outdated. Update it only when you actually verify the status.

Include the details you usually remember

Routine exceptions are easy to omit because they feel obvious to you. Note a recurring approval step, a supplier's lead time, or a meeting that happens on a different schedule. Explain the reason when it helps the next person decide what to do if circumstances change. Avoid editorial comments about colleagues. “Approval is required from the finance contact” is useful; “Finance always makes this difficult” is not a dependable instruction.

Test the handoff

Ask the recipient to identify the next action for one project using only the notes. Any question they ask may reveal a missing link, unclear term, or assumed piece of context. If possible, do a brief walkthrough and record the clarifications. A handoff is complete when the next person can find the work, understand the status, and know whom to ask about unresolved issues.