Comparing SPI Vs CPI: A Practical Guide To Measuring Project Performance

SPI vs CPI is a practical comparison every project manager needs when schedule and budget start drifting in different directions. A project can look healthy on the calendar and still burn cash too fast, or stay under budget while quietly slipping milestones. In project analysis, earned value management gives you a clearer read on project performance than watching budget or timeline alone.

SPI formula	Earned Value ÷ Planned Value
CPI formula	Earned Value ÷ Actual Cost
What SPI measures	Schedule efficiency
What CPI measures	Cost efficiency
Healthy benchmark	1.0 or above, depending on context and as of June 2026 thresholds
Best use	Tracking earned value management trends in baseline-driven projects
Main caution	SPI and CPI are not interchangeable and can diverge sharply

Understanding SPI And CPI

Schedule Performance Index (SPI) is the ratio of earned value to planned value, and it shows how efficiently work is progressing against the schedule baseline. Cost Performance Index (CPI) is the ratio of earned value to actual cost, and it shows how efficiently work is being completed against the budget. In plain terms, SPI answers “Are we getting the planned amount of work done on time?” while CPI answers “Are we getting the work done without overspending?”

These are both performance ratios, which makes them easy to read once you know the scale. A value above 1.0 usually means favorable performance, 1.0 means performance is exactly on plan, and below 1.0 means unfavorable performance. That sounds simple, but the meaning changes depending on whether you are looking at time or money.

For example, if a software team finishes more story points than planned by a sprint review date, SPI may be above 1.0 even if the team used expensive contractors to make it happen. That same project could have a CPI below 1.0 because the earned work cost more than expected. This is why SPI vs CPI matters in project analysis: the two metrics measure different dimensions of project performance, and neither one replaces the other.

One metric can flatter the project while the other tells the truth. That is why experienced project managers do not look at schedule or budget in isolation when using earned value management.

The PMI standard used in the PMP® 8 – Project Management Professional (PMBOK® 8) course context reinforces this idea through disciplined baseline tracking and variance analysis. The course is useful here because scope change control and performance interpretation are exactly where many projects go sideways.

For a broader management standard, Project Management Institute materials remain the primary reference for earned value concepts, and the NIST approach to measurement discipline is a good reminder that metrics are only as useful as the data behind them.

How The Formulas Work

SPI and CPI rely on three core inputs: earned value (EV), planned value (PV), and actual cost (AC). Earned value is the budgeted value of the work actually completed, planned value is the budgeted value of the work scheduled to be completed by a certain date, and actual cost is what you really spent to complete that work. These values usually come from project tracking systems, time sheets, work package updates, procurement records, and approved progress reports.

The formulas are straightforward:

• SPI = EV ÷ PV
• CPI = EV ÷ AC

Here is a simple SPI example. Suppose a project planned $50,000 worth of work by the end of month two, but the team only completed $40,000 worth of the baseline scope. SPI equals 40,000 ÷ 50,000 = 0.80. That means the project is completing work at 80% of the planned schedule rate, which is a clear schedule warning.

Now the CPI example. Suppose the team completed that same $40,000 of earned work but spent $50,000 to do it. CPI equals 40,000 ÷ 50,000 = 0.80. That means the project is getting only 80 cents of value for every dollar spent. In other words, the work is costing too much.

Reliable calculations depend on consistent data collection. If EV is updated late, if progress is guessed instead of measured, or if AC excludes some labor and overhead, both indices become misleading. That is why project controls teams often treat data quality as part of resource allocation and reporting discipline rather than a clerical task.

For software and infrastructure projects, CIS Benchmarks and other standards show how repeatable measurement supports control. The same principle applies to project performance: if the baseline and inputs are sloppy, the indices will be too.

Why SPI And CPI Often Diverge

SPI and CPI often diverge because schedule efficiency and cost efficiency are affected by different forces. A project can be ahead of schedule but over budget if extra labor, overtime, or premium procurement speeds up delivery. It can also be under budget but behind schedule if the team reduces spend by delaying work, limiting staffing, or waiting on external approvals.

That divergence is not a contradiction. It is a diagnostic signal. A high SPI with a low CPI often points to schedule recovery tactics that cost more than planned. A low SPI with a high CPI often points to conservative spending, understaffing, or procurement delays that protect the budget while hurting timeline.

Several real-world conditions drive this split:

• Overtime can improve SPI temporarily while lowering CPI.
• Rework inflates cost without necessarily moving milestones.
• Procurement delays can stall schedule even when spending stays low.
• Scope changes can distort both metrics if the baseline is not updated correctly.
• Resource allocation choices can favor speed or cost, but rarely both at once.

Consider a cloud migration where the team adds contractors to meet a cutover date. The schedule improves because tasks are being finished faster, but the actual cost jumps because contractor rates are higher than internal labor rates. That project may post a better SPI while CPI slides below 1.0.

On the other side, imagine a compliance remediation project that delays noncritical work to avoid overtime and keep purchase orders tight. The CPI can look healthy because spending is controlled, but SPI falls because deliverables are not arriving when expected. In project analysis, that pattern usually means the project is optimizing the wrong constraint.

For governance and measurement discipline, the PMI framework and ANSI-style standardization thinking both support the same practical point: a metric is only useful if you know what behavior is driving it.

How To Interpret SPI

SPI greater than 1.0 means the project is completing work faster than planned. SPI equal to 1.0 means the project is exactly on schedule relative to the baseline. SPI less than 1.0 means the project is behind schedule. That is the headline interpretation, but the real value comes from understanding how far the number is from 1.0.

A small deviation, such as 0.97 or 1.03, may be acceptable if the work is within normal control limits and the milestone is not critical. A larger gap, such as 0.75 or 1.25, needs attention because it usually reflects a structural issue, not a random fluctuation. SPI is most useful when the project has clear milestones, stable baselines, and measurable deliverables.

SPI can mislead late in a project if progress was front-loaded. A testing phase may show strong SPI early because documentation and planning tasks were easy to complete, then collapse when hard integration work begins. It can also mislead when teams estimate percent complete subjectively. If one lead says a task is “90% done” for two weeks straight, the metric will look cleaner than reality.

Actions that can improve SPI

1. Resequence work so dependent tasks do not idle behind avoidable blockers.
2. Add resources carefully if the constraint is truly labor capacity, not decision latency.
3. Fast-track parallel tasks when risk is manageable and the baseline supports it.
4. Remove procurement bottlenecks by approving long-lead items earlier.
5. Revalidate scope so teams are not chasing work that no longer matters.

Schedule Performance Index is a strong signal, but it is not a schedule plan by itself. The Project Management Institute has long emphasized that earned value works best when paired with disciplined baseline control and variance review. That is the heart of practical project analysis.

For formal schedule planning concepts, the ISO 21502 project management guidance is useful background, especially when teams need to connect schedule metrics to governance and delivery discipline.

How To Interpret CPI

CPI greater than 1.0 means the project is earning more value per dollar than planned. CPI equal to 1.0 means the project is on budget for the earned work. CPI less than 1.0 means the project is spending too much to produce the current amount of earned value. In budget terms, CPI below 1.0 says the project is paying more than planned for each unit of completed work.

CPI is especially useful because it often behaves like a strong early predictor of final cost outcomes when trends remain stable. If CPI stays at 0.85 for several reporting periods, the project is consistently overspending relative to earned value. That is usually more informative than watching only the total budget consumed.

Several cost drivers can pull CPI down:

• Labor rates that exceed the original estimate
• Material price increases after procurement planning
• Change orders that are not fully absorbed into the baseline
• Rework caused by quality defects or unclear requirements
• Waste and idle time from poor coordination

Cost-control actions should address the cause, not just the number. Reducing waste helps, but so does improving estimating accuracy for future phases, tightening approval workflows, and preventing uncontrolled scope expansion. If the root cause is repeated rework, then the fix is probably requirements clarity or quality control, not more budget review meetings.

Cost Performance Index is also the metric most teams use when asking whether the project is financially efficient. That makes it a core tool in earned value management, especially on projects where labor, materials, and vendor commitments can be measured cleanly.

For broader financial and governance context, the AICPA and COBIT frameworks reinforce a basic management idea: you cannot control cost if you cannot measure it consistently.

Using SPI And CPI Together

Using SPI and CPI together gives a much more complete view of project performance than reading either one alone. SPI tells you whether the project is moving at the expected pace, and CPI tells you whether that progress is being bought efficiently. When the two move together, the story is simpler. When they diverge, the project manager gets a useful warning that the plan and reality are not aligned.

Common patterns matter more than any one data point:

• High SPI and low CPI usually means the project is buying schedule at a premium.
• Low SPI and high CPI usually means the project is saving money while missing milestones.
• Both below 1.0 usually means the project is slipping and overspending, which is the worst operating pattern.
• Both above 1.0 can be a good sign, but it may also mean the baseline was too conservative or progress was overstated.

Dashboards and trend charts help here. A single monthly snapshot can hide the pattern, but a line chart showing SPI and CPI over time makes drift obvious. Many PMO teams also pair the indices with schedule variance, cost variance, and milestone status so executives do not have to translate earned value jargon into business terms.

Trend lines matter more than single readings. A project with a temporary dip may be fine, while a project with a steady decline is already in trouble.

If a project must recover schedule, the manager should expect CPI to suffer unless the team finds another offset such as scope reduction, automation, or lower-cost resourcing. If a project must reduce spend, SPI may slow unless the team can remove waste without reducing throughput. That tradeoff is exactly why SPI vs CPI belongs in project analysis and not in a budget spreadsheet alone.

For measurement vocabulary and reporting structure, the FTC and CISA both reflect a broader management truth in different contexts: clear reporting beats ambiguous dashboards when decisions are on the line.

What Are The Common Mistakes When Comparing SPI And CPI?

The biggest mistake is assuming one favorable metric means the project is healthy overall. A project with strong SPI can still be burning through cash, and a project with strong CPI can still be slipping past critical dates. The second mistake is comparing SPI and CPI without understanding the project phase, the baseline quality, or the accuracy of the source data.

Another common problem is subjective percent-complete reporting. If teams estimate progress loosely, both EV and the resulting indices become unreliable. A task reported as 80% complete for three weeks in a row often means the project has a measurement problem, not a delivery problem. That is why many project controls teams insist on objective milestones, quality gates, or measurable deliverables.

Teams also fixate on the lower metric without asking why it dropped. A weak CPI may be caused by rework, but the real root cause could be unclear requirements, supplier delays, or a bad change request process. A weak SPI may be caused by schedule pressure, but the actual constraint could be procurement lead time or limited tester availability. Treating the metric as the problem usually wastes time.

Finally, short-term swings are often overreacted to. A one-period fluctuation can happen because of invoice timing, partial deliveries, or reporting lag. What matters is whether the trend persists across multiple review cycles.

The Center for Internet Security and NIST Cybersecurity Framework both emphasize repeatability and control, and the same logic applies to project metrics: consistent inputs produce credible outputs.

What Is The Best Way To Report And Act On SPI And CPI?

The best reporting approach is to set clear thresholds before the project slips. Many PMOs use warning bands so the team knows when SPI or CPI drift enough to trigger corrective action. A weekly or biweekly review cadence is usually better than monthly reporting because it catches small problems before they become expensive or irreversible.

Metric changes should always connect to a specific action, owner, and due date. Saying “CPI is low” is not enough. A useful report says, “CPI dropped to 0.86 after vendor rework, and procurement will revise the estimate at completion by Friday.” That level of specificity turns reporting into management.

Stakeholders who are not familiar with earned value terminology need plain language. Instead of saying “SPI is 0.82,” say “We are completing work slower than planned.” Instead of saying “CPI is 0.91,” say “We are spending slightly more than planned for the work finished so far.” Clear language makes the data easier to act on.

Good reporting habits

1. Track trends instead of only reporting current values.
2. Use the same baseline unless a re-baseline is formally approved.
3. Document assumptions behind progress, cost, and change requests.
4. Escalate exceptions when thresholds are breached.
5. Update forecasts so the estimate at completion reflects reality.

Re-baselining should be rare and justified. It is appropriate after approved scope changes, but not as a way to hide poor performance. That discipline is a core part of project analysis and a recurring theme in the PMP® 8 – Project Management Professional (PMBOK® 8) course, especially when scope change control and stakeholder communication are involved.

For practical governance and workforce alignment, U.S. Department of Labor guidance on labor trends and Bureau of Labor Statistics Occupational Outlook Handbook data help explain why labor availability and cost pressure affect both schedule and budget performance. That matters when you are forecasting whether current SPI and CPI trends can actually be sustained.

Decision Criteria For Choosing How To Read SPI Vs CPI

Choosing how to act on SPI vs CPI comes down to the problem you are trying to solve. If the business cares most about a date-driven milestone, schedule efficiency gets priority. If the business cares most about budget control, cost efficiency gets priority. If both matter, which is most common, you need to balance them rather than chase the lower number blindly.

Five factors usually decide the response:

• Use case — delivery date, budget cap, regulatory deadline, or operational readiness.
• Project phase — early planning, execution, testing, or closeout.
• Data quality — objective progress measurement versus subjective estimates.
• Team experience — whether the team can recover schedule without waste.
• Baseline stability — whether the scope and plan are still valid.

If the project is in a high-risk execution phase, a falling SPI may justify resequencing work or adding temporary support. If CPI is falling while SPI is stable, the issue is more likely rework, labor inefficiency, or procurement cost pressure. If both are falling, the project needs immediate management attention, not a longer status meeting.

The right decision also depends on whether the project is part of a regulated environment. Frameworks such as ISO 27001 and HIPAA often impose delivery and control expectations that make schedule slips or cost spikes more consequential than they would be on a simpler internal project.

When to pick schedule-first action

Pick schedule-first action when missing a date creates business, compliance, or operational risk. That often means fast-tracking, resequencing, or adding capacity. The tradeoff is usually higher spend, so CPI may worsen in the short term.

When to pick cost-first action

Pick cost-first action when the budget cap is fixed or when the project can tolerate a longer delivery window. That often means tighter scope control, more efficient staffing, and stronger vendor management. The tradeoff is usually slower progress, so SPI may soften before it improves.

Pick SPI-first action when the schedule is the business constraint; pick CPI-first action when the budget is the business constraint. That sentence is the cleanest way to explain the decision to executives who do not want an earned value lecture.

For labor and compensation context, Robert Half Salary Guide and PayScale both show how specialized project and technical labor can drive cost pressure. Even without quoting a single role-specific salary here, the trend is obvious: when the team gets expensive, CPI becomes harder to protect unless productivity rises too.

Conclusion

SPI vs CPI is not an either-or comparison. SPI measures schedule efficiency, and CPI measures cost efficiency. That difference matters because one project can be moving quickly and still overspending, while another can be controlling costs and still missing milestones.

The most useful comparison comes from looking at both metrics together, then checking the trend, the phase of the project, and the quality of the underlying data. That approach gives project managers an early warning system for project performance instead of a delayed explanation after the damage is done.

Use these metrics as decision tools, not just status report numbers. Track them consistently, investigate anomalies fast, and act before a temporary variance becomes a structural problem. That is how earned value management helps project analysis produce better outcomes.

Pick SPI when schedule recovery is the priority; pick CPI when cost control is the priority. Better yet, use both to decide whether the project needs more capacity, tighter control, a scope reset, or a formal re-baseline.

PMI®, PMP®, and PMBOK® are registered marks of Project Management Institute, Inc.