> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sameitem.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cross-Team Handoffs in monday.com: The Same Item Changing Rooms

> Stop losing context when work moves between teams in monday.com. A handoff is not a new item on another board — it is the same item appearing in the next team's context.

## The short answer

Most monday.com handoffs die in translation: marketing "finishes" a brief, someone re-creates it as a ticket on the dev board, half the context stays behind, and two weeks later marketing asks about progress on an item dev has never seen. The fix is to change the model: **a handoff is not a new item — it is the same item appearing in the next team's board**, with each team seeing its own columns and context.

## The pattern

1. **The item is born where the work starts** — say, a campaign item on the marketing board with marketing's columns: audience, channel, copy status.
2. **When it's ready for the next team**, the same item appears on the dev board — shared automatically by an [automation recipe](/features/automations) ("when status changes to Ready for dev, share item to Dev board") or [manually](/features/manual-sharing) for one-offs. With [Same Item Multiple Boards](https://monday.com/marketplace/10000363), it's the same item, not a copy.
3. **Each board keeps its own extra columns.** Dev adds estimate, sprint, and technical owner on their board; marketing never sees them (columns sync only where names and types match — [column mapping](/features/column-mapping)).
4. **Shared columns and the updates thread stay common.** Status, dates, files, and the [conversation](/features/updates-sync) live on the one item both teams share — the requirements never get lost in a Slack message again.
5. **When dev finishes**, their status flip is instantly visible on the marketing board. No status meeting about status.

## Chains, not just pairs

The same mechanics extend to longer flows — sales → delivery → operations → finance. Each stage shares the item onward at a status change; every team works in its own board; the item accumulates context instead of shedding it at each hop. The [Item Locations column](/features/item-locations) shows every room the item is in.

## What this replaces

| The usual workaround                           | What goes wrong                                                                                                        |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| "Create item in board X" automation at handoff | Two items immediately [drift](/guides/duplicate-items-drift); files and comments stay on the original                  |
| One giant shared board for both teams          | Each team drowns in the other's columns and views; permissions get messy                                               |
| Mirror columns on the receiving board          | Read-only — dev can't run their own automations or views on mirrored values ([why](/guides/mirror-column-limitations)) |
| Slack messages + re-entry                      | Context loss, no audit trail, "where's that thread?"                                                                   |

## FAQ

### Does the receiving team need edit rights on the sender's board?

No — they work on the item from their own board. That's the point: contexts stay separate, the item stays one.

### Can the item leave the first board once handed off?

Your choice. Keep it on both (marketing watches progress live), or unlink it from the marketing board at a final status to keep boards lean.

### What about subitems created by the receiving team?

Subitems sync across the boards the parent lives on — see [subitems across boards](/guides/sync-subitems-across-boards).