Change Load Score
How Cursus measures cumulative change burden across stakeholder groups — and what to do when it's high.
The Change Load Score is one of Cursus's most actionable metrics. It measures the cumulative burden of active change initiatives on a stakeholder group — not just the number of changes, but their intensity, overlap, and timing.
What it measures
Change load is calculated per stakeholder group and reflects:
- Volume — How many active programs impact this group
- Intensity — The assessed significance of each change (role impact, process change, technology adoption)
- Concurrency — How many changes are active at the same time vs. staggered
- Capacity signals — Ambient indicators of how well the group is coping
Scores run from 0–100. The risk bands are:
| Score | Risk level | What it means |
|---|---|---|
| 0–39 | Low | Manageable. Normal change velocity. |
| 40–69 | Moderate | Monitor. Consider sequencing. |
| 70–84 | Elevated | Intervention likely needed. |
| 85–100 | Critical | Active risk. De-prioritize or delay. |
How it's calculated
Cursus aggregates change load from the bottom up:
- Each change impact is scored for magnitude (1–5 scale) based on role disruption, process change, and technology shift
- All active impacts on a group are weighted by their program phase (planning, active, sustaining)
- Capacity signals adjust the score — a group showing resilience carries more load without elevated risk
- The portfolio-level score is the weighted average across all groups, surfaced in the Change Pulse dashboard
What to do with a high score
A critical change load score is a signal to act, not just report. Cursus's Lumen AI will proactively surface intervention recommendations:
- Sequencing — Identify which programs could be phased to reduce overlap
- Capacity building — Trigger targeted check-ins or coaching for overburdened groups
- Stakeholder engagement — Increase communication frequency for high-load groups
- Executive escalation — Brief flag for sponsors when load approaches critical thresholds
Aggregation and privacy
Change load scores are always computed at the group level — never for individuals. Groups must meet the minimum membership threshold (configurable, default: 5 people) before a score is displayed.