Scenarios
Compare alternatives without changing the approved budget.
Branch from a known starting point
Choose the BudgetVersion and source Scenario that the alternative should inherit. The clone keeps the budget cells, driver values, defaults and formula revisions used at that point. Active Scenarios shows the alternatives available for the review. A branch named BoardCommit does not itself establish board approval, and a scenario copied from a locked plan does not gain permission to change that plan. Keep the author and lineage visible so another reviewer can reconstruct the starting assumptions.
Change the assumption and retain the result
Apply an override to the scenario’s own driver basis, such as a revised sales growth assumption or a different hiring schedule. Validate dependencies before computing the affected lines. Scenario Results retains each WhatIfRuns execution and its input summary rather than replacing the previous result. Compare outputs using the same periods, entities and reviewed account mapping. The planning EBITDA measure requires its defined revenue, cost-of-sales and operating-expense classes; a generic total of expense accounts is not a sufficient calculation basis.
| Run Number | Scenario | Baseline Revenue | Scenario Revenue | Baseline EBITDA |
|---|---|---|---|---|
| WIR-18679 | SCN-4093 | 31,097.29 | 26,831.72 | 4,827.93 |
| WIR-34145 | SCN-3342 | 24,995.30 | 9,741.34 | 4,172.99 |
| WIR-96640 | SCN-1510 | 28,238.45 | 38,104.97 | 35,730.37 |
| WIR-79568 | SCN-4433 | 39,967.85 | 35,871.70 | 47,010.97 |
| WIR-51032 | SCN-7106 | 34,445.76 | 18,088.56 | 41,513.76 |
| WIR-93103 | SCN-1323 | 37,035.82 | 38,636.46 | 22,183.41 |
Bring a reviewed alternative into planning
A scenario comparison informs a decision; it does not approve a budget or forecast. If Finance chooses an alternative, create the intended draft version or explicitly scoped forecast changes, retain the source run and complete the applicable review route. ForecastAdjustments belongs to a particular RollingForecast and cannot be copied into an annual scenario without an explicit conversion. Preserve the original what-if evidence even after a new plan is selected so later reporting can explain the decision in context.
Rollout checks
Pilot a base, upside and downside run using the same monthly population. Change one driver at a time and compare its effect with the expected formula result. Confirm that repeated calculations retain their own evidence and cannot overwrite the approved baseline. Test that a shared scenario does not expose restricted personnel inputs through its detail links or exports.
Modules
-
Budget planning
Build a plan your teams can explain and your finance leaders can review.
-
Drivers and assumptions
Show which assumptions produced each planning number.
-
Scenarios
Compare alternatives without changing the approved budget.
-
Rolling forecasts
Refresh the outlook while keeping earlier forecasts intact.
-
Budget controls
Keep budget changes and spending follow-up accountable.
-
Variance and board packs
Explain performance against the plan and share a consistent review.
Reports
All reportsEBITDA Bridge
Walks from prior-period EBITDA to current-period EBITDA via Volume, Price, Mix, Cost, and Headcount drivers using the BudgetLines × Drivers decomposition. Powers the "what changed" narrative in every BoardPack. US dollars only at this tier.
Scenario Comparison
Side-by-side WhatIfRuns for one Version: BaselineRevenue, ScenarioRevenue, BaselineOpEx, ScenarioOpEx, BaselineEBITDA, ScenarioEBITDA, RevenueDelta, EBITDADelta, with InputsSummary expanded. Used by FP&A Director and CFO to stress-test the call before it goes to the board.
Roles and permissions
Owns Targets, signs off the final BudgetVersion, reviews and approves BoardPacks. The named approver at the top of the budget-approval chain.
Designs each BudgetCycle, manages Versions through the cycle, runs Scenarios, owns the RollingForecasts, builds BoardPacks. The day-to-day owner of the planning workbench.
Operational role. Loads Actuals, runs and reviews VarianceAnalyses, prepares FluxComments, supports Cost-Center Heads through the submission cycle, drafts BoardPacks for Director review.
Department / cost-center owner. Submits own Entity's BudgetLines (Type: Budget) during the cycle, defends Variance each month with FluxComments, requests BudgetTransfers.
Line-of-business manager with scope limited to inputs that feed budget — headcount asks, capex requests, vendor cost estimates for own org. Sees aggregate own-org budget but no peer detail.
Read-only access to BoardPacks, top-line dashboards, and the approved BudgetVersion summary. Used by board members and exec staff.
Read-only with full AssumptionsLog access for compliance and internal-audit work. Includes draft and approved artifacts.
Related processes
Build and approve the budget
Take a scoped proposal through the required financial decisions.
5 stages · 3 approvals
Refresh the rolling forecast
Publish an accepted outlook with a reproducible monthly basis.
4 stages · 1 approval
Compare planning scenarios
Test alternative assumptions and retain the comparison evidence.
4 stages · 0 approvals