You send a draft with “Could you take over?” You know which section is finished and which decision is missing. The other person initially sees only a file. They might continue with an old version or assume that everything has already been agreed.
Sending a file and handing over a task are separate steps. A handover needs a clear account of progress and confirmed responsibility. This article offers editorial organisation suggestions and a fictional example, not a personal success story. AuDHD is a community term for co-occurring autism and ADHD, not a separate diagnosis.
What exactly are you handing over?
Name a limited request: complete a section, arrange an appointment or review a proposal. “Take over the project” leaves scope and responsibility open. Distinguish a request for support, a decision and taking over an action.
Waiting for responses covers a missing external requirement. Here, another person is supposed to continue the work. Asking does not mean they have agreed.
Show the actual progress
Separate finished, unchecked and open work. “Text written, figures still unchecked” is more useful than “almost done”. Reference the current file and specific section. A collection of materials does not replace this explanation.
The National Autistic Society discusses written lists as organisational support. This is general background, not evidence that this note or an app is effective. Use approved tools only; do not copy confidential information into extra personal storage.
A handover note to copy
Keep the note at the agreed working location:
Progress and materials: What is finished or unchecked, and which version applies?
Open point: Which question or requirement remains unresolved?
Next action: What specifically needs to happen next?
Responsibility and timing: Who has agreed to do what, and when will we review progress?
If nobody has confirmed the handover, write “requested” rather than assigning their name as an agreed owner. A requested deadline remains a request until agreed. Existing delivery dates still need to be visible.
A fictional example: Alex hands over to Sam
Alex is finishing work and asks Sam to complete the second section of a draft tomorrow. The note reads:
- Progress: Draft v3 in the shared folder; section one checked, figures in section two unchecked.
- Open: Choice between options A and B; requested from the project lead.
- Next action: Once the choice is made, check the relevant figures and complete section two.
- Responsibility: Sam asked to take over, no agreement yet. Clarify at tomorrow's team meeting; existing Friday delivery deadline remains visible.
Sam agrees to check the figures only. The note is updated accordingly; completing the text remains unassigned. A partial agreement does not automatically create responsibility for the whole draft.
Confirm understanding and responsibility
Ask about scope and next steps: “Is the applicable version clear? Can you take over checking the figures? What do you need?” The other person can flag missing access or a conflict with existing work.
For a larger handover, consider a short joint review. A “seen” reaction in a chat does not necessarily mean acceptance. If nobody agrees, discuss responsibility and priority again. Planning message replies explores the difference between reading a message and doing the work.
Update your own list afterwards
After confirmed acceptance, remove the handed-over step from your active list. A follow-up or review may remain your responsibility. Record that as a specific action instead of continuing the entire task in parallel.
If the version changes or a new decision arrives, update the shared working location and notify the other person through the agreed channel. Conflicting notes create extra searching. Moving a reminder alone does not document a new agreement.
Start small rather than reorganising everything
Try the note for one manageable handover. Can the other person find the right version? Are the open points clear? Do you know which responsibilities remain yours? Add the detail that is missing.
The free interruption note also records progress and materials; add confirmed responsibility there. Paper or an existing document is enough. The note is an organisational aid, not a guarantee of successful collaboration. Its practical purpose is to let the next person see where the work stands without guessing.