Understanding SPI And CPI Relationships: How Schedule And Cost Performance Reveal Project Health

SPI and CPI are two of the fastest ways to tell whether a project is healthy or quietly drifting off course. If you manage project metrics, performance indicators, or project success through earned value management, these indices show whether work is being delivered efficiently against the plan and the budget. SPI measures schedule efficiency. CPI measures cost efficiency. Used together, they tell you whether the project is on track, slipping, overspending, or recovering.

What SPI Measures	Schedule efficiency as of June 2026
What CPI Measures	Cost efficiency as of June 2026
Core Formula	SPI = EV / PV; CPI = EV / AC as of June 2026
Interpretation Threshold	Above 1.0 is favorable; below 1.0 signals concern as of June 2026
Primary Use	Project control, forecasting, and variance analysis as of June 2026
Typical Data Sources	Earned value reports, baseline schedule, cost tracking systems as of June 2026
Best Practice	Track trends, not one-off snapshots, as of June 2026

What SPI And CPI Mean In Earned Value Management

Earned value management (EVM) is a project control method that compares what was planned, what was earned, and what was actually spent. SPI and CPI come from that framework, which is why they are so useful in project metrics, performance indicators, and project success analysis. They are not opinions. They are ratios built from controlled project data.

The three building blocks are Performance, planned value, earned value, and actual cost. Planned Value (PV) is the budgeted value of work scheduled to be done by a certain date. Earned Value (EV) is the budgeted value of the work actually completed. Actual Cost (AC) is what the project really spent to perform that work.

From those values, the formulas are straightforward:

• SPI = EV / PV
• CPI = EV / AC

That simplicity is the point. If EV is lower than PV, the project is behind schedule. If EV is lower than AC, the project is over budget. Because both indices are relative measures, they do not tell you “three days late” or “$50,000 over budget” by themselves. They show efficiency, not raw amount.

Project health gets clearer when you compare earned value to both plan and cost, not just one or the other.

For project managers preparing for the PMP® 8 – Project Management Professional (PMBOK® 8) course content, this is one of the core habits to build. You do not manage projects by staring at dates alone or by checking invoices in isolation. You compare planned work, actual work, and actual cost, then make decisions based on the gap.

That is why SPI and CPI are more useful than a simple “percent complete” update. Percent complete can be subjective. EVM ratios are consistent across work packages, phases, and full programs when the baseline is built correctly.

How Does SPI And CPI Work?

SPI and CPI work by converting project progress into ratios that can be compared against 1.0. Once you have a baseline and current status data, the formulas immediately show whether the project is performing efficiently. That makes them practical project metrics for weekly reviews, phase gates, and executive reporting.

1. Set the baseline. The project team defines scope, schedule, and budget so planned value can be measured over time.
2. Record actual progress. Completed work is converted into earned value based on the budget assigned to that work.
3. Capture actual cost. Labor, materials, vendor charges, and other expenditures are added to actual cost.
4. Calculate SPI and CPI. SPI compares EV to PV, while CPI compares EV to AC.
5. Interpret the result. Values above 1.0 indicate favorable efficiency; values below 1.0 point to underperformance.

Why the ratios matter

The ratios matter because they create a common language for project health. A schedule delay and a cost overrun can happen together, but they do not always happen for the same reason. A project can be moving quickly but burning money too fast. It can also be spending carefully while finishing work too slowly.

That distinction is why project managers use SPI and CPI as performance indicators instead of absolute measures. The numbers help compare one project phase with another, one team with another, or this week’s status with last month’s trend.

If you are working in Environment settings with strict change control, such as regulated healthcare or financial systems, these ratios are especially helpful because they expose drift early. You see the trend before the program crosses a hard threshold.

Why Are SPI And CPI Often Used Together?

SPI and CPI are often used together because schedule performance and cost performance are related, but not identical. That difference matters in real projects. One metric can look healthy while the other is already warning you about trouble.

A project can be on schedule and still over budget if the team is paying overtime, expediting materials, or bringing in expensive specialists to maintain pace. The reverse is also true. A project can be under budget because it is using fewer resources than planned, but still fall behind because those resources are not producing finished work fast enough.

• SPI alone can hide overspending.
• CPI alone can hide schedule slips.
• SPI plus CPI gives a more balanced view of project control.

That combined view is what executives usually want. They do not just ask whether the team is busy. They ask whether the project is producing value at the expected pace and cost. That is also why these are standard project metrics in formal status reviews.

Forecasting is where the pair becomes even more useful. When SPI and CPI move together, the story is usually straightforward. When they diverge, it tells you where the tradeoff is happening. That can drive faster decisions on staffing, scope changes, vendor negotiations, or milestone re-sequencing.

For example, if CPI is strong but SPI is weak, the project may be conserving money at the cost of time. If SPI is strong but CPI is weak, the team may be throwing resources at the schedule. Either way, looking at only one number creates a false sense of project success.

According to the Project Management Institute, disciplined measurement and governance are central to effective project control, and EVM is one of the most established ways to do that. That is why many organizations use these indices alongside schedule variance and cost variance rather than as stand-alone scores.

How Do You Interpret Different SPI And CPI Combinations?

SPI and CPI combinations tell you whether a project is ahead, behind, efficient, or unstable. The interpretation is simple once you treat 1.0 as the break-even point. Above 1.0 is favorable. Below 1.0 is unfavorable. The real value comes from reading both numbers together.

SPI and CPI	Interpretation
SPI > 1.0 and CPI > 1.0	The project is ahead of schedule and under budget.
SPI < 1.0 and CPI < 1.0	The project is behind schedule and over budget.
SPI > 1.0 and CPI < 1.0	The project is moving fast but spending too much to do it.
SPI < 1.0 and CPI > 1.0	The project is controlling cost but not moving quickly enough.

Favorable performance

When both SPI and CPI are above 1.0, the project is producing more value than planned and earning that value at a lower cost than expected. That is the cleanest signal of project health, but it still needs context. Sometimes an early-stage project appears excellent because only easy work has been completed.

Mixed performance

The mixed cases are the ones that demand leadership judgment. Strong schedule performance with weak cost performance often shows up in crash efforts, where the team adds overtime, extra shifts, or premium vendor support. Strong cost performance with weak schedule performance can happen when the team is understaffed, delayed by dependencies, or waiting on approvals.

Real-world project managers learn quickly that a “good” number can hide a bad tradeoff. The job is not to celebrate a single index. The job is to decide what to fix first so project success remains possible.

These combinations are also useful in project reviews because they guide the next question. If both are low, start with root causes. If one is high and the other low, identify the tradeoff. If both are high, verify that the status is not being inflated by incomplete work definition.

A project that looks efficient on one axis and broken on the other is not healthy; it is compensating.

What Causes SPI And CPI To Change?

SPI and CPI change when the project loses alignment between planned work, completed work, and actual spending. The causes are usually operational, not mathematical. The ratios only reveal the symptom; the underlying issue sits in scope, resources, quality, or external constraints.

• Scope changes add new work or alter existing work, which can distort both schedule and cost performance.
• Resource shortages slow progress and can also drive expensive overtime or contractor use.
• Labor inefficiencies reduce output per hour, lowering earned value compared with actual cost.
• Procurement delays block downstream tasks and often increase idle time or expedite costs. A Procurement delay is one of the most common schedule-to-cost chain reactions in project work.
• Rework and quality defects consume time and money without adding new earned value.
• Unrealistic baselines create bad comparisons from day one, making healthy work look unhealthy.
• External risks such as vendor disruption, market shifts, and regulatory changes can hit both metrics at once.

Rework is one of the most expensive hidden drivers because it consumes team capacity twice. First, the team builds the wrong thing or builds it incorrectly. Then it spends more time and money fixing it. That pattern crushes CPI quickly and often drags SPI with it.

Unrealistic planning is just as damaging. If the original baseline assumed overly optimistic productivity, the project can look off track even when the team is working hard and doing good work. That is why project metrics must be tied to a planning process that is grounded in actual capacity and historical data, not wishful thinking.

According to NIST guidance on process and control discipline, weak baselines and poor measurement practices undermine management decisions. That principle applies directly to EVM: if the inputs are weak, the SPI and CPI outputs will mislead you.

How Can You Use SPI And CPI For Forecasting?

SPI and CPI can be used for forecasting by extending current efficiency into future project outcomes. That is why these indices matter beyond status reporting. They help estimate whether the project is likely to finish on budget, on time, both, or neither.

Two common forecasting concepts are Estimate at Completion (EAC) and time-to-complete. EAC predicts the likely total final cost of the project based on current performance. Time-to-complete estimates how much schedule remains before the project finishes. Both improve when SPI and CPI trends are stable.

1. Review current SPI and CPI. A single data point gives a snapshot, not a forecast.
2. Check the trend over multiple reporting periods. Three or four points are much more useful than one.
3. Compare the trend against the critical path and major deliverables. A delay in a noncritical work package may not matter much, while a delay in a gated dependency may matter a lot.
4. Decide whether corrective action is needed. Forecasts should trigger management action, not just reporting.

Forecasts are strongest when they are based on stable work packages. They are weakest early in a project if the team has not yet completed enough measurable work. That is why managers should avoid extrapolating too aggressively from the first few reporting cycles. Early SPI and CPI values often swing because the project is still ramping up, vendor purchases are front-loaded, or major tasks have not yet been closed.

As of June 2026, the PMI continues to emphasize forecast-driven control in professional project management practice, and that aligns with the PMP® 8 – Project Management Professional (PMBOK® 8) course focus on decision-making under pressure. Forecasts are only useful if they lead to decisions: re-baselining, de-scoping, reassigning resources, or escalating constraints.

In practical terms, a low CPI trend may lead to a spend freeze on lower-priority work. A low SPI trend may lead to schedule compression or dependency removal. The point is not to chase the numbers. The point is to change the plan before the gap becomes unrecoverable.

What Are The Limitations And Misinterpretations Of SPI And CPI?

SPI and CPI are useful, but they can be misleading if you treat them as complete measures of project success. They do not measure quality, user adoption, stakeholder satisfaction, or business value. They only measure efficiency against the baseline.

A project can have strong SPI and CPI values and still fail if the delivered product does not meet business needs. It can also have weak SPI and CPI values and still produce a strategically valuable result if the scope changed in a controlled way. That is why these indices should never be used as the sole basis for judgment.

• Weak baselines make the comparison unreliable.
• Outdated baselines hide the real project condition after major approved changes.
• Late-stage recovery can make the numbers look better after earlier damage.
• Activity progress is not the same as deliverable completion.
• Customer satisfaction and business outcomes sit outside the ratio.

That distinction between activity and completion matters. A team may report that 80 percent of tasks are underway, but if the hardest integration work is still pending, the project is not truly 80 percent complete. SPI and CPI only become trustworthy when the status rules for earning value are strict and consistent.

Industry guidance from GAO on program oversight consistently stresses the same point: controls matter, but controls only work when leaders understand their limits. That is exactly how SPI and CPI should be treated in project governance.

How Can You Monitor SPI And CPI Effectively?

SPI and CPI are most useful when they are monitored on a consistent cadence and tied to corrective action. A monthly dashboard that nobody uses is not project control. It is paperwork. Monitoring needs to be frequent enough to catch drift while there is still time to fix it.

Use a consistent reporting cadence

Weekly reporting works well for fast-moving delivery teams. Biweekly or monthly reporting may be enough for larger programs with slower-moving work packages. The key is consistency. If one report is based on Thursday data and the next is based on Monday data, the trend becomes hard to trust.

Track trends, thresholds, and exceptions

Dashboards should show SPI and CPI over time, not just as isolated values. Add variance flags for thresholds that matter to your organization. Many teams use a yellow zone for early warning and a red zone for escalation. That gives leaders time to intervene before the project slips into recovery mode.

Go deeper than the project total

Project-level averages can hide trouble in a specific phase or work package. A strong overall CPI may cover a weak integration stream. A strong SPI may hide a critical procurement issue. Drill down into the work breakdown structure when the top-line number changes.

That approach matches how the CISA and other oversight bodies think about control: broad indicators matter, but the value comes from the ability to isolate the problem fast. The same logic applies to project control dashboards.

One practical operating rule is to ask three questions whenever either index drops:

1. What changed in scope, staffing, vendor support, or quality?
2. Is the issue isolated or systemic?
3. What action will change the trend by the next reporting cycle?

That is the part many teams miss. Reporting SPI and CPI is easy. Acting on them requires leadership discipline, especially when the corrective action affects scope, budget, or schedule commitments.

Real-World Examples Of SPI And CPI In Use

SPI and CPI show up in real projects whenever leaders need to compare progress and spending against a baseline. They are not theoretical tools reserved for textbooks. They are used in construction, software delivery, defense programs, and enterprise transformations.

Example from an enterprise software rollout

A company migrating a legacy finance system to Microsoft Azure may see CPI fall below 1.0 because integration tasks take longer than planned and require specialist contractors. At the same time, SPI may remain near 1.0 if the team is meeting interim milestone dates by adding overtime. In that case, the project is hiding cost pressure behind schedule control.

This is where official vendor documentation becomes useful. Microsoft Learn provides practical guidance on cloud services, architecture, and deployment patterns that help teams reduce rework and reduce unnecessary spend. The lesson is simple: better planning and better technical alignment usually improve both SPI and CPI over time.

Example from a security implementation

A cybersecurity program aligning controls to the NIST Cybersecurity Framework may initially show weak SPI because the team is waiting on policy approvals, access reviews, and procurement decisions. CPI may remain healthy if the team is small and tightly controlled. That combination tells management the issue is schedule friction, not runaway spend.

Security programs are especially sensitive to hidden work. Activities like access review, evidence collection, and remediation can consume time without producing visible “features.” SPI and CPI help translate that invisible work into governance language executives understand.

Example from a regulated infrastructure project

A telecom or utility upgrade affected by vendor-delivered hardware can suffer when shipments slip by two weeks. SPI drops because the installed work cannot progress. CPI may also fall if the team keeps labor on standby. This is a classic external-risk case where project metrics reveal the operational damage quickly enough for action.

According to the Bureau of Labor Statistics, project management roles continue to require strong coordination, analysis, and communication skills. That lines up with the reality of EVM work: the numbers matter, but the manager’s ability to interpret them and escalate the right issue matters just as much.

These examples show why SPI and CPI are so valuable. They turn the question “Are we okay?” into a more precise question: “Are we spending the right amount to produce the right amount of finished work at the right time?”

Conclusion

SPI and CPI work together to give a clearer view of project health than either metric can provide alone. SPI tells you whether the project is moving through planned work efficiently. CPI tells you whether that work is being delivered at a sensible cost. When you read them together, you get one of the most practical views of project metrics, performance indicators, and project success available in earned value management.

Do not use either ratio in isolation. A strong SPI can hide cost pressure. A strong CPI can hide schedule risk. The right response is to track trends, investigate root causes, and act early while the project still has room to recover.

That is the real value of disciplined project control. It combines data, context, and timely decisions. For readers working through the PMP® 8 – Project Management Professional (PMBOK® 8) course, this is exactly the kind of judgment that separates routine reporting from effective leadership.

If you want better control of project health, start by reviewing the baseline, measuring SPI and CPI consistently, and using both numbers to drive conversations about scope, schedule, and budget before problems become expensive.

CompTIA®, Microsoft®, PMI®, NIST, CISA, and BLS are referenced for informational purposes. PMI® and PMP® are trademarks of Project Management Institute, Inc. Microsoft® is a registered trademark of Microsoft Corporation. CompTIA® is a registered trademark of CompTIA, Inc.