Not what it could show. Not what it was configured to show during the implementation. What it actually shows you when you open it this morning.

For most FM teams that have a dashboard — whether it’s their CMMS reporting module, a custom Power BI setup, or a vendor-provided analytics interface — the honest answer is one of three things: charts showing historical data they already know, metrics that require significant interpretation before they’re actionable, or a view they stopped checking regularly because it didn’t tell them what they needed to know before they needed to know it.

The FM dashboard problem is not a technology problem. It’s a design problem. Dashboards are built by people who think about data. They’re used — or not used — by people who think about decisions.

→ How operational visibility connects to maintenance program effectiveness: Commercial Building Maintenance Guide

The FM dashboard problem is not a technology problem. It’s a design problem. Dashboards are built by people who think about data. They’re used by people who think about decisions.

What Most FMs Would Say If Asked This Morning

Ask a Director of Facilities to pull up their dashboard right now and answer three questions:

  • Question 1: Which work orders in your portfolio are at risk of SLA breach today?
    Most dashboards can tell you how many work orders are open. They typically don’t surface which ones are trending toward breach before the breach happens — they report breaches after they occur.
  • Question 2: Which vendors have the lowest first-time completion rate across your portfolio in the last 90 days?
    Most dashboards can show total work orders by vendor. They rarely calculate first-time completion rate automatically and surface it in a ranked view without requiring manual export and analysis.
  • Question 3: What is your PM completion rate for this quarter — not scheduled, but executed with documented evidence of completion?
    Most CMMS dashboards show PM schedule compliance — the percentage of PMs that were dispatched on time. They don’t distinguish between a PM that was dispatched and a PM that was completed with a service report uploaded at close. Those are different states.

If the answer to all three of these questions requires pulling a report, exporting to a spreadsheet, and doing manual analysis — the dashboard isn’t reducing the FM’s decision-making burden. It’s adding a step between the FM and the answer they need.

The Difference Between a Dashboard That Shows Data and One That Shows Decisions

Every FM dashboard shows data. The ones that get opened every morning and drive operational decisions are built on a different design principle: they show the next required action, not the last recorded event. The distinction in practice:

EXAMPLE 1 SLA Breaches

Data-oriented: “You have 47 open work orders.”

Decision-oriented: “You have 3 work orders breaching SLA in the next 4 hours. Here are the vendor contacts and the current status of each.”

EXAMPLE 2 PM & Compliance

Data-oriented: “Your PM schedule is 82% on track.”

Decision-oriented: “6 PMs are overdue as of today. 2 are in life safety categories. Here are the asset locations and the last service dates.”

EXAMPLE 3 Vendor Performance

Data-oriented: “Vendor A completed 34 work orders this quarter.”

Decision-oriented: “Vendor A has a 58% first-time completion rate this quarter — the lowest in your portfolio. 3 open work orders are currently assigned to them.”

The data in both views is the same. The dashboard design determines whether the FM has to interpret it or act on it.

What the Dashboard That Gets Used Every Morning Looks Like

Based on the operational requirements of commercial FM — managing multiple assets, vendors, compliance timelines, and work order queues across one or more locations — the dashboard that drives daily FM decisions has five sections, each answering a specific operational question:

  • 1. Critical Now: What requires immediate action today? SLA breach risk, overdue life safety items, compliance exposure flagged since yesterday’s close. This section should have zero items on a well-run day. When it has items, the FM knows exactly what they are and what action is required.
  • 2. Pending Decisions: What is waiting for FM input before it can move? Vendor estimates awaiting approval. Invoice discrepancies flagged for review. Work orders where the vendor has raised a scope question. Repair vs. replace recommendations from the PM that came in yesterday. The FM’s job in this section is to clear the queue — not to find out what’s in it by searching.
  • 3. PM and Compliance Status: What is the executed PM completion rate for this period — not scheduled, executed? Which compliance items are due in the next 30 days? Which vendor certifications are expiring in the next 60? This section runs in the background; the FM reviews it when it surfaces a flag, not on a manual pull.
  • 4. Vendor Performance: What is the current SLA compliance rate by vendor for the last 30 days? Who has open work orders past the expected completion date? This section doesn’t require a quarterly scorecard review — the score is live, and the FM sees which relationships need attention without waiting for the next vendor review cycle.
  • 5. Budget and Spend: What is the current maintenance spend against budget for this period, by site and by trade? What invoices are pending payment — and have they been matched against the corresponding work orders and completion documentation?

The Metric That Tells You If the Dashboard Is Working

One number captures FM dashboard effectiveness: the percentage of work order exceptions the FM identifies through the dashboard before they escalate, versus the percentage they learn about when someone calls or the situation has already deteriorated.

An FM team that learns about SLA breaches when vendors call to explain, about compliance gaps when the inspector arrives, and about invoice discrepancies when the CFO asks — is managing reactively regardless of what the dashboard shows. The information existed. The dashboard didn’t surface it at the right moment.

The Operational Standard

An FM team that opens the dashboard each morning and clears a defined set of decisions — SLA risks, pending approvals, overdue PMs, vendor flags — before the first tenant call arrives is managing the operation from the front. The dashboard is doing the work of collecting, filtering, and surfacing information. The FM is doing the work of deciding. The former model exists everywhere. The latter is what a dashboard that actually reduces FM workload looks like. The gap between them is not the data — it’s whether the dashboard was designed around the data or around the decisions.

Sources: