A handoff transfers work between people, agents or software components. A good handoff includes the goal, evidence, current state, unresolved issues and authority for the next step. Losing those details can make a locally correct component contribute to an incorrect overall outcome.
Describe what actually happened
Record the goal, completed steps, outstanding work and exact artefacts involved. Distinguish intended actions from successful ones. The receiving agent should not have to guess whether a document was saved, a record changed or a message sent.
Carry the constraints
Preserve the user’s relevant preferences, permissions and unresolved questions. Include source dates and reasons for decisions when they affect the next step. Keep the handoff concise enough that the recipient can identify the next useful action.
Practise a restart
Pause a workflow and ask another agent to continue using only the handoff. Look for duplicate actions and lost assumptions. For a document review, name the completed sections and remaining issues rather than saying it is nearly finished. Include a recovery path if a required file is unavailable. A strong handoff is an operational record that makes continuation possible even when the original agent or temporary workspace disappears. It should reduce reconstruction work without concealing uncertainty about the task’s status.
A worked example
An assistant prepares a customer-response draft for review. It includes the relevant policy passage, the customer's question and a flagged ambiguity. The reviewer can then decide whether to edit, escalate or send. Passing only a polished draft would hide why the answer was proposed. For software handoffs, include machine-readable status and identifiers so retries do not duplicate work.
Questions readers ask
What should an agent handoff contain?
Provide the task, evidence, completed actions, unresolved questions and the next actor's permitted scope. Clear state is as important as a fluent summary.
Follow the evidence.
AI-assisted explanation with linked technical references. Examples are illustrative learning exercises, not reported customer deployments or experimental results.
Public sources support the factual background. Analysis and illustrative exercises are identified in the text. How we assess AI · Editorial standards
Spot a factual error or an outdated detail?



