When colleagues use different AI tools, hand over the work in a format the recipient can use, together with its sources, review status, unresolved questions and next action. The receiver should be able to continue the job without reconstructing the sender's private chat. Agree what they are accepting: a draft to develop, a result to check, or work already approved for a particular use.
This is a practical part of designing tools and workflows. It applies to everyday documents, analyses and content moving between people. A production software system needs a more extensive technical handover; a quick spelling correction usually needs less.
A file that opens is only the first test
There are two distinct questions at a handoff. Can the next person read and edit the artifact? And can they understand what it means well enough to take responsibility for the next step?
Some conversion behavior is documented. Google Docs Help says Microsoft Office tracked changes become suggestions when converted to Google Docs, and Docs suggestions become tracked changes when converted to Office. That is a specific file-editing capability. It is not a promise that every AI service will inherit the source context, permissions or decisions behind a document.
Test the actual receiving environment. Open the exported file, follow a source link and inspect any pending edits that matter. If the recipient cannot access a source, attaching a polished summary does not resolve the gap. Arrange permitted access or provide an approved alternative before asking them to rely on it.
The harder failure can occur even when the file is perfectly readable. In a public Reddit account, a user who had built a team monitoring tool described receiving a coworker's long, unread AI-generated suggestions and being asked to respond thoughtfully. The complaint concerned the work pushed onto the recipient. It is one unverified account, but it makes a useful distinction: sending output is not the same as preparing it for someone else's review.
Before sending, read the artifact yourself and remove claims you cannot explain. If you want early feedback on something unfinished, say which part is uncertain and ask a specific question. “Please check whether this proposed workshop date matches the exhibition programme” gives a colleague a bounded task. “Thoughts?” beside several pages of unchecked output does not.
Make uncertainty visible in a school-visit pack
Suppose a museum's visitor-services coordinator, Sam, uses an approved AI assistant to prepare a school-visit information pack from public exhibition pages. Alex, an education editor, will adapt the draft in a different approved writing tool before the usual publication review.
The public programme lists an exhibition opening date and describes a possible workshop whose date is still to be announced. Sam checks the draft against those pages and catches a sentence presenting the workshop as confirmed for opening day. Sam removes that claim and records the unresolved date beside the draft.
Leave a record the recipient can use
Keep the record with the current artifact in the team's existing document, ticket or folder. Use one maintained location. Record the information the recipient needs to act; include a tool version or instruction when it matters for interpretation, investigation or an organizational requirement.
For Sam and Alex's school-visit pack, a usable record could read:
Artifact and task: Visit pack, version 3 in the shared education folder. Alex will prepare the teacher-facing draft.
Evidence and scope: The linked public exhibition programme is the source. The draft covers that programme, not every event the museum may run.
Checked: Exhibition details compared with the source programme. The unsupported opening-day workshop claim has been removed.
Open: The workshop date is unconfirmed. Exclude it from booking instructions. The education manager owns confirmation and publication approval.
Acceptance: Alex can edit this version and ask Sam about its sources. Receipt for editing does not approve publication.
Adapt the labels to your work and replace the source description with the actual permitted link and version. A blank “checked” field should remain visibly unchecked. Do not let the assistant fill it with an assurance that nobody has verified.
Share a whole AI conversation only when it is appropriate and permitted. A shorter record is useful when it preserves the constraints and unresolved decisions; it fails when the summary quietly removes them. Check it against the artifact before sending.
A team AI agreement can establish these expectations. The individual handoff records how they apply to this artifact.
Alex opens the current file and the source programme, checks that the pending question is still visible, and confirms receipt for editing. That acknowledgment does not approve the pack for publication. The education manager's decision remains outstanding.
Receipt for editing is separate from permission to publish
Current visit-pack file and source programme
Alex must be able to open and edit the version Sam actually checked.
Exhibition details compared with the programme
The unsupported opening-day workshop claim has been removed.
Workshop date unconfirmed
Keep it out of booking instructions, even if another tool rewrites the pack.
Education manager confirms and approves publication
Alex’s acknowledgment accepts the editing handoff; it does not approve publication.
If Alex's assistant rewrites the pack, the workshop date must remain unresolved. A second tool's confident wording is not new evidence. Alex checks the revised version against the same source and keeps the pending decision visible until the responsible person resolves it.
Accept the next task explicitly
For a recurring handoff, agree a small acceptance check with the person receiving the work. Make it fit the consequence of a mistake. A visitor leaflet and a safety-critical operating instruction should not inherit the same review standard just because both are documents.
- Open the current artifact. Confirm the recipient has the intended version and can use the parts needed for their task.
- Inspect the evidence and gaps. Verify access to the sources and identify the checks or decisions that remain.
- Confirm the next responsibility. State whether the recipient is editing, reviewing or approving, and who retains any other decision.
- Resolve a failed handoff. Return a specific missing item to the sender or agree a smaller task that can proceed safely.
For the museum pack, Alex can accept the editing task while the workshop date remains open. If Alex cannot access the public programme, source-dependent editing waits until that access problem is resolved. The team should not call the pack ready simply because it reached the right inbox.
Keep this acknowledgment in the normal work record. A routine transfer may need one sentence; a complex or consequential one may need a conversation and a recorded decision. What matters is that the next owner and the remaining work are clear.
Test whether the handoff saves anyone work
Research gives a reason to examine what happens after the sender finishes. BetterUp and Stanford Social Media Lab's survey asked 1,150 full-time US desk workers about AI-generated material that left colleagues to repair it. The published page describes a September 2025 online survey. It is self-reported commercial research, not a timed experiment or a measurement of your own team.
Adding a protocol is not automatically the remedy. In the Gap employee experiment, the structured joint-use condition had worse observed document results than naturalistic use with the same Copilot access. Session timing, unequal non-submission and grading sensitivity limit the preprint's interpretation. It did not test transfers between different AI products.
The broader evidence also makes the comparison matter. A 2024 systematic review and meta-analysis distinguished improving on a person working alone from outperforming the better of a person or AI alone. Its 106 experiments were reported in papers published from 2020 to mid-2023, across mixed tasks and systems, with different findings for creation and decision tasks. It does not establish a handoff benefit. It does show why “better” needs an explicit comparison.
For the museum, the practical question is whether the team produces an accepted visit pack with less complete effort. Count preparation, review and later clarification separately. Record waiting time as elapsed time, so it does not get added to active work as though someone spent the whole delay editing.
Suppose the team compares the same kind of pack, with the same publication standard, using these illustrative person-minutes:
| Active work | Existing process | AI-assisted process |
|---|---|---|
Sender prepares and checks the draft | 25 | 8 |
Recipient reviews and prepares it for approval | 10 | 20 |
Later clarification and repair across the people involved | 0 | 12 |
Total active effort | 35 | 40 |
The sender saves 17 minutes while the team spends five more. Count each activity once. If Sam and Alex both spend six minutes on a clarification call, that is twelve person-minutes and six minutes of elapsed time. Work that fails the agreed standard remains a failed attempt, with its effort included.
On real transfers, record ordinary cases, exceptions and unfinished attempts. Use the net-time-savings method to make the comparison consistent across attempts.
For the next pack, Sam and Alex should identify what caused the extra review and repair. Missing source access calls for an access fix; a lost qualification calls for a better source check. An unused field in the record may be removable. Keep the smallest record that lets the recipient perform the task reliably.
If the same information has to be copied repeatedly between several systems, test how a connection would reach the working record. Investigate the whole workflow when the problem spans the larger process. Try the next handoff with its receiver present, then keep the record that makes the next transfer easier.
Questions about AI-assisted handoffs
Do colleagues need to use the same AI tool?
Colleagues do not necessarily need the same AI tool to exchange a document or analysis. They need approved tools, a usable artifact, accessible evidence and a clear next task. Test the actual format and important edits in the receiving environment; do not assume a successful file import also transfers the original AI context. The file and evidence checks help separate those questions.
Should the sender share the whole AI conversation?
Share the parts of an AI-assisted task that the recipient needs to continue or review it, subject to the organization's information rules. That normally means relevant sources, constraints, checks and unresolved decisions. A full conversation may be appropriate for investigation or a required record, but it can also contain irrelevant or restricted material. Start with the handoff record and add permitted detail when the recipient's task requires it.
Can the recipient use another AI tool to verify the work?
Another approved AI tool can suggest checks, but agreement between generated answers does not establish that a claim matches the original evidence. The recipient still needs the source, the important acceptance conditions and a person who can resolve uncertainty. For the museum pack, a second assistant cannot confirm a workshop date absent from the programme. Alex can continue editing while the education manager resolves that decision. Use the human review guide to decide which claims to check and who can approve the result.



