Health scores and status

Every engagement has a health score from 0 (critical) to 100 (excellent). The score is calculated for each domain and combined into an overall figure.

Status bands

Status	Meaning	Typical range
Green	Healthy. Actuals tracking plan.	70–100
Amber	Warning. Notable variance, needs attention.	40–69
Red	Critical. Significant deviation, action needed.	0–39

What drives each score

Finance: how close revenue and cost actuals are to plan. Cost overruns or revenue shortfalls drag the score down.
Performance: how many KPIs are on target versus amber or red. A single missed term has a strong impact.
Capacity: whether utilisation sits in the healthy range. Both under-use (paying for unbilled time) and over-use (burnout risk) hurt the score.
AI Usage: whether token spend stays inside the budget per use case. Repeated overruns drag the score down.
Overall: a weighted combination, so a critical failure anywhere shows in the headline.

Portfolio health

Portfolio health rolls the scores of every service and engagement inside it into one view. Two things matter beyond the average:

Distribution: how many engagements are green, amber, or red. An average of 65 looks very different if most are healthy with two in crisis.
Trend: improving, declining, or steady against the previous period.

Attention flags

The dashboard highlights engagements that need a look:

Health score dropped by more than the limit you set.
Check‑in is overdue.
A contract term has been missed.
Plan and actuals have diverged sharply.

Flags split into overdue (past‑due check‑ins, open misses) and upcoming (check‑ins due this week, renewals approaching).

Tuning the bands

The default Red, Amber, Green bands work for most teams. If a 5% variance is acceptable in your business, widen the green band. In a high‑SLA environment, tighten it.

Pulse: see attention flags first thing.
Thresholds: tune the bands.
Data domains: the inputs each score uses.