Blog · Board and management reporting
Design a revenue dashboard around a reconciled bridge and its contributing sales rows. This guide covers the source file, worked figures, spreadsheet formulas and controls for product, customer and regional reviews.
A revenue driver analysis dashboard connects a revenue change to the sales rows that explain it. Build the view around a reconciled bridge, then place customer, product and regional contributions beside it so reviewers can turn the figures into specific follow-up work.
Start with the question the finance and sales meeting must answer: what explains the revenue movement, and which accounts or products need attention? A sales trend alone shows direction but cannot separate more units, different realized prices and customer turnover.
Choose the comparison, currency, net-sales definition and treatment of credits before designing the page. Keep the price volume mix formulas as the owner of the detailed calculation method when that decomposition fits your products. The dashboard's job is to make the chosen method and its evidence reviewable.
For general sales performance layouts, see sales dashboard examples. This design gives the revenue bridge priority over activity measures or a broad collection of sales indicators.
Use posted sales lines for both periods, including credits. Keep line ID, date, customer ID, product code, quantity, selling unit, net revenue, region and reporting period. Match stable codes rather than descriptions, and define how reassigned customers are attributed to regions.
Reconcile each period's net revenue to its ledger total before explaining the difference. Keep a separate adjustment line for timing differences or commercial credits that cannot honestly be assigned a quantity and unit price.
The illustrative US distributor below compares two equal periods in USD. Each row has one product and one selling unit. Alpha is retained, Beta has no current sales, and Gamma has no prior sales. Those are comparison-period classifications, not claims about the lifetime customer relationship.
| Customer | Prior quantity B | Prior price C (USD) | Current quantity D | Current price E (USD) | Prior revenue F (USD) | Current revenue G (USD) |
|---|---|---|---|---|---|---|
| Alpha, retained | 1,000 | 100 | 1,100 | 96 | 100,000 | 105,600 |
| Beta, inactive | 200 | 100 | 0 | 0 | 20,000 | 0 |
| Gamma, new | 0 | 0 | 300 | 100 | 0 | 30,000 |
| Total | 120,000 | 135,600 |
Calculate F as =B2*C2 and G as =D2*E2, filled through row 4. Revenue rose $15,600, or $15,600 / $120,000 = 13.0%, rounded to one decimal place.
For this view, classify new and inactive accounts first. Apply quantity changes at prior prices and realized price changes at current quantities only to retained rows. This avoids counting new-customer revenue in a second driver.
| Driver | Calculation from the rows | Movement (USD) |
|---|---|---|
| Retained quantity | (1,100 - 1,000) × 100 | 10,000 |
| Retained realized price | 1,100 × (96 - 100) | -4,400 |
| Inactive customer | 0 - 20,000 | -20,000 |
| New customer | 30,000 - 0 | 30,000 |
| Total change | 10,000 - 4,400 - 20,000 + 30,000 | 15,600 |
The proof is $120,000 + $10,000 - $4,400 - $20,000 + $30,000 = $135,600. Put prior revenue in J2, the four movements in J3:J6 and current revenue in J7. The visible residual is:
=J7-(J2+SUM(J3:J6))
It returns zero. A nonzero result means the bridge is incomplete or uses a different scope from the revenue totals. Do not hide the difference inside a generic driver just to make the chart close.
This example uses a matched-row quantity effect, not a separate pooled mix calculation. If you add mix, use a documented method with comparable units and recalculate the bridge consistently.
| Area | Display | Review purpose |
|---|---|---|
| Scope strip | Periods, USD, net-sales policy, comparison method | Establish what every figure includes |
| Revenue summary | 120,000 prior; 135,600 current; 15,600 change; 13.0% growth | State the result |
| Bridge | Opening total, four driver movements, closing total | Explain the movement |
| Contributor table | Customer, product, region, driver and contributing amount | Show the supporting rows |
| Reconciliation | Zero residual and ledger tie status | Establish whether the view is complete |
| Follow-up table | Commercial explanation, owner and next action | Turn the review into work |
A waterfall is a useful chart for the bridge. Microsoft's waterfall chart guidance explains that it shows a running total as values are added or subtracted. Set the opening and closing columns as totals; treat the drivers as movements, and keep their signs visible.
Keep a flat contributor worksheet named Drivers with customer in A, product in B, region in C, driver in D and signed amount in E. If H2 names a region and I2 names a driver, its contribution is:
=SUMIFS(Drivers!$E:$E,Drivers!$C:$C,$H2,Drivers!$D:$D,$I2)
Microsoft documents SUMIFS as summing values meeting multiple criteria. Use this to build region and driver tables from the same contributions, rather than maintaining separately typed summaries. Product analysis dashboards cover the broader product review beyond this bridge.
Covirage is not affiliated with Microsoft.
Finance owns the reconciliation and method; sales owners explain account movements. A useful review ends with an explanation tied to rows, rather than a chart color interpreted as a cause.
Bring a sample of your own sales export with periods, customers, products and revenue, plus comparable quantities when available. Covirage maps the columns, its tools compute and check the figures, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account, set up your business and bring your file to work through the comparison.
See revenue driver analysis for the supporting approach behind a bridge that reconciles.
Include the reporting scope, prior and current revenue, the change, a driver bridge and a contributor table. Show the reconciliation residual beside the bridge. Add product, customer and regional breakdowns only when their fields are consistently available in the source sales rows.
Yes, but it can explain revenue movements by customer, product or region rather than separating price from quantity. Keep those limits visible. Revenue alone does not establish a realized price change, so do not fill a missing quantity column with invented units.
Choose whether the selection shows that region's contribution to the company bridge or calculates a separate regional bridge. Label the choice clearly, since mix calculations can change when the reference population changes. All displayed totals must follow the same selection rule.