CIO dashboard KPIs: twelve indicators with thresholds
A CIO dashboard needs about twelve indicators, each with a definition, a formula and an amber and a red threshold: six on the budget (revised budget, actuals to date, spend rate against the share of the year elapsed, commitment rate, forecast variance, budget lines on alert), four on the project portfolio (active projects, share of green projects, red projects, average delay), one on risks (open high or critical risks) and one on execution (overdue actions). Team capacity adds a leading indicator: the number of team-months above 100% load. The thresholds below are the default settings of the IT PMO Cockpit, offered as starting points to calibrate, not as industry norms.
Twelve indicators are enough
An indicator earns its place if a red value leads to a decision someone can name. Long catalogues of KPIs fail that test: they are hard to read in a meeting, and the few that matter get lost. Twelve fit on one page, can be commented quickly by starting with the reds, and can be computed from four sources the IT department already holds: the budget sheet, the project portfolio, the risk register and the decision log. If you need a governance reference, ISO 21502:2020, Project, programme and portfolio management — Guidance on project management, gives guidelines for project management; it does not set KPI thresholds, which remain your choice.
Budget indicators
| No. | Indicator | Formula | Amber | Red |
|---|---|---|---|---|
| 1 | Revised IT budget | Sum of the revised budgets of all lines | — | — |
| 2 | Actuals to date | Sum of the monthly actuals | — | — |
| 3 | Budget spend rate | Actuals / revised budget, compared with the share of the fiscal year elapsed | Ahead by 5 points or more | Ahead by 10 points or more |
| 4 | Commitment rate | Committed / revised budget | — | Above 100% |
| 5 | Forecast variance | (Year-end forecast − revised budget) / revised budget | 5% or more | 10% or more |
| 6 | Budget lines on alert | Number of lines whose forecast variance is amber or red | 4 or more | 8 or more |
Indicator 5 is the one to manage: it says where the year will end. Indicator 3 needs a benchmark, the share of the fiscal year elapsed at the status date: =(StatusDate-DATE(FY,1,1)+1)/(DATE(FY,12,31)-DATE(FY,1,1)+1). The alert fires only when spending runs ahead; spending far behind raises a question (late invoices, slipping projects) rather than an alarm. How the forecast is built line by line is explained in the IT budget template with CapEx, OpEx and forecast.
Portfolio indicators
| No. | Indicator | Formula | Amber | Red |
|---|---|---|---|---|
| 7 | Active projects | Projects neither completed nor cancelled | — | — |
| 8 | Share of green projects | Green projects / active projects | Below 70% | Below 50% |
| 9 | Red projects | Number of projects with a red status | 1 or more | 3 or more |
| 10 | Average delay of active projects | Average of (forecast end − baseline end), in days | 15 days or more | 30 days or more |
These indicators are only as honest as the project status behind them. Compute it from delay and budget drift rather than letting each project manager choose a colour, and measure the delay against the original end date, not the latest re-plan.
Risk and decision indicators
| No. | Indicator | Formula | Amber | Red |
|---|---|---|---|---|
| 11 | Open critical or high risks | Risks not closed with a score (probability × severity, 1 to 25) of 12 or more | 3 or more | 6 or more |
| 12 | Overdue actions | Actions neither done nor cancelled whose due date has passed | 3 or more | 6 or more |
Indicator 12 measures the committee's own discipline: if it climbs, decisions are being taken and not carried out. With the decision log in a table, it is one line: =COUNTIFS(Actions_Status,"<>Done",Actions_Status,"<>Cancelled",Actions_Due,"<"&StatusDate). If your dashboard also covers suppliers, the contract register adds two counts in the same spirit, notices due soon and notice deadlines missed: see the IT contract register.
Capacity indicators
Team overload is an early signal of a delay that has not yet appeared in the portfolio. Two measures are enough:
- Load rate per team and month: FTEs assigned / FTEs available. Amber from 90%, red above 100%.
- Overloaded team-months: the number of team × month pairs above 100%, over the next months. Amber from 3, red from 8.
A team planned above 100% three months from now is likely to delay a project then, unless a lower-priority project moves or the team is reinforced. That is a decision for the committee, which is why capacity sits on the same page as the budget.
Thresholds and reading
Set each threshold once, in a settings tab that drives the colours, and review them at a quarterly review, never the day before a committee. Read the page from red to green: say in one sentence why an indicator is red and what you ask of the committee; note the greens without comment.
A fictitious example: at a status date of 30 September in a calendar fiscal year, 273 of 365 days have elapsed, 74.8% of the year. Actuals stand at 81% of the revised budget, 6.2 points ahead: indicator 3 is amber, and the question becomes whether invoices arrived early or the forecast is too low. The same month, commitments reach 103% of the revised budget: indicator 4 is red, and the overrun must be dealt with before the invoices arrive.
FAQ
Why not track more indicators?
Because each extra one dilutes the page. Keep supporting figures in a backup tab, and promote one to the dashboard only when a red value would change a decision.
Where do the thresholds come from?
The values above are the cockpit's defaults, suited to its target of IT departments in companies of 200 to 5,000 employees. Adjust them after two or three committees, based on how often each one fires.
Monthly or weekly?
Budget indicators move monthly, after the accounting close; portfolio, risk and action indicators can be refreshed weekly when project managers update their rows.