What is a flexible budget?
A flexible budget is a budget that adjusts to the actual level of activity a business achieves. Instead of fixing every cost line at a single assumed volume for the year, it separates costs into fixed and variable components and recalculates the variable portion once actual output is known. Performance is then judged against what spending should have been at the volume the business actually delivered — not against the volume someone guessed at twelve months earlier.
That distinction sounds technical, but it changes what your variance report means. Compare actual costs to a static budget and every variance is a blend of two things: how efficiently the business operated, and how far actual volumes drifted from the planning assumption. A cost centre can look wildly over budget simply because the business sold more than planned — which is usually good news dressed up as bad. A flexible budget strips the volume effect out, so the variance that remains is a genuine efficiency signal.
Flexible budgets are a staple of management accounting for exactly this reason: they make cost accountability fair. An operations director who is asked to explain a £40,000 overspend caused entirely by a 15% jump in orders will, quite reasonably, stop taking the budget seriously. Flex the budget first and the conversation becomes about the 2% of overspend they can actually influence.
The flexible budget formula
The flexible budget formula is:
Flexible budget = fixed costs + (variable cost per unit × actual activity)
Three inputs, each of which forces a useful discipline:
- Fixed costs — the spend that does not move with volume within the relevant range: rent, salaried headcount, insurance, most software licences.
- Variable cost per unit — the budgeted rate at which cost should scale with activity: materials per unit, freight per shipment, payment fees per transaction, support cost per ticket.
- Actual activity — the volume the business really achieved in the period, measured in whatever driver the variable rate is expressed in.
A worked example
A manufacturer budgets a production cost centre at £180,000 of fixed cost per month plus £22 of variable cost per unit, and plans for 10,000 units. The static budget is therefore £180,000 + (£22 × 10,000) = £400,000.
In March the plant actually produces 11,500 units and spends £441,000. Against the static budget that is a £41,000 overspend — an alarming headline. But flex the budget to actual activity first:
Flexible budget = £180,000 + (£22 × 11,500) = £433,000
| Line | Static budget (10,000 units) | Flexed budget (11,500 units) | Actual | Variance vs flexed |
|---|---|---|---|---|
| Fixed costs | £180,000 | £180,000 | £183,500 | £3,500 adverse |
| Variable costs | £220,000 | £253,000 | £257,500 | £4,500 adverse |
| Total | £400,000 | £433,000 | £441,000 | £8,000 adverse |
Of the £41,000 headline variance, £33,000 is a volume variance — the plant made 1,500 more units, and variable cost is supposed to rise with output. Only £8,000 is a genuine spending variance the production manager should be asked about. The flexible budget turns a misleading number into two honest ones.
Flexible vs static budgets
| Static budget | Flexible budget | |
|---|---|---|
| Activity assumption | One volume, fixed at approval | Recalculated to actual volume each period |
| Cost treatment | All lines set as absolute amounts | Split into fixed amounts and variable rates |
| What a variance means | Efficiency and volume effects mixed together | Efficiency isolated; volume shown separately |
| Effort to maintain | Low — set once, compare monthly | Moderate — requires cost classification and clean driver data |
| Best suited to | Stable, predictable cost bases; fixed spending envelopes | Volume-sensitive operations; volatile demand |
| Risk | Punishes or rewards managers for volumes they don't control | Can excuse poor volume performance if used carelessly |
The two are not rivals so much as tools for different questions. The static budget remains the commitment — the number the board approved and the target bonuses hang off. The flexible budget is the analytical lens you place over actuals to understand why the business is beating or missing that commitment. Mature finance teams keep both: static for accountability to the plan, flexible for accountability to efficiency.
When flexible budgeting works — and when it doesn't
Where it earns its keep
- Manufacturing and production — the classic case: material, labour and energy costs scale with units, and volumes rarely land on plan.
- Logistics and fulfilment — carriage, packaging and warehouse labour flex with shipment counts.
- Customer operations — support and onboarding costs that scale with customers, tickets or transactions.
- Usage-based technology costs — cloud infrastructure, payment processing and API fees are variable costs in all but name, and static budgets handle them badly.
- Any business with volatile demand — seasonal, project-based or fast-growing companies, where the static volume assumption is stale within a quarter.
Where it struggles
- Mostly-fixed cost bases. A professional services firm or a SaaS business whose costs are overwhelmingly salaries gains little: there is not much variable cost to flex, so the flexed budget barely differs from the static one.
- Step costs. Some costs are fixed until a threshold — one warehouse shift until volume forces a second. A simple linear rate misstates these; you need step logic, which adds modelling effort.
- Poor driver data. If actual activity can't be measured reliably and promptly, the flex is only as good as the guess it rests on.
- As an excuse machine. Flexing must never be allowed to absorb a revenue miss. If volumes fell 20%, the flexed cost budget falls too — but someone still has to answer for the volume. Keep the volume variance visible, not buried.
How to build a flexible budget
- Classify every cost line as fixed, variable or stepped. Be honest — "semi-variable" lines should be split into their fixed and variable components rather than fudged.
- Choose the driver for each variable line. Units produced, orders shipped, tickets resolved, transactions processed — the driver should be the thing that genuinely causes the cost, and it must be measurable from your systems each month.
- Set the budgeted rate per driver unit from history, adjusted for known price changes. This rate is itself a target: procurement savings show up as a favourable rate variance.
- Define the relevant range. Fixed costs are only fixed within limits. State the volume band the model holds for, and flag when actuals approach the edge of it.
- Flex monthly, automatically. The flexed budget should be a calculated column in your reporting, refreshed with actual driver volumes at close — not a spreadsheet someone rebuilds by hand.
A note on semi-variable and step costs, because they trip up most first attempts. A cost like warehouse labour is often fixed in the short run and stepped in the medium run: one shift handles up to 14,000 units, then a second shift adds a lump of cost. Model the step explicitly rather than smearing it into an average rate — an average rate will flatter you below the threshold and ambush you above it. Utilities, maintenance and overtime usually split cleanly into a fixed floor plus a variable rate once you regress a year of actuals against the driver; an afternoon with the data is enough for a workable first cut.
Flexible budget variance analysis in practice
Once the flexed budget exists, the monthly variance analysis splits cleanly into layers, each with a different owner:
- Volume variance — static budget vs flexed budget. This is the cost consequence of activity landing away from plan. It belongs to whoever owns the demand number: sales, commercial, or the market itself. It should be reported next to the revenue variance it mirrors, because more volume usually means more revenue as well as more cost.
- Rate variance — did each unit of activity cost what it was supposed to? A freight rate that crept from £4.10 to £4.45 per parcel shows up here, even in a month when total freight spend looked unremarkable because volumes dipped. Rate variances are procurement and operational-efficiency territory.
- Fixed cost variance — the fixed base against its budget, which should be boring. When it isn't — an unbudgeted hire, an early renewal — the explanation is usually a discrete, nameable event rather than a trend.
This decomposition is what makes monthly cost reviews fast. Instead of debating a single blended number, each variance already points at its owner and its cause. A useful habit: publish the three layers in the management pack every month with one line of commentary each, and reserve discussion time only for variances that persist for two consecutive periods. One-month noise is rarely worth a meeting.
Two refinements matter as the process beds in. First, watch for rate variances that are really mix: if the average cost per unit rose because customers bought a more expensive product mix, that is commercial news, not operational failure — split mix out if it is material. Second, revisit the budgeted rates themselves at least twice a year. A rate set generously stops being a target and becomes a hiding place; inflation-era rates left unrevised do the opposite, manufacturing adverse variances nobody can action.
Flexible budgets, driver-based planning and rolling forecasts
A flexible budget is really the entry point to a bigger idea: that the P&L is an output of operational drivers, not a list of independent numbers. Once you have classified costs and tied each variable line to a driver rate, you have built the skeleton of a driver-based planning model. The same rates that flex last month's budget can project next quarter's costs from a demand forecast — which is precisely how a rolling forecast stays light enough to refresh every month without re-forecasting hundreds of GL lines.
Teams usually mature in that order: static budget, then flexed variance analysis, then a full driver-based model that plans, flexes and re-forecasts from a single set of assumptions. If you are ready to make that move, our driver-based planning practice helps finance teams design the driver tree, set the rates and automate the monthly flex.
The destination is worth the effort. A flexible budget doesn't just tidy up the variance report — it changes the monthly conversation from "why are we over budget?" to "which of our assumptions was wrong, and what do we do about it?". That is the conversation a finance team is actually for.