Blog · Board and management reporting
A PMO dashboard compares forecast project costs, milestone exceptions and resource demand across a portfolio. Work through a complete example that shows why a balanced total can conceal project overruns and staffing shortages.
PMO dashboards compare project costs, milestone delays and resource demand across a portfolio so leaders can decide where to intervene. Use one agreed reporting date, then retain the project rows behind every total. A portfolio can meet its overall budget while an individual project runs over and another team lacks the hours needed to deliver.
Start with a project register that identifies the approved portfolio, project owner, status, baseline version and reporting date. Decide explicitly whether completed, paused and proposed projects belong in each measure. A proposed project's staffing request should not silently enter the same total as approved delivery commitments.
Connect the register to a cost ledger export, the latest remaining-cost forecast, a milestone schedule and a resource demand file. Stable project identifiers let those files describe the same work. Finance owns the cost cutoff; project managers own remaining estimates; resource leads confirm available hours and the assignments they support. The PMO owns the combined review and its action list.
The US Department of Energy's explanation of earned value management emphasizes the integration of cost, schedule and scope. That is a useful discipline for a portfolio review, even when the supplied records do not support a full earned value calculation. Spending below budget alone does not prove that work is ahead of plan.
Consider three internal delivery projects at a US distribution company, reporting at September 30, 2026. Actual costs include approved accruals through that date. Forecast remaining cost includes all expected future work, including outstanding commitments; commitments are not added again as a separate cost layer.
| Project | Approved budget (USD) | Actual cost to date (USD) | Forecast remaining cost (USD) | Forecast final cost (USD) | Forecast less budget (USD) |
|---|---|---|---|---|---|
| Atlas | 200,000 | 80,000 | 130,000 | 210,000 | 10,000 |
| Beacon | 150,000 | 60,000 | 80,000 | 140,000 | -10,000 |
| Cedar | 100,000 | 20,000 | 80,000 | 100,000 | 0 |
| Portfolio | 450,000 | 160,000 | 290,000 | 450,000 | 0 |
Forecast final cost = Actual cost to date + Forecast remaining cost
Forecast budget variance = Forecast final cost − Approved budget
Atlas forecasts 80,000 + 130,000 = $210,000, exceeding its $200,000 budget by $10,000. Beacon's 60,000 + 80,000 = $140,000 forecast is $10,000 below budget. Cedar forecasts 20,000 + 80,000 = $100,000, equal to its budget.
The portfolio check is 160,000 + 290,000 = $450,000, which also equals 210,000 + 140,000 + 100,000. Its net variance is zero, but the dashboard should display $10,000 of gross overruns and $10,000 of forecast savings separately. Ask Atlas's owner what changed and Beacon's owner whether the expected saving depends on scope being removed.
Keep the baseline visible beside any approved changes. Replacing the original budget with the latest forecast makes the variance disappear without explaining the decision. The broader cost variance method covers consistent signs and comparison bases.
For this example, the milestone denominator includes all approved baseline milestones due before the reporting cutoff. The overdue count includes those still incomplete at that cutoff. Completed milestones that finished late need a separate historical measure; they are not included in this current overdue count.
| Project | Baseline milestones due before cutoff | Still incomplete and overdue | Overdue share |
|---|---|---|---|
| Atlas | 5 | 1 | 20.0% |
| Beacon | 4 | 2 | 50.0% |
| Cedar | 3 | 0 | 0.0% |
| Portfolio | 12 | 3 | 25.0% |
The portfolio rate is 3 / 12 = 25.0%, calculated from the summed counts. It does not measure portfolio completion: the table counts milestones, which may differ greatly in effort and business importance. Percentages are rounded to one decimal place throughout.
Beacon needs a delivery discussion despite its forecast cost saving. Ask whether delayed work is merely pushing costs into a later period, or whether the remaining forecast genuinely covers it. Identify the overdue milestones, their owners and their consequences for dependent projects. Use a progress dashboard for milestone-level investigation and a project KPI dashboard for the individual project's wider performance.
Resource demand uses a forward window, clearly labeled here as the week beginning October 5, 2026. Available hours are approved project allocations after leave and other commitments. Each person's hours are allocated once across the projects, so the portfolio does not count the same shared capacity repeatedly.
| Project | Required hours | Allocated available hours | Required less allocated hours | Project shortage hours |
|---|---|---|---|---|
| Atlas | 160 | 140 | 20 | 20 |
| Beacon | 120 | 120 | 0 | 0 |
| Cedar | 90 | 100 | -10 | 0 |
| Portfolio | 370 | 360 | 10 | 20 |
The portfolio needs 370 / 360 = 102.8% of its allocated available hours. Its net gap is 10 hours, but Atlas's shortage is 20 hours while Cedar has 10 spare hours. The shortage column sums project-level positive gaps, so it deliberately differs from the net gap.
Do not assume those spare hours can move to Atlas. Confirm skills, timing and dependencies before reassigning people. Review resource utilization for the separate question of how available labor is used; this table compares future demand with approved allocations.
Reconcile actual costs to finance's project ledger and remaining costs to the approved forecast version. Confirm every included project appears once in the summary, and identify missing forecasts explicitly. A blank remaining estimate must not imply that no further spending is expected.
For an Excel export with project IDs in column A and actual cost entries in column B, the Atlas subtotal is:
=SUMIFS(B2:B1000,A2:A1000,"Atlas")
Restrict the export to the agreed cutoff and extend the range to include every row. Microsoft documents SUMIFS as summing amounts that meet the specified criteria. Covirage is not affiliated with Microsoft.
Bring your project register, cost export, remaining forecast, milestones and resource allocations to Covirage, which maps the columns so its tools can compute and check the comparisons. The external AI model explains the result with every figure traced to its rows. Create a free Covirage account, then set up your business and bring a sample of your own data.
See project cost control for the supporting business context.
Include the approved portfolio, project owners, cost baselines, actual costs, forecast remaining costs, overdue milestones and upcoming resource demand. Add the reporting date and forecast version. Every exception should identify the decision required and the person responsible for resolving it.
A PMO dashboard compares multiple projects and shared constraints so leaders can allocate resources and resolve portfolio conflicts. A project dashboard provides more detail about one project's work packages and delivery. The portfolio view should retain links or identifiers that lead back to that supporting detail.
Yes. Forecast savings on one project can offset an overrun elsewhere, leaving the portfolio total unchanged. Show overruns and savings separately alongside the net variance, and confirm that the forecast savings are credible before treating them as available headroom.
Match the update frequency to the decisions and available records. A weekly delivery review can use current milestone and staffing records, while monthly cost figures should follow finance's close. Clearly mark different cutoffs if a single meeting uses both, and avoid implying they are synchronized.