Cross-Team Operations Dashboard with Bidirectional Sync

Overview

When your organisation grows beyond a single team, monday.com boards multiply fast. Engineering has their sprint board. Marketing has their campaign board. Support has their ticket board. And someone — usually an operations lead — is expected to keep track of everything across all of them.

The typical approach is a dashboard with mirror columns. But mirror columns are read-only — you cannot use them in formulas, filters, or automations. And changes only flow one way: from department boards to the dashboard.

This template solves both problems. Bidirectional status sync means updates on either the dashboard or the department board propagate in both directions. Mirror columns are copied to editable columns so you can build cross-team KPIs. And formula change triggers log every shift for an audit trail.

Who This Template Is For

• Operations managers overseeing multiple departments from a single view
• COOs and VPs who need real-time portfolio visibility without context-switching between boards
• Process improvement teams tracking cross-functional dependencies
• Scaling companies where coordination between teams is becoming the bottleneck

Board Structure

Central Operations Dashboard

Department Boards (Same Pattern for Each)

Each department board follows a consistent structure:

Setting Up the Automations

Automation 1: Bidirectional Status Sync

This uses the Sync Status Bidirectionally recipe.

What it does: When the operations lead updates a status on the dashboard, it propagates to the department board. When a department lead updates their board, it propagates back to the dashboard. Built-in loop prevention stops infinite cascading.

How to set it up:

1. On the Operations Dashboard, open the Automations Centre
2. Search for Community Cookbook recipes
3. Select: Keep a status in sync between this board and a connected board in both directions
4. Map the Overall Status column on the dashboard to the Status column on each department board
5. Repeat for each connected department board
6. Activate

The key benefit: the operations lead can update statuses directly on the dashboard during leadership meetings, and those changes immediately appear on department boards. No more "I updated the dashboard but forgot to tell Engineering."

Automation 2: Copy Mirrors to Editable Columns

This uses the Copy Mirror Column Value to Editable Column recipe.

What it does: Mirror columns showing department statuses are read-only. This recipe copies them into editable Status columns so you can use them in formulas that calculate cross-team health scores.

How to set it up:

1. On the Operations Dashboard, open the Automations Centre
2. Search for Community Cookbook recipes
3. Select: Read a mirror column and write its value to a real column
4. Map each mirror to its local counterpart:
   • Eng Status (Mirror) to Eng Status (Local)
   • Mkt Status (Mirror) to Mkt Status (Local)
5. Activate

Once the values are in editable columns, your Cross-Team Health formula can reference them. For example, assign numeric scores to each status (On Track = 3, At Risk = 2, Blocked = 1) and average them for an overall health score.

Automation 3: Log Formula Changes for Audit Trail

This uses the Formula Column Change Trigger.

What it does: Whenever the Cross-Team Health formula recalculates — because a department status changed, a priority shifted, or a timeline moved — the trigger fires. Use this to log the change on a separate audit board, update the Last Updated date, or notify leadership.

How to set it up:

1. On the Operations Dashboard, open the Automations Centre
2. Search for Community Cookbook recipes
3. Select: When a formula column's calculated value changes
4. Choose the Cross-Team Health formula column
5. Set the action to create an item on an Audit Log board with the current date and new value (or simply update the Last Updated date column)
6. Activate

This gives you an automatic history of how cross-team health has changed over time — invaluable for retrospectives and leadership reporting.

Tips and Variations

• Start small: Begin with two department boards and the dashboard. Add more departments as you refine the process. Each new department follows the same pattern.
• Colour-coded statuses: Use the same status labels and colours across all boards so the dashboard is instantly readable. Standardise on: Not Started (grey), In Progress (blue), On Track (green), At Risk (amber), Blocked (red), Complete (dark green).
• Weekly snapshots: Create a native monday.com automation that duplicates the dashboard items to a "Snapshots" board every Friday. This gives you week-over-week comparison without manual effort.
• Executive view: Create a dashboard view with charts showing: items by status (pie), timeline (Gantt), and health trend (chart widget pulling from the audit log).
• Escalation paths: Combine the bidirectional sync with the OR Status Trigger. When any department board item hits "Blocked", automatically notify the operations lead and escalate to the relevant VP.
• Cross-team dependencies: Add a Dependency column to the dashboard to show which initiatives are blocking others across departments. This makes stand-ups more productive.

What You Will Need

• A monday.com account (Standard plan or above for Connect Boards)
• Community Cookbook installed from the monday.com marketplace
• At least 2 department boards plus the central dashboard
• Connect Boards columns set up between the dashboard and each department
• About 30 minutes for initial setup (plus 10 minutes per additional department)

Frequently Asked Questions

Will the bidirectional sync cause infinite loops?+

How many department boards can I connect?+

Can different departments use different status labels?+

What if I only want one-way sync for some departments?+

How does this scale as we add more teams?+