Sign in

Blog · Board and management reporting

Power BI project management dashboard: costs and progress

Compare approved project budgets, actual costs, and evidenced progress at the same reporting date. A worked portfolio example shows why budget remaining alone cannot establish project health.

The short answerA Power BI project management dashboard should compare actual costs with approved budgets and independently measured progress at the same cutoff. Include planned work value, earned work value, cost variance, schedule variance, and unresolved exceptions. Reconcile project totals to the cost export, and weight portfolio progress by approved budget rather than averaging project completion percentages.

A Power BI project management dashboard should compare actual costs with approved budgets and verified progress at the same reporting cutoff. Budget remaining tells you how much approved funding has not been spent; it does not establish how much work is finished or whether the project is on schedule.

Microsoft defines a Power BI dashboard as a single page of visual highlights, supported by related reports. The business layout below puts portfolio exceptions on that page and keeps the arithmetic visible in the project detail. Covirage is not affiliated with Microsoft, the maker of Power BI and Excel.

Choose a common basis for cost and progress

Consider an illustrative Colorado manufacturer reviewing internal improvement projects on October 23, 2026. Its project cost export contains approved budget, planned work value at the cutoff, verified physical completion, and actual cost including the finance team's recorded accruals. All amounts are USD.

Approved budget is the current authorized baseline for the complete project. Planned value is the budget assigned to work that should be completed by the cutoff. Completion is based on accepted deliverables, with the method agreed before reporting. Actual cost is the recorded cost of work performed to that same date.

The US Department of Energy describes earned value management as integrating scope, cost, and schedule. This example uses that comparison to stop spending from being mistaken for progress. It is a business review of the exports, rather than platform setup instructions.

The project manager owns completion evidence. Finance owns the cost reconciliation. The budget approver owns authorized changes to the baseline. A single person can coordinate the page, but these responsibilities should remain visible when a disputed number reaches the review meeting.

Work the example from the project rows

For this example, each project's completion percentage represents the share of its budget-weighted work that has been accepted. That assumption allows earned value to be calculated as approved budget multiplied by completion. It would not be valid for a percentage based only on elapsed time.

Project Approved budget (USD) Planned value at cutoff (USD) Verified completion Actual cost (USD)
Order system upgrade 120,000 60,000 40.0% 75,000
Warehouse redesign 80,000 48,000 60.0% 55,000
Customer portal 100,000 30,000 20.0% 35,000
Total 300,000 138,000 Calculated below 165,000

Use the following definitions, with a positive variance favorable:

Earned value = Approved budget × Verified budget-weighted completion

Cost variance = Earned value − Actual cost

Schedule variance = Earned value − Planned value

Project Earned value calculation (USD) Earned value (USD) Cost variance (USD) Schedule variance (USD)
Order system upgrade 120,000 × 40.0% 48,000 -27,000 -12,000
Warehouse redesign 80,000 × 60.0% 48,000 -7,000 0
Customer portal 100,000 × 20.0% 20,000 -15,000 -10,000
Total 48,000 + 48,000 + 20,000 116,000 -49,000 -22,000

The upgrade has consumed $75,000 to deliver work budgeted at $48,000. Its cost variance is 48,000 − 75,000 = -$27,000. Planned value was $60,000, so its schedule variance is 48,000 − 60,000 = -$12,000. The latter is a budget-dollar measure of work behind plan, not a count of days late.

The warehouse has delivered the planned amount of work but at a higher cost. The portal is both behind its planned work value and unfavorable on cost. Those are different conversations, so avoid a single color that obscures the cause.

Reconcile the portfolio before interpreting it

Actual cost is 75,000 + 55,000 + 35,000 = $165,000. Tie that amount to the project cost export and its reconciliation to the finance records. Check that cost reversals, transfers, and accruals are included once, rather than assuming every payment belongs to completed work.

The variance checks are:

Check Calculation (USD) Result (USD)
Cost variance from totals 116,000 − 165,000 -49,000
Sum of project cost variances -27,000 − 7,000 − 15,000 -49,000
Schedule variance from totals 116,000 − 138,000 -22,000
Sum of project schedule variances -12,000 + 0 − 10,000 -22,000

The matching totals prove that the portfolio summary uses the same rows as the detail. A mismatch means the filters or classifications need correction before the meeting.

Budget utilization is 165,000 / 300,000 = 55.0%. Budget-weighted completion is 116,000 / 300,000 = 38.7%, rounded to one decimal place. The simple average of 40.0%, 60.0%, and 20.0% is 40.0%; it answers a different question by giving every project equal weight.

For the full monthly review sequence, use the management reporting guide. The broader Power BI dashboard examples cover the executive presentation around these project-specific measures.

Change only the upgrade's completion evidence

Suppose accepted work now supports 50.0% completion for the order system upgrade, replacing 40.0%. Change that input alone: approved budgets, planned values, and actual costs remain fixed. This is an evidence revision at the same cutoff, rather than a prediction about what extra spending would achieve.

Measure Original evidence Revised completion evidence
Upgrade completion 40.0% 50.0%
Upgrade earned value (USD) 48,000 60,000
Upgrade cost variance (USD) -27,000 -15,000
Upgrade schedule variance (USD) -12,000 0
Portfolio earned value (USD) 116,000 128,000
Portfolio cost variance (USD) -49,000 -37,000
Portfolio schedule variance (USD) -22,000 -10,000
Portfolio budget-weighted completion 38.7% 42.7%

The additional earned value is 120,000 × (50.0% − 40.0%) = $12,000. Upgrade earned value becomes 120,000 × 50.0% = $60,000, giving cost variance of 60,000 − 75,000 = -$15,000 and schedule variance of 60,000 − 60,000 = $0. Portfolio earned value is 60,000 + 48,000 + 20,000 = $128,000; its variances are 128,000 − 165,000 = -$37,000 and 128,000 − 138,000 = -$10,000.

Portfolio completion becomes 128,000 / 300,000 = 42.7%. The upgrade catches up with planned work value but still has an unfavorable cost variance; the evidence change does not erase its cost overrun relative to completed work.

Turn the measures into a review decision

Put approved budget, actual cost, weighted completion, and unfavorable variances at the top. Underneath, show the project comparison and the specific unaccepted milestones or disputed costs. A reviewer should be able to move from an exception to its owner and supporting record.

Construction-specific comparisons belong in the Power BI construction dashboard, while potential future exposures belong in the Power BI risk management dashboard. For a spreadsheet route to the review, see the Excel dashboard guide.

Where it goes wrong

  • Calling spending progress. Deposits and rework can raise actual cost without completing budgeted work.
  • Mixing cutoffs. A later cost export against earlier completion evidence creates a variance that cannot be interpreted fairly.
  • Averaging project percentages. Equal weighting changes the portfolio question and should never be hidden.
  • Changing the baseline silently. An approved scope revision needs a dated explanation so the comparison remains understandable.
  • Reading dollars as days. Schedule variance in earned value terms does not establish the calendar delay.

Compare your project export in Covirage

Bring a sample of your own project budget, cost, and progress file with a common reporting date. Covirage maps the columns, its tools compute and check the figures, and the external AI model explains the differences with every figure traced to its rows. Create a free Covirage account; account creation takes about a minute, then you set up your business and bring your file.

See project cost control for the supporting business context.

Questions people ask

What belongs on a project management dashboard?

Show approved budget, actual cost, planned progress, verified completed work, and the differences that need action. Include the reporting cutoff and named owner. Milestone evidence and unresolved cost items are more useful than a status color without an explanation.

Can budget spent stand in for project progress?

No. Paying for materials, deposits, or rework can increase spending without increasing completed work. Measure progress using accepted deliverables or another documented method, then compare its approved budget value with actual cost for the same project scope.

Should portfolio completion be an average of project percentages?

Use a weighting that matches the decision. Budget-weighted progress compares completed work with the portfolio's approved cost baseline. A simple average instead gives a small project the same influence as a large one. Label the weighting so readers know what it measures.

Does schedule variance show days late?

Not when calculated as earned value minus planned value. That variance is expressed in budget dollars and compares work accomplished with work planned. Use milestone dates or schedule records to determine the calendar delay and its effect on the completion date.