Impact Score is the headline number on every scenario page. It tells you what would happen to your organization if the scenario plays out — on a signed ±100 scale anchored to your own baseline expectation.
Reading the score
- **0** — The scenario does not change your YoY trajectory vs. baseline.
- **+100** — The scenario massively accelerates above baseline — impossibly positive.
- **-100** — The scenario massively destroys baseline — impossibly negative.
The score is color-coded — cyan for favorable, coral for adverse, mute for roughly neutral — with a band label underneath ("Mildly negative", "Severe positive", and so on).
The math
Open the **How the Impact Score is computed** accordion at the bottom of any scenario page. Every component is shown — strength-weighted coefficient, confidence damping, probability factor, baseline shift, and per-signal contribution. Nothing is hidden.
The formula is:
weighted_coeff = sum(strength × org_impact_coefficient) / sum(strength) confidence_mult = { low: 0.6, medium: 0.8, high: 1.0 } prob_factor = probability / 100 raw_impact = weighted_coeff × confidence_mult × prob_factor × 100 baseline_shift = -baseline_yoy × prob_factor × 0.25 impact_score = clamp(round(raw_impact + baseline_shift), -100, +100)
Calibrating
Every scenario signal carries an **org-impact coefficient** — a number between -1 and +1 that maps the signal's contribution to your business outcome. By default the coefficient is 0 (neutral), so a new scenario reads at 0 until an admin sets the coefficients.
To calibrate: open a scenario, click the gear (top right) to enter edit mode, set the coefficient per signal in the Signal Map editor (negative when the scenario movement hurts you, positive when it helps), then save. The score recomputes on the next page render.
You also set an organization-level baseline expectation in Settings → Company → Baseline YoY growth. That anchors the score so it tracks against your own normal, not a generic baseline.