Every month, finance teams across Switzerland produce variance reports that say some version of the same thing: revenue was below budget, costs were above budget, EBITDA missed by CHF X. And every month, the CEO reads those three lines, nods, and asks the question the report did not answer: “Yes, but why?”
That gap between what most variance reports say and what leadership actually needs to know is not a data problem. The numbers are usually right. It is a communication problem, and specifically a failure to distinguish between describing a variance and explaining it.
Describing a variance is easy. Explaining it requires breaking it down into its component causes: how much of the miss came from selling less volume than planned, how much came from selling at a different price than planned, how much came from selling a different mix of products or clients than planned, and how much is simply a timing difference that will reverse next month. That decomposition is called a bridge, and it is one of the most valuable analytical tools a controller can put in front of a leadership team.
This article walks through how to build a variance bridge step by step, how to translate it into commentary that a CEO actually reads, and what distinguishes analysis that drives decisions from analysis that just fills a slide.
Why Most Variance Commentary Fails
Before the method, it is worth understanding why the standard approach does not work.
The typical variance report presents a table of actuals versus budget with a CHF gap and a percentage next to each line. The commentary, if it exists at all, restates the number in sentence form. “Revenue was CHF 120K below budget, representing a shortfall of 8.3 percent.” That sentence contains no information that was not already in the table. It is not commentary. It is transcription.
The reason this pattern persists is that it is safe. A controller who says “revenue missed by CHF 120K” has not committed to an explanation. A controller who says “the revenue miss was driven by a volume shortfall on Product A, partially offset by a price increase on Product B, with a timing delay on one client accounting for the remainder” has taken a position. Positions can be wrong. Transcription cannot.
But a management report that never takes a position is not helping anyone manage the business. The controller’s job is to have a view and to explain it clearly enough that leadership can challenge it, refine it, or act on it. That requires a bridge.
What a Variance Bridge Is
A variance bridge, sometimes called a waterfall analysis, is a structured decomposition of the gap between two numbers: usually budget versus actual, but the same method works for prior period versus current period or prior year versus current year.
The bridge breaks the total variance into its component causes and quantifies each one individually. The components add up to the total variance, which means the bridge is both an explanation and a proof: if your components do not sum to the total gap, you have missing causes or calculation errors.
For a revenue bridge, the standard components are:
Volume effect: How much of the variance is explained by selling more or fewer units than planned, at the budgeted price and mix? This isolates pure volume movement.
Price effect: How much of the variance is explained by selling at a different price than budgeted, assuming the volume and mix were as planned? This isolates the impact of pricing decisions or market pricing pressure.
Mix effect: How much of the variance is explained by selling a different combination of products, services, or clients than planned? A business that sells proportionally more of a low-margin product than budgeted will miss its gross profit even if total volume and average price are on target.
Timing effect: How much of the variance is explained by revenue or costs that belong to the current period but have not yet been recognised, or that were recognised early? Timing effects reverse in subsequent periods and should be clearly separated from structural variances.
The same logic applies to cost bridges. A personnel cost variance can be decomposed into a headcount effect (more or fewer people than planned), a rate effect (paying more or less per head than budgeted), and a mix effect (a different seniority or role composition than planned). An operating expense variance can be decomposed into a volume effect (costs that are genuinely variable and moved with activity) and a fixed cost variance (costs that should not have moved at all but did).
Building a Revenue Bridge: Step by Step
The following walks through the mechanics of a revenue bridge. The accompanying Excel file contains a worked numerical example you can adapt.
Step 1: Establish your start and end points.
The bridge starts at budget and ends at actual. The total variance is the gap between them. Write down the total variance first. Everything else must explain this number exactly.
Example: Budget revenue CHF 1,450K. Actual revenue CHF 1,310K. Total variance: CHF -140K.
Step 2: Calculate the volume effect.
The volume effect answers: if we had sold at the budgeted price and the budgeted mix, how much revenue would we have generated at actual volume?
Formula: Volume effect = (Actual units sold minus Budgeted units sold) multiplied by Budgeted average selling price.
If you budgeted 1,000 units at CHF 1,450 average and sold 950 units, the volume effect is (950 minus 1,000) multiplied by CHF 1,450, which equals CHF -72,500.
This tells you that CHF 72,500 of the revenue miss came purely from selling fewer units, before any price or mix effect is considered.
Step 3: Calculate the price effect.
The price effect answers: for the units we actually sold, how much revenue did we gain or lose because we sold at a different price than budgeted?
Formula: Price effect = (Actual average selling price minus Budgeted average selling price) multiplied by Actual units sold.
If you sold 950 units at an actual average of CHF 1,378 versus a budgeted CHF 1,450, the price effect is (CHF 1,378 minus CHF 1,450) multiplied by 950, which equals CHF -68,400.
Step 4: Calculate the mix effect.
The mix effect is often the most complex and the most misunderstood. It captures the revenue impact of selling a different proportion of high-value versus low-value products or clients than planned.
The simplest approach for the one-page commentary is to calculate mix as the residual: total variance minus volume effect minus price effect minus any identified timing effects. If the residual is material, it warrants a more granular analysis by product or client segment. If it is small, flag it as a minor mix shift and move on.
In more sophisticated analyses, particularly for businesses with distinct product lines or client tiers, the mix effect is calculated line by line: for each product or segment, compare its actual weight in the revenue total versus its budgeted weight, and multiply the difference by the segment’s budgeted revenue contribution. The sum of all segment mix effects equals the total mix effect.
Step 5: Identify and isolate timing effects.
Timing effects require a judgment call. They are revenue or costs that will appear in a subsequent period and therefore represent a genuine expectation that the full-year picture is unchanged. Isolating them matters because they change the interpretation entirely: a CHF 70K miss due to a delayed delivery that ships next week is a very different message from a CHF 70K structural shortfall.
To identify a timing effect: can you point to a specific transaction, invoice, or delivery that was planned for this period and will occur in the next period? If yes, quantify it and present it as a timing item. If no, it is not a timing effect and should not be labelled as one.
Step 6: Verify that your components sum to the total variance.
Volume effect plus price effect plus mix effect plus timing effect must equal the total variance. If they do not, you either have an unidentified cause or a calculation error. Do not present a bridge where the components do not sum correctly. Leadership will notice, and it will undermine everything else in the report.
Step 7: Translate the bridge into commentary.
The bridge is an analytical tool. The commentary is the communication product. They are not the same thing. A controller who presents the bridge as a series of formulas in a meeting has done the analysis but not the job. The job is to turn the bridge into a narrative that a non-finance reader can follow in sixty seconds.
From Bridge to Commentary: What Good Looks Like
Using the example above, here is what the commentary should look like:
“Revenue missed budget by CHF 140K in October. The miss breaks down as follows: CHF 73K was driven by lower-than-planned volumes on Product A, where two orders were pushed to November by a client scheduling change. CHF 68K reflects a pricing adjustment made in Q3 on a contract renewal that was not fully reflected in the October budget. The remaining CHF 1K is a minor mix effect from selling proportionally more of our lower-priced configurations this month. The timing component (CHF 73K) will reverse in November. The pricing adjustment is structural and the full-year budget should be updated to reflect it. Net of timing, the underlying revenue shortfall is approximately CHF 67K, which management should monitor but which does not yet require intervention.”
Notice what this commentary does. It gives leadership the total number, breaks it into three causes, quantifies each one, distinguishes between what is temporary and what is structural, and tells them what the appropriate response is. A CEO reading this knows exactly what happened, why it happened, and what to watch next month. They can ask a specific question or make a specific decision. That is what variance commentary is for.
Now compare it to: “Revenue was CHF 140K below budget due to lower volumes and a pricing adjustment.” That sentence is technically accurate and completely useless.
Applying the Same Logic to Cost Variances
Revenue bridges get most of the attention, but cost bridges are equally important, especially for businesses where the controller’s primary value-add is cost discipline rather than revenue management.
For personnel costs, the bridge typically has three components:
The headcount effect: actual FTE multiplied by budgeted cost per head, minus budgeted FTE multiplied by budgeted cost per head. This isolates the cost of having more or fewer people than planned.
The rate effect: actual FTE multiplied by actual cost per head, minus actual FTE multiplied by budgeted cost per head. This isolates the cost of paying differently than budgeted, whether from salary increases, overtime, or a different seniority mix than planned.
The mix effect: if you have multiple employee categories or cost centres, the mix effect captures the impact of having a different composition than budgeted.
For operating expenses, the bridge is simpler:
Variable cost variance: actual variable costs minus (budgeted variable cost rate multiplied by actual activity). This tells you whether variable costs are behaving as expected at actual activity levels.
Fixed cost variance: actual fixed costs minus budgeted fixed costs. Fixed costs should not move with volume. If they do, the classification was wrong or there is a genuine spend control issue.
The Four Questions Every Variance Commentary Should Answer
Regardless of which line item you are commenting on, every piece of variance commentary should answer four questions:
What is the variance and how big is it relative to the total? A CHF 50K miss on a CHF 5M revenue base is a rounding issue. A CHF 50K miss on a CHF 500K revenue base is a ten-percent shortfall requiring attention. Context matters.
What caused it? Volume, price, mix, timing, or a combination. Name the cause specifically.
Is it structural or temporary? Structural variances require a response: a revised forecast, a pricing decision, a cost action. Temporary variances require monitoring. The most common mistake in variance commentary is treating a structural issue as a timing problem to avoid an uncomfortable conversation.
What happens next? One sentence on the expected trajectory and any action being taken. Leadership does not need a full action plan in the monthly report, but they need to know whether somebody is on it.
A Note on Presenting the Bridge to Non-Finance Audiences
The bridge as an analytical framework is not always the right format to present to a board or a CEO. Not everyone thinks in waterfalls. When presenting to non-finance audiences, convert the bridge into plain language first, and have the bridge available as a backup if someone asks how you arrived at the numbers.
The bridge is your working. The commentary is your conclusion. Lead with the conclusion.
Why This Matters Beyond the Monthly Report
The discipline of building proper variance bridges does something beyond improving your monthly report. It builds a model of how the business actually works: which revenue lines are price-sensitive, which costs move with volume and which are genuinely fixed, where timing differences are structural features of the business versus genuine exceptions.
Over time, a controller who produces rigorous bridge analyses every month develops an increasingly precise understanding of the business levers. That understanding is what allows the controller to shift from reporting what happened to contributing to discussions about what should happen next. That is the difference between a reporting function and a controlling function, and it is ultimately what separates a finance team that leadership turns to for guidance from one they turn to for numbers.
The Excel file accompanying this article contains a worked variance bridge example for a revenue line and a personnel cost line, with the step-by-step calculations and a waterfall chart you can adapt to your own numbers.
Download the Variance Bridge Template
If your current management reporting does not include a variance bridge and you want to introduce one without disrupting your existing process, book a free 30-minute call at /contact.html.
Ready to improve your financial reporting? Book a free 30-minute call to discuss your situation.
Alessandro Ratzenberger is a fractional CFO and business controller based in Zurich, with 15 years of operational finance experience at Dufry Group and Bomi (UPS Group).
