Tornado: compare selected ranges

Methods and settings

Build a defensible shortlist

Choose the target, add drivers through the workspace or explicit Search, and review each range and unit. A revenue percentage, a currency amount and a multiple use different units. Document why each range is plausible in the model’s notes or comments where supported. Running Tornado does not overwrite the model’s current assumptions.

Read the bar and Base

Each driver changes alone while the other selected assumptions remain at Base. The chart compares low/high outcomes with Base and orders the tested span including Base. The widest span identifies the greatest movement under these particular ranges. It does not establish the most likely risk, nor do all endpoints describe one combined scenario.

Separate range impact from uncertainty

If two drivers interact, use a two-variable Sensitivity test. If several assumptions may vary together probabilistically, configure Stochastic and understand its independent sampling boundary. If the question is which permitted changes achieve a target, use Reverse. A Tornado ranking is conditional on your shortlist, ranges and model; omitted drivers are not proven unimportant.

Public models do not store this analysis session

Tornado configuration and rankings are not persisted in public model snapshots. Publication preserves operator inputs and deterministic operator outputs. After Fork, run this analysis again locally against the restored editable inputs. A reviewed change explicitly applied to an underlying operator input can be published as that input; the analysis session that produced it is still excluded.