Write a handoff another person can actually use
Package the current state, working files, unresolved decisions and next action without confusing a draft with approved work.
Take the next useful step.
A handoff is successful when another person can find the current work and take the next appropriate step. A long chronology is rarely enough. AI can help turn notes into a compact working record, but it needs exact status and file references. Begin with a fictional example, then use the same structure on permitted work material.
Describe the state before the history
Use this fictional record: “Workshop page draft v3 is in the review folder. The contact link works in a local preview. The venue has not approved the capacity statement. The accessibility review is scheduled but unfinished. Nothing has been published.” Those distinctions belong near the top of the handoff.
An opening such as “The page is complete” would erase three important limits. Write “The draft is ready for content review; capacity and accessibility remain unresolved.” The reader can then judge what work is appropriate without reconstructing the entire project.
Give each file a job
Make a small file map: draft-v3 contains current wording; approved-facts contains verified venue details; open-questions lists unresolved decisions. Include exact paths or ordinary shared links that the recipient is permitted to open. A file called final-final is not a status system.
Ask the assistant to distinguish files it actually inspected from names merely mentioned in notes. If a file cannot be opened, retain that limitation. A handoff should not imply that every attachment was reviewed just because its name appeared in a summary.
A request you can adapt
Draft a handoff from these records. Lead with current state, then list working files and their purpose, checks performed, unresolved decisions and the first next action. Preserve draft, local, unreviewed and unpublished status. Do not infer approvals or claim that mentioned files were inspected.
Make the first action specific
An authored next action is: “Ask the venue owner to confirm the capacity statement in open-questions. After that decision, update the draft and repeat the content review.” That is more usable than “finish the website.” It identifies the missing decision and the document it affects.
Record the local contact-link test separately: the preview link opened the expected form during this check. It does not establish that the public site was updated or that a real submission was delivered. Keep the scope of the evidence beside the claim.
Try resuming from the handoff
Have a colleague, or a fresh assistant session with the permitted files, explain what it would do first. If it chooses an outdated draft or assumes publication, revise the handoff. This small rehearsal tests whether the document carries the state clearly enough.
Remove secrets, unnecessary personal details and irrelevant conversation history before sharing. Keep the handoff focused on the work the recipient is authorized to continue. Source files may need their own access permissions; a link alone does not grant access.
Keep it current when the decision changes
For a fresh exercise, imagine the venue approves a capacity of 18 instead of the proposed 24. Identify every statement that must change and which checks must be repeated. The earlier review should no longer imply that the revised capacity wording was checked.
End each work session with a small update to the current-state paragraph and next action. Keep historical detail only when it explains a decision or prevents a known mistake. A concise, accurate handoff is easier to maintain than a transcript disguised as documentation.
Take this into your next task
A handoff should preserve the state of the work and make the next appropriate action easy to find.
Questions people ask
How long should a handoff be?
Long enough to state the current result, files, evidence, open decisions and next action. Put detailed background behind links.
Can AI summarize a whole project chat?
It can draft from permitted material, but check every status claim against the files and decisions. Mentioned work may never have happened.
What if the next person lacks access?
List the missing access and who can resolve it. Do not copy restricted material into a less protected location just to complete the handoff.
Sources and editorial notes
Reviewed 2026-09-07. Product capabilities depend on the app, plan, region and workspace settings. Workflows and prompts are authored teaching material, not recorded model results or measured time-saving claims.
Keep going
- AI at Work: Practical Skills, Examples and a Learning Roadmap
- Compare document versions without losing the meaning of a change
- AI Mission Control: From Idea to Verified Result
Related Power of AI pages
Keep reading with Start here, everyday uses, the tool guide, the writing workshop, and sources and standards.