Create a handover note that preserves open work

A handover should make unfinished work visible and distinguish decisions from suggestions. The receiving person needs source locations and next checks, not just a narrative.

Bound the operating task

Provide the relevant records and define what is a draft recommendation versus an approved action. Keep original records intact and ask for an output manifest so you can find the result. Start with file generation and human review before adding any external action through a connected tool. A useful operations deliverable should make exceptions and missing information visible.

Inputs for this workflow: Project notes, current task list and approved owner information.

Work through the task

1. Separate complete, active and blocked work.
2. List the next action and evidence for each item.

A brief you can adapt

Write handover.docx with status, owner when known, source link and next step. Include access prerequisites without including credentials.

The filenames above are examples. Replace them with your actual inputs and destination before submitting the task.

Review the deliverable

Ask the receiver to locate one source and identify the highest-priority unresolved item.

Where this approach can fail

Do not assign ownership to someone merely because their name appears in a discussion.

For the related desktop setup, see review results.