Health, Quality & Capacity Bands
Sprint Health, Team Health, and Team Quality Score are all labeled using fixed score bands (Excellent, Healthy, Watch, and so on) shared consistently across every module. This page shows exactly what those bands are — and the one related value that actually is tenant-configurable: the Capacity "healthy utilization" range.
Where to find it
Under Setup → Health, Quality & Capacity Bands, its own entry in the sidebar, right below Sprint Intelligence Setting — not nested inside General Settings.
Sprint & Team Health score label bands (read-only)
The 5 bands used to label both Sprint Health Score and Team Health Score wherever either appears — the overall score cards, Intelligence dashboards, and reports:
| Label | Score range | Description |
|---|---|---|
| 🟢 Excellent | ≥ 90 | Outstanding health. Keep maintaining. |
| 🟢 Healthy | 80 – 89 | Good health. Continue to monitor. |
| 🟡 Watch | 70 – 79 | Some risks detected. Attention recommended. |
| 🟠 At Risk | 60 – 69 | High risk of issues. Action required. |
| 🔴 Critical | < 60 | Critical risk level. Immediate action required. |
Team Quality score label bands (read-only)
A separate 4-level scale used specifically for Team Quality Score — deliberately different cut points than the Health bands above, since Quality Score is derived from open risk points, not the same blend Sprint/Team Health use:
| Label | Score range | Description |
|---|---|---|
| 🟢 Excellent | ≥ 90 | Outstanding quality. |
| 🟢 Good | 75 – 89 | Good quality. |
| 🟡 Fair | 50 – 74 | Average quality. Improvement needed. |
| 🔴 Needs Attention | < 50 | Below average. Immediate improvement needed. |
Both label-band cards are explicitly read-only in this release — editing 4 or 5 ordered cutoffs safely (no gaps, no overlaps, correct ordering) is materially harder to validate than the single min/max pair below, and wasn't part of what this page set out to solve. Each card states this plainly and links to Support Center if you need a cutoff changed.
Capacity utilization band (editable)
The one real setting on this page: Minimum (Healthy) and Maximum (Healthy), both percentages, defining the logged-vs-available hours range treated as healthy utilization. Ships at the same values the app always used: 70% – 100%.
Validation
Minimum must be at least 50% and less than Maximum. Maximum must be at most 100% and greater than Minimum — both bounds AND the cross-field rule are enforced, so an inverted range (e.g. Min 90 / Max 80) can't be saved.
Reset to defaults / Cancel / Save changes
Reset restores 70%/100% in the form (still requires pressing Save). Cancel discards unsaved edits. Save is disabled until the form is both valid and different from what's currently saved.
Timing
Saving doesn't rewrite any score that's already stored — the new range only takes effect the next time a sprint's health score, or a Team Intelligence snapshot, is recalculated.
What this range actually feeds
| Consumer | How it's used |
|---|---|
| Sprint Health – Capacity pillar | The Minimum value is the utilization curve's inflection point — below it, capacity scores a full 100; above it, the score drops 2 points per percentage point over. |
| Team Intelligence – Capacity analysis | Uses both Minimum and Maximum — utilization inside the range scores 100; below Minimum or above Maximum, the score is penalized proportionally on whichever side it falls. |
| Capacity dashboards & reports | Reflects the same configured range wherever "healthy utilization" is displayed. |
Persistence
One tenant-wide value, stored through the same generic settings mechanism every other Setup page uses — no per-project or per-sprint override exists or is planned.
Permissions
| Permission | What it controls |
|---|---|
HealthQualityCapacityBands.View | See the page — both reference cards and the current Capacity range |
HealthQualityCapacityBands.Edit | Change the Capacity range, Reset to defaults, and Save |
Magic Wand
A single healthQualityCapacityBands panel reports the current Capacity range, whether it still matches the shipped default, whether the form is currently valid, and whether there are unsaved changes — with an explicit reminder that Risk Management's thresholds are unaffected by this page.
Who uses this, and why
What's deliberately left out, and why
- The Sprint/Team Health and Team Quality label bands aren't editable in this release — see the reasoning above.
- Risk Management's Capacity Risk severity thresholds are independent and fixed — this page doesn't touch them.
- No per-project or per-sprint override for the Capacity range — it's one value per tenant, like General Settings.
- Saving doesn't retroactively recalculate any sprint's already-stored score.
Rating this page
Anyone reading this documentation can mark whether it answered their question — no permission required. It only helps the SprintUnity team see which pages need more detail.