Blog · Board and management reporting
Build a project management report that connects the approved baseline with incurred costs, open commitments and forecast completion. A worked warehouse installation shows the report tables, spreadsheet formulas and reconciliation checks.
A project management report compares approved cost and delivery milestones with incurred costs, remaining work and forecast completion. Its purpose is to show what has changed, what the project is now expected to cost, and which decisions need an owner. A low spending total is not evidence that delivery is on track.
Identify the project, reporting cutoff, currency, scope and approved baseline version on the opening page. Preserve the original budget and show approved changes separately. A pending request belongs in the exception discussion until it is authorized.
The Department of Energy's explanation of earned value management connects cost, schedule and technical accomplishments. The same discipline helps an ordinary project review: spending, progress and milestones must describe the same work at the same date.
Use the project KPI guide for measure definitions and project cost management for the broader control process. This report brings their results together for a sponsor's review.
Bring the approved budget, change register, project cost export, remaining purchase commitments and the delivery team's estimate of uncommitted work. Keep work-package identifiers on every file. Retain document references so finance can distinguish posted invoices, accruals and future purchases.
Consider a US distributor installing equipment in a warehouse. Its September 30, 2026 report starts with this Budget worksheet. Columns A through D contain the fields below; data occupy rows 2 through 5.
| Work package | Original budget (USD) | Approved changes (USD) | Approved baseline (USD) |
|---|---|---|---|
| Design | 60,000 | 0 | 60,000 |
| Equipment | 180,000 | 20,000 | 200,000 |
| Installation | 120,000 | 10,000 | 130,000 |
| Testing | 40,000 | 0 | 40,000 |
| Total | 400,000 | 30,000 | 430,000 |
Calculate the approved baseline in D2, then fill down:
=B2+C2
The change register must support the $30,000 addition. The DOE implementation guidance treats change control as a distinct part of project management. Preserve that distinction here: a higher forecast is not itself permission to increase the baseline.
On a Review worksheet, use columns A through G for this cost page. Commitments cover future work only. The uncommitted estimate covers remaining work that is neither incurred nor included in those commitments.
| Work package | Baseline (USD) | Incurred cost (USD) | Open commitments (USD) | Uncommitted remaining cost (USD) | Forecast total (USD) | Forecast minus baseline (USD) |
|---|---|---|---|---|---|---|
| Design | 60,000 | 58,000 | 0 | 0 | 58,000 | -2,000 |
| Equipment | 200,000 | 90,000 | 80,000 | 20,000 | 190,000 | -10,000 |
| Installation | 130,000 | 65,000 | 30,000 | 45,000 | 140,000 | 10,000 |
| Testing | 40,000 | 5,000 | 10,000 | 35,000 | 50,000 | 10,000 |
| Total | 430,000 | 218,000 | 120,000 | 100,000 | 438,000 | 8,000 |
Use these formulas in B2, F2 and G2, respectively, and fill down:
=SUMIF(Budget!$A$2:$A$5,A2,Budget!$D$2:$D$5)
=SUM(C2:E2)
=F2-B2
Positive cost variance means a forecast overrun in this report. Design and equipment provide favorable offsets, but installation and testing still need attention. A project total can hide those opposing movements.
Use the approved schedule export and a current delivery forecast. Keep actual acceptance dates separate from future forecasts; a task marked started is not an accepted deliverable.
| Milestone | Baseline date | Current forecast date | Delay, calendar days |
|---|---|---|---|
| Equipment delivered | October 15, 2026 | October 22, 2026 | 7 |
| Installation complete | November 15, 2026 | November 22, 2026 | 7 |
| Final acceptance | December 1, 2026 | December 8, 2026 | 7 |
With actual spreadsheet dates in columns B and C, calculate the delay in D2:
=C2-B2
Format the result as a number. These are calendar-day differences; they do not establish working-day impact or prove which dependency drives the finish date. Ask the delivery owner to explain the connection between delayed equipment, installation and final acceptance.
The incurred cost is $218,000 / $430,000 = 50.7% of the approved baseline, rounded to one decimal place. That is a spending comparison. It does not say half the work has been accepted.
Three checks make the headline reproducible:
Finance should tie incurred costs to its project ledger and explain unposted accruals. Procurement should validate the remaining commitment balances. Keep incurred cost distinct from payments; accrual versus cash accounting explains why those amounts can differ.
The executive summary can now state that the project forecasts an $8,000 overrun and final acceptance seven calendar days after baseline. The exception page should identify who will validate installation labor, who will confirm the testing estimate, and which delivery decision the sponsor must make. Add a due date and evidence required for closing each action.
Place the material project movement in the company's management reporting package, with the detailed work-package tables available behind it.
Bring your budget, cost, commitment and milestone files, with the current remaining-cost estimates. Covirage maps the columns, its tools compute and check the comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own project export.
See project cost control for the supporting business context.
Include the reporting date, approved baseline version, cost and milestone comparisons, forecast assumptions and unresolved exceptions. Add the evidence behind completed work and the decisions required from the sponsor. Readers should be able to trace the summary back to the underlying work packages.
Only the portion covering future work belongs in remaining commitments. Work already received should be included in incurred cost under the finance team's cutoff policy. Remove that portion from the commitment balance before adding it to the forecast, or the same work appears twice.
Use a cadence that matches reliable cost and progress information. A monthly review can suit a longer project, while critical delivery periods may need more frequent updates. Each issue should state its cutoff, input versions and any estimates that have not yet been confirmed.