Project Portfolio Dashboard: What to Include (With Examples)

What Can a Portfolio Dashboard Do That a Project Dashboard Cannot?

A portfolio dashboard compares projects against each other and against available capacity, which a project dashboard cannot do because it only sees one project. That comparison is what supports a decision to stop, defer or reallocate, rather than a report that one project is behind.

The difference sounds administrative and is not. Ten project dashboards all showing green can coexist with a portfolio that is undeliverable, because each one is green against its own plan and none of them knows that the same four specialists appear in all ten. Aggregating ten green projects produces a green portfolio and a false sense of safety.

So the test for a portfolio dashboard is not whether it displays every project. It is whether it can answer a question no individual project can: given everything we have committed to, what should we stop?

Which Six Components Earn Their Space?

Six. Anything beyond these should name the decision it informs or come off.

• Portfolio health trend. Counts by status over time, not a static pie. The signal is movement: how many went green to amber since last period.
• Capacity committed against available. By team or skill. The number most portfolios have never calculated, and the one that explains most slippage. It comes from demand and capacity planning.
• Exceptions requiring a decision. A short list, each with an owner and the decision needed. The only component that makes the screen actionable rather than informational.
• Financial position with variance. Budget, actual and forecast, CapEx and OpEx separated. If finance cannot reconcile it against their ledger, the dashboard loses its authority.
• Schedule and cost performance. SPI and CPI rolled up, which turns “roughly on track” into a number. The mechanics are in EVM formulas and metrics explained.
• Benefits delivered against promised. The component most dashboards omit, and the one that keeps business cases honest. See how portfolio owners monitor benefit delivery.

Which Widgets Look Useful and Are Not?

These survive design reviews because nobody argues against them, and then quietly consume the space the six components need.

• The RAG pie chart. “62% green” without a trend says nothing. A portfolio going from 80% green to 62% and one climbing from 40% to 62% are in opposite situations and render identically.
• Portfolio-level burndown. Burndown assumes a shared backlog. Summing unrelated projects into one line produces a chart that cannot be wrong and cannot be useful.
• Average resource utilization. Averaging across the organization hides the bottleneck, which is the entire reason you were looking. 85% average utilization is compatible with one team at 140%.
• Projects delivered this quarter. An activity count. Delivering six low-value projects beats delivering two important ones on this measure, which is precisely backwards.
• Open risk count. Thirty-four risks tells you nothing without severity and age. Two unowned critical risks matter more than thirty-two logged minor ones.
• Milestone completion percentage. Milestones are not equal in size or importance, so the percentage is an unweighted average of incomparable things.

Each of these answers a question nobody is actually asking. The cost is not the pixel space, it is that they are easier to read than the components that matter, so attention lands on them first.

Why Is Percent Complete the Most Misleading Number on a Portfolio Dashboard?

It deserves its own section because it is the number executives reach for and the one that conceals trouble longest.

Three problems compound. First, percent complete usually measures effort consumed, not value delivered. A project 90% through its budget has delivered nothing if the remaining 10% is the integration that makes it work. Effort spent is a cost measure wearing a progress label.

Second, it cannot be aggregated honestly. Averaging 90% on a two-week project with 40% on a nine-month one produces 65%, a number describing no real state of the world. Weighting by effort helps slightly and still treats incomparable work as a single quantity.

Third, and most damaging, it moves smoothly while reality does not. Projects fail in steps, usually at integration, qualification or adoption. A line advancing two points a week right up to the moment it stops at 95% is the single most common shape in failed portfolios.

Replace it with three things that do move when reality does: milestones completed against milestones planned for this period, SPI, and remaining effort re-estimated rather than subtracted. The third is the uncomfortable one, because an honest re-estimate can increase, which is exactly why it is worth having.

Who Is the Dashboard For?

Three audiences, one dataset, three views. Building one screen for all three is the most common and most expensive design error.

The Three Dashboard Views Compared

The executive view is the one most often got wrong, because it is usually built by people who find the detail interesting. If it takes more than about ninety seconds to read, it will be replaced by someone’s summary slide, and the dashboard stops being the source of truth. The role-specific needs behind each column are set out in what PMO directors should look for in PMO software.

What Do Three Real Dashboards Look Like?

Three concrete layouts. The widget counts are deliberate: each view is sized to be read in one screen without scrolling.

Example 1: Executive portfolio dashboard

Read before a monthly portfolio review. Five widgets, no project-level detail.

• Portfolio health trend. Counts by status over six months, so direction is visible rather than the snapshot.
• Exceptions needing a decision. Maximum five rows: project, issue, owner, decision required. More than five means the threshold is set too loosely.
• Budget position. Committed, spent and forecast against the annual envelope, variance as one percentage.
• Strategic alignment. Share of active spend traceable to a stated objective, with the unaligned amount in currency.
• Benefits realized against promised. Rolling twelve months, as a ratio.

Example 2: PMO portfolio dashboard

The working view, read weekly. Capacity is the organizing idea, not status.

• Capacity heatmap by team or skill, flagging over-allocation.
• Committed demand against available capacity for the next two quarters.
• Cross-project dependency map, highlighting downstream risk from slipped upstream milestones.
• Projects by stage gate, showing what is waiting for a decision and for how long, based on each project’s tollgate stage.
• SPI and CPI by project, sorted worst first.
• Intake queue: requests received, triaged and decided, with average decision time.
• Risks and issues above a severity threshold, with owner and age.
• Resource conflicts: named people committed to more than one project in the same window.

Example 3: Delivery team dashboard

Read daily. Scoped to the team’s own work, with just enough portfolio context to explain priority.

• Milestones due in the next 30 days, with health.
• Blocked items, with what each is waiting on and who owns it.
• Team capacity this sprint against committed work.
• Dependencies owed to and from other teams.
• Open risks and issues for this team’s projects.
• The objective each project supports, so priority has a visible reason when it changes.

The same records feed all three. When a milestone slips on the delivery view, the PMO view’s dependency map and the executive view’s exception list both update without anyone rebuilding a deck.

How Do You Read One in a Live Review?

A dashboard earns its place in the meeting or it does not have one. Here is a 20-minute portfolio review run from the executive view alone, with no supporting slides.

1. Minutes 0 to 2: direction, not position. Open on the health trend. The question is not “how many are green” but “which way is this moving and since when”. A single period’s snapshot gets skipped.
2. Minutes 2 to 6: the exception list, top to bottom. Each row gets a decision or an owner and a date. Rows that get neither are removed from the list, because an exception nobody will act on is not an exception.
3. Minutes 6 to 10: capacity. If committed demand exceeds available capacity, this is the only agenda item that matters and the rest of the meeting changes shape. Most reviews skip this because it is uncomfortable.
4. Minutes 10 to 14: money. Variance against forecast, and specifically whether the forecast changed since last period. A forecast that never moves is not being maintained.
5. Minutes 14 to 18: benefits. What completed since last review, and what it actually delivered against its business case. This is the agenda item most often dropped for time, which is why business cases inflate.
6. Minutes 18 to 20: what stops. Close by naming anything being stopped, paused or deferred, and where the released capacity goes. A review that never produces one of these is a status meeting.

Whatever sends someone reaching for a spreadsheet during that twenty minutes is your missing widget. Whatever nobody looks at across three consecutive reviews should come off.

What Can a Portfolio Dashboard Not Tell You?

Knowing the limits is what stops a dashboard being trusted beyond its evidence.

• Whether a project should exist. A dashboard reports on what was funded. Deciding what deserves funding is a separate exercise, done with a project prioritization matrix against capacity.
• Whether the estimates are honest. Garbage in renders beautifully. A portfolio of optimistic estimates produces a confident green dashboard right up until it does not.
• Whether anyone is working around it. Shadow spreadsheets are invisible to the system they replace, and their existence is the clearest sign the dashboard has lost trust.
• What it will cost politically to stop something. The dashboard can show a project is failing. It cannot tell you that its sponsor is about to be promoted, which is frequently the operative fact.
• Quality. On time, on budget and unusable is a real outcome, and no portfolio metric catches it. Only the benefits check after go-live does.
• Whether a decision was acted on. Dashboards show state, not follow-through. That needs the decision log and a mechanism like go, hold, or stop decisions.

None of this argues against dashboards. It argues against treating a dashboard as the whole governance system, which is how organizations end up well-informed and still unable to change course. The reconciliation question specifically is covered in the portfolio reporting metrics every CFO should ask for.

Where Does the Data for All This Come From?

From the systems the work already happens in, ideally, rather than from anyone assembling it. Profit.co’s project portfolio management software generates all three role-based views from the same project records, so the executive exception list and the delivery milestone board are the same data read at different altitudes.

See how Profit.co builds executive, PMO and delivery views from one portfolio. Book a demo.