How Do I Calculate CPI and SPI for Project Tracking

When a project starts slipping, the first question is usually the wrong one. Teams ask whether they are “busy enough” instead of checking CPI and SPI, the two project management metrics that show whether work is landing earned value analysis on target for cost and schedule control.

Understanding Earned Value Management Basics

Earned Value Management (EVM) is a method for comparing planned work, completed work, and money spent so you can see project performance in one model. It is useful because it gives you a cleaner read on whether a project is drifting on scope, schedule, or cost instead of relying on gut feel.

The three foundational inputs are Planned Value (PV), Earned Value (EV), and Actual Cost (AC). PV is the value of work that should have been completed by the reporting date, EV is the value of work actually completed, and AC is the real money spent to produce that work.

The project baseline is the approved reference point for comparing what should have happened with what actually happened. Without a baseline, CPI and SPI lose meaning because there is no stable plan to measure against.

In practical terms, cost performance asks, “Did we spend efficiently?” while schedule performance asks, “Did we finish the amount of work we planned by now?” Those are related questions, but they are not the same.

When EVM is worth using

EVM is strongest in work that can be broken into measurable deliverables or milestones. Construction, manufacturing, infrastructure, and software delivery all benefit when progress can be tied to objective completion criteria.

• Construction: progress is measurable by completed phases, inspections, and installed materials.
• Software delivery: progress can be tied to completed stories, tested features, or signed-off releases.
• Manufacturing: production lines and batch output lend themselves to time-phased tracking.
• Professional services: EVM works when work packages are defined tightly enough to avoid vague percent-complete reporting.

You will also see terms like Budget at Completion (BAC), Estimate at Completion (EAC), variance, and performance index. The PMI standards used in project controls treat these measures as a practical way to connect schedule control with financial control, while the U.S. federal EVM community uses similar discipline in oversight-heavy programs.

“If the baseline is weak, the metrics are weak. CPI and SPI only work when the plan, the work breakdown, and the reporting discipline are all tight.”

What CPI Means and How To Calculate It

Cost Performance Index (CPI) is a measure of cost efficiency. It tells you how much value the project is earning for every dollar spent.

The formula is simple: CPI = Earned Value / Actual Cost. If EV is $80,000 and AC is $100,000, CPI is 0.80, which means the project is getting 80 cents of value for every dollar spent.

How to read CPI

• CPI above 1.0: the project is under budget for the value delivered.
• CPI equal to 1.0: the project is spending exactly what the work is worth.
• CPI below 1.0: the project is spending more than the value earned, which usually means cost overrun.

Here is a simple example. A team completes work worth $45,000 and the verified actual cost is $60,000. CPI = 45,000 / 60,000 = 0.75. That tells you the project is inefficient from a cost standpoint, even if the team is staying busy.

Cost variance is related but not identical. Cost variance is EV – AC, so in the same example the variance is -$15,000. CPI tells you the ratio, which is easier to compare across projects of different sizes, while cost variance tells you the raw dollar gap.

A common mistake is using budgeted cost in the denominator instead of actual cost. That error turns CPI into a fake efficiency score and can hide real overruns. The official PMI guidance and project control practices used in government programs emphasize verified actuals, not estimates, when calculating cost performance.

For foundational project control discipline, the National Institute of Standards and Technology (NIST) promotes measurement rigor across technical systems, and that same discipline applies here: clean input data produces meaningful performance indicators.

What SPI Means and How To Calculate It

Schedule Performance Index (SPI) is a measure of schedule efficiency. It tells you whether the project is earning planned value at the rate expected by the baseline schedule.

The formula is SPI = Earned Value / Planned Value. If EV is $80,000 and PV is $100,000, SPI is 0.80, which means the project has completed only 80% of the value it should have completed by that date.

How to read SPI

• SPI above 1.0: the project is ahead of schedule in earned value terms.
• SPI equal to 1.0: the project is on schedule against the baseline.
• SPI below 1.0: the project is behind schedule in terms of earned work.

A practical example helps. Suppose the plan said the team should have completed $120,000 worth of work by month-end, but the team has only completed $90,000 worth. SPI = 90,000 / 120,000 = 0.75. That does not just mean time has passed; it means the project has failed to earn the value it expected to earn by now.

That distinction matters because SPI is based on earned value, not just the calendar. A project can be on the calendar and still lag in deliverables if key tasks remain incomplete or partially complete.

SPI and schedule variance often move together, but they answer slightly different questions. Schedule variance is EV – PV, which shows the gap in dollarized value. SPI is the ratio, which is better for comparing performance across reporting periods or projects. The Cybersecurity and Infrastructure Security Agency (CISA) often stresses measurable progress in operational programs, and the same logic applies to schedule control: what matters is whether the work is actually done.

How To Gather the Right Data Before Calculating CPI and SPI

Data quality is the difference between a useful EVM report and a misleading one. Before you calculate CPI and SPI, make sure your baseline documents, cost records, and progress rules are aligned.

You need the schedule baseline, cost baseline, and work breakdown structure (WBS). The WBS matters because it breaks the project into manageable work packages that can be valued, tracked, and reported consistently.

What to pull before you calculate

• Approved project plan with dated milestones.
• Time-phased budget that shows Planned Value by period.
• WBS or control accounts that define the work scope.
• Verified accounting records for labor, materials, and vendor costs.
• Progress evidence such as deliverable acceptance, test sign-off, or milestone completion.

Planned Value comes from the approved plan, not from current status guesses. If a task was budgeted at $20,000 in March, that value only counts in PV when the baseline says the work should have been scheduled by the reporting date.

Earned Value is calculated from actual completion, usually through percent complete, weighted milestones, or completed deliverables. Objective methods are better than subjective opinions, especially for complex tasks where “almost done” can mean anything.

Actual Cost should come from confirmed labor charges, vendor invoices, or posted financial records. Late cost reporting is a common cause of distorted CPI, because the project appears healthier than it really is until the missing invoices arrive.

Consistent measurement periods matter too. Weekly and monthly reporting cycles are common because they create stable trend lines. The ISC2® workforce and governance materials consistently reinforce the value of disciplined measurement in risk-sensitive environments, and project controls benefit from the same approach.

Step-By-Step Calculation Example

Here is a full worked example you can use as a model for project tracking. Assume a small implementation project with three work packages and a reporting date at the end of week six.

1. Set the baseline. The original plan assigns $50,000 to design, $80,000 to build, and $70,000 to test, for a total BAC of $200,000. By week six, the baseline says design should be complete, build should be 50% complete, and testing should not yet have started.

2. Calculate Planned Value. Design is fully planned at $50,000, build is half planned at $40,000, and testing is not planned yet. That gives a PV of $90,000 as of the reporting date.

3. Calculate Earned Value. Design is complete, build is only 40% complete, and testing has not started. EV is $50,000 + $32,000 + $0 = $82,000. Use accepted completion evidence, not a casual percentage guess.

4. Calculate Actual Cost. Labor has posted $60,000, materials total $18,000, and a vendor invoice adds $12,000. That makes AC = $90,000. The number should come from verified financial records, not from team estimates.

5. Compute CPI and SPI. CPI = EV / AC = 82,000 / 90,000 = 0.91. SPI = EV / PV = 82,000 / 90,000 = 0.91. The project is slightly over budget and slightly behind schedule.

6. Interpret the result. The project is earning 91 cents of value for every dollar spent and has completed 91% of the value it planned to complete by this point. That is not a crisis, but it is a clear signal that corrective action may be needed if the trend continues.

This example shows why earned value analysis is useful in real project control. A manager looking only at task activity might think the team is working steadily, while CPI and SPI reveal that the work is costing more than planned and delivering slightly less than scheduled.

The PMI PMBOK Guide is a useful reference for formal project performance tracking, and the course content in PMP® 8 – Project Management Professional (PMBOK® 8) fits directly into this kind of reporting discipline.

How To Interpret CPI and SPI Together

CPI and SPI are best read as a pair. One tells you whether the project is spending efficiently, and the other tells you whether it is earning planned value on time.

A project with high CPI and low SPI may be using money efficiently while still falling behind schedule. That happens when the team slows work to control spend, or when scope is being delivered too slowly for the baseline.

A project with low CPI and high SPI can look fast but wasteful. That pattern often appears when teams accelerate delivery by throwing extra labor or vendor support at the problem without controlling cost.

When both CPI and SPI are below 1.0, the project is both late and over budget. That combination deserves immediate attention because it usually signals either underestimated work, weak execution, or unstable scope.

Why trends matter more than snapshots

One reporting period can mislead you. A single bad week can look worse than it is, and a temporary rebound can hide deeper problems.

• Declining CPI over three periods: cost efficiency is weakening.
• Declining SPI over three periods: schedule recovery is not happening.
• Flat CPI with falling SPI: the team is spending at the same rate but earning value more slowly.

Consistent declines are what trigger corrective action. That may mean resequencing work, reducing scope, reforecasting dates, or escalating to sponsors before the gap becomes unmanageable.

“A single CPI or SPI value is a snapshot. Three reporting periods tell you whether the project is actually changing direction.”

For project managers who need formal governance discipline, the ISACA® body of knowledge reinforces the value of controls, evidence, and repeatable measurement, all of which support strong project tracking.

Using CPI and SPI To Forecast Project Outcomes

Forecasting is where CPI and SPI become more than status indicators. They help estimate what the project may cost and when it may finish if current performance continues.

CPI is commonly used to estimate Estimate at Completion (EAC). A simple approach is BAC divided by CPI when the current cost trend is expected to continue. If BAC is $200,000 and CPI is 0.91, the rough EAC becomes about $219,780.

SPI can support timeline forecasting by showing whether the project is earning value fast enough to meet the planned finish date. In practice, schedule forecasts often need more than one formula, because time does not always move linearly with earned value.

Common forecasting use cases

• Budget reforecasting: update leadership on likely final cost.
• Delivery date review: estimate whether the finish date will move.
• Escalation decisions: determine when to request extra funding or scope changes.
• Management reporting: explain why the current baseline is no longer realistic.

Forecasts improve after enough actual data has accumulated. Early in a project, one unusual purchase or one delayed milestone can distort the numbers. After several reporting cycles, the trend is more reliable and decision-making gets better.

This is where the schedule control discipline from PMP-style project practice matters. You are not just reporting status; you are using performance history to defend a change request, a revised delivery date, or a cost contingency discussion.

The U.S. Bureau of Labor Statistics tracks project management specialist employment and pay, which underscores how central measurable project control has become in real organizations. For forecasting methods and control structure, official guidance from PMI and government performance-control practices remain the strongest references.

Tools, Templates, and Reporting Practices

You do not need a complex system to calculate CPI and SPI, but you do need a disciplined one. A spreadsheet can work for small projects, while larger programs often rely on project management software and EVM dashboards.

A good reporting template should include PV, EV, AC, CPI, SPI, cost variance, schedule variance, and trend notes. If you cannot see all of those in one place, managers end up arguing about definitions instead of making decisions.

What a useful report should show

• Current period values for PV, EV, and AC.
• Calculated indices for CPI and SPI.
• Variance lines to show dollar gaps.
• Trend charts for several reporting periods.
• Assumptions and notes to explain any unusual movements.

Charts matter because stakeholders scan. A simple line chart showing CPI and SPI over time is often more persuasive than a dense spreadsheet. Heat maps work well for portfolio views, while trend lines are better for a single project with multiple work streams.

Regular review cadence keeps the data honest. A weekly checkpoint with team leads can validate percent complete, a finance review can confirm posted costs, and a sponsor review can decide whether the trend needs escalation.

Documented assumptions protect future reporting. If a deliverable was valued using weighted milestones, write that down. If certain costs will post late, note the timing. That documentation keeps the numbers auditable and stable from one reporting cycle to the next.

The Microsoft® Project documentation and Google support resources are useful examples of how vendors frame planning and reporting discipline, but the real point is simple: use a tool that preserves your baseline, not one that constantly rewrites it.

Common Pitfalls and Best Practices

The biggest problem with CPI and SPI is not the formulas. It is bad inputs. If percent complete is loose, the metrics become decorative instead of useful.

One common failure is changing baselines without control. A re-baseline may be legitimate, but if teams keep moving the target every time the project slips, CPI and SPI stop measuring performance and start measuring paperwork.

Pitfalls to avoid

• Subjective percent complete: “looks 80% done” is not good enough.
• Late invoices: AC that posts weeks late gives false optimism.
• Small-task noise: tiny tasks can distort value if they are overtracked.
• Uncontrolled re-baselines: moving the target without governance breaks comparability.
• Ignoring context: metrics alone do not explain vendor issues, dependencies, or scope change.

Best practice is to use objective completion criteria. For example, a testing task should be worth value only when test cases are executed and signed off, not when the team says it is “mostly ready.” Weighted milestones also help when work is hard to measure by percent complete.

Compare the numbers with the project context. A low SPI on a heavily regulated implementation may be acceptable if approvals are the real bottleneck. A low CPI during a hardware surge may reflect a one-time procurement spike rather than a structural problem.

The Gartner and Verizon Data Breach Investigations Report style of evidence-driven reporting is a reminder that decisions improve when data is consistent, current, and comparable over time. Project controls work the same way.

Conclusion

CPI and SPI give you a fast, objective view of project performance. CPI tells you whether you are getting enough value for the money spent, and SPI tells you whether you are earning value on time.

The core formulas are straightforward: CPI = EV / AC and SPI = EV / PV. The hard part is not the math. The hard part is getting accurate PV, EV, and AC data from a disciplined baseline and a consistent reporting process.

Use these metrics regularly, not just when the project is already in trouble. That is how project managers spot issues early, communicate clearly with sponsors, and keep schedule control from turning into schedule recovery.

For teams building stronger project control skills, the PMP® 8 – Project Management Professional (PMBOK® 8) course is a practical fit because it reinforces baseline management, scope discipline, and decision-making under pressure. If you want CPI and SPI to mean something, make the reporting process as reliable as the formulas.

PMI® and PMP® are trademarks of the Project Management Institute, Inc.