CPI And SPI: How To Use Them Together Effectively

Cost Performance Index (CPI) and Schedule Performance Index (SPI) are the two earned value analysis metrics that tell you whether a project is burning money too fast, moving too slowly, or both. If you manage project management metrics for a PMO, a client, or a steering committee, the real value is not reading CPI or SPI alone. It is learning how to combine them so you get an early warning signal before a project slips into a recovery mode.

Metric type	Earned value management ratios
Primary formula	CPI = EV / AC; SPI = EV / PV
Meaning of 1.0	Performance is exactly on plan as of June 2026
Meaning above 1.0	Favorable performance as of June 2026
Meaning below 1.0	Unfavorable performance as of June 2026
Best use	Combined trend analysis for corrective action as of June 2026
Related discipline	Project Management Institute standards and earned value management

Understanding CPI And SPI

CPI is the ratio of earned value to actual cost, and it answers a simple question: how much value did the project earn for each dollar spent? SPI is the ratio of earned value to planned value, and it answers a different question: how much work did the project accomplish compared with the plan?

In plain language, CPI tells you whether you are spending efficiently, while SPI tells you whether you are progressing efficiently. Both are ratio-based metrics, which is why they work so well in status meetings where people need a quick read instead of a long narrative.

What the formulas mean

The formulas are straightforward:

• CPI = EV / AC, where EV is earned value and AC is actual cost.
• SPI = EV / PV, where PV is planned value.

If CPI is 1.0, the project is getting exactly one dollar of earned value for every dollar spent. If CPI is 1.2, the project is generating more value than it is spending. If CPI is 0.8, the project is spending more than the value delivered.

SPI follows the same logic. An SPI of 1.0 means the project has completed work exactly as planned by the status date. An SPI below 1.0 means the project has earned less value than scheduled. An SPI above 1.0 means the project has earned more value than planned.

Ratios are useful because they normalize performance. A small project and a large project can both be compared using CPI and SPI without needing separate scoring rules for every budget size.

Common misunderstandings

The biggest mistake is treating SPI as a direct measurement of calendar delay. It is not. SPI is a schedule efficiency ratio, not a guarantee that the project is exactly one week late, two weeks late, or ten days late.

That distinction matters because two projects can have the same SPI and very different delivery outcomes. One may be late on a non-critical activity, while another may be one task away from missing a hard milestone. For schedule implications, you still need milestone review, critical path analysis, and forecast dates.

For formal earned value management guidance, the U.S. Department of Defense and the Defense Acquisition University maintain public resources on performance measurement and program control, while PMI’s standards library provides the broader project management context used in many organizations.

Why CPI And SPI Should Be Interpreted Together

Cost and schedule problems usually travel together. A team that is rushing to recover lost time may burn extra labor hours, increase overtime, or pay for expedited shipping. A team trying to protect budget may slow work, defer testing, or stretch dependencies, which can damage schedule performance.

That is why CPI alone can hide schedule slippage and SPI alone can hide overspending. A project can look financially healthy while quietly drifting past key milestones. Another project can move quickly and still be consuming too much money to sustain that pace.

What combined review tells you

Reading CPI and SPI together gives you a rough but valuable diagnosis. If both are healthy, the project is probably under control. If one is healthy and the other is not, you already know which side needs attention first.

This is where project management gets practical. If CPI is weak and SPI is strong, you may have a staffing or productivity problem, but the deadline is still being met. If CPI is strong and SPI is weak, the team may be conserving spend at the expense of time. Those are not the same problem, and they should not get the same corrective action.

PMOs use this combined view because it works as an early warning system. A dashboard with CPI, SPI, forecast at completion, and variance explanations tells stakeholders more than a status report that just says “green” or “yellow.”

CPI focus	Efficiency of spending
SPI focus	Efficiency of progress against plan
Together	Whether the project is delivering value at the right pace and price

For broader performance reporting practices, the Project Management Institute and the National Institute of Standards and Technology both emphasize disciplined measurement, baseline control, and repeatable reporting logic in their public guidance on management systems and measurement discipline.

What Do Common CPI And SPI Combinations Mean?

The most useful way to interpret earned value analysis is to look at the four basic combinations. Each one points to a different management response, and each one carries a different risk profile. The ratios are not magic, but they are fast indicators of where the project is drifting.

Both CPI and SPI are above 1.0

This is the best-looking scenario. The project is earning more value than it spends and achieving more work than planned by the status date. In practical terms, the team is efficient and productive.

Do not assume the project needs no oversight, though. A project can look great early and still fail later if quality, scope, or dependency risks are being ignored. High CPI and SPI should still be paired with forecast checks and milestone review.

CPI is above 1.0 but SPI is below 1.0

This means the project is under budget but behind schedule. It often happens when a team is working carefully, using fewer resources than expected, but not completing planned work fast enough.

That can be acceptable in some settings, especially if speed is less important than cost control. In other cases, it signals under-resourcing, waiting on approvals, or work packages that are blocked by dependencies. The management response may involve reallocating people, resequencing tasks, or removing bottlenecks.

CPI is below 1.0 but SPI is above 1.0

This is the opposite pattern: the team is moving faster than planned, but spending too much to do it. That can happen with overtime, contractor spikes, rushed procurement, or rework caused by poor quality upstream.

On paper, progress looks good. In reality, the project may be buying speed at an unsustainable cost. This is often where leadership has to decide whether the schedule gain justifies the budget damage.

Both CPI and SPI are below 1.0

This is the distress signal. The project is both over budget and behind schedule, which means the team is likely dealing with poor estimates, scope volatility, execution problems, or all three at once.

When both metrics fall below 1.0, the next step is not panic. It is diagnosis. You need to isolate whether the cause is poor planning, a bad dependency chain, a resource shortage, or repeated change requests that were never integrated into the baseline.

For benchmark language around program control and ratio performance, practitioners often align reporting with structured portfolio and governance practices described by ISACA and measurement-oriented guidance from CISA for operational oversight and risk communication.

How Do You Read CPI And SPI In Context?

You read them against the project baseline, not against a random target someone invented in a meeting. Baselines matter because earned value is all about planned work versus accomplished work, and that only works if the plan itself is approved and controlled.

Context also changes by phase. Early-stage projects often show unstable ratios because requirements, estimates, and resource loading are still settling. A slightly weak CPI or SPI in the first few reporting cycles may be normal if the team is still validating assumptions.

What affects acceptable ranges

• Project complexity: Complex integrations and regulatory work tend to show more variance than repetitive build tasks.
• Uncertainty: New technology, new vendors, or unclear scope often create temporary swings.
• Work package size: Small work packages exaggerate noise; larger packages smooth it out.
• Phase of work: Planning, design, build, testing, and rollout each behave differently.

That is why project managers should avoid overreacting to a CPI of 0.97 or an SPI of 0.98 in isolation. Those numbers may be perfectly acceptable if the project is still stabilizing. The real question is whether the trend is flattening, improving, or deteriorating.

This is also where Trend Analysis becomes essential. A single snapshot can mislead you, while a four-week trend will often reveal whether the problem is temporary or structural.

Look below the summary line

One of the smartest habits is to inspect work package-level data. If the project summary says CPI is weak, look for the specific packages driving the problem. If the issue is only in one vendor stream or one testing stream, you do not need a full-project response.

Temporary variance usually comes from timing differences, late invoices, or a scheduled task that has not been formally credited yet. Structural problems show up as repeated rework, recurring blockers, or a pattern of underestimating effort. Those require different fixes.

The NIST Information Technology Laboratory regularly stresses measurement discipline and repeatable assessment methods in technical programs, and that same discipline applies to project reporting. Consistent data beats dramatic interpretation.

How Do You Use CPI And SPI Together To Make Decisions?

The best use of CPI and SPI is not reporting. It is action. These metrics help leaders choose the right corrective move instead of guessing whether the project needs more time, more money, more people, or less scope.

If SPI is weak but CPI is acceptable, the decision may be to re-sequence work, remove blockers, or add targeted resources to the critical path. If CPI is weak but SPI is acceptable, the decision may be to slow spending, renegotiate vendor terms, or trim nonessential scope before the budget gets out of hand.

Decision examples by situation

• Under budget, behind schedule: Move people to high-priority work, remove approval bottlenecks, or split dependent tasks.
• Over budget, ahead of schedule: Check whether overtime, rework, or urgent procurement is driving cost leakage.
• Both weak: Reassess scope, plan quality, and estimate accuracy before adding more resources.
• Both strong: Maintain the current approach, but continue monitoring forecast variance and dependency risk.

Management should use CPI and SPI to support a decision, not to replace judgment. A project with strong indices can still be strategically wrong if it is delivering the wrong scope. A project with weak indices can still be worth rescuing if the business value is high enough.

The right question is not “What is the number?” It is “What action does this number justify right now?”

For teams learning structured decision-making and status control, the concepts line up well with the planning and monitoring discipline taught in ITU Online IT Training’s PMP® 8 – Project Management Professional (PMBOK® 8) course, especially when scope changes and resource trade-offs start affecting outcomes.

How Should You Monitor And Report CPI And SPI?

Active projects should review CPI and SPI weekly or biweekly, depending on work pace and reporting requirements. Monthly reporting is often too slow for delivery teams that need to react before milestones are missed.

The report itself should be simple. Put the numbers first, then add trend charts, variance explanations, and forecast data. Stakeholders should be able to understand the health of the project in less than a minute.

What good reporting includes

• Status date clearly identified.
• Baseline version noted so everyone knows what plan is being measured.
• Variance narrative explaining why the index changed.
• Forecast at completion to show whether the current trend is sustainable.
• Data source documented so finance, PMO, and delivery teams are aligned.

Visuals matter. A line chart showing CPI and SPI over time is often easier to absorb than a dense table. If you add color coding, make sure the thresholds are documented and used consistently. Otherwise, “green” and “yellow” become subjective, and the reporting loses credibility.

For reporting consistency, it helps to align with recognized control and governance practices from ISO-style management discipline and public project control guidance from GAO on traceable performance reporting and accountability.

What Mistakes Should You Avoid With CPI And SPI?

The first mistake is using CPI and SPI as the only success criteria. A project can be on budget and on schedule and still fail the business if quality is poor, requirements are wrong, or users reject the deliverable.

The second mistake is overreacting to small fluctuations. Early-stage variance is common. If you chase every tiny shift, you create noise and force the team into unnecessary recovery actions.

Other common errors

• Confusing SPI with calendar delay instead of schedule efficiency.
• Inflating progress estimates to make metrics look better than reality.
• Ignoring forecast metrics because the current indices still look acceptable.
• Failing to document assumptions such as status date, scope changes, and cost recognition rules.

Manipulating progress estimates is especially dangerous. It may temporarily improve SPI, but it destroys the usefulness of the entire control system. Once the team stops trusting the numbers, the metrics stop driving decisions.

Forecasts matter because current CPI and SPI only describe what has happened up to the status date. They do not guarantee what comes next. A healthy current index can still hide a bad completion forecast if the remaining work is harder, riskier, or more expensive than the work already done.

Public guidance from the U.S. Department of Labor and the Bureau of Labor Statistics reinforces the importance of accurate reporting, accountable measurement, and realistic workforce planning in operational environments. That same discipline applies to project controls.

How Do You Build A Simple CPI And SPI Action Framework?

A simple action framework keeps the team from freezing when the numbers move. Start with a repeatable review process, then assign an intervention type, an owner, and a due date. The goal is not to admire the dashboard. The goal is to change outcomes.

A practical workflow

1. Review the latest CPI and SPI against the approved baseline.
2. Identify the variance driver at the work package or milestone level.
3. Classify the issue as cost-focused, schedule-focused, or combined.
4. Choose a corrective action such as scope reduction, work resequencing, vendor renegotiation, or staffing adjustment.
5. Assign an owner and deadline so the action is not left vague.
6. Recheck the indices after implementation to confirm the change worked.

Examples matter here. If procurement delay is driving a weak SPI, resequencing nondependent tasks may recover time without adding cost. If rework is driving a weak CPI, staffing more testers may help, but only if the defect source is already understood. If both metrics are poor, scope reduction may be the cleanest option.

Good action frameworks also record expected impact. “Add two analysts” is not enough. You need to know whether that change is expected to improve CPI, SPI, or both, and by how much. Without that expectation, follow-up reviews become opinion-based instead of evidence-based.

Corrective action should be measurable. If a response cannot be tied to an expected shift in CPI, SPI, schedule forecast, or cost forecast, it is probably too vague to manage.

For project professionals who want stronger decision discipline, the project controls concepts in ITU Online IT Training’s PMP® 8 – Project Management Professional (PMBOK® 8) course fit naturally with this framework because scope change control and performance review are part of the same operating rhythm.

Conclusion

CPI and SPI are most powerful when they are treated as complementary signals rather than isolated scores. CPI tells you whether the project is efficient with money. SPI tells you whether it is efficient with time. Together, they show whether the project is healthy, drifting, or in real trouble.

The most useful combinations are easy to remember: strong on both usually means control is solid, strong CPI with weak SPI points to schedule drag, weak CPI with strong SPI suggests speed is being bought too expensively, and weakness on both usually calls for a deeper recovery plan. But none of those readings should be made without context, baseline discipline, and trend review.

If you manage project management metrics for real decisions, not just status reports, keep the focus on what the numbers justify. Look at the trend, check the root cause, document the assumptions, and assign clear actions. Pick CPI when cost efficiency is the main question; pick SPI when schedule efficiency is the main question; pick both when you need the full picture of project control.

CompTIA®, Cisco®, Microsoft®, AWS®, EC-Council®, ISC2®, ISACA®, and PMI® are trademarks of their respective owners.