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

# Case Study: One Intake Form, Every Team's Board — 200 Columns, Zero Manual Mapping

> How an operations team routed monday.com form submissions to the right team boards in sync — replacing a ~200-column manual mapping project with name-based column syncing.

## The setup

An operations team takes all requests through a monday.com form that lands on one intake board — roughly **200 columns** of request data per submission. Each request then needs to reach the responsible team's board, stay in sync as it's worked, and leave the original submission untouched on the intake board (their audit requirement).

Their first plan was native automations: "when item created, create item in team board" plus per-column value-setting. Mapping \~200 columns by hand across several destination boards was the blocker — tedious to build and worse to maintain every time a column changed.

## What they built instead

With [Same Item Multiple Boards](https://monday.com/marketplace/10000363):

* **Name-based syncing killed the mapping project.** Columns with matching names and types sync on their own ([how matching works](/features/column-mapping)) — nothing to configure per column. The destination boards simply hold the subset of columns each team needs.
* **Deliberate non-syncing by renaming.** For the few fields a team should see but not have overwritten, they *renamed the column* on the destination board — no name match, no sync. The simplest field-level control there is.
* **The original stays pristine.** The intake board remains the system of record; teams work on the same item from their own boards, and every update is visible everywhere ([updates sync](/features/updates-sync)).
* **Permissions were the real gotcha.** Routing to private team boards failed until the user who authorized the automations was added to those boards — the automation acts as its authorizer ([permissions troubleshooting](/troubleshooting/permissions-error)).

## The outcome

Form intake routes itself. The mapping spreadsheet was never built, adding a column to the flow means adding it (same name) to the boards that need it, and "which version of this request is real?" stopped being a question — there is only one item.

## Steal this setup

1. Form → intake board, untouched originals.
2. [Automation](/features/automations): "when item is created / when Department is set → share item to team board."
3. Match column names on destination boards for what should sync; rename what shouldn't.
4. Add the automation's authorizing user to every private destination board.

Full pattern write-up: [Send form submissions to multiple boards](/guides/form-submissions-to-multiple-boards).