Lesson 2 of 7 · 3 min
Scenarios
Create a named scenario and use it to isolate one decision.
A scenario is a bundle of choices, not a copy of your data.
+ Add new scenario asks for a Name, then a plan for each of Select revenue plan, Selected headcount plan, Select expenses plan and Select investments plan — each starting from No plan selected — and finally Select assumptions you want to include.
The plans themselves have to exist first; a scenario only chooses between them, it does not create or merge them. Saving tells ValueWorks which versions belong together for this read of the cash picture.
That makes a scenario the right tool for isolating one decision. To test a more aggressive hiring plan, build a new scenario that keeps the same revenue, expenses and investments plans and swaps only the headcount plan. Whatever moves in the Overview afterwards is attributable to that one change.
- 1Name
- 2One dropdown per plan area — revenue, headcount, expenses, investments
- 3Select assumptions you want to include
- 4Cancel and Save
ValueWorks 2026.08
Takeaways
A scenario selects one plan per area — it does not build or merge them.
Plans must already exist before a scenario can choose them.
To test one decision, change only that plan and hold the rest constant.
Surfaces covered
- Liquidity
Micro-check
Two quick questions
Practice only — nothing here is scored or recorded.
1. You want to see the runway effect of a more aggressive headcount plan, and nothing else. What do you do?
2. A dropdown in the dialog still reads "No plan selected" after you save. What happens to that part of the scenario?