VALUEWORKSInsights to Results
Sign in
Help center

Assumptions

Model a cash effect that isn't represented in any plan.

Not every cash event deserves a whole plan built around it.

Add assumption, reached from a named scenario, asks for a Name, an optional Description, an Assumption category, a Start date and optional End date, a Reoccurence in months, a Value and a Change per occurrence — the last two switchable between an absolute number and a percentage.

Reoccurence sets how often the value repeats; Change per occurrence lets each repeat grow or shrink from the last. A flat €10,000 every month for six months, with no change per occurrence, has a straightforward total: six repeats of the same figure.

Assumptions belong to a named scenario, which is why Add assumption is greyed out on the Default scenario — there is nowhere for the overlay to attach until you have created one to attach it to.

The Assumption dialog with Name, Description, Assumption category, Start date set to Sep 2026 with an empty End date, Reoccurence in months set to 1, a Value field with a number and percent toggle, and a Change per occurrence field with the same toggle.
  1. 1Name and Description
  2. 2Assumption category
  3. 3Start date and End date — an empty End date means it does not stop on its own
  4. 4Reoccurence in months
  5. 5Value, and its # / % toggle
  6. 6Change per occurrence, with the same toggle

ValueWorks 2026.08

Takeaways

  • An assumption is Start, End, Reoccurence, Value and an optional Change per occurrence.

  • Assumptions attach to a named scenario — that is why the Default scenario can't take one.

  • Value and Change per occurrence can each be a number or a percentage.

Surfaces covered

  • Liquidity

Also taught in the Academy

Module 6 · Liquidity and runway

Take it as lesson 6.3 in Business Analyst & FP&A