How project & programme health works
このコンテンツはまだ日本語訳がありません。
Every project shows a health indicator: a RAG colour (red / amber / green) and a 0–100 score. This page explains exactly what they mean — they’re computed from data the platform already has, not entered by hand.
The four dimensions
Section titled “The four dimensions”Project health is built from four signals:
| Dimension | What it reflects |
|---|---|
| Sentiment | The mood of recent communications, weighted by who said it. |
| Delivery | How work is actually flowing (from your tracker). |
| Risk & issues | The state of the risk and issue registers. |
| Actions | Whether action items are on track or overdue. |
On the project Overview these appear as four dots — S / D / R / A — so you can see at a glance which dimension is dragging.
Weakest-link RAG
Section titled “Weakest-link RAG”The project’s colour is set by its worst dimension — its weakest link. A project with three green dimensions and one red one is red, because the red one is what needs attention. This is deliberate: health is a prompt to act, not an average that hides problems.
- 🟢 Green — healthy
- 🟡 Amber — at risk
- 🔴 Red — critical
- ⚪ Grey — no data yet
The 0–100 score sits alongside the colour as a magnitude, so you can compare two projects that are both, say, amber.
“Biggest drag”
Section titled ““Biggest drag””The Overview names the biggest drag — the specific dimension pulling the project down — so you know where to look first.
Rolling up to programmes and clients
Section titled “Rolling up to programmes and clients”The same idea repeats upward:
- A programme’s health is a weakest-link rollup of its member projects.
- A client’s health rolls up from its projects in turn.
So a single struggling project will surface at the programme and client level rather than being averaged away.
What you can see is what is counted
Section titled “What you can see is what is counted”Health is worked out from the records you are allowed to open. A risk, issue, task, tracker item or message above your clearance on a project is not counted in your health for that project. Two people with different clearance can see different colours for the same project, and that is expected. A workspace admin sees everything, so their health covers every record.
The same applies when health rolls up. A programme or client rollup scores each project from what you can see on it. A parent project only rolls up the sub-projects you have a role on, and the Sub-projects panel and the sub-project count in Settings only count those.
One exception remains for now: a risk marked as visible to project managers only is still counted in the health of anyone whose clearance reaches it, even though the risk register does not list it to them. That goes away when the project-manager-only mark becomes a clearance level of its own.