Financial Dashboards: What to Show and What to Skip

A financial dashboard is a single view of the numbers a finance leader needs to run the business, built to answer specific questions quickly. This guide is part of business analytics for finance and operations, follows KPIs for CFOs and KPI scorecards, and leads to executive dashboard examples and Power BI vs. Tableau. The test of a good one is not how much it displays but how fast a reader can tell whether anything needs attention and what to do about it. Most dashboards fail that test. They show every number the system can produce, mix definitions, bury the three items that matter among thirty that do not, and are rebuilt by hand every month. This guide covers what to put on a financial dashboard and what to leave off, how to lay it out, how to handle targets and variances, how to keep the data reliable, and how to build one in stages. It includes worked examples for a 13-week cash view and a variance tile with checked arithmetic. The figures it shows come from budgeting and forecasting and from cash flow management.

Start with decisions, not data

Before choosing a chart, write down the decisions the dashboard should support and who makes them. A CFO may need to decide whether to draw on a credit line, whether to hold back discretionary spending or whether to adjust the forecast. A controller may need to decide where to focus the close review. A head of sales may need to decide where to chase collections. Each decision implies a small set of numbers. If a number does not inform any decision on the list, it does not belong on the page. This is the discipline that separates a dashboard from a data dump.

Write the questions in plain language: Do we have enough cash for the next 13 weeks? Are we on track to hit this quarter's revenue and margin? Where are we over or under budget, and why? Is working capital getting better or worse? What risks are growing? A dashboard that answers these five questions on one page is a strong first version for most finance leaders.

What to show

Cash and liquidity. The current cash balance, the 13-week forecast, the minimum cash level and headroom against it. A weekly line chart with a minimum-cash line is the clearest form. Cash is the one area where a surprise can be fatal, so it takes the top left of the page.

Performance against plan. Revenue, gross margin and operating profit for the month and year to date against budget and against last year. Show the variance in dollars and percent, and a one-line reason for the largest variances.

Working capital. Days sales outstanding, days of inventory and days payable, with the cash conversion cycle. Show the trend over 12 months, because a single month hides direction. See cash conversion cycle.

Forward indicators. Order backlog, pipeline, open purchase commitments, or whatever predicts the next quarter in your business.

Risk items. Customer concentration, covenant headroom, aged receivables over 60 days, aged inventory. These change slowly, so a compact table is enough.

Forecast accuracy. The error in last month's and last quarter's forecast, with bias. It tells readers how much to trust the forward numbers.

What to skip

• Anything nobody acts on. If the number has been on the page for a year and has never prompted a question, remove it.
• Detail that belongs in a drill-down. The full income statement belongs behind a link, not on the front page.
• Metrics without targets or comparisons. A number alone cannot be judged. Show a target, a prior period or a range.
• Decorative elements. Gauges, 3D effects, background images and heavy borders consume space and attention.
• Too many decimals. Showing revenue to the dollar when you manage to the thousand makes the page harder to read and implies false precision.
• Duplicates. Showing the same measure in a tile, a chart and a table.
• Vanity measures, which look good and drive nothing.

A worked cash example

A 13-week cash view needs few numbers. Suppose the company opens the period with $600,000 of cash, forecasts $2,340,000 of receipts over 13 weeks and $2,460,000 of payments (hypothetical), and its policy is to hold at least $400,000. Ending cash is 600,000 + 2,340,000 - 2,460,000 = $480,000, and headroom over the minimum is 480,000 - 400,000 = $80,000. On its own, a positive ending balance looks fine. But a weekly view might show that the low point falls in week 9, where timing of a payroll and a tax payment pushes cash to $360,000, below the minimum. The dashboard should therefore plot all 13 weeks with the minimum line and highlight the lowest week. The ending balance answers one question, and the low point answers the question that matters: when do we need to act? Include the forecast accuracy for cash from previous periods: if past 13-week forecasts missed receipts by 8 percent on average, then $2,340,000 of expected receipts could plausibly be $2,153,000 (2,340,000 × 0.92), which would take ending cash down to $293,000. That downside case, a drop of $187,000, deserves a place on the page as a second line.

A worked variance tile

A variance tile for revenue might show: actual $4.35 million, budget $4.80 million, variance -$0.45 million, or -9.4 percent (0.45 / 4.80 = 0.09375). Gross margin is 38.2 percent against 39.0 percent, a shortfall of 0.8 points. On revenue of $4.35 million, 0.8 points is $34,800 of gross profit (0.008 × 4,350,000). A good tile adds one sentence: "Revenue is 9.4 percent below budget, driven by delayed orders from two accounts worth about $310,000; margin is 0.8 points lower on mix." The reader sees the number, the size of the gap, the cause and the scale of the effect. Without the sentence, the tile creates a question for the finance team to answer by email.

Layout principles

1. Put the most important item top left, where eyes land first. For many finance leaders, that is cash.
2. Group related items, and give each group a small label.
3. Use consistent visual rules. The same color always means the same thing, such as red for unfavorable. Do not use red for decoration.
4. Show scale and context. Tiles with a trend line, a target and a comparison are more informative than a bare number.
5. Leave white space. Dense pages are tiring to read, and they hide what matters.
6. Design for the device and setting, such as a laptop in a meeting or a printed page in a board pack.
7. Link to detail. Each tile should lead to a table or report that shows what is behind it.

Targets, thresholds and status

Give every measure a target or a range and a rule for status. A common rule uses green when the measure is at or better than target, amber when it is within 5 percent and red beyond. For volatile measures, set wider bands or use a trailing average. Publish the rules in a definitions panel. See KPI scorecards.

Data and refresh

A dashboard is only as reliable as its data. Four rules prevent most problems.

1. Reconcile to the ledger. The revenue and profit figures on the dashboard should match the financial statements at each month-end. Build a check that compares them and flags differences.
2. Define once. Hold each definition in one place, such as a semantic model or a data dictionary, so that "revenue" means the same thing on every page. See single source of truth.
3. Show the as-of date and the data source on the page.
4. Automate refresh, and schedule it. A dashboard that depends on someone pasting numbers every month will be late, and it will occasionally be wrong.

Building in stages

Start with a spreadsheet version using last month's data and test it with two or three users. Ask what they looked at first, what they ignored and what they wished it showed. Revise. Then connect it to live data in a business intelligence tool, and add drill-downs. Add features only when users ask. A dashboard that is used and trusted is more valuable than an elaborate one that is not. See how to build an Excel dashboard.

Common mistakes

1. Starting with the data available instead of the decisions needed.
2. Too many measures.
3. No targets or comparisons.
4. Inconsistent definitions.
5. No reconciliation, which damages trust the first time numbers disagree with the reports.
6. Unclear ownership, so nobody maintains or retires items.
7. Treating the first version as final.

Showing the outlook, not just the past

A financial dashboard that reports only actuals is a rear-view mirror. Add an outlook tile that combines year-to-date actuals with the forecast for the rest of the year. Suppose first-half revenue is $8.9 million and the forecast for the second half is $9.2 million (hypothetical). The full-year outlook is 8.9 + 9.2 = $18.1 million, against a budget of $18.4 million, which is a shortfall of 0.3 million or (18.1 - 18.4) / 18.4 = -1.6 percent. Add a downside case beside it. If the second half comes in 5 percent lower than forecast, it would be 9.2 × 0.95 = $8.74 million, the full year would be 8.9 + 8.74 = $17.64 million, and the gap to budget would widen to (17.64 - 18.4) / 18.4 = -4.1 percent. Showing the base and the downside next to the budget gives leaders a sense of the range and the room for action. Label the forecast as a forecast, mark the date it was last updated, and show how accurate previous forecasts were.

Ownership and change control

Every dashboard needs an owner who is responsible for its accuracy, its definitions and its relevance. Keep a short change log on a hidden or reference tab: what changed, when, why and who approved it. When a definition changes, note the effect on history. Review the dashboard every quarter with its main users, and remove measures that have not been used. Without ownership, dashboards accumulate measures and lose focus, and without a change log nobody can explain why a number differs from last quarter's version.

Who sees what

Financial dashboards often contain sensitive information, such as margins by customer, salaries or covenant calculations. Decide in advance who may see which pages. Use role-based access in your tool, or maintain separate versions for different audiences, such as an executive page and a department page. Test the permissions with real accounts. Where data is shared with the board or lenders, produce a locked snapshot as a PDF so the figures cannot change after distribution.

FAQs

What should a financial dashboard include?

Cash and liquidity, performance against plan, working capital, forward indicators, key risks and forecast accuracy, each with a target or comparison.

How many metrics should a financial dashboard have?

Enough to answer the key questions on one page, often 10 to 15, with detail available by drill-down.

How often should a financial dashboard be updated?

Cash weekly or daily, most other measures monthly, with an as-of date on the page.

What is the difference between a dashboard and a report?

A dashboard gives a quick view of key measures for monitoring and decisions. A report presents fuller detail for analysis and record-keeping.

How do I make sure the numbers are right?

Reconcile to the ledger at each close, define each measure once and show the data source and as-of date.