CPI vs. SPI: Understanding the Difference Between Cost and Schedule Performance
Cost and schedule performance are connected, but they are not interchangeable. A project can spend money efficiently while falling behind, or deliver work quickly while consuming its budget too fast. The Cost Performance Index (CPI) and Schedule Performance Index (SPI) help project managers distinguish these conditions by comparing the value of completed work with either its actual cost or its planned value.
Both measures come from Earned Value Management (EVM), which combines scope, schedule, and cost data into a consistent performance picture. Their value is not the arithmetic alone. It is the management decision that follows: whether to investigate productivity, change sequencing, control spending, revise a forecast, or escalate a delivery risk.
What CPI and SPI Measure
CPI measures cost efficiency. It compares the budgeted value of work completed with the actual cost incurred to complete it. SPI measures schedule efficiency by comparing the budgeted value of completed work with the budgeted value of work that should have been completed by the status date.
Three inputs underpin both calculations:
Planned Value (PV): the budgeted value of work scheduled to be completed by a specified date.
Earned Value (EV): the budgeted value of work actually completed by that date.
Actual Cost (AC): the cost incurred for the work performed by that date.
The distinction between earned value and actual cost matters. EV is not revenue, cash received, or the market value of a deliverable. It is the portion of the approved project budget assigned to work that has genuinely been completed, measured using the project's agreed progress rules. If progress is overstated or costs are recorded inconsistently, the indices can look precise while telling a misleading story.
The CPI formula
CPI = EV ÷ AC
A CPI of 1.00 means the value earned equals the cost incurred. A result above 1.00 indicates that the project has earned more budgeted value per unit of cost than planned. A result below 1.00 indicates that the work completed has cost more than its budgeted value.
For example, if EV is $240,000 and AC is $300,000, CPI is 0.80. The project has earned 80 cents of budgeted value for every dollar spent. That is a cost-efficiency warning, not automatically proof that the total project will finish 20% over budget. The final outcome depends on remaining work, the cause of the variance, and whether current performance continues.
The SPI formula
SPI = EV ÷ PV
An SPI of 1.00 means completed work matches the budgeted value of work planned by the status date. A result above 1.00 indicates more budgeted work value has been completed than planned; a result below 1.00 indicates less.
If EV is $240,000 and PV is $300,000, SPI is 0.80. The team has completed 80% of the work value planned for that date. It does not mean the project is necessarily 20% late in calendar time. EVM's traditional SPI is value-based, not a direct calculation of days early or late.
CPI vs. SPI: The Key Differences
CPI and SPI use the same earned-value figure but compare it with different baselines. CPI asks whether the completed work was achieved efficiently in cost terms. SPI asks whether the amount of work completed is keeping pace with the plan. Reading them together helps explain whether the main pressure is cost, progress, or both.
Comparison | Cost Performance Index (CPI) | Schedule Performance Index (SPI) |
Core question | How efficiently are we spending to produce completed work? | How much planned work value have we completed by this date? |
Formula | EV ÷ AC | EV ÷ PV |
Denominator | Actual Cost (AC) | Planned Value (PV) |
At 1.00 | Earned value equals actual cost | Earned value equals planned value |
Above 1.00 | Favorable cost efficiency | Progress ahead of the value-based plan |
Below 1.00 | Unfavorable cost efficiency | Progress behind the value-based plan |
Typical management response | Investigate rates, waste, rework, estimates, and cost controls | Investigate dependencies, sequencing, capacity, blockers, and progress assumptions |
Important limitation | Does not measure delivery speed or quality | Does not directly quantify calendar delay or critical-path impact |
Three observations are worth carrying into project reviews. First, the indices diagnose different dimensions, so a favorable CPI cannot compensate for an SPI below 1.00 when a contractual milestone is at risk. Second, neither metric explains the cause of poor performance; they identify a signal that needs investigation. Third, SPI can move toward 1.00 as a project approaches completion because the value of remaining uncompleted work diminishes. It should therefore not be treated as a standalone forecast of the final delivery date.
How to Interpret CPI and SPI Together
The combined pattern is more useful than either number in isolation. A project manager should interpret the indices alongside trend data, milestone forecasts, risk exposure, quality measures, and the critical path.
Consider a hypothetical software implementation with EV of $240,000, AC of $300,000, and PV of $280,000 at the same status date. CPI is 0.80 ($240,000 ÷ $300,000), while SPI is approximately 0.86 ($240,000 ÷ $280,000). The project is both cost-inefficient and behind its value-based plan. The next step is not simply to tell the team to work faster or spend less. The manager should determine whether rework, underestimated complexity, delayed decisions, scarce specialist capacity, or other causes are driving the result.
Use the four broad patterns as a diagnostic starting point:
CPI below 1.00 and SPI below 1.00: both cost efficiency and progress are unfavorable. Establish the main drivers, protect critical-path work, and update the cost and completion forecasts.
CPI below 1.00 and SPI above 1.00: work is progressing faster than planned but at an unfavorable cost rate. Check overtime, premium suppliers, additional resources, and whether acceleration is necessary for a valuable milestone.
CPI above 1.00 and SPI below 1.00: cost efficiency is favorable while progress is lagging. Investigate constraints, approvals, dependencies, resource availability, and whether apparent savings reflect deferred work rather than genuine efficiency.
CPI above 1.00 and SPI above 1.00: both indicators are favorable, but verify that scope, acceptance criteria, and quality remain intact. Early favorable performance does not guarantee the same result through the remaining phases.
These patterns do not prescribe automatic corrective actions. For instance, adding people to a delayed task may increase coordination overhead or have little effect if the task is constrained by approvals or a predecessor deliverable. Cost reductions can also make schedule performance worse if they remove a resource needed for a critical activity. The intervention should address the verified cause, not just improve the dashboard color.
Using the Indices for Decisions and Forecasts
CPI and SPI become more valuable when they are measured consistently and connected to decisions. Agree on the status date, cost treatment, work-package progress rules, and source systems before comparing results. A common measurement baseline is essential if project teams or portfolio leaders are expected to compare performance across workstreams.
Establish trustworthy progress data
Define what counts as complete for each work package. For tangible deliverables, use objective acceptance criteria where possible. For longer activities, agree on a defensible progress method rather than relying on unsupported percentage-complete estimates. Reconcile actual costs to the same reporting period and document late invoices, accruals, or cost allocations that could distort the comparison.
Track trends, not just the latest result
A single CPI or SPI reading can reflect timing, a one-off purchase, or a temporary constraint. Review the cumulative indices alongside period-by-period results and the reasons for material movement. A deteriorating CPI across several reporting periods may indicate a persistent productivity or estimating problem. A falling SPI may reveal that planned work is not converting into accepted deliverables at the expected rate.
Set escalation thresholds that fit the project's risk profile rather than treating a universal percentage as suitable for every project. A small variance may be material on a safety-critical or contractually constrained project, while a larger temporary variance may be manageable on a flexible internal initiative. Thresholds should trigger investigation and ownership, not automatic blame.
Forecast with explicit assumptions
CPI is often used in an Estimate at Completion (EAC) calculation. If current cost efficiency is assumed to continue, a simple forecast is:
EAC = Budget at Completion (BAC) ÷ CPI
This is an assumption-based forecast, not a certainty. It may be unsuitable when the current variance is exceptional, the remaining work differs significantly from completed work, or management has credible evidence that future performance will change. The forecast should state why the chosen method is appropriate and be updated when conditions change.
SPI can help identify schedule pressure, but a traditional SPI should not be converted directly into a promised finish date. Schedule recovery decisions require a schedule analysis that considers activity durations, dependencies, float, resource constraints, and the critical path. Where a more time-oriented earned-value measure is required, Earned Schedule techniques may complement traditional EVM, but they still need sound underlying progress data.
Turn indicators into accountable actions
Every material variance should lead to a named owner, a cause to test, an action, a due date, and a measure of whether the intervention worked. For example, if rework is driving low CPI and delayed approvals are driving low SPI, the response should address both quality at source and decision turnaround. A generic request to “improve productivity” is not an adequate corrective-action plan.
Limitations Project Managers Must Recognize
CPI and SPI are useful controls, not complete measures of project health. They do not directly measure customer value, deliverable quality, safety, benefits realization, or stakeholder confidence. A project can report favorable indices while producing an unusable outcome if progress credit is awarded too early or quality checks are weak.
The schedule index also has a structural limitation: it compares budgeted values rather than elapsed time. Work packages with different budget profiles can make the ratio difficult to interpret as a time measure, and a favorable SPI does not prove that the critical path is safe. Use the integrated schedule and milestone forecasts to assess actual delivery consequences.
Comparability can also break down when baselines change without disciplined approval, cost data is incomplete, or progress rules differ between teams. Re-baselining may be justified after an authorized scope change, but it should not be used to erase an unfavorable performance history. Preserve the original baseline and explain the approved change so leaders can distinguish a legitimate plan change from a performance problem.
Over the next two years, organizations are likely to continue embedding earned-value measures into portfolio dashboards and project controls, with more automation for data collection and variance alerts. Automation can improve timeliness, but it cannot resolve poor scope definitions, unreliable progress estimates, or inconsistent cost coding on its own. The outlook depends on governance and data quality as much as on the reporting technology.
FAQs
Is CPI or SPI more important?
Neither is universally more important. CPI is central when cost efficiency and budget exposure are the immediate concern; SPI is central when delivery pace matters. For most controlled projects, review both with critical-path and quality information.
Can SPI tell me exactly how many days a project is late?
No. Traditional SPI compares earned value with planned value, not elapsed days. Use the integrated schedule, milestone forecasts, dependency analysis, and critical-path assessment to estimate calendar impact.
What should I do when CPI and SPI are both below 1.00?
Validate the data, identify the main causes, assess critical-path and budget exposure, and update forecasts. Assign corrective actions to accountable owners, then monitor whether the interventions improve the underlying causes.
Conclusion: CPI vs. SPI: Understanding the Difference Between Cost and Schedule Performance
CPI and SPI provide complementary views of project performance. CPI compares completed work's budgeted value with actual cost; SPI compares that value with the work planned by the status date. Used together, they help project managers identify whether cost efficiency, progress, or both need attention.
Their greatest value comes from disciplined interpretation. Validate the underlying data, examine trends, connect schedule signals to the critical path, and make corrective actions specific and accountable. Neither index replaces professional judgment, but both can make project reviews more evidence-based when the numbers are tied to the realities of delivery.
