> ## 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.

# Send monday.com Form Submissions to Multiple Boards (and Keep Them in Sync)

> A monday.com form creates its item on one board. Here is how to make each submission appear on every team board that needs to act on it — as one synced item, not drifting copies.

## The short answer

A monday.com form always creates its item on **one** board — the form's board. If several teams need to act on each submission (intake + the assigned team + a manager view), the reliable pattern is: keep the form's intake board as the system of record, then **share each new item to the other boards automatically** so every board works on the *same* item. Duplicating submissions with "create item in board X" automations gives every team a different copy, and the copies immediately stop agreeing with each other.

## The pattern

1. **Intake board** — where the form lives. Every submission lands here first, untouched. This protects the integrity of the original data.
2. **Routing automation** — with [Same Item Multiple Boards](https://monday.com/marketplace/10000363) installed, add an [automation recipe](/features/automations) on the intake board: *"when item is created, share item to board X"* — or route conditionally: *"when Department is set to Facilities, share to the Facilities board."*
3. **Column names must match** between the intake board and destination boards for their values to sync — [column mapping](/features/column-mapping) previews this and creates missing columns in one click. Columns you *don't* want shared (internal triage notes) simply don't exist on the destination.
4. **Work happens anywhere** — the team updates status on their board, the intake team sees it on theirs, and any manager view sees the same. One item, one truth, one updates thread ([how updates sync](/features/updates-sync)).

## Real example (from a customer setup)

A request form feeds an operations intake board with \~200 columns of request data. Submissions route to the responsible team's board by department. Mapping those columns manually with native automations was the blocker — with name-based column syncing there was nothing to map: matching columns sync, the rest stay home.

## FAQ

### Why not just point automations at each team board?

"When item created, create item in board X" makes a **copy**. The team updates their copy; the intake board still shows the original untouched; reporting is now wrong. Sharing the item instead means there is nothing to reconcile later. More on why copies drift: [duplicate items drift](/guides/duplicate-items-drift).

### Can one submission go to several boards at once?

Yes — stack recipes or share to multiple destinations; the item lives on all of them ([Item Locations](/features/item-locations) shows every board it's on).

### What about private destination boards?

The user who authorizes the automation needs access to the destination boards — a common gotcha with private boards ([permissions troubleshooting](/troubleshooting/permissions-error)).