How Do I Calculate CPI and SPI for Project Tracking?
If your project is busy but still drifting, CPI and SPI are the two numbers that tell you whether the work is actually under control. They cut through status noise and show whether you are spending efficiently, finishing work on time, or slowly bleeding both budget and schedule.
PMP® 8 – Project Management Professional (PMBOK® 8)
Discover essential project management skills to handle scope changes, make sound decisions under pressure, and lead successful projects with confidence.
Get this course on Udemy at the lowest price →This guide explains how to calculate CPI and SPI for project tracking, how to collect the right inputs, how to interpret the results, and how to use the numbers in real project decisions. It also shows how Earned Value Management supports cost and schedule control in a way that busy project teams can actually use.
Quick Answer
CPI and SPI are Earned Value Management indices used to measure project cost efficiency and schedule efficiency. Calculate CPI = EV / AC and SPI = EV / PV, where EV is Earned Value, AC is Actual Cost, and PV is Planned Value. A result above 1.0 is favorable, 1.0 is on target, and below 1.0 signals underperformance.
Quick Procedure
- Confirm the approved baseline for scope, schedule, and budget.
- Set the reporting date and identify work scheduled by that date.
- Calculate Planned Value from the baseline plan.
- Measure Earned Value using objective completion criteria.
- Collect verified Actual Cost from approved financial records.
- Compute CPI and SPI using EV / AC and EV / PV.
- Compare the result to the baseline and trend it over time.
| Primary Formulas | CPI = EV / AC; SPI = EV / PV |
|---|---|
| Metric Meaning | CPI measures cost efficiency; SPI measures schedule efficiency |
| Input Variables | Planned Value, Earned Value, Actual Cost |
| Best Used With | Earned Value Management and a stable project baseline |
| Result Format | Unitless index, not dollars or days |
| Interpretation | Above 1.0 is favorable; below 1.0 is unfavorable |
| Common Use | Project tracking, forecasting, corrective action, stakeholder reporting |
Understanding CPI and SPI in Earned Value Management
Earned Value Management (EVM) is a project control method that compares planned work, completed work, and actual spending so you can see performance early. The core idea is simple: if a project says it has finished 50% of the work, the numbers should prove whether that is true in terms of budget and schedule.
Three inputs drive the entire method. Planned Value (PV) is the budgeted value of work that was supposed to be done by the reporting date, Earned Value (EV) is the budgeted value of the work actually completed, and Actual Cost (AC) is what the work really cost.
What each metric tells you
CPI stands for Cost Performance Index. It answers a direct question: “For every dollar spent, how much planned value did we earn?” If CPI drops below 1.0, the project is getting less value than expected for each dollar spent.
SPI stands for Schedule Performance Index. It answers a different question: “For every dollar of work we planned to complete by now, how much did we actually complete?” If SPI drops below 1.0, the project is behind schedule relative to the baseline.
Why the baseline matters
Both metrics depend on a stable baseline. If scope changes, milestones move, or budgets are reset, the comparison becomes meaningless unless the change is formally approved and reflected in the project plan. A bad baseline creates fake confidence, and fake confidence is worse than a bad number.
“CPI and SPI do not measure activity. They measure whether activity is producing the planned result.”
For official guidance on Earned Value concepts and project performance measurement, refer to NASA project management references and the project control practices described in the Project Management Institute ecosystem. For project managers sharpening this skill set, this is also a practical place to connect theory with the PMBOK-based planning discipline taught in ITU Online IT Training’s PMP® 8 – Project Management Professional (PMBOK® 8) course.
What Do the CPI and SPI Formulas Mean?
The formulas are straightforward, but the meaning behind them matters more than the arithmetic. CPI = EV / AC and SPI = EV / PV are ratios, so they show relative performance rather than absolute cost or time.
That means a CPI of 0.80 does not mean you are “20% over budget” in the plain-English sense unless you understand the estimate structure. It means the project is earning only 80 cents of value for every dollar spent, which is a warning sign that deserves attention.
How to read the numbers
| Result | Meaning |
|---|---|
| Above 1.0 | Better than planned performance |
| Exactly 1.0 | On target against the baseline |
| Below 1.0 | Worse than planned performance |
These are unitless indices, not dollars, hours, or days. You cannot say “SPI equals 0.9 days” because the metric is not measuring time directly. It is measuring the efficiency of progress against the amount of work that should have been done by the reporting date.
Why consistent measurement matters
The formulas only work when EV, PV, and AC are measured in the same structure and with the same rules. If one team uses subjective percent-complete estimates and another uses accepted deliverables, your CPI and SPI will not be comparable.
For standard project management definitions, the PMI PMBOK Guide remains a widely recognized reference point, and IT governance teams often align reporting with control objectives from ISACA COBIT when project performance needs to roll up into governance reporting.
How Do I Collect the Right Inputs Before Calculating CPI and SPI?
The calculation is the easy part. The hard part is making sure your inputs are real, consistent, and approved. If the inputs are weak, CPI and SPI will still produce a number, but the number will be fiction dressed up as reporting.
Start by confirming the approved baseline. That means your scope, schedule, and budget have been authorized and are still the official reference point for measuring performance.
Build the three inputs correctly
- Planned Value comes from the baseline schedule and cost plan for work that should have been completed by the reporting date.
- Earned Value comes from objectively completed work, not optimism, not “almost done,” and not percent-complete guesses.
- Actual Cost comes from verified financial records such as invoices, timesheets, procurement systems, or accounting reports.
Use objective completion rules
A work package should have clear finish criteria before the project starts. For example, “configure firewall rules, test access, and get sign-off from the security lead” is measurable. “Make progress on security setup” is not.
In project environments that use formal controls, the discipline of approved change management is just as important as the math itself. The National Institute of Standards and Technology also emphasizes repeatable measurement and control in its guidance ecosystem, which is why many project and security teams borrow the same logic: define, measure, verify, then report.
Warning
Never mix approved costs with forecasted costs in Actual Cost. AC must reflect what has actually been spent or committed under your reporting rule, not what you expect to spend later.
How Do I Calculate CPI and SPI Step by Step?
You calculate CPI and SPI by fixing the reporting date, measuring completed work against the baseline, and applying the two ratios. The process is simple, but every step must be disciplined if you want the result to support decisions.
-
Set the reporting date. Choose a date that matches your project status cycle, such as Friday close or month-end close. This date becomes the cut line for what counts as planned, earned, and spent.
-
Identify scheduled work by that date. Use the baseline schedule to determine which tasks, milestones, or work packages were supposed to be complete. This gives you Planned Value, usually expressed as the budgeted cost of scheduled work.
-
Measure Earned Value objectively. Review completion criteria for each work package and count only the work that actually meets those criteria. If a task is 80% done but not accepted, it is not 100% earned value.
-
Collect Actual Cost from verified records. Pull labor, vendor, and material costs from approved systems such as accounting, ERP, or timesheet data. Do not estimate AC if actual data is available.
-
Apply the formulas. Divide EV by AC to get CPI, and divide EV by PV to get SPI. Keep the result to two decimal places for reporting, but preserve the raw numbers for auditability.
-
Compare against the baseline and trend. A single snapshot tells you where you are, but multiple snapshots tell you where you are headed. CPI that declines for three reporting cycles in a row is a stronger warning than one weak month.
Here is the practical rule: if the input data cannot be defended in a status meeting, it is not ready for EVM reporting. That standard is why project controls teams often pair EVM with governance practices found in ISO/IEC 20000 and ISO/IEC 27001 environments, where traceability and consistency matter.
Worked Example of CPI and SPI Calculation
Suppose a project has a budgeted phase plan of $100,000 for a software rollout. By the reporting date, the baseline says $60,000 of planned work should be complete. The team has completed work worth $50,000, and actual spending has reached $62,500.
Now calculate both indices. CPI = EV / AC = 50,000 / 62,500 = 0.80. SPI = EV / PV = 50,000 / 60,000 = 0.83.
What the example tells you
The CPI of 0.80 means the project is spending more than planned for the value it is earning. The SPI of 0.83 means the project is also behind schedule. That combination is common when work is being done inefficiently and some tasks are slipping at the same time.
Now compare that to a different scenario. If EV were $70,000, PV were still $60,000, and AC were $62,500, then CPI would be 1.12 and SPI would be 1.17. In that case, the team would be ahead of plan on both cost efficiency and schedule efficiency.
Why one metric can look good while the other looks bad
A project can be spending efficiently but still lag on delivery. For example, a team may have low labor waste and a strong CPI, but if it is waiting on approvals, hardware, or dependencies, SPI can still fall below 1.0.
The reverse happens too. A project may push hard to catch up on schedule and burn extra hours or premium vendor support, which can improve SPI while damaging CPI. That is why project tracking must look at both metrics together, not as isolated scorecards.
“A good CPI does not rescue a bad schedule, and a good SPI does not rescue a bad budget.”
How Should You Interpret CPI and SPI Results?
Interpretation is where project controls become useful. Numbers only help if they lead to action, and CPI and SPI are action-oriented metrics. They are not trophies.
What CPI means in practice
- CPI above 1.0: The project is getting more earned value than planned for each dollar spent.
- CPI = 1.0: The project is spending exactly as planned for the value earned.
- CPI below 1.0: The project is spending more than planned for the value earned.
A low CPI can signal rework, poor estimating, scope creep, or inefficient execution. It can also point to hidden friction such as tool issues, vendor delays, or labor overruns that are not obvious from a simple status report.
What SPI means in practice
- SPI above 1.0: The project is completing more work than planned by the reporting date.
- SPI = 1.0: The project is exactly on schedule against the baseline.
- SPI below 1.0: The project is behind schedule relative to the baseline.
A low SPI can point to blocked work, dependency failures, staffing gaps, long lead items, or a schedule that was too aggressive from the start. In many real projects, schedule slips begin before anyone feels them operationally, which is why SPI is valuable as an early warning indicator.
Note
Trend direction matters more than one month’s result. A CPI of 0.94 that improves every period is usually less alarming than a CPI of 1.01 that steadily declines.
The U.S. Bureau of Labor Statistics Occupational Outlook Handbook remains a useful external reference for understanding project-related job growth and the broader demand for analytical project roles, while CIO-level governance teams often align these metrics with business outcome reporting rather than raw activity tracking.
How Can CPI and SPI Be Used for Forecasting and Decision-Making?
CPI and SPI become more valuable when you use them to predict what happens next. If a project repeatedly posts a CPI below 1.0, it is signaling that budget pressure is likely to continue unless something changes.
Repeated low SPI values suggest the team is not just having a bad week. They suggest a structural schedule problem, such as unrealistic sequencing, dependency delays, or insufficient capacity in a critical path area.
What to do when the trend turns negative
- Review the root cause. Determine whether the problem is estimating, execution, dependency management, or scope change.
- Isolate the work package. Find the part of the project driving the decline instead of assuming the whole project is equally affected.
- Decide on corrective action. Options include resequencing work, adding resources, removing low-value scope, or changing the delivery approach.
- Escalate when needed. If the performance trend is persistent, the sponsor needs to know early enough to act.
- Reforecast carefully. Update the forecast only after the cause is understood and the new plan is approved.
Forecasting gets stronger when CPI and SPI are tracked together over time. If CPI keeps falling while SPI stays steady, you may be maintaining schedule by spending too aggressively. If SPI falls while CPI stays strong, you may be efficient but delayed, which can still be a major business problem.
For organizations that rely on governance controls, this is the point where project metrics intersect with risk management. That connection is consistent with the ISO 31000 risk management approach: measure, interpret, respond, and review.
Industry-Specific Examples of CPI and SPI in Practice
CPI and SPI behave differently depending on how progress is defined. The formulas do not change, but the measurement method absolutely does. That is why industry context matters.
Construction
Construction teams often measure progress through completed phases, installed materials, inspections, or signed-off milestones. A completed foundation, finished framing package, or approved electrical rough-in can be assigned earned value only when the acceptance criteria are met.
This works well because construction already relies on visible deliverables. The risk is over-crediting work that looks physically advanced but has not actually been accepted.
Software delivery
Software teams may use finished features, accepted user stories, tested releases, or production-ready increments as the basis for EV. A partially coded feature is not earned value if it is not accepted under the team’s definition of done.
In software environments, CPI and SPI are often most useful when paired with release milestones, defect trends, and dependency tracking. That prevents the team from mistaking raw activity for real progress.
Manufacturing and professional services
Manufacturing teams can track production output, batch completion, or inspection-approved units. Professional services teams often rely on tightly defined work packages, because vague percent-complete estimates become unreliable very quickly.
For service projects, the key is to define measurable deliverables early. If the work is advisory, break it into tangible outputs such as completed workshops, documented assessments, or approved deliverable sets.
The Cybersecurity and Infrastructure Security Agency often emphasizes measurable resilience and operational accountability, which mirrors the same principle behind reliable project tracking: define what done means before you start counting it.
What Are the Most Common Mistakes That Distort CPI and SPI?
Most bad CPI and SPI numbers do not come from the math. They come from poor measurement discipline.
- Using vague percent-complete estimates. “Almost done” is not a metric.
- Measuring progress differently across teams. One team may count effort hours while another counts accepted deliverables.
- Failing to update the baseline after approved change. A stale baseline makes good performance look bad, or bad performance look acceptable.
- Mixing approved and unapproved costs. AC must be clean or CPI loses credibility.
- Looking at a single reporting period only. Trend lines are more useful than one snapshot.
- Ignoring scope, risk, and quality. A project can have a decent CPI and SPI while still delivering a poor outcome.
Another common mistake is using the metrics as punishment. That creates bad behavior, because teams start optimizing for the number instead of the work. Good project controls should improve transparency, not create fear.
The best defense is a measurement rulebook that everyone follows. That is standard practice in disciplined project environments and aligns well with the kind of control thinking used in PMI-based project governance and formal change control.
How Do CPI and SPI Fit with Other Project Management Metrics?
CPI and SPI are powerful, but they are not enough by themselves. They show efficiency, not the full health of the project. A project can have good indices and still be failing in scope, quality, risk, or stakeholder alignment.
That is why experienced project managers read CPI and SPI alongside milestone status, defect counts, scope changes, risk exposure, and delivery quality. The goal is not to collect more metrics for their own sake. The goal is to avoid being fooled by one favorable number.
How the metrics work together
| If CPI is strong but SPI is weak | The project may be efficient but late |
|---|---|
| If SPI is strong but CPI is weak | The project may be moving fast but overspending |
| If both are weak | The project needs immediate review |
| If both are strong | The project is tracking well against the baseline |
Integrated reporting gives stakeholders a better answer than a single index ever can. Finance wants budget confidence. Delivery leadership wants schedule confidence. Sponsors want decision confidence. CPI and SPI help all three, but only when they are placed inside a broader control framework.
For governance and assurance, many organizations align project reporting with broader control models such as COBIT and risk practices influenced by the NIST Cybersecurity Framework when delivery projects affect infrastructure, security, or regulated systems.
Can You Use CPI and SPI in Agile or Hybrid Projects?
Yes, but Agile teams need clear completion rules or the metrics become misleading. In iterative delivery, work is often sliced into stories, increments, or features, which means earned value must be tied to accepted output, not effort spent.
That is the main challenge. Agile emphasizes working software and rapid feedback, while EVM asks for structured measurement against a baseline. Those two ideas can work together, but only if the team defines what counts as complete.
How to make Agile measurement practical
- Use accepted stories or increments as the basis for EV.
- Track milestones such as release readiness, integration completion, or approved testing.
- Define completion before sprint execution so teams know how earned value will be recognized.
- Use hybrid reporting when part of the project is plan-driven and part is iterative.
Hybrid projects often benefit the most from CPI and SPI because they combine formal planning with evolving delivery. A network upgrade, data migration, or enterprise application rollout may have fixed milestones at the top level and iterative task execution underneath.
For Agile or hybrid teams, the rule is consistency. If one sprint counts stories at acceptance and the next sprint counts them at development complete, the trend becomes unreliable. That same discipline is reflected in official guidance from Atlassian’s Agile resources and broader project controls practice, even when the delivery model is flexible.
How Do You Build a Reliable Reporting Routine for Project Tracking?
A reliable CPI and SPI routine turns project control from a monthly panic into an early-warning system. That only happens when the process is repeatable, validated, and understood by everyone who sees the report.
Set a recurring cadence, such as weekly or monthly, and use the same rules each time. The schedule should fit the project’s speed. A fast technical rollout may need weekly measurement, while a multi-year construction program may report monthly.
What a solid routine should include
- Validate the inputs. Confirm PV, EV, and AC before publishing the result.
- Document assumptions. Note how completion was measured and whether any exceptions were made.
- Track the trend. Compare the current period with prior periods, not just the last report.
- Communicate in business language. Sponsors need to know what the numbers mean, not just what the numbers are.
- Escalate early. Do not wait until the project is severely off track before raising a flag.
Good reporting makes CPI and SPI useful for decision-making. Bad reporting turns them into wallpaper. The difference is usually not the dashboard; it is the discipline behind the data.
For workforce and project management context, the BLS project management specialists profile is useful background on the role’s analytical nature, while structured project practice reinforces why recurring measurement matters in real delivery environments.
Key Takeaway
CPI and SPI are simple ratios, but they only work when your baseline is stable, your completion criteria are objective, and your costs are verified.
- CPI = EV / AC measures cost efficiency and shows whether spending is producing value.
- SPI = EV / PV measures schedule efficiency and shows whether work is being completed on time.
- Both metrics are unitless indices, so they should be interpreted as ratios, not dollars or days.
- Trend analysis is more useful than a single snapshot because it reveals whether the project is improving or slipping.
- Strong reporting depends on clean inputs, a controlled baseline, and consistent measurement rules across the project.
PMP® 8 – Project Management Professional (PMBOK® 8)
Discover essential project management skills to handle scope changes, make sound decisions under pressure, and lead successful projects with confidence.
Get this course on Udemy at the lowest price →Conclusion
If you need to calculate CPI and SPI for project tracking, the method is straightforward: use EV / AC for cost efficiency and EV / PV for schedule efficiency. The harder part is making sure the inputs are clean, the baseline is stable, and the measurement rules are applied consistently.
Used well, these metrics do more than report status. They help project managers spot drift early, forecast trouble sooner, and make better decisions before problems become expensive.
If you want to strengthen the project control skills behind these numbers, ITU Online IT Training’s PMP® 8 – Project Management Professional (PMBOK® 8) course is a practical place to build that discipline and connect earned value thinking to real project leadership.
PMI® and PMP® are registered marks of the Project Management Institute, Inc.
