A dashboard full of numbers still makes the reader do the work of deciding which are good and which are bad. Conditional formatting shifts that judgment onto the dashboard itself, coloring each value by whether it is on target, marginal, or in trouble, so status is read before the number is. This guide explains how traffic-light or RAG coloring turns raw KPI values into at-a-glance status, the threshold-design mistakes that undermine it, and why dashboard color conventions differ from the color rules used on process HMIs.
Conditional Formatting (Dashboards) in one line: Conditional formatting is a dashboard technique that changes the color of a value based on where it falls against defined thresholds, most commonly a red-amber-green (RAG) or traffic-light scheme in which green means on target, amber means marginal, and red means a problem. It converts a raw KPI into an immediate status the reader perceives before reading the digits, letting someone scan many metrics and spot the ones that need attention at a glance. Its usefulness depends entirely on the thresholds behind the colors being set sensibly, and its color meanings are a management convention distinct from the alarm-color rules used on process HMIs.
Color is processed pre-attentively - the eye registers it before the conscious mind reads a number - which is exactly why conditional formatting works. By mapping each KPI to a color based on its value, a dashboard lets a manager take in the status of dozens of metrics in a single sweep, landing on the red ones without having to read and mentally evaluate every figure. The traffic-light metaphor carries its meaning for free: green is understood as good, amber as caution, red as stop-and-look, so no legend study is required to grasp what the dashboard is saying.
The RAG scheme's power is that it compresses a continuous number into a discrete status the reader actually needs. A manager scanning a production dashboard rarely needs to know that a figure is exactly ninety-four percent of target; they need to know whether it is fine, slipping, or failing. Conditional formatting makes that classification the dominant visual, with the precise number available underneath for anyone who wants it. The same idea extends beyond simple color fills to data bars, heat-map cells, and icon sets, but the principle is constant: encode the judgment about a value into an instantly perceived visual, so the reader spends attention only on what is off.
Conditional formatting is only as trustworthy as the thresholds that assign the colors, and this is where it most often goes wrong. Thresholds set carelessly - arbitrary round numbers, limits copied from a different metric, or bands that do not reflect real acceptable performance - produce colors that mislead. If green is defined too generously, a metric quietly drifts into a bad state while still showing green, and the dashboard gives false comfort. If red trips too easily, the dashboard lights up with reds that do not warrant action, and the reader learns to ignore the color entirely, which is worse than having no color at all.
Several subtler pitfalls compound this. A threshold that flips a value between amber and green on tiny fluctuations makes a metric flicker distractingly right at the boundary, so bands usually need a buffer to stay stable. Static thresholds can become stale as a process or a target changes, leaving the colors calibrated to conditions that no longer apply. And a dashboard where too many tiles are colored at once loses the whole benefit, because if everything is colored, nothing stands out - the same failure mode that afflicts an over-colored HMI. Good conditional formatting is therefore restrained: thresholds grounded in genuine performance limits, bands wide enough to be stable, colors reserved so that a red genuinely means something, and the scheme reviewed as targets evolve.
It is tempting to assume the reds and greens on a management dashboard mean the same thing as the reds and greens on a control-room HMI, but they follow different conventions and it matters to keep them separate. On a process HMI, color coding is governed by operational and safety conventions: color is used sparingly, often reserved almost entirely for abnormal and alarm states, and its meanings are tied to specific alarm priorities and equipment conditions that demand a defined operator response. A green element on an HMI frequently just means running or normal, and heavy use of color is deliberately avoided so that a genuine alarm stands out.
Dashboard conditional formatting serves a management audience and a different purpose, so its color use is broader - many tiles may be colored at once to express performance status across an operation, and amber routinely marks a metric that is merely off target rather than an actionable alarm. Confusing the two can be dangerous: a dashboard's red does not necessarily call for the same immediate, procedure-driven response that an HMI alarm does, and treating a management RAG status as if it were a safety alarm, or vice versa, misreads what the color is telling you. In a well-run environment the dashboard's RAG scheme is documented and understood as a performance convention, deliberately distinct from the alarm-color standard that governs the operators' screens. Where they share a platform, the design keeps the audiences and the meanings apart on purpose.
RAG stands for red, amber, green, the traffic-light color scheme used in conditional formatting to show a KPI's status at a glance. Green indicates the metric is on target, amber that it is marginal or slipping, and red that it is in trouble and needs attention. The scheme works because color is perceived before the number is read, letting someone scan many metrics and immediately see the ones that are off.
Base them on genuine performance limits - a real target, a contractual or historical acceptable band - rather than arbitrary round numbers, and make each band wide enough that a value hovering near a boundary does not flicker between colors. Review the thresholds as targets and conditions change so the colors stay meaningful. Avoid coloring so many tiles at once that nothing stands out, since over-coloring destroys the at-a-glance benefit.
No. HMI alarm coloring follows operational and safety conventions, uses color sparingly and reserves it largely for abnormal states, and ties specific colors to alarm priorities that demand a defined operator response. Dashboard conditional formatting is a management convention that colors many performance metrics at once, where a red often means merely off target rather than an actionable safety alarm. They should be kept distinct so a management color is not mistaken for a control-room alarm.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.