Executive Portfolio Escalation Summary(3.6.8)

This is the board-ready summary. It distills the entire portfolio's governance state into a handful of KPIs: number of projects currently in escalation, number approaching the escalation threshold, portfolio-level average risk score, and week-over-week change. No charts, no detail — just the numbers that executives need to assess whether the portfolio requires their attention.

What you can conclude

• A rising count of projects in escalation means the pattern is appearing in more projects rather than deepening in one, which is a portfolio-level reading rather than a project-level one.
• A falling portfolio average score means the projects' latest scores are lower on average than before; the cards do not show why.
• A stable count with no change from last week means the same number of projects sit in escalation; read the absolute level to know whether that number is high or low.

How this chart works

KPI card set showing: projects currently in escalation (score ≥70), projects requiring board alert (score ≥85), portfolio average score, and highest individual project score.

Reading the cards

A value shown as — means the read returned nothing or the figure could not be measured. It is never to be read as a zero: a measured zero is printed as a zero. A card with no figure also carries no accent color, because a tint is a judgment about a number and there is no number to judge.

The date range selects whether the portfolio snapshot appears at all, while the figures themselves are still taken from each project's latest complete scored week; the total projects tracked and the period start cover all recorded activity. Narrowing the range therefore changes whether these cards are shown, not the period they measure.

The week in progress is not counted: only complete weeks enter this number, so it does not change as the current week fills.