How to Document Budget Assumptions So They Survive Scrutiny

Budget assumptions are the beliefs your numbers rest on: that prices will rise 3 percent, that wages will rise 4 percent, that conversion will hold at its current level, that a supplier will keep its quote. When they are written down, with a source and an owner, a budget can be challenged, updated and learned from. When they live in people's heads, the first hard question from a board member or lender stalls the meeting, and a year later nobody can say why the plan missed. This guide shows how to build an assumptions register, how strong the evidence behind each assumption should be, how to rank assumptions by their effect on profit and how to keep them current. It supports budgeting and forecasting and slots into the annual budgeting process.

What counts as an assumption

An assumption is any input to the budget that is not a contract or a known fact. Group them to keep the register manageable.

The assumptions register

A simple register is a table with the same columns for every assumption.

Keep it in the same workbook as the budget, with the assumptions tab driving the formulas. Every assumption in the register should be an input cell, and no hidden numbers should sit inside formulas.

Rate the strength of evidence

Not all assumptions are equal. A contract price is not the same as a guess about customer behavior. A simple scale is enough.

Low-evidence assumptions that have a large effect on profit are the ones to test, stage and monitor most closely.

Rank assumptions by their effect on profit

Spending equal time on every assumption wastes effort. Calculate the profit effect of a one percent change in each major assumption, and focus on the biggest.

Worked example

A hypothetical company has revenue of $12,000,000, a contribution margin of 40 percent, materials cost of $4,500,000, payroll of $2,000,000 and freight of $600,000.

The ranking is clear. Price is by far the most sensitive assumption, then volume and materials. Wages matter less per point, though they can move more than one point. Freight is minor. A board discussion that spends an hour on the freight rate and five minutes on pricing is misdirected. Use this table to choose where to apply the strongest evidence standard, where to hold scenarios and where to set review triggers. See sensitivity analysis in financial models.

What a good write-up looks like

For the top assumptions, add a short narrative of three or four sentences.

Assumption A1: Price increase of 3.0% effective April 1.
Basis: List prices are 4 to 6 percent below the two nearest competitors on
comparable items. Our last increase, 2.5% in the prior year, reduced unit volume
by an estimated 0.6% according to the sales team's win-rate analysis.
Risk: Larger customers may resist; the top five account for 38% of revenue.
Test: Budget assumes 90% of the increase is realized (2.7% effective).
Owner: Sales lead. Review: monthly price realization report.

The write-up states the number, the evidence, the risk, the test applied and how it will be tracked. A reader can challenge it, and a successor can understand it.

Ranges and scenarios

Single-point assumptions invite false precision. For the major ones, add a low, base and high value.

Use the ranges in the scenarios that the board or lenders see. See scenario planning for finance teams.

Linking assumptions across departments

A common failure is inconsistent assumptions: the sales plan assumes 120,000 orders, the support budget assumes 100,000. Prevent this by publishing one set of company-wide assumptions (volumes, prices, inflation, exchange rates, tax) at the start of the process and requiring departments to use them. Department-specific assumptions go in the department's own register, and any that depend on another department are cross-referenced.

Versioning and change control

Assumptions change. Keep a log.

When a variance appears, the log shows whether it came from a changed assumption or from execution.

Review triggers

Set events that force a review, instead of relying on memory:

• A quarterly review date for all high-impact assumptions
• A threshold on an index, such as a commodity price moving more than 5 percent
• A change in a key customer, supplier or competitor
• A variance above a set level for two consecutive months
• A new law, tax rule or major policy change

Questions you will be asked

Boards and lenders often probe the same areas. Be ready to answer:

1. What is the biggest assumption in the plan, and what happens if it is wrong?
2. What evidence supports the revenue growth rate?
3. What are costs doing, and which have contracts?
4. How does the plan compare with the last two years' accuracy?
5. What would you do if sales came in 10 percent lower?
6. Which assumptions have you changed since the last version, and why?

Connecting assumptions to unit economics

The most useful assumptions describe what happens at the level of a unit: a customer, an order, a product. Margin per unit, cost to serve and retention are the building blocks of the budget. If those are documented, the budget stands on firm ground. See unit economics.

Common mistakes

• Leaving assumptions undocumented or buried in formulas.
• Using single values for uncertain items.
• Giving every assumption equal attention.
• Not recording who owns an assumption.
• Failing to update the register when conditions change.
• Using assumptions that are inconsistent across departments.
• Treating the register as a one-time exercise.

Related guides

For who approves the budget and how changes are handled, see budget approval workflow. For common planning errors, read 12 budgeting mistakes that quietly derail plans.

FAQs

What are budget assumptions?

The inputs and beliefs behind the budget numbers, such as price increases, wage rates, volume growth and customer payment days.

How should I document budget assumptions?

In a register with the value, basis, source, owner, evidence strength and review trigger, kept in the same file that drives the budget.

Which assumptions matter most?

Those with the largest effect on profit per one percent change, usually price, volume and the largest cost lines.

How often should I review assumptions?

At least quarterly, and whenever a defined trigger occurs.

Should I use ranges or single numbers?

Use single base-case values in the budget and ranges for major assumptions in scenarios.