Blog · Board and management reporting
A tabular dashboard compares business units through consistent columns of results, targets, and exceptions. Build one from operating exports, check the totals, and give each exception an owner.
A tabular dashboard compares business units in rows, with consistent columns for actual results, targets, and exceptions. It is useful when a manager needs the exact amount behind a status and a clear place to start investigating. The table works only when every row uses the same period, units, and calculation rules.
Build the table around a recurring question: which units missed their revenue targets, exceeded their spending budgets, or need an explanation? Avoid filling it with every column available in an export. A useful dashboard lets the reader move from a result to a specific owner and next action.
The U.S. Web Design System's table guidance describes tables as a way to organize structured information for comparison and recommends brief, scannable cell content. For a business review, that means amounts belong in the comparison table and lengthy explanations belong below it.
Use one row per business unit for the selected period. If a unit has multiple product lines, summarize those lines before placing the unit beside its peers. Mixing detail rows with their subtotals invites double counting and makes large units look more important simply because they occupy more space.
For a monthly revenue and spending review, bring the revenue export, operating expense export, approved budget, and business-unit ownership list. Retain the underlying transaction identifiers so a reviewer can trace a total to the contributing rows.
The revenue file needs a posting date, business-unit identifier, and net revenue amount. The expense file needs the same date and unit conventions with the expense amount. The budget needs period, unit, revenue target, and expense budget. Match on the unit identifier and period rather than on a display name that may change.
Before calculating anything, decide how credits, reversals, shared costs, and late postings are treated. Record the reporting cutoff in the table caption. A correct comparison is still misleading if actuals include a closed period while the budget includes an extra month.
Consider a US business reviewing September 2026. The first table contains the summarized source amounts. All amounts are USD, and expense amounts are displayed as positive spending.
| Business unit | Revenue actual (USD) | Revenue target (USD) | Expense actual (USD) | Expense budget (USD) |
|---|---|---|---|---|
| East | 240,000 | 250,000 | 120,000 | 125,000 |
| Central | 180,000 | 180,000 | 81,000 | 75,000 |
| West | 100,000 | 120,000 | 63,000 | 60,000 |
| Total | 520,000 | 550,000 | 264,000 | 260,000 |
Use separate calculations for revenue performance and spending control:
Revenue variance = Actual revenue − Revenue target
Revenue attainment = Actual revenue / Revenue target
Spending index = Actual expense / Expense budget
Revenue attainment improves as it rises. A spending index above the budget means an overrun, so the direction is different. The following table displays percentages rounded to one decimal place; retain full precision in the calculations.
| Business unit | Revenue variance (USD) | Revenue attainment | Spending index | Exception to review |
|---|---|---|---|---|
| East | −10,000 | 96.0% | 96.0% | Revenue below target |
| Central | 0 | 100.0% | 108.0% | Spending above budget |
| West | −20,000 | 83.3% | 105.0% | Revenue and spending |
| Total | −30,000 | 94.5% | 101.5% | Revenue and spending |
East's revenue calculation is 240,000 / 250,000 = 96.0%. Central's spending calculation is 81,000 / 75,000 = 108.0%. West's revenue shortfall is 100,000 − 120,000 = −$20,000.
The written exception rule here is deliberately simple: flag revenue below target and spending above budget. A separate RAG dashboard explains how to add graduated thresholds when the review needs several levels of severity.
The revenue variances must reconcile: −10,000 + 0 − 20,000 = −$30,000, which also equals 520,000 − 550,000. Spending exceeds budget by 264,000 − 260,000 = $4,000. Those identities provide direct checks on the summarized dashboard.
Total revenue attainment is 520,000 / 550,000 = 94.5%. It is not the simple average of the unit percentages, which would be 93.1% using unrounded inputs. The correct calculation weights units by their targets because the dashboard asks how much of the combined target was achieved.
Tie revenue actuals and expenses back to the source exports separately. Then check that every expected unit appears once, no transaction appears twice, and the budget contains no duplicate period-and-unit combinations. Keep missing budgets visible as unavailable comparisons rather than turning them into zero targets.
For additional examples of denominator and reconciliation failures, see bad dashboard examples.
Place comparable numeric columns next to each other. Use the same precision down a column and put the currency or unit in its header. Sort by the issue the meeting will address, while keeping a stable unit identifier available for reference.
Write descriptive headers such as revenue target rather than target when several targets appear. The W3C tables tutorial explains that accessible data tables need clearly associated headers and cells. A business reader benefits from the same clarity when a table is copied into a report or viewed with assistive technology.
Use color as an extra cue alongside text. W3C guidance on use of color calls for a visible alternative when color conveys information. An exception label such as spending above budget remains understandable without a red background.
West needs a revenue explanation and an expense review. Central needs a spending explanation even though it met its revenue target. East needs a revenue discussion, but its spending result should not be presented as an overrun.
Finance owns the reconciliation and calculation definitions. Business-unit leaders own the explanations and corrective actions. The report preparer owns the period label, completeness checks, and consistent layout. An accountability dashboard can carry the resulting actions and due dates without crowding this comparison table.
Bring your revenue, expense, and budget exports with the same period and unit identifiers. Covirage maps the columns, and its tools compute the comparisons and check the totals; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, which takes about a minute, and bring a sample of your own data after setting up your business.
See self-service analytics for the supporting business workflow.
Use a table when readers need exact values, several measures for the same business units, or a list of exceptions to investigate. A chart may explain a trend more quickly, while the table provides the amounts and ownership needed for follow-up.
Start with the reporting period, business unit, actual result, target, absolute variance, percentage comparison, and exception label. Add an accountable owner where action is required. Keep units in column headers so readers can distinguish dollars, hours, counts, and percentages.
Calculate it from the summed numerator and denominator. For revenue attainment, divide total actual revenue by total target revenue. A simple average of unit attainment percentages gives a small unit the same influence as a large one and can misstate performance.
No. Include a written status and the underlying variance so the meaning survives printing and remains understandable to readers who cannot distinguish colors. State whether higher or lower results are desirable, and make the thresholds visible beside the table.