Skip to main content
A scenario layers a set of assumption changes on top of a budget version so you can ask “what if” and compare the answer against your base, side by side. The base plan is never touched, so you can explore freely and keep only the versions worth keeping.

​
What You Can Change

  • Hiring pace and timing for headcount.
  • Growth, churn, and renewal rates for revenue.
  • Specific assumptions on specific departments, streams, or periods.
A scenario starts identical to its base. Only the assumptions you change are different; everything else inherits, so the comparison shows the effect of your change alone.

​
How to Use It

1

Create a scenario

Branch from a base version. The scenario starts as an exact copy.
2

Adjust assumptions

Change only what you want to test. You can ask Nova to draft the assumption changes from a plain-language description, then accept or refine them.
3

Run the forecast

Re-run so the engine projects the scenario with your changes applied.
4

Compare

View the scenario against the base in the Comparison Center to see the delta on every line.

​
Scenarios vs Mid-Year Updates vs Rules

Scenarios are non-destructive. Because the base is frozen relative to the scenario, you can spin up several what-ifs from the same base and compare them all against it.

​
Common Questions

No. A scenario is a separate layer. Your base version stays exactly as it was, which is what makes the side-by-side comparison meaningful.
Open the Comparison Center and put the scenario against its base. Every line shows the dollar and percent delta.
Yes. Describe the what-if in plain language (“push all engineering hires to Q3, raise churn to 8 percent”) and Nova drafts the assumption changes for you to review before applying.
Promote it: once a what-if is the direction you want, you keep it as a version and compare future work against it. The original base remains available for history.

​
If the Numbers Look Off

  • The scenario looks identical to the base: you have not changed an assumption that the engine reads, or you have not re-run the forecast since changing it.
  • A change had no effect on a line: confirm the assumption you edited is scoped to the department, stream, or period that line belongs to.