Available modeling methods
| Method / input | Behavior |
|---|---|
| Base and overrides | Scenario inputs inherit Base unless a local override replaces the relevant field or method setup. |
| Comparison and copy | Use Display for visible scenarios and Copy modeling for selected modeling scope. |
Change only the intended assumptions
In Advanced, select the scenario before editing. Unchanged assumptions continue to follow Base; an overridden period method retains its own method and inputs together. Scenario-specific items use stable identities. If a referenced item or period is removed, an unresolved override is reported rather than silently attached to a different target.
Adjustments and valuation
Groups, component periods and valuation assumptions use the same scenario architecture. A first scenario WACC edit does not freeze every unrelated Base valuation assumption. Display can compare scenario statements; Valuation includes a scenario comparison when multiple scenarios are visible.
Example workflow
Keep the operating model in Base. In another scenario, lower revenue growth and increase collection days, then compare EBITDA and cash. Reset the relevant overrides to return to inheritance. Use What-If for a discrete transaction instead of a permanent forecasting-method change.
Documents the current implemented behavior. Example assumptions are not market data.