A monday.com RAG rollup for customer implementations works when every implementation shows one overall color set by a written rule, a one-sentence reason, and the date someone last checked it. Native monday.com features cover only part of that view, so the rule, the reason, and the weekly check are work you set up yourself. This guide covers the building blocks, the color rules, the roll-up levels, the points where native features stop, and a weekly routine that keeps the colors honest.
What should each customer row in the rollup show?
Each customer row should show one overall color, a reason in one sentence, the decision or help needed from the sponsor, the next step with an owner and date, and the date someone last checked the row. Keep the same fields for every customer so the executive can compare rows week to week.
- Write the question the executive asks about each customer, such as "Will [customer] go live on [date]?" One question keeps the rows comparable.
- Pick the few dimensions that matter for this rollout, such as schedule, scope, budget, and customer-side blockers. Each dimension gets its own rating, and each owner should be able to rate it honestly every week.
- Copy this row into the summary and to the top of each customer board:
[Customer name] implementation: [Green / Amber / Red]
Reason: [one sentence naming the blocker, slip, or decision needed]
From the sponsor: [decision, review, or help needed, or "none this week"]
Next step: [action], owner [name], by [date]
Last checked: [date]
Editorial judgment: the executive should read the color first and the reason second, so the reason sits directly beside the color. TechTide Solutions agrees that each RAG color should have a predetermined action, which is why the next step and sponsor line belong in the row.
Which monday.com building blocks do you need?
Test any formula or mirror column on one board before relying on it across all of them.
Plan details differ, so check each block in your own account. Use this table to decide what each block holds and what to test first.
| Building block | What it holds in the rollup | Test to run on one board first |
|---|---|---|
| Status column | The overall color, labeled Green, Amber, and Red exactly as in the rule sheet | Set one test item to Red and confirm the label matches the sheet word for word. |
| Text column | The one-sentence reason | Confirm the reason shows in the summary view without opening the item. |
| Date column | The last-checked date | Change the date and confirm the summary shows the new value. |
| Formula column | A value calculated from other columns on the same board, where your account offers one | Build it on one board and check its output against a few test rows you set by hand. |
| Mirror or connected column | A value copied from another linked board, where your account offers one | Mirror the color from one customer board into a summary board, change the source, and confirm the summary updates. |
| Dashboard table | The rows, shown as a table or chart | Check that the table can show the reason beside the color. |
A monday.com community feature request says dashboard widgets render as tables or charts, so plan for a table rather than a card layout.
- Duplicate one customer board so every board has the same column names as your rule sheet.
- Run the status, formula, and mirror tests above on that one board.
- Copy the structure to the other boards only after the tests work.
How do you set color rules people will agree to?
A simple rule uses the worst dimension rating as the overall color, and a weighted score suits a team where one dimension should count more. Agree the sheet with the executive before the first review.
- Write a test for each color, with placeholders:
- Green: [milestone] is on or before [agreed date], and every open blocker has an owner.
- Amber: [milestone] will pass [agreed date] unless [named decision or help] arrives by [date].
- Red: [milestone] has passed [agreed date], or [named blocker] has no path to resolution.
- Write the roll-up rule on the first line of the sheet, for example: "Overall is the worst dimension rating." If you use a weighted score, write each weight beside its dimension.
- Agree the sheet with the executive before the first review, so later debates focus on evidence rather than on the rules.
| Color | What the lead does next |
|---|---|
| Green | Keeps the normal update, and checks the reason and the date. |
| Amber | Names the owner of the risk and the date the help is needed. |
| Red | Puts the decision or help in front of the sponsor the same week. |
How do ratings roll up from task to implementation to portfolio?
The roll-up for customer implementations runs level by level: a task rolls up to its dimension, the dimensions roll up to the implementation color, and the implementation colors roll up to the portfolio. Under the worst-dimension rule, one Red dimension makes the implementation Red. Under a weighted score, the written weights decide the color.
Editorial judgment: applying the same rule at each level keeps the logic consistent. This is our recommendation, not a monday.com feature.
An illustrative example, with placeholder values and not real customer data:
- Dimensions for [Customer A]: schedule Amber, scope Green, budget Green, customer blockers Red.
- Worst-dimension rule: overall Red, because one dimension is Red.
- Weighted rule: write a weight for each dimension, such as [weight for schedule], and map the total to a color using [score bands agreed with the executive]. A weighted total can land on Amber even when customer blockers are Red, so add a floor to the sheet: "A Red in customer blockers makes the overall Red, whatever the weights say."
For the portfolio line, show each implementation with its color and reason, and set the portfolio reading to [agreed portfolio rule, such as the worst implementation color]. A Red portfolio should point to a named customer row, never to an unexplained color.
Where do monday.com's native rollups stop?
Monday.com users have requested a native executive status scorecard RAG dashboard widget. The support article describes project health as set by hand to Off Track, At Risk, or On Track, and describes portfolio roll-up as Enterprise-only. Keep the rule, the reason, and the weekly check as your own work.
We could read the monday.com support article on advanced projects only through its search summary, because the full page blocked access. Confirm the Off Track, At Risk, and On Track wording and the Enterprise-only point against your own plan before you promise either to an executive.
- Health is set by hand. The support article describes each project's health as set by hand. A color chosen at one review can be out of date by the next, so keep a last-checked date on every row.
- Portfolio roll-up depends on the plan. The support article describes linking project boards to a portfolio that rolls up progress across many projects. Without that feature, the summary table in the next section is your rollup.
- Dashboard widgets show tables and charts. The community request asks for a card-style scorecard, and the thread has no official reply, so plan for a table.
- Templates do not calculate the rollup. Analysistabs says its automated RAG calculation and multi-project portfolio rollup are in its premium packs, not in its free templates.
How do you build the executive view on a board?
The executive view is one summary table with the customer name, color, reason, and last-checked date for every implementation, sorted so Red comes first. Open a filtered view for Amber and Red before each weekly review, and read the reason column first.
- Name the summary board [Customer implementations: executive view].
- Bring in the color, reason, and last-checked fields from each customer board with mirror columns, if your account supports them. If it does not, paste the three fields in from each owner's message.
- Sort the table by color so Red rows sit at the top.
- Create a filtered view named [Amber and Red for review] and open it before each weekly review. The reasons show the blocker or decision behind each color.
- Share the full table only after the green check in the next section.
How do you catch a green row that hides a blocker?
The check for a green row that hides a blocker compares the color with the last milestone date and the open blockers before the executive sees it. A Green with a passed milestone or an unowned blocker is watermelon reporting: green on the surface, red underneath, and it goes back to the owner.
Ask these questions of each Green row:
- Is the last milestone date still ahead, or was it met? If the date has passed and the milestone is still open, the row is not Green.
- Does every open blocker have an owner and a date? If one does not, move the row to Amber at least.
- Does the reason name a fact, or only say "on track"? An empty or generic reason sends the row back to its owner.
- Is the last-checked date later than the last review? An older date means the color may no longer match the work.
An illustrative example with placeholder values: [Customer B] is Green, with the reason "on track." Its milestone [milestone] was due [date] and is still open, and [blocker] has no owner. The check moves the row to Red until the owner names a path, and the decision goes to the sponsor the same week.
Editorial judgment: the lead, not the owner, makes the final check on Green rows.
How do you get weekly colors without updating every status by hand?
Owners change a color only when dated evidence changes, and a summary built from their short messages goes to the lead for review first. Gravity's guide says statuses, due dates, and anything a client reads stay with a person, so the color stays a human decision.
- Send each owner this message on the same day before the review, with placeholders filled in:
Subject: [Customer name] status, week of [date]
Color: [Green / Amber / Red]
What changed since last week: [one sentence with the evidence]
Blocker or decision needed: [name it, or "none"]
- Owners change the color only when the evidence changes: a new date, a closed item, or a recorded decision.
- The lead runs the Green check above, then builds the summary from the messages.
- The summary goes to the executive with the Red and Amber reasons first.
If you use an AI tool to draft the summary, check its price first. Gravity's guide lists AI Blocks at eight credits per trigger, one item at a time, so per-item summaries across many implementations add up quickly.
This week, copy one customer board, write the rule sheet, and run one review with that owner before you build the next board.