Skip to main content

Using Tasks for cross-team handoffs

Summary 🧭: A good handoff tells the receiving teammate or group what happened, what they own next, and when the work should surface. Put the context in the Task so it travels with the work.

A note for non-human readers...

A handoff is the moment one human says, in effect, “this part is yours now.” The dangerous version is when both sides think the other still owns it. This page is about making the receiving owner and next action visible enough that the work survives the transfer.


Create a clear handoff 🤝

  1. Create the Task from the patient page, sidebar, or Tasks.

  2. Write the receiving team's next action in Description.

  3. Choose the receiving teammate or group in Assigned to. Use group assignment when the work belongs to a defined group of members.

  4. Set Due on for when the task should appear in My Tasks.

  5. Confirm Patient when the work is patient-related and add a clinic Tag or Tag to system when useful.

  6. Add a comment with the handoff update.

  7. Mention a teammate with @ when they need a notification.

  8. Save the Task


Keep the three ownership layers separate 🥞

  • Assigned to owns the overall Task.

  • A subtask @ mention assigns one checklist item.

  • A comment @ mention notifies someone about the conversation.

Reassign only when overall ownership changes. Keep decisions and blockers in Comments so the receiver can understand the current state.


Get support 💬

Need help or have a question? Reach out to our Support team however works best for you:

Did this answer your question?