Planning4 September 20264 min read

A dashboard per role: why one Command Center isn't one screen

A lot of business software starts with one ambitious dashboard: every figure, every job, every invoice on one screen. In practice, such a screen is clear for no one, because a technician needs different information than an owner, and a planner needs something different again than someone in admin. This article looks at why a shared dashboard often disappoints, and how a home screen per role, with a separate action center for what needs attention now, solves that.

Why doesn't one dashboard for the whole business usually work?

A dashboard that tries to show everything quickly turns into a long list of widgets everyone has to search through themselves for what is relevant to them. That filtering costs time, and that time is exactly what a dashboard is supposed to save.

Worse, information that is crucial for one role, like outstanding invoice amounts for an owner, is noise for another role, like a technician on the road, that only distracts from what he needs to know right now: which job is scheduled next.

The result is that people leave the shared dashboard alone and fall back on their own method: a chat group, a separate notepad, or simply calling. Exactly the behaviour the system was supposed to replace.

What does a home screen per role solve?

Instead of one dashboard for everyone, a role-based home screen shows only what is relevant to that person's task. A technician sees his route and today's jobs, a planner sees the day at a glance, and an owner sees the figures that matter for the overview of the business.

TelMaar calls this the Command Center: every user logs into the same platform, but the home screen adapts to the role. That is not a different application per role, but the same underlying data, presented differently based on what someone needs to do their job.

That distinction prevents a technician from having to scroll through screens full of invoices to reach his schedule, and prevents an owner from having to wade through planning details to find a revenue overview.

What is an Action Center and why does it stand apart from the rest?

Alongside the role-based overview, there is a need for something else: what needs a decision NOW, regardless of which part of the dashboard that would normally sit in. A job with no technician assigned, an invoice past its due date, or a quote about to expire.

An Action Center gathers these signals at the top of the screen, separate from the rest of the overview, so they do not disappear among the daily routine information. The idea is that you never have to search for what needs attention; the system lets it surface on its own.

It is important that an Action Center stays selective. A list that flags everything, including things that can wait, quickly loses its value: people learn to ignore it, just like a smoke alarm that goes off too often for nothing.

How does this connect to the path from job to cash?

A role-based dashboard is not a goal in itself, it exists to shorten the path from a job to getting paid. A planner who quickly sees which job still has no technician plans faster. A technician with a clear route and jobs finishes work faster. An admin employee who sees which invoices are outstanding can follow up more precisely.

Every step in that chain, from planning to execution to job sheet to invoice to payment, has a different owner at a different moment. A dashboard that ignores that distinction forces everyone to figure out for themselves what is relevant in a process that should actually flow smoothly.

The Command Center and the Action Center are therefore not separate features, but a way to make that entire chain visible to whoever needs to act on it at that moment.

What should you look for when judging a dashboard per role?

Test whether the system actually shows different screens to different roles, or whether it just hides or shows a few widgets without adjusting the core of the overview. That difference determines whether it was really built for multiple roles or lightly adapted afterwards.

Look critically at what gets marked as 'action required'. If everything is shown as urgent, nothing is really urgent in practice; the value of such a signal stands or falls with restraint.

And ask whether new roles or teams can easily get their own tailored view, or whether that can only be adjusted by the supplier itself. A growing business will sooner or later get a role that does not exist yet.

Frequently asked questions

Do all users see the same data in a role-based dashboard?

The underlying data is the same, but the presentation differs per role. A technician sees different screens than an owner, even though the figures come from the same system.

What should and shouldn't belong in an Action Center?

Only what genuinely needs a decision now, such as a job with no technician or an overdue invoice. A list that flags too much loses its value because people start ignoring it.

Is a Command Center the same as separate reports?

No, reports show what has happened. A Command Center mainly shows what needs attention now, adjusted to the role of the user logging in.

This article is general information, not tax or legal advice. When in doubt, consult an adviser; rules can change.