"I understand everything but how to get the assumptions for the forecasting part after doing the yoy for the drivers."
— Source: r/financialmodelling (20 upvotes)
The formulas in a budget are the easy part. Revenue equals orders times average order value; marketing equals new customers times acquisition cost. The hard part is the inputs: what conversion rate, what order value, what acquisition cost, and why.
When those inputs live as unlabeled numbers in cells, nobody can tell which ones were measured, which were guessed, and which ones the whole plan hinges on. When the year goes off track, the review turns into an argument about the forecast instead of a decision about the business.
This guide covers: how to separate facts from assumptions and judgments, how to build an assumption register, how to rank assumptions by sensitivity so you know which to defend, and how to treat temporary vs recurring drivers when you reforecast.
What Is a Planning Assumption?
A planning assumption is an explicit, written belief about the future value of a driver that a budget or forecast depends on. Examples: next year's DTC conversion rate, average order value, customer acquisition cost, return rate, landed cost per unit, or number of wholesale doors. Good assumptions have an owner, a source, evidence and a review date.
Assumptions sit underneath every number in a plan. A revenue line is only as credible as the traffic, conversion and order value behind it. A gross margin line is only as credible as the landed cost and pricing behind it.
The goal is not to eliminate assumptions; you can't plan without them. The goal is to make them visible, owned and testable, so that when results differ from the plan you can see exactly which belief was wrong.
Fact vs Assumption vs Judgment
Before you write a single assumption down, sort the inputs into three kinds. Each one needs a different type of evidence and a different level of challenge in review.
| Type | What it is | Consumer-brand example | Evidence it needs |
|---|---|---|---|
| Fact | Something that already happened and can be checked | Last quarter's Shopify conversion rate, from the store report | A source system and a date range |
| Assumption | A belief about the future value of a driver | Conversion holds at the same rate next year | History, trend, and the reason the trend should continue |
| Judgment | A belief about cause and effect | A new checkout flow will lift conversion | A test result, a comparable launch, or an explicit owner's call |
The distinction matters because the three fail in different ways. Facts fail when the source is wrong or the period is unrepresentative. Assumptions fail when conditions change. Judgments fail when the cause you believed in doesn't produce the effect. Labeling them tells reviewers where to push.
A practical rule: if a number in the plan can't be traced to a fact, it is an assumption or a judgment, and it belongs in the register.
The Assumption Register
An assumption register is a single table that lists every key assumption in the plan. Keep it on its own tab, next to the model, and link the model's input cells to it so there is one source for each value.
Columns to include
| Column | What to record |
|---|---|
| ID | A short code so variance commentary can reference it (A1, A2...) |
| Assumption | The driver and its planned value, in plain words |
| Type | Fact-based, assumption or judgment |
| Owner | One named person who is accountable for the value |
| Source and evidence | Where the number came from and why it is reasonable |
| Sensitivity | How much contribution or cash moves if the value is off by a realistic amount |
| Review trigger | A date, or an event that forces a review (for example, a supplier price change) |
Illustrative example: assumption register for an omnichannel brand
Illustrative example. A personal care brand sells DTC on Shopify and wholesale through specialty retailers. These are the six assumptions its annual plan depends on most:
| ID | Assumption | Type | Owner | Source and evidence | Review trigger |
|---|---|---|---|---|---|
| A1 | DTC sessions: 2,000,000 for the year | Assumption | Growth lead | Trailing 12 months of traffic plus the planned content calendar | Monthly |
| A2 | DTC conversion rate: 2.5% | Assumption | Ecommerce lead | Trailing 12 months from the store report; no site changes planned | Monthly, or any checkout change |
| A3 | Average order value: $70 | Assumption | Ecommerce lead | Trailing average, adjusted for the planned bundle launch | Monthly |
| A4 | Return rate: 10% of DTC orders | Fact-based | Operations lead | Returns report for the last four quarters | Quarterly |
| A5 | CAC: $45 for 30,000 new customers | Judgment | Growth lead | Paid media plan; assumes auction costs stay near this year | Monthly |
| A6 | Landed cost: $21 per DTC order, $7 per wholesale unit | Fact-based | Supply chain lead | Current supplier quotes, freight and duty rates | Any supplier, freight or tariff change |
| A7 | Wholesale: 120 doors selling 6 units per door per week at $18 | Assumption | Wholesale lead | Signed doors plus sell-through history from retailer reports | Quarterly, or any door change |
Notice that every row has one owner. When conversion misses, the review goes to the ecommerce lead with the evidence in front of everyone, not to a debate about whose spreadsheet is right.
Worked Example: Ranking Assumptions by Sensitivity
Not every assumption deserves the same scrutiny. The way to find the ones that matter is to flex each one and measure how much the result moves. For a deeper treatment of the technique, see scenario and sensitivity analysis.
Step 1: The base plan
Illustrative example, using the register above. To keep it simple, returned DTC orders are refunded and restocked at no extra cost, and fulfillment is $8 per kept order.
| Line | Calculation | Amount |
|---|---|---|
| DTC orders | 2,000,000 sessions × 2.5% | 50,000 |
| DTC net revenue | 50,000 × $70 × (1 − 10%) | $3,150,000 |
| DTC landed cost | 45,000 kept orders × $21 | −$945,000 |
| DTC fulfillment | 45,000 × $8 | −$360,000 |
| Acquisition spend | 30,000 new customers × $45 | −$1,350,000 |
| DTC contribution | $495,000 | |
| Wholesale revenue | 120 doors × 6 units × 52 weeks × $18 | $673,920 |
| Wholesale landed cost | 37,440 units × $7 | −$262,080 |
| Wholesale contribution | $411,840 | |
| Total contribution | $906,840 |
Step 2: Flex each assumption by 10% in the unfavorable direction
| Assumption | Flexed value | New total contribution | Change | % of base contribution |
|---|---|---|---|---|
| A3 Average order value | $70 → $63 | $591,840 | −$315,000 | −34.7% |
| A2 Conversion rate | 2.5% → 2.25% | $722,340 | −$184,500 | −20.3% |
| A5 CAC | $45 → $49.50 | $771,840 | −$135,000 | −14.9% |
| A6 Landed cost | +10% on both channels | $786,132 | −$120,708 | −13.3% |
| A7 Wholesale doors | 120 → 108 | $865,656 | −$41,184 | −4.5% |
| A4 Return rate | 10% → 12% | $865,840 | −$41,000 | −4.5% |
How the biggest rows are calculated: at a $63 order value, DTC net revenue falls to 50,000 × $63 × 90% = $2,835,000, a drop of $315,000, while costs stay the same. At a 2.25% conversion rate, orders fall to 45,000, so net revenue falls to $2,835,000, landed cost to $850,500 and fulfillment to $324,000: DTC contribution falls from $495,000 to $310,500, a change of −$184,500.
Step 3: Decide where to spend review time
In this example, order value, conversion, CAC and landed cost together drive most of the risk. Those four deserve evidence, a range and a named owner in the budget review. Doors and return rate still belong in the register, but they don't need the same depth of defense.
Caution: a 10% move is not equally likely for every assumption. Landed cost can jump far more than 10% after a tariff change, while a signed wholesale door count may barely move. Once you have the ranking, replace the uniform 10% with a realistic range for each assumption.
Temporary vs Recurring Drivers in a Reforecast
When actuals come in, the register tells you which assumption was off. The next question decides what you do with the forecast: is the cause temporary or will it persist?
- Temporary: a one-off event that won't repeat. Record the variance, explain it, and leave the forward assumption alone.
- Recurring: a change in conditions that will continue. Update the assumption, change the forecast for the remaining months, and note the new evidence in the register.
Illustrative example: Q1 reforecast decisions
| Driver | What happened | Classification | Reforecast treatment |
|---|---|---|---|
| Conversion rate | A three-day site outage in February | Temporary | Keep the forward conversion assumption; explain the miss in variance commentary |
| CAC | Paid social auction costs stayed higher for the whole quarter | Recurring | Raise the forward CAC assumption and update the acquisition budget or the new-customer target |
| Landed cost | A supplier price increase took effect in March | Recurring | Update landed cost for every remaining month and re-run margin by SKU |
| Wholesale velocity | One retailer ran a promotion that pulled sales forward | Temporary, with a payback | Keep the annual units, but shift some volume out of the following months |
This classification is the bridge between budget vs actual variance analysis, which explains the past, and a driver-based rolling forecast, which updates the future.
How to Defend Assumptions in a Budget Review
"you have to make so many rubbery assumptions to get the numbers to add up that the outputs are frequently meaningless"
— Source: r/FPandA (73 upvotes)
That is what a plan looks like when assumptions are hidden. A defensible plan is the opposite: a small number of material assumptions, each with evidence and an owner.
- Lead with the top few by sensitivity. Show the ranking table first. Reviewers should spend their time where the money is.
- Show the evidence, not just the number. "2.5% conversion, the trailing 12-month average, with no checkout changes planned" is defensible. "2.5%" alone is not.
- Give a range. State the low and high case for each material assumption and what the plan looks like at each end.
- Name the owner. The person accountable for the assumption should present it.
- State what would change your mind. For example: "If CAC is above $50 for two consecutive months, we cut the new-customer target rather than increase spend."
- Separate the debate about assumptions from the debate about targets. A stretch target is a management choice; the assumption should still be your honest estimate.
"Ngl I only skimmed this but I really like this example scenario because it comes up time and time again and at the end of the day everyone wants to blame the forecast."
— Source: r/FPandA (50 upvotes)
A register with owners changes that conversation. When a number misses, the question becomes "which assumption was wrong, and is the cause temporary or recurring?" instead of "who built this forecast?"
Common Mistakes
- Assumptions typed into formulas. A conversion rate buried inside a revenue formula can't be found, reviewed or flexed. Keep every assumption in a labeled input cell that links to the register.
- Mixing facts and beliefs. Presenting a judgment ("the new bundle will lift order value") with the same confidence as a fact hides the real risk.
- No owner. An assumption owned by "the team" is owned by nobody.
- Stale assumptions. Landed cost from a quote that expired months ago, or a door count that has since changed. Every row needs a review trigger.
- Treating every assumption equally. Without a sensitivity ranking, review time goes to whatever is easiest to argue about.
- Single-point estimates only. One number with no range invites false precision.
"Make sure the inputs in your sensitivity table axes are hard coded, not linked to the assumptions running through the math"
— Source: r/financialmodelling (56 upvotes)
That advice is specific to spreadsheet data tables: the flexed values on a data table's axes must be typed values, or the table recalculates against itself. It doesn't contradict the main rule. Your planning assumptions still live in one input location, and the sensitivity table varies them.
For Consumer Brands: The Assumptions That Usually Matter
Consumer brands carry more assumptions than most businesses because each channel has its own drivers, and supply decisions are made months before demand shows up.
| Area | Typical assumptions to register |
|---|---|
| DTC | Sessions, conversion rate, average order value, repeat rate, return rate, CAC by channel |
| Amazon | Sessions and unit session percentage, average selling price, referral and fulfillment fees (from Amazon's published fee schedules), advertising spend |
| Wholesale | Doors, velocity per door, wholesale price, trade spend and deductions, payment terms |
| Supply | Landed cost per unit, tariffs and duties, freight, lead time, minimum order quantities |
| Seasonality | Monthly share of annual demand, promotion calendar, Q4 inventory build |
Two consumer-brand habits make the register far more useful. First, register assumptions at the level you make decisions: by channel and, for your biggest SKUs, by SKU. A blended conversion rate hides the fact that one hero product carries the plan. Second, tie supply assumptions to cash: a landed cost or lead-time change hits the 13-week cash flow forecast before it shows up in margin.
Make Every Number Traceable
A plan is only as strong as the assumptions under it. Write them down, give each one an owner and evidence, rank them by sensitivity, and decide in every reforecast whether a miss is temporary or recurring.
Niblin is FP&A built for consumer brands: budgets at SKU × channel × month, a driver-based rolling forecast re-cut monthly, and plan vs actual variance with price, volume and mix bridges, so each assumption is visible and tied to the results it drives.
See which assumptions your plan really depends on.
Model drivers by channel and SKU, flex them in scenarios, and trace every variance back to the assumption behind it.
See how Niblin models it
Key Takeaways
- A planning assumption is a written belief about the future value of a driver that the plan depends on.
- Separate facts (observed history), assumptions (beliefs about future values) and judgments (beliefs about cause and effect); each needs different evidence.
- Keep an assumption register: value, type, one owner, source and evidence, sensitivity, and a review trigger for every key assumption.
- Rank assumptions by flexing each one and measuring the change in contribution or cash; defend the top few in detail.
- In a reforecast, classify each variance as temporary or recurring before changing forward assumptions.
- Keep assumptions in labeled input cells linked to the register, never typed into formulas.
Frequently Asked Questions
What is a budget assumption?
A budget assumption is an explicit belief about the future value of a driver that the plan depends on, such as conversion rate, average order value, customer acquisition cost or landed cost. Good assumptions are written down, owned by one person, backed by evidence and reviewed on a set date or trigger.
What should an assumption register include?
At minimum: an ID, the assumption and its value, whether it is fact-based, an assumption or a judgment, one named owner, the source and evidence, its sensitivity, and a review date or trigger. Link the model's input cells to the register so each value has a single source.
How do I know which assumptions matter most?
Flex each assumption by a realistic amount and measure how much contribution, profit or cash changes. Rank the results. In most consumer-brand plans a handful of drivers, often order value, conversion, acquisition cost and landed cost, account for most of the risk. Spend review time on those.
What is the difference between an assumption and a judgment?
An assumption is a belief about the future value of a driver, such as conversion holding at its trailing average. A judgment is a belief about cause and effect, such as a new checkout lifting conversion. Judgments need a test result, a comparable case or an explicit owner's call.
Should I change assumptions when actuals miss the plan?
Only if the cause will persist. Classify the variance first: a one-off event such as a site outage is temporary, so explain it and keep the forward assumption. A lasting change such as higher auction costs or a supplier price increase is recurring, so update the assumption and the forecast.
How often should budget assumptions be reviewed?
Set a review trigger for each one. Fast-moving drivers such as conversion and acquisition cost suit a monthly review alongside the forecast. Slower drivers such as wholesale doors may suit a quarterly review. Supply assumptions should be reviewed whenever a supplier, freight or tariff change occurs.
By