Reporting dashboards: period results and exceptions

Reporting dashboards compare a defined period's results with targets and earlier periods, then identify the exceptions that require a decision. The useful output is a reconciled comparison with an explanation and an owner. A rising company total can still hide a business unit that is falling behind.

Start with the reporting contract

Before choosing a chart, write down the reporting period, the business units included, the accounting basis, and the source cutoff. A reader should know whether September is closed, whether an acquisition is included, and whether the target is the original budget or a revised forecast.

Use a small definition table for each measure: name, calculation, unit, source file, responsible owner, and comparison basis. Revenue might mean recognized net revenue after credits; margin might use direct costs allocated under an agreed policy. Those choices must hold across both periods.

The broader management reporting package provides the narrative, financial statements, and supporting schedules. This page concerns the period comparison within that package. For the choice of presentation format, see dashboard vs report vs list.

A practical layout has a company summary, business-unit comparisons, a short exception table, and a reconciliation status. Put the cutoff beside the title and the units beside each measure. Readers should not need to infer whether a number is dollars, orders, or a percentage.

Work the same business units through both periods

Consider an illustrative US business services company. Finance has closed August and September 2026. All amounts below are USD; net revenue excludes sales tax, and direct costs use the same classification in both months. The September revenue targets were approved before the period.

These are the grouped inputs from revenue, direct-cost, and budget exports. The spreadsheet columns are A through F in the order shown.

The first business unit occupies row 2. Calculate the revenue change, target gap, and current gross profit as follows:

Revenue change: =C2-B2
Target gap: =C2-D2
Target gap percentage: =(C2-D2)/D2
Gross profit: =C2-F2
Gross margin: =(C2-F2)/C2

Here, every revenue denominator is positive. If a real unit has no revenue or no target, show the corresponding ratio as unavailable and explain why. Keep its dollar amounts in the reconciliation.

Dollar amounts are exact; displayed percentages round to one decimal place from unrounded calculations. Total revenue rose by 20,000 / 600,000 = 3.3%, but missed target by 30,000 / 650,000 = 4.6%. The two comparisons answer different questions: whether the business grew and whether it delivered the plan.

Prove the summary before explaining it

The revenue bridge is 600,000 + 20,000 - 15,000 + 15,000 = 620,000. The target gaps also reconcile: -10,000 - 25,000 + 5,000 = -30,000. A dashboard that shows a different company variance has either omitted a unit or used another comparison basis.

Current gross profit is 620,000 - 381,750 = $238,250. August gross profit was 600,000 - 360,000 = $240,000. Profit therefore fell by $1,750 even though revenue increased. The gross profit margin calculation explains the ratio in more detail; here, the reporting question is which unit needs investigation.

Divide total gross profit by total revenue. Do not average the business-unit margins. As a second check, multiply each unit's unrounded margin by its revenue, add the products, and divide by total revenue. In Excel, SUMPRODUCT multiplies corresponding ranges and adds their products. That weighted calculation must also return 38.4% when displayed to one decimal place.

When grouping the underlying transaction export, SUMIFS supports multiple criteria, such as business unit and reporting period. Use identical row boundaries for the value and criteria ranges, and reconcile the grouped amount to the complete source export. Covirage is not affiliated with Microsoft.

Turn the exception into a decision

Suppose management's agreed revenue exception threshold is a shortfall of at least 5.0% against target. Central crosses it at 11.4%; North does not. Central's $25,000 shortfall should lead the exception table, even though the company shortfall of 4.6% is below the threshold.

Give Central's operating leader a question: does the gap arise from missing volume, lower realized prices, or credits? Ask finance to validate the direct-cost classification before attributing the unit's 35.0% margin to operating performance. The grouped table locates the issue; it does not prove its cause.

Record the action, owner, evidence required, and review date beside the exception. Keep the explanation provisional until the transaction detail supports it. If the next step is choosing a reporting application, use the separate dashboard software evaluation guide.

Where it goes wrong

• Changing the comparator. Replacing the approved target with a later forecast makes the same result appear better without changing performance. Label each comparison explicitly.
• Mixing closed and provisional periods. Late credits or cost postings can move a result after it was discussed. Preserve the reporting cutoff and identify subsequent adjustments.
• Averaging ratios. Business units have different revenue weights. Recompute company margins from summed amounts.
• Hiding exceptions in totals. Favorable South performance partly offsets Central's shortfall. Review units as well as the company figure.
• Treating a variance as a cause. A shortfall shows where to investigate. Validate the explanation against the underlying rows before assigning corrective work.

Check your reporting period in Covirage

Bring a sample of your own revenue, cost, and target files, or a Google Sheet, to Covirage; it maps the columns, and its tools compute and check period comparisons and 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 set up your business with a sample of your own export.

See self-service analytics for business teams for the supporting use case.