Blog · Board and management reporting
Project KPIs compare actual cost, accepted work, and milestone dates with an approved baseline. Follow a worked US business project, reconcile its costs, and see which owner should act on each exception.
Project KPI meaning is straightforward: a key performance indicator shows whether a project is delivering its approved scope, cost, and schedule commitments. Spending alone cannot answer that question, because a team can spend exactly what it planned while completing less work. Compare cost with accepted progress, then check the milestone dates that matter to the business.
A useful KPI connects a result to a decision. For a project, that connection starts with an approved scope, a budget assigned to the work, and a schedule showing when the work should be completed. Keep the original baseline and approved changes identifiable.
The Department of Energy's earned value explanation describes comparing work, cost, and schedule with an approved baseline. Its important business point is that comparing spending with planned spending can mislead when physical progress is missing.
Choose a reporting cutoff before combining files. Costs posted after the cutoff and progress accepted before it require deliberate treatment. Finance should identify unposted costs for completed work; the delivery lead should distinguish work started from work accepted. A project report cannot resolve that difference by making every task look complete.
The following example concerns an internal inventory redesign at an illustrative US distributor, Cedar Ridge Supply. It is a general business project, with design, configuration, and training workstreams. Construction-specific measures and ongoing factory measures need their own definitions; manufacturing KPIs address the latter.
Use exports the project team already maintains. Join them by project and work-package identifiers, and preserve the source record identifiers for checking exceptions.
| Export | Record represented by a row | Fields needed |
|---|---|---|
| Approved baseline | Work package | Project ID, package ID, approved budget, scheduled progress at cutoff, baseline version |
| Cost ledger | Cost transaction | Transaction ID, package ID, posting date, cost date, signed amount, accrual status |
| Progress register | Acceptance event or package assessment | Package ID, accepted progress, evidence, acceptance date, approver |
| Milestone schedule | Milestone | Milestone ID, baseline due date, actual completion date, accountable owner |
Do not repeat a package's full budget on every ledger transaction and then sum it. Aggregate transactions to the package first, or calculate the budget from the separate baseline register. Project cost management covers the broader cost control process; this comparison concentrates on interpreting performance at one cutoff.
Cedar Ridge reports through October 16, 2026. All amounts below are USD, and the accepted shares use the completion rules approved for each workstream. Planned value is the budgeted amount of work scheduled by the cutoff, not the full workstream budget.
| Workstream | Full approved budget (USD) | Planned value at cutoff (USD) | Accepted share | Earned value (USD) | Actual cost through cutoff (USD) |
|---|---|---|---|---|---|
| Design | 50,000 | 50,000 | 100.0% | 50,000 | 55,000 |
| Configuration | 100,000 | 60,000 | 50.0% | 50,000 | 60,000 |
| Training | 50,000 | 10,000 | 10.0% | 5,000 | 5,000 |
| Total | 200,000 | 120,000 | Budget-weighted below | 105,000 | 120,000 |
For this example, earned value equals each workstream's full approved budget multiplied by its accepted share. Configuration earns 100,000 × 50.0% = $50,000; training earns 50,000 × 10.0% = $5,000. These are budget values of accepted work, not revenue or cash receipts.
Cost performance index (CPI) = Earned value / Actual cost
Schedule performance index (SPI) = Earned value / Planned value
The National Science Foundation's earned value reference sets out these indices and the corresponding cost and schedule variances. Applied to Cedar Ridge's totals:
| Measure | Calculation from workstream totals | Result |
|---|---|---|
| Cost performance index | 105,000 / 120,000 | 0.875 |
| Schedule performance index | 105,000 / 120,000 | 0.875 |
| Cost variance (USD) | 105,000 - 120,000 | -15,000 |
| Schedule variance in budget terms (USD) | 105,000 - 120,000 | -15,000 |
| Budget-weighted completion | 105,000 / 200,000 | 52.5% |
| Budget spent | 120,000 / 200,000 | 60.0% |
| Planned budget-weighted completion | 120,000 / 200,000 | 60.0% |
Percentages are shown to one decimal place; indices are shown to three. Actual spending equals planned value, but the project has accepted less work than scheduled. The $15,000 unfavorable cost variance measures the difference between work earned and cost incurred. It does not prove that the final project will exceed its budget by that amount.
The schedule index expresses work in budget terms. It does not give the number of days a particular milestone is late. Cedar Ridge therefore checks every milestone due by the cutoff:
| Milestone | Baseline due date | Actual completion | Completed by due date? | Days late, floored at zero |
|---|---|---|---|---|
| Design approval | September 30, 2026 | September 29, 2026 | Yes | 0 |
| Configuration checkpoint | October 9, 2026 | October 12, 2026 | No | 3 |
| Training preparation | October 15, 2026 | October 15, 2026 | Yes | 0 |
On-time milestone attainment is 2 / 3 = 66.7%, rounded to one decimal place. The configuration checkpoint is late even though it is complete at the reporting cutoff. Record that history; replacing the baseline date with the actual date would erase the miss.
The milestone count also needs context. An approval that blocks launch deserves separate attention even if other milestones finish early. Review dependencies with the schedule owner before translating a late checkpoint into a revised launch date.
The workstream costs reconcile as 55,000 + 60,000 + 5,000 = $120,000. That amount must match the scoped ledger export, including agreed accruals. The approved budgets sum to $200,000, and earned value sums to $105,000. Finally, earned value minus cost variance returns actual cost: 105,000 - (-15,000) = $120,000.
Finance owns that reconciliation. Workstream leads own the acceptance evidence. The project manager owns the schedule comparison, and the sponsor owns decisions about scope, additional funding, and baseline changes. Configuration warrants a joint review because its accepted work trails scheduled work and its cost exceeds earned value.
Use KPI reporting to carry the exception into a recurring management review. Keep the evidence, accountable owner, next action, and decision date beside the result.
Bring a sample of your own baseline, project cost export, progress register, and milestone file; Covirage maps the columns, and its tools compute and check the comparisons. The external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your files.
See project cost control for the supporting business context.
A task status describes an individual activity, such as pending approval or complete. A project KPI summarizes performance against an objective or baseline. Task records supply evidence, but counting completed tasks does not establish whether valuable work was delivered on time or within budget.
Yes. Spending below the planned amount can mean work has been delayed. Compare actual cost with the budgeted value of accepted work, then compare that work with the amount scheduled. Review milestone dates separately to understand the delivery consequences.
The project manager coordinates the definitions, finance validates cost treatment, and workstream leads confirm completion evidence. The sponsor approves the baseline and material changes. Name one accountable owner for each measure so exceptions lead to decisions rather than disputes about the calculation.