Scenario ownership and shared state

Methods and settings

A scenario is a set of differences

New workspaces provide Base, Upside and Downside, and Advanced can create additional scenarios. A scenario inherits Base wherever it has no own supported difference. A change to an inherited Base assumption can therefore update several scenarios without editing each one.

A local method and its drivers form one forecast setup. An override for one period does not silently become the assumption for every later period. Use Apply Forward or an explicit scenario copy when that is intended. Clearing a local override restores inheritance; disabling it retains the stored work while temporarily excluding it.

What remains common

Actual observations, historical-source plans, the calendar, functional/display currency and opening history are shared Base state. Ownership’s holders, securities, option-pool records and Equity Transactions also remain shared. Changing the selected Model Scenario does not create another Cap Table or another set of transaction inputs.

The three saved 13W planning windows have shared plan-owned inputs. The selected Model Scenario can change a linked model baseline, but does not silently duplicate manual weekly values, timing profiles or operational overrides into separate scenario plans.

What can differ across scenarios

Supported operating forecasts, named lines, methods, forecast sources and adjustments can differ. Value and Deals assumptions, committed Financing, capacity/covenant settings and Refinancing cases also use their supported scenario ownership. Read the operator’s selected scenario before editing a visible field.

The resulting output may combine shared records with scenario-linked economics. For example, shared Ownership inputs can be valued using a scenario-dependent source; a 13W plan can use a different scenario’s operating baseline while keeping the same operational override. The output context and the write owner are related but not identical.

Analysis, copying and unresolved work

Deterministic and stochastic runs are temporary evaluations. Reverse Solve and Preview also do not apply their candidate changes automatically. Apply solution revalidates the current inputs and their owners; shared plan or Ownership inputs do not become scenario-local merely because the target uses a non-Base scenario. See Preview and Apply for the explicit write boundary.

Deleting a referenced line, changing a source or removing a period can leave a stored override unresolved. The product retains it for review rather than applying it to an unrelated replacement. Scenario comparison explains recovery and independent copying.

Scenario ownership of listed capital returns

The optional listed schedule allows scenario-specific capital events, dividend/SBC policies, award assumptions, prices and denominator choice. Opening shares, historical share data, issuer metadata, sources and split basis remain Base-owned. This exception does not turn the existing Cap Table/ESOP ledger or 13W manual plans into scenario-local records.