The setup
A performing-arts organization runs each production and internal project on its own monday.com board — clean ownership per team, but leadership had no single view of everything in flight. Their first attempt was the classic one: a “master board” filled by create-item automations. It produced the classic result — copies whose statuses no longer matched the source boards, and a master board nobody trusted.What they built instead
With Same Item Multiple Boards, the key items from every project board also live on one master board:- Real Kanban lanes. Because the shared items’ status columns are real columns (not mirrors), the master board’s Kanban view groups and drags like any native board — something mirror columns can’t do.
- Origin labels. An automation on each project board stamps a label column with the board’s name before sharing, so every card on the master shows where it came from.
- Automated cleanup. Completed items leave the master board on a timer — a date-based automation removes them from the master a week after completion while they stay on their source boards, matching the org’s retention preference and keeping the control tower focused on live work.
- Bulk onboarding, in batches. Existing in-flight items were shared to the master with batch actions in small groups (~15 at a time) to stay clear of monday API rate limits — the recommended approach for bulk syncing.
The outcome
One board answers “what’s in flight and where is it stuck?” — without a human synchronizing it. Project teams never changed how they work; the master board is simply where their items also are.Steal this setup
- Create the master board with a group per team or per stage.
- On each project board: one automation to stamp the origin label, one to share the item to the master on your trigger status.
- One automation on the master to remove items N days after completion.
- Backfill current work with batch actions, ~15 items per batch.