Visual Hierarchy in Dashboards: How to Make the Right Thing Obvious
Most dashboard problems aren’t “data problems.” They’re attention problems.
If everything on a BAS dashboard looks equally important, operators have to think too hard to figure out what matters. That costs time, increases errors, and turns the interface into a screen people tolerate instead of trust.
Visual hierarchy is the discipline of arranging information so the operator’s eyes naturally land on the right thing first—without needing instructions, tribal knowledge, or five clicks of exploration.
This post lays out how to build visual hierarchy in building automation dashboards so abnormal conditions stand out, routine actions are obvious, and the UI feels fast.
What Visual Hierarchy Means (In BAS Terms)
Visual hierarchy is simply:
The system of cues that tells an operator what to look at first, second, and third.
In a BAS environment, hierarchy should help an operator answer these questions at a glance:
What’s wrong right now?
Where is it?
How bad is it?
What do I do next?
If the dashboard can’t answer those quickly, the operator has to create their own hierarchy mentally—and that’s where mistakes happen.
The #1 Rule: Normal Should Be Quiet, Abnormal Should Be Loud
A high-performing dashboard behaves like a good control room:
Normal conditions blend into the background
Exceptions demand attention
If “everything is colorful,” nothing is meaningful.
Practical implications:
Don’t light up the whole screen with bright statuses.
Reserve strong emphasis for things that require action: alarms, offline equipment, overrides, failed starts, out-of-range conditions.
The Operator Attention Stack (Design Around This)
Operators naturally prioritize by risk:
Safety / shutdown conditions
High-priority alarms
Comfort-critical deviations
Equipment down or in manual
Efficiency and optimization
Your dashboard should match that stack.
If “energy savings” is visually louder than “critical alarms,” the dashboard is lying to the operator.
The 5 Building Blocks of Visual Hierarchy
1) Size: Big = Important
The most important information should literally take up more visual real estate.
Use size for:
alarm count by priority
top exceptions list
critical system status (plant, AHUs, primary zones)
“what changed” since last shift
Avoid:
giant decorative graphics that don’t change operator decisions
making everything the same size
2) Placement: Top-Left Is Prime Real Estate
People scan screens predictably. Put the most important information where the eye goes first.
Typical dashboard placement:
top left: critical status / alarm summary
top center: building/system health overview
upper right: quick actions (acknowledge, navigate, open console)
lower areas: trends, KPIs, deeper detail
If an operator has to scroll to see critical issues, you’ve already lost.
3) Contrast: Use It Sparingly and Deliberately
Contrast draws attention—so if you use it everywhere, it works nowhere.
Use contrast for:
alarm states
overrides
comm loss/offline
failed starts
severe out-of-range
Keep everything else visually calm.
4) Grouping: Related Things Must Live Together
Grouping reduces cognitive load. It makes the UI feel “organized” and easier to trust.
Group by:
system type (AHUs, plant, lighting)
function (supply, return, outside air)
workflow (alarms → diagnosis → action)
Avoid scattering related points across multiple panels.
5) Labels: Clarity Beats Cleverness
Labeling is a huge part of hierarchy because labels define meaning.
Good labeling:
consistent naming conventions
units shown when relevant (°F, %RH, kW, psi)
status vs command clearly separated
setpoint vs actual clearly separated
Bad labeling forces guessing—and guessing causes mistakes.
Make the “Next Action” Obvious
Many dashboards show information but don’t show what to do.
If a unit is in fault, the dashboard should guide the operator:
where to drill down
what to check first
how to view history/trends
whether it’s in override or locked out
which related equipment is impacted
Even simple UI patterns help:
“View Equipment” button
“View History” button
“Open Alarm Console” button
“View Trends” link for the exact equipment
Good hierarchy isn’t just “what stands out.” It’s also “where do I go next?”
Common Dashboard Hierarchy Mistakes
Mistake 1: Too many colors
If every status is bright, nothing is meaningful.
Mistake 2: KPIs louder than problems
Energy charts are great—until they hide a failed AHU.
Mistake 3: No exception summary
Operators shouldn’t have to find what’s wrong. The dashboard should tell them.
Mistake 4: Data density without prioritization
A screen full of points isn’t information. It’s a burden.
Mistake 5: Inconsistent layouts across equipment
If each AHU page looks different, every page costs time.
A Simple “Hierarchy Checklist” for BAS Dashboards
If you want a quick gut-check, answer these:
Can someone see critical issues in 5 seconds?
Are alarm counts and priorities obvious?
Are overrides impossible to miss?
Is command vs status clearly separated?
Is setpoint vs actual always presented the same way?
Is there a consistent drill-down path from overview → equipment → trends?
Does the design stay calm when everything is normal?
If the answer is “no” for any of these, hierarchy is your opportunity.
The Bottom Line
Visual hierarchy is how you make dashboards feel fast.
It reduces:
operator errors
time-to-diagnosis
wasted clicks
training time
missed issues and slow responses
And it increases trust—because a good dashboard behaves like a good operator: it prioritizes.
Want a Quick Hierarchy Review?
If you send an overview dashboard screenshot and one equipment page (AHU/plant), we can point out what’s stealing attention, what’s being under-emphasized, and what layout changes would make the right thing obvious—without rebuilding your entire system.
