Handoff
Can the next person continue without chasing me?
Learn to make a handoff usable by naming the current record, unresolved work, next owner and acknowledgement required before the workflow can continue.
Required: your AI Work Delegation Blueprint and either your own workflow or the fictional starter case. AI/GPT is not required for the core simulation.
Map local completion versus the overall outcome, write a handoff for the next person and resolve a conflicting-version example.
An acknowledged handoff with a current record and explicit outcome owner.
This session uses supplied records, partner review and simulation evidence. Do not label a designed or role-play result as live execution.
What you will leave with
An acknowledged handoff with a current record. Add this to your AI Work Delegation Blueprint.
Use your own workflow or the fictional quotation case. No coding or live customer action is needed.
Start with a decision · 10 minutes
Give one person the send receipt and another the blank follow-up record. Both report their local status. Ask who owns the unfinished customer question.
Bite A · Connect local completion to the outcome
Question: Who can declare the whole job complete?
Input: S6/S8. Open the case cards.
Try · 12 minutes: Draw the author, approver and receiver. Label what each finishes and the overall outcome owner. Mark the incomplete delivery question.
Compare after you have decided
The send is complete. Delivery follow-up is not. Someone must own the cross-step result even when every local tool looks green.
Keep: Responsibility and outcome map.
Bite B · Pass enough context to continue
Question: What does Farah need without another chat?
Input: Q-104, approved v2, S6 and outstanding postcode/stock. Open the case cards.
Try · 12 minutes: Write a handoff with current version, evidence, missing facts, next action and recipient. Swap it without explaining; receiver marks missing context and acknowledges.
Compare after you have decided
Producing the card is not acknowledgement. Farah must know what is owed and accept the next action.
Keep: Handoff with recipient acknowledgement.
Bite C · Resolve conflicting versions
Question: Where is the current record?
Input: v1 unapproved versus v2 with Mira’s 10:03 approval. Open the case cards.
Try · 12 minutes: Choose the authoritative current record and explain how a receiver resolves conflict. Remove one version link and repeat the check.
Compare after you have decided
Use the approved-version record and receipt. The most convenient chat message is not automatically current.
Keep: Location, version and conflict-resolution rule.
Put it together · 20 minutes
A recipient can act on the handoff, explain remaining uncertainty and identify the outcome owner without oral rescue. Revise the weakest item and have a partner use it. Keep the result and one limitation.
Close your question · 10 minutes
Return to Can the next person continue without chasing me? and your own opening question. Answered, partly answered or still open? Show the evidence. Save the updated AI Work Delegation Blueprint. A reasoned decision to keep a step human-led is useful work.
Common trap
A sent handoff is not an accepted handoff. Do not hide missing ownership behind technical storage terminology.
Do I need a shared database? You need a clear current record; a simple controlled sheet or paper card can demonstrate the principle.
Where this appears in real work
Alamak and Zenneth: show brief → approved asset → publisher, preserving version, channel and ownership. The class uses the fictional packet; selected project demonstrations and technical walkthroughs can add detail later.