Cost Performance Index Calculator
Calculate the Cost Performance Index (CPI) — the ratio of Earned Value to Actual Cost — to measure cost efficiency. Use it as a core EVM metric to determine whether the project is delivering value efficiently or overrunning the budget.
Last updated: May 2026
Compare with similar
About this calculator
Cost Performance Index (CPI) is the cost-side companion to SPI in earned-value management (EVM). The formula is: CPI = Earned Value / Actual Cost. Variables: Earned Value (EV) is the budgeted cost of work completed to date; Actual Cost (AC) is real money spent to date. Edge cases: CPI > 1.0 means the project is under budget (you're producing more value than you're spending); CPI = 1.0 means exactly on budget; CPI < 1.0 means over budget. CPI of 0.80 means you're getting only 80 cents of value per dollar spent (significant cost overrun); CPI of 1.10 means 110% value per dollar (efficient performance). Interpretation thresholds: CPI 0.95–1.05 is normal noise; 0.90–0.95 deserves attention; 0.80–0.90 requires management action; below 0.80 is serious. Research (Christensen 1994, DoD studies) shows CPI is remarkably stable: once a project is 15–20% complete, the final CPI typically stays within ~10% of the early CPI. This means EAC projections from early in the project are surprisingly reliable, contrary to optimism that 'we'll recover.' The CPI-based EAC formula: EAC = BAC / CPI projects final project cost if current performance continues. For a project with BAC $1,000,000 and current CPI of 0.85: EAC = 1,000,000 / 0.85 = $1,176,000 — projected 17.6% overrun. Mature project organizations act on negative CPI trends early because waiting for recovery rarely works.
How to use
Example 1 — Project running over budget. Earned Value $200,000 (work completed valued at budget rates), Actual Cost $240,000 (real spending). Step 1: CPI = 200,000 / 240,000 ≈ 0.83. Verify ✓. CPI of 0.83 means about $1.20 spent per $1.00 of work value — a 20% overrun. EAC = BAC / CPI projects: if BAC is $1,500,000, EAC = 1,500,000 / 0.83 ≈ $1,807,000 — projected $307,000 overrun. Management action: investigate root cause, evaluate scope/recovery options. Example 2 — Efficient performance. EV $625,000, AC $570,000. Step 1: CPI = 625,000 / 570,000 ≈ 1.10. Verify ✓. CPI 1.10 means $1 of work value per $0.91 spent — 10% under budget. Solid performance. If sustained, EAC projects favorable cost: with BAC $1,500,000, EAC = 1,500,000 / 1.10 ≈ $1,364,000 — about $136,000 savings vs original budget. Verify the savings are real (not from scope reduction or low-cost shortcuts that defer cost to later).
Frequently asked questions
How reliable is CPI as a forecast?
Research consistently shows CPI is one of the most reliable early-warning project metrics. DoD studies (Christensen 1994 and later) and academic research demonstrate that once a project is 15–20% complete (early in execution), the final CPI typically stays within ~10% of the CPI at 20% complete. This means: a project with CPI 0.85 at 20% complete is highly likely to finish with CPI between 0.75 and 0.95 — translating to 5–25% overrun. The 'we'll catch up' optimism that follows early cost overruns is contradicted by data; CPI rarely recovers significantly. Implications: (1) Act early on negative CPI trends — recovery from 20% overrun mid-project is much easier than from 40% near end; (2) Use CPI-based EAC for honest stakeholder communication, even when uncomfortable; (3) When CPI drops below 0.95, expect scope reduction, schedule extension, or budget increase to be needed. The stability of CPI is also why aggressive early action (descoping, accelerating, escalating) typically produces better outcomes than incremental adjustments.
What's the difference between CPI and budget variance?
Both measure cost performance but in different forms. Budget Variance (BV%) = ((Actual Spent − Planned Budget) / Planned Budget) × 100 — a percentage difference between actual and planned spending. CPI = Earned Value / Actual Cost — a dimensionless ratio of value to cost. The key difference: budget variance compares against the PLAN (what should be spent by now), while CPI compares against ACTUAL WORK COMPLETED (what value was earned). A project at 50% completion with 75% of budget spent has positive budget variance (over plan) but the CPI depends on whether the 75% spending produced 50% value (CPI = 0.67, real overrun) or 60% value (CPI = 0.80) or 50% (CPI = 0.67). CPI separates cost performance from schedule effects in a way that simple variance cannot. For status reporting, CPI is more diagnostic; for budgetary control, both are useful together. Mature EVM practitioners use CPI + SPI + variance metrics together rather than choosing one.
What are the most common mistakes with CPI?
The biggest is computing CPI without rigorous Earned Value measurement — subjective '50% done' reports inflate EV and produce false CPI. Use objective measurement (0/100, weighted milestones, equivalent units). The second is treating CPI as a discipline metric for individuals when systemic factors (scope changes, vendor delays, resource constraints) often dominate. The third is comparing CPI across very different project types (R&D vs construction vs IT) without recognizing that variance norms differ. The fourth is ignoring CPI trends in favor of single snapshots; declining CPI is more concerning than stable below-1.0 CPI. The fifth is using CPI to evaluate completed projects without context; a project completing at CPI 0.85 may have been excellent if the original budget was unrealistic, or poor if requirements were stable and well-understood. The sixth is failing to act on CPI warnings; tracking metrics without intervention is theater. The seventh is using CPI alone without SPI; cost performance only tells half the story.
When should I NOT use CPI?
Skip CPI for projects without rigorous EV measurement infrastructure — without objective work measurement, CPI is meaningless. Avoid CPI for time-and-materials contracts where there's no fixed scope to measure against; cost is purely a function of hours billed. Do not use CPI for agile projects where scope evolves continuously and there's no fixed BAC; agile uses velocity, burnup/burndown, and value-based prioritization. Skip CPI for highly exploratory work (research, innovation) where the original budget reflects guess more than commitment. Do not use CPI as the sole performance metric for project managers; many factors (resource constraints, scope changes, vendor issues, customer behavior) are outside PM control. And do not compare CPI across organizations or contracts without normalization — different cost accounting, different overhead allocations, different scope-of-work definitions can produce wildly different CPI for similar real-world performance.
How do CPI, SPI, and EAC work together for project forecasting?
CPI tells you cost efficiency now; SPI tells you schedule efficiency now; EAC projects final cost. Standard EAC formulas: (1) EAC = AC + (BAC − EV) assumes future work performance returns to budget rate (optimistic); (2) EAC = BAC / CPI assumes future performance equals current CPI (most realistic for stable projects); (3) EAC = AC + (BAC − EV) / (CPI × SPI) assumes both cost AND schedule problems compound for remaining work (conservative). Smart project managers track all three and use the appropriate one based on project context: stable project with one-time cost variance → formula 1; ongoing systemic cost issues → formula 2; both schedule and cost problems → formula 3. The forecast helps stakeholders make informed decisions: scope cuts, additional funding, schedule extension, or project termination. Without honest EAC, projects continue toward predictable failure while everyone hopes for recovery that statistical evidence shows rarely happens. The discipline of CPI + SPI + EAC measurement plus action is what distinguishes mature project organizations from chronic-overrun ones.