Portfolio Visibility at Scale: What 25+ Dashboard Widgets Reveal About Program Health
Portfolio visibility at scale means seeing the financial, funding, execution, and risk condition of every project in one governed view — segmented by the type of work, tailored to the role looking at it, and built on metric definitions everyone trusts. A good project portfolio dashboard doesn’t just display more charts. It answers seven specific questions about program health, without anyone having to assemble a report first.
Most organizations don’t lack data. They lack a view of that data that still holds up at 50, 150, or 250 projects. Finance pulls one export, the PMO builds another, and executives get a monthly deck that’s already out of date when it’s presented. By the time a cost trend or an approval backlog shows up in that deck, it has usually been compounding for weeks.
This guide breaks down the seven signals a portfolio dashboard should reveal, what to evaluate for each one, and how PACE by Frontrol covers them with more than 25 configurable widgets — built separately for capital owners and for the firms that deliver their projects.
IN THIS GUIDE
- Why portfolio visibility breaks down at scale
- The 7 signals of program health
- What makes a portfolio dashboard trustworthy
- An illustrative scenario: the monthly portfolio review
- Questions to ask a vendor
- How PACE solves this, end to end
- Frequently asked questions
Why Portfolio Visibility Breaks Down at Scale
At five projects, a spreadsheet and a weekly meeting can keep everyone aligned. At fifty, the same approach starts to crack. At a few hundred, it stops working entirely. Three failure modes show up again and again.
One view for everyone. A capital owner and a delivery firm look at the same project and ask completely different questions. The owner wants to know how much of each funding source has been consumed, how spend splits between capex and opex, and which authorizations are still waiting for approval. The delivery firm wants to know how much work is unbilled, how old its receivables are, and whether margin is holding. A generic dashboard that tries to serve both ends up serving neither.
Metrics nobody can explain. When “cost to date” means one thing in the finance report, another in the PMO tracker, and a third in the project manager’s spreadsheet, the portfolio review turns into a reconciliation exercise. The meeting is spent agreeing on the numbers instead of acting on them.
Reporting as a project of its own. Someone spends days each month exporting, cleaning, and formatting data so leadership can see it. The dashboard becomes a snapshot of last month rather than a view of now — and the person building it has no time left to analyze what it shows.
That’s why counting widgets is the wrong way to evaluate a portfolio tool. The right question is: which decisions does each view support, and for whom? The seven signals below are a practical way to answer it.
The 7 Signals of Program Health
1. Financial performance against plan
The first question at any portfolio review is simple: is the work tracking to budget and forecast — and in which direction is it moving? A single variance number isn’t enough. Leaders need to see trend, and they need to see it across the portfolio, not one project file at a time.
WHAT TO EVALUATE
- Is earned value visible at the portfolio level, not only inside individual projects?
- Can you see performance trend over time, not just a point-in-time snapshot?
- Does the view distinguish budget, month-to-date, year-to-date, inception-to-date, and forecast?
INSIDE PACE PACE’s Earned Value, Trend analysis, Project performance trend, and Profit and loss widgets show performance against plan across the portfolio. For contract programs, PACE rolls CPI, SPI, percent complete, cost, and revenue up from every sub-project into a single program view. When finance needs the numbers in its own models, the Excel (all tabs) export downloads a complete workbook with Budget, MTD, YTD, ITD, and Forecast tabs — the same figures the dashboard shows, with no rebuilding. |
2. Funding and capital consumption
For capital owners, the most consequential question isn’t only “are we on budget?” but “which money are we spending, and how much of it is left?” Grants, reserves, and debt carry different rules and different consequences when they run short. A portfolio dashboard that can’t show spend by funding source leaves the most important constraint invisible.
WHAT TO EVALUATE
- Can you see spend by source of funds — the “color of money” — across the portfolio?
- Is the capex/opex split visible without a separate finance report?
- Are you warned before a funding allocation runs out, or only after?
INSIDE PACE The Color of money and Capex/Opex widgets are part of PACE’s Capital widget catalog. Underneath them, PACE tracks consumed funds against remaining funds on every funding line and raises alerts as a line approaches its threshold or goes negative. Business rules protect the funding envelope itself: a proposed allocation can’t exceed remaining funds, and funding can’t be reduced below what has already been consumed. |
3. Cash, billing, and receivables
For engineering, construction, and consulting firms, program health is also a cash question. A project can be on schedule and on budget while unbilled work piles up and receivables age past terms. Those signals rarely appear in a project manager’s status update, which is exactly why they belong on the portfolio view.
WHAT TO EVALUATE
- Are aged receivables and aged unbilled work visible as trends, not just balances?
- Can you move from the portfolio view into billing detail by project?
- Is the net receivables position visible without waiting for month-end close?
INSIDE PACE PACE’s Contract widget catalog includes Aged AR trend, Aged unbilled trend, Billing & AR details, Net receivables, and Profit and loss — the cash view delivery firms need, kept separate from the capital owner’s funding view so each audience sees the metrics that matter to its business. |
4. Commitments and spend exposure
Actual cost tells you what has already happened. Commitments tell you what is about to. Purchase orders, subcontracts, and supplier invoices in flight are where tomorrow’s overrun is already visible today — if anyone is looking.
WHAT TO EVALUATE
- Are commitments and purchase order status visible against budget?
- Can you see supplier invoices before they post as actuals?
- Is current-week cost visible, or only last month’s close?
INSIDE PACE The Commitments detail & PO status, Supplier invoices, and This week cost widgets surface exposure before it lands in the actuals, so the portfolio view reflects what’s coming as well as what’s already been spent. |
5. Change exposure
A handful of approved change orders rarely threatens a program. A growing backlog of pending ones often does. The signal to watch isn’t any single change — it’s the volume and value of changes moving through the pipeline, and how that trend will eventually show up in the forecast.
WHAT TO EVALUATE
- Can you see change orders by status and by value across the whole portfolio?
- Is the financial trend of changes visible over time?
INSIDE PACE PACE’s change order widgets show both number and value by status, plus a Change order financial trend, so a rising volume of pending changes is visible at the portfolio level before it reaches the forecast. |
6. Execution flow and bottlenecks
Some of the most expensive delays in a capital program have nothing to do with cost codes. They come from work that is simply waiting: an approval sitting in someone’s inbox, a submittal pending review, an RFI with no clear owner. At portfolio scale, these bottlenecks are invisible unless the dashboard shows where work is stuck — and on whom.
WHAT TO EVALUATE
- Are pending approvals visible across the portfolio?
- Can you see open RFIs and submittals, and who holds the next action?
- Is deliverable progress measured from actual quantities, or estimated by feel?
INSIDE PACE The Pending approvals, RFI, Submittals, Transmittals, Deliverables, Activities, Task assignment trend, and Business process widgets show where execution is moving and where it’s stuck. Submittal dashboards break open items down by ball in court and by subcontractor, so every bottleneck has a name. Deliverable progress is calculated, not declared: Percent Complete = Actual Quantity ÷ Planned Quantity × 100. |
7. Risk exposure
A risk register that lives in project folders protects individual projects. A risk view at portfolio level protects the program. Leaders need to see which risks are most severe across all projects, who owns them, and how much contingency stands behind them — scored the same way everywhere, so comparisons actually mean something.
WHAT TO EVALUATE
- Is risk visible at the portfolio level, or only inside each project?
- Is severity calculated consistently, or rated subjectively by each project manager?
- Is contingency tied to risk level?
INSIDE PACE The Risk Register widget brings project risks into the portfolio view. In PACE, Risk Level is calculated automatically from likelihood and impact and can’t be overridden manually, and the Net Contingency Amount updates with it — so the portfolio sees risk scored on the same scale for every project. A KPI widget complements it for the indicators each organization tracks. |
What Makes a Portfolio Dashboard Trustworthy
The seven signals describe what a dashboard should show. Whether people actually rely on it depends on three design choices underneath.
It’s built for the type of work. Capital programs and contract delivery are different businesses with different metrics. In PACE, the available widget catalog changes with the project class — Capital, Contract, or blended. Blended portfolios that mix both are supported; for certain widgets they’re limited to 250 projects, beyond which PACE suggests refining filters or splitting the portfolio. It’s a deliberate choice to keep each view meaningful rather than averaging two businesses into one.
Every metric has a definition. A number people can’t explain is a number people won’t act on. Each PACE widget includes a Help icon that explains its source logic and metric definitions. The dashboard isn’t a black box — anyone in the review can see how a figure was calculated.
Each role gets its own view without breaking the shared picture. Finance, the PMO, and executives need different cuts of the same data. PACE users build views from selectable widgets, personalize table columns and filters inside a widget without changing the dashboard’s global filter, open any widget in full-screen mode for reviews, and export to Excel, CSV, or a complete multi-tab workbook. Standard portfolio reports — portfolio project report, AFE summary and details, single project list, submittals, and RFIs — cover the recurring outputs.
An Illustrative Scenario: The Monthly Portfolio Review
ILLUSTRATIVE SCENARIO — NOT A REAL CLIENT CASE A capital program office oversees 140 active projects across three business lines. Preparing the monthly portfolio review takes the team most of a week: exports from the financial system, a funding tracker in Excel, risk logs from individual project folders, and one slide per business line. With segmented, role-based dashboards, the preparation step largely disappears because the views are already current. Finance opens the Capital view and sees, in the Color of money widget, that one grant-funded line is close to its threshold — PACE has already flagged it. The PMO’s view shows a cluster of submittals waiting on the same review group, broken down by ball in court. The executive view shows, through Trend analysis and Earned Value, three projects whose performance has slipped for three consecutive periods, and the Risk Register widget shows two Very High risks with their contingency attached. The meeting starts with decisions instead of reconciliation: reallocate the constrained funding line, escalate the review backlog, approve a mitigation plan. The numbers aren’t debated, because everyone can see where they come from. |
Questions to Ask a Vendor
Use these questions to test whether a portfolio tool delivers real visibility or just more charts:
- Does the dashboard adapt to the type of project — capital versus contract — or is it one generic view for everyone?
- Can we see funding consumption by source, and are we alerted before an allocation is exhausted?
- How is each metric defined, and can users see the calculation behind it?
- Can each role build its own view without changing what everyone else sees?
- Are execution bottlenecks — approvals, RFIs, submittals — visible at portfolio level, with a named owner for the next action?
- Is risk scored consistently across projects, and is contingency tied to the score?
- What happens at scale — how many projects can a mixed portfolio view handle, and how does the tool behave beyond that?
- Can we export the underlying numbers — budget, MTD, YTD, ITD, forecast — without rebuilding them?
How PACE Solves This, End to End
A dashboard is only as good as what sits underneath it. In PACE, portfolio widgets read from the same modules teams use to run the work every day: funding lines and AFEs, estimates and forecasts, commitments and supplier invoices, RFIs, submittals, deliverables, and the risk register. Nobody rebuilds a report for the portfolio view — it reflects the work as it is recorded.
That shared foundation is what lets PACE speak two business languages without forcing a generic model. Capital owners see capital: color of money, capex/opex, funding consumption, and AFE status. Delivery firms see the business of delivery: receivables, unbilled work, profit and loss, and change orders. Both see execution flow and risk on the same scale.
And because status reports in PACE pull live widgets — financials, risks and issues, deliverables — into a dated snapshot that becomes read-only once completed, the history of program health is preserved and auditable. Leaders can see not only where the portfolio stands today, but how it got there.
The result is a portfolio view people trust enough to act on: built for the type of work, defined metric by metric, and current without anyone having to assemble it.
Frequently Asked Questions
What is a project portfolio dashboard?
A project portfolio dashboard is a single view that consolidates financial, funding, execution, and risk data across many projects, so leaders can compare performance and spot problems without assembling reports manually.
What should a capital program dashboard include?
For capital owners, it should show performance against plan, funding consumption by source (color of money), the capex/opex split, change exposure, execution bottlenecks, and risk with contingency. PACE’s Capital widget catalog covers each of these.
How is a dashboard for service providers different?
Engineering, construction, and consulting firms also need cash signals: aged receivables, aged unbilled work, billing detail, net receivables, and profit and loss. PACE provides these in a separate Contract widget catalog.
How many dashboard widgets does PACE offer?
PACE documents more than 25 widget types, including Earned Value, Color of money, Capex/Opex, Aged AR trend, Change order financial trend, Pending approvals, RFI, Submittals, Risk Register, and KPI.
Can one dashboard combine capital and contract projects?
Yes. PACE supports blended portfolios. For certain widgets, blended portfolios are limited to 250 projects; beyond that, PACE suggests refining filters or splitting the portfolio to keep the view meaningful.
How do I know the dashboard numbers are right?
Each PACE widget includes a Help icon that explains its source logic and metric definitions, and key values such as risk level and percent complete are calculated by the system rather than typed in by hand.
Can we still work in Excel?
Yes. Any widget can be exported to Excel or CSV, and the Excel (all tabs) option downloads a complete workbook with Budget, MTD, YTD, ITD, and Forecast tabs.
