Budget Variance Analysis for Managers: What Changed, Why and What to Do Next

A variance is not the answer. It is the starting point for a management question.

If a cost is above budget or revenue is below plan, the useful question is not simply “why are we off budget?” It is “what changed, what caused it, and what should we do next?”

Start With Materiality

Not every variance deserves the same attention.

Consider:

• absolute value;
• percentage difference;
• business importance;
• whether the issue is recurring;
• whether it affects future periods.

A 50% variance on a tiny cost line may matter less than a 4% variance on a major revenue stream.

Separate Favorable and Unfavorable Carefully

A favorable cost variance is not always good news.

For example, payroll may be below budget because critical roles are vacant, which could also reduce delivery capacity.

A favorable revenue variance may come from a one-off event that will not repeat.

Classify the Driver

Useful variance drivers include:

• price;
• volume;
• mix;
• timing;
• productivity;
• headcount;
• supplier cost;
• scope change;
• forecast assumption.

Example: Revenue Variance

Revenue is below budget by 8%.

Possible causes:

• lower sales volume;
• lower average selling price;
• customer mix shifted toward lower-value products;
• planned sales occurred later than expected;
• one major account did not renew.

Each cause requires a different management response.

Example: Payroll Variance

Payroll is below budget.

Ask:

• Were planned roles not hired?
• Were employees hired later?
• Was overtime lower?
• Did people leave?
• Did contractors replace employees elsewhere in the P&L?

The financial result cannot be interpreted without the operating explanation.

Separate Timing From Structural Change

A timing variance moves between periods.

A structural variance changes the expected future.

If a project invoice was delayed from September to October, the annual result may be unchanged. If customer demand has permanently fallen, the forecast should change.

Compare Actual, Budget and Forecast

Managers should look at three views:

• Budget: what was originally planned.
• Actual: what happened.
• Forecast: what is now expected.

This avoids the mistake of using an outdated budget as the only reference.

Ask for the Operational Driver

For each material variance, write one sentence:

“The variance occurred because…”

If the explanation uses only another financial number, keep going until the operating cause is clear.

Decide Whether Action Is Required

Possible actions include:

• change price;
• reduce discretionary spend;
• accelerate hiring;
• change supplier;
• reallocate budget;
• adjust sales activity;
• revise project scope;
• update the forecast.

Do Not Chase Every Variance Back to Zero

Management should not automatically force actual results back to the original budget if conditions changed legitimately.

The goal is sound performance, not artificial compliance with an old assumption.

Use a Variance Commentary Template

• Line item:
• Variance:
• Primary driver:
• Temporary or structural:
• Management action:
• Forecast impact:
• Owner:
• Review date:

Look for Repeated Patterns

If the same variance appears every month, the issue may be the budget model rather than execution.

Repeated patterns may reveal:

• poor forecasting assumptions;
• unrealistic productivity targets;
• chronic vacancies;
• unstable demand;
• persistent supplier inflation.

Break Variance Into Price, Volume and Mix Where Useful

For revenue and direct cost, managers can often learn more by separating three common effects.

• Price: did the selling or purchase price change?
• Volume: did quantity change?
• Mix: did the combination of products, customers, suppliers, or services change?

This is useful because a revenue shortfall caused by lower volume needs a different response from one caused by discounting.

Build Variance Ownership Into the Monthly Review

Each material variance should have an operational owner who can explain the driver and proposed action.

Finance can support the analysis, but the manager closest to the activity should understand the business cause.

Use Variance to Improve the Forecast

If a variance reveals that an assumption has changed, update the forecast.

Examples:

• supplier inflation is likely to continue;
• a customer contract has been delayed;
• a planned hire will start later;
• sales conversion is structurally lower;
• project scope has expanded.

Do not wait until year-end to acknowledge information already visible today.

Distinguish Controllable and Uncontrollable Drivers

Managers should focus action where they have influence.

An exchange-rate movement may be outside the manager’s direct control, but purchasing timing, hedging policy, supplier terms, or pricing response may still be manageable.

Use Trend, Not One Month Alone

One unusual month can mislead. Look at:

• current month;
• year-to-date;
• rolling trend;
• forecast.

A persistent small variance can matter more than one large temporary spike.

Example Commentary

“Travel cost is 14% above budget because the implementation team added two unplanned site visits. The overspend is temporary and the project remains within total budget. No corrective action is required, but October travel has been reforecast lower.”

That is more useful than simply reporting that travel is unfavorable.

Separate Volume, Price and Efficiency Effects

A useful variance explanation goes beyond saying that a line is over or under budget. Ask which driver moved.

• Volume: did the business sell, produce, hire, or use more or less than expected?
• Price or rate: did the unit price, salary rate, supplier rate, or selling price differ from the assumption?
• Mix: did the business sell or consume a different combination of products, people, or services?
• Efficiency: did the activity require more time, material, or effort than planned?
• Timing: did the cost or revenue simply land in a different month?

This distinction matters because each driver requires a different management response.

Favorable Does Not Always Mean Good

A favorable cost variance can reflect smart control, but it can also reflect delayed hiring, deferred maintenance, under-investment, or work that was not completed.

Likewise, an unfavorable variance can sometimes be intentional if management chose to spend more to protect revenue, quality, safety, or a strategic priority.

Always connect the number back to the operating reality.

Write a Three-Line Variance Commentary

For material variances, managers should be able to write a short commentary:

1. What changed? State the size and direction of the variance.
2. Why? Identify the operational driver.
3. What now? Explain the management action or the reason no action is required.

Example:

“External contractor cost is above plan because two permanent vacancies remained open longer than expected. Recruitment is now complete, so contractor use should reduce over the next two months. No further expansion of contractor scope will be approved without director review.”

Review the Forecast After the Variance

A meaningful variance should often change the forecast. If a cost or revenue driver has shifted structurally, keeping the old forecast simply because it matches the budget hides useful information.

The budget remains the original plan. The forecast should reflect the current expectation.

Read the variance in the context of the decision

A variance is the difference between what was planned and what happened, but the sign does not tell managers what to do. Higher revenue may appear favorable until you see that it came from discounts, unusual demand or a costly change in product mix. A lower expense may appear favorable because maintenance was deferred or employees were not hired when needed. Define the relevant outcome, the time period, the source data and whether the number measures revenue, cost, profit, cash or a nonfinancial result.

Begin by reconciling the actual and budget definitions. Check currency, units, cut-off dates, one-off adjustments and whether a transaction was assigned to the correct team or period. A budget-to-actual comparison cannot explain operations if the two figures were calculated differently. Ask finance to confirm the data before managers spend time debating a story that may be a reporting artifact.

A worked example: explain the bridge rather than the headline

Consider a purely illustrative monthly service operation. Its plan includes revenue of 100 units of currency and direct operating cost of 60, leaving planned contribution of 40. Actual revenue is 92 and actual direct cost is 68, leaving contribution of 24. Contribution is therefore 16 lower than planned: 8 from revenue underperformance and another 8 from higher direct cost. The arithmetic identifies the scale of the issue, not its root cause.

The manager must now ask whether sales volume fell, realized pricing changed, a higher-cost customer segment grew, overtime increased or supplier charges moved. Distinguish factors the team can influence from assumptions that should change in the forecast. A single high-level variance figure cannot decide whether a new price, staffing model or service standard is justified.

Separate volume, price, mix and timing effects

For revenue, test whether fewer units were sold, average realized price changed or the mix shifted to lower-value products. For cost, check whether higher volumes legitimately required more resources, input prices rose, productivity changed or spending was delayed from a previous period. For projects, identify whether a timing difference simply moves cost between months or signals a genuine full-year overrun. A timing difference can matter for cash even when expected annual cost is unchanged.

Where the business has reliable quantity and price records, finance can build a more detailed reconciliation. Use consistent units and avoid double-counting a mixed change in volume and price. If the data do not permit a defensible decomposition, state that limitation and prioritize the most consequential questions for investigation rather than inventing exact percentages.

Turn investigation into management action

A good variance meeting does not end with the observation that spending is “high” or sales are “low.” Assign a person to verify the main driver, agree the action they can take and identify the expected evidence in the next period. A recurring supplier premium may call for procurement review; persistent rework needs process diagnosis; a shift in client demand may justify updating assumptions rather than pressuring teams to meet an obsolete target.

Separate one-off corrections from structural changes. If a delivery delay caused temporary overtime, examine the incident and whether recurrence controls are needed. If a core cost assumption has changed for the year, update the forecast and inform decision-makers who rely on it. The decision should match the cause instead of treating every unfavorable variance as a reason for across-the-board cost cuts.

Questions executives should ask before reacting

• Are the plan and actual measured on a comparable basis?
• Which parts are volume, price, mix, productivity or timing?
• What evidence confirms the proposed explanation?
• Is the driver controllable, temporary or structural?
• Does the problem affect cash, quality, people or customers as well as profit?
• Who owns the next decision, and what should change before the next review?

Good variance analysis makes the next action more intelligent. It does not turn every accounting difference into a reason for urgent intervention.

Where to Go Next

The Budgeting, Forecasting and Cost Control course develops budget construction, forecasting, variance analysis, cost control and management action. Managers who need broader financial literacy can use Financial Management for Non-Finance Managers.

Variance analysis becomes useful when it moves from reporting the gap to explaining the driver and deciding what management should do next.