Owner routines
A building dashboard that does not hide uncertainty
A dashboard looks reassuring, yet its green indicators include tasks waiting for acceptance and records that have not been updated.
A useful summary shows the quality and freshness of the information behind the status.
Start with the decisions the owner needs to make. A summary of overdue work, blocked approvals and unresolved recurring issues may be more useful than a large collection of activity counts. Each indicator should explain its time period and inclusion rules so readers do not compare unlike measures.
Keep administrative progress distinct from outcomes. A request received, a provider contacted and work accepted are different stages. Combining them into a single completion number can create a misleading impression. If information is stale, say so. An empty field should not silently become a positive result.
Use the dashboard as a doorway to evidence. The owner should be able to find the relevant issue, responsible person and next action without searching another system from scratch. Where the underlying process is still a demonstration or manual workflow, label that clearly. A polished display is not evidence that data collection, notifications or follow-up are operational. Document corrections when a count is wrong so readers understand what changed between the two reports.
Put it into practice
- Define what each status and measure means.
- Display missing updates and pending acceptance separately.
- Link important indicators to the underlying record and its date.
What to verify
Sample the records behind the dashboard. Confirm that the displayed count matches its stated definition and that unknowns are not counted as satisfactory results.
Check three dashboard indicators against their source records.