A dashboard can show the right number and still leave a person unsure what to do. ?Profit below budget? identifies a result. It does not explain the cause, distinguish an assumption from a fact or assign the follow-up.
We designed our management reporting workspace so the summary leads to an explanation and then to owned actions. The sample report gives us a concrete way to discuss what belongs between a headline figure and a decision.
Start with a question the dashboard must answer
The report shows operating profit of AUD 50,000 against a budget of AUD 65,000. Rather than leaving the AUD 15,000 gap as a red card, the variance view explains it: AUD 12,000 less gross profit and AUD 3,000 of additional operating costs.
The revenue shortfall is broken down by stream. Retained services are AUD 10,000 below budget, project delivery is AUD 20,000 below and training matches the plan. With the sample gross margin unchanged at 40%, the AUD 30,000 revenue gap accounts for AUD 12,000 of the profit difference.
These are authored reporting figures, but the design problem is real: the reader needs to know which part of the result warrants attention before deciding what to investigate.
Explain the gap behind the headline figure
Distinguish explanation from assumption
The management note attributes the project gap to two deliverables moving beyond the reporting cut-off. It does not assume that the missing revenue will automatically return next month. The resulting action is to confirm revised delivery dates before revisiting the forecast.
That distinction should survive the visual design. A chart can show the gap. A note can explain management's current interpretation. A task can record what must be checked before that interpretation becomes a planning assumption.
Putting all three under ?insights? would make them sound equally settled. Separate labels are more useful than a clever umbrella term.
Let the count lead to a manageable queue
The action page shows two open actions, one overdue within those open actions, and one completed action. ?Overdue? is a subset of ?open,? not another item to add to the total.
The records then explain the work. One owner is checking delivery dates. Another is reconciling software seats and distinguishing unused seats from necessary service accounts. A completed payroll review records that no reclassification was made, so the reported variance remains.
This is why we design the destination before the dashboard card. If the next screen cannot explain the count, the count is not ready to be useful.
From number to action
- 01DefineState the period, unit and scope of the figure.
- 02InspectOpen the contributing records with the filter retained.
- 03ActAssign the decision or follow-up to an owner.
Give status a meaning beyond colour
An overdue action needs its due date and owner. A completed action needs an outcome. Colour can support those distinctions, but it cannot carry them alone.
The same applies to financial direction. A negative cost variance does not always mean a worse result. In this example, lower direct costs accompany lower revenue. The profit bridge explains the combined effect instead of presenting every negative number as an alert.
Keep definitions, units and periods close to the figures. A reader should not need to open an unrelated methodology document to discover whether they are comparing a closed month with a partial one.
Design for missing and stale data
A dashboard needs an answer when an input has not arrived. Zero, unavailable and unchanged are different statements. If the system has no current data, displaying zero may turn a technical problem into a false business conclusion.
Our monitoring exception workspace offers another setting for this principle: a reading and the rule that flags it should remain inspectable. The exception-handling article explains how the next action changes with the kind of interruption.
Open the work behind the dashboard count
For charts that carry important information, include a text explanation or accessible table. W3C's complex-image guidance provides the accessibility reference. The benefit for the working team is equally direct: people can discuss the same definition rather than interpreting a graphic differently.
We start custom software development with the decisions and records behind the screen. The business process modeling guide explains that groundwork. Once it is clear, dashboard design becomes a question of how quickly someone can move from ?what changed?? to ?what needs my attention??
Sources and calculation notes
The sample report reconciles AUD 65,000 budget operating profit to AUD 50,000 actual: a revenue gap of AUD 30,000 at the stated 40% gross margin gives AUD 12,000 less gross profit, plus AUD 3,000 extra operating costs. The action register contains two open actions (one overdue) and one completed action; overdue is a subset of open. Figures describe the portfolio dataset.
- Our client reporting and action review project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- Our monitoring exception and review project. The project page includes the design account, delivered scope and screenshots discussed in this article.
- W3C complex images. Supports text descriptions of information carried in complex visual material.
External references checked on 31 October 2026.