EVM Formulas and Metrics Explained

EVM formulas are not reporting tools – they are early-warning signals, and treating them as status deck data is why most teams act too late.

What Are EVM Formulas – and Why Do Most Teams Misuse Them?

EVM formulas are not reporting tools. They are early-warning signals. The mistake most project teams make is treating Cost Performance Index (CPI) and Schedule Performance Index (SPI) as data for the monthly status deck rather than as decision triggers. By the time those numbers appear in a PowerPoint, the window to intervene has usually closed.

The common assumption is that a CPI of 0.9 means the project is “roughly on track.” That assumption is wrong. A CPI of 0.9 means you are spending $1.00 to deliver $0.90 of planned value – and unless efficiency improves, your final cost will be roughly 11% above budget. On a $5M project, that is a $550,000 overrun hiding behind a single decimal.

EVM was formalised by the US Department of Defense in the 1960s and absorbed into PMI’s Project Management Body of Knowledge (PMBOK). For PMP certification candidates, EVM formulas account for a significant portion of the quantitative questions on the exam – which is why “EVM formulas PMP” ranks among the most searched EVM queries. But the formulas are only useful if teams act on what they show. Project cost overruns are not random – they follow predictable patterns that EVM is specifically designed to expose. Applied consistently, EVM is the mechanism to surface those patterns before they compound into irreversible overruns.

How Do You Calculate the Core EVM Metrics?

Every EVM formula derives from three baseline values – here is how each one works and what it signals.

EVM builds on three baseline values. Every formula derives from these three numbers.

EVM Base Metrics: PV, EV, and AC at a Glance

The three base metrics – and their legacy aliases used in government and PMI documentation – in one reference table.

Note on terminology: BCWP, BCWS, and ACWP are the original DoD and government contract terms still used in federal project reporting, PMI PMBOK documentation, and PMP exam questions. Modern PMI guidance uses PV, EV, and AC – both sets refer to identical values.

The table below covers every EVM formula you need – with the calculation, what a result above or below 1.0 signals, and the action threshold.

EVM Formula Quick Reference: All Calculations, Signals, and Thresholds

BAC = Budget at Completion (the original total approved budget for the project).

What Is the CPI Formula in EVM?

The CPI formula in EVM is: CPI = EV ÷ AC (Earned Value divided by Actual Cost). A CPI above 1.0 means the project is under budget – each dollar spent is delivering more than a dollar of planned value. A CPI below 1.0 means the project is over budget – each dollar spent is delivering less planned value than it costs.

CPI (Cost Performance Index) is the single most cited EVM formula because it answers the question every project sponsor asks first: “Are we spending what we planned to spend?” Unlike cost variance (CV = EV − AC), which gives an absolute dollar figure, CPI gives a ratio that works across projects of any size.

CPI Formula: Components and Calculation

CPI in EVM: Interpretation by Result

CPI Formula in EVM: Worked Example

A software project managed by James Okafor at Apex Digital at the 40% completion mark has the following data:

• EV (Earned Value / BCWP): $160,000
• AC (Actual Cost / ACWP): $200,000
• BAC (Budget at Completion): $400,000

CPI = EV ÷ AC = $160,000 ÷ $200,000 = 0.80

EAC = BAC ÷ CPI = $400,000 ÷ 0.80 = $500,000 (a $100,000 projected overrun)

A CPI of 0.80 means every dollar spent is only delivering 80 cents of planned value. At this rate, the $400,000 project will cost $500,000 to complete. And because CPI stabilises after the 20% completion mark, a CPI of 0.80 at 40% is not a temporary fluctuation – it is a structural signal.

Why CPI Is the Controlling Formula in EVM

CPI is not just a diagnostic metric – it is the controlling variable in cost forecasting. CPI is the denominator in EAC (Estimate at Completion = BAC ÷ CPI). A CPI improvement of 0.05 on a $5M project changes the EAC forecast by approximately $294,000. That is why weekly CPI tracking catches problems that monthly reporting misses.

CPI also feeds TCPI (To-Complete Performance Index = (BAC − EV) ÷ (BAC − AC)), which answers whether hitting the original budget is structurally realistic from today forward. When TCPI exceeds 1.1, it means the team would need to become 10% more efficient than their current rate – which almost never happens without a formal rebaseline or scope reduction.

Profit.co’s Project Portfolio Management platform calculates CPI automatically from live milestone and cost data, surfaces the result on the portfolio dashboard alongside SPI and TCPI, and flags projects where CPI drops below your defined threshold – without requiring manual formula entry.

What Do CPI and SPI Actually Tell You About Project Health?

CPI stabilises after 20% project completion – making it the most actionable early indicator you have.

CPI and SPI are the two metrics that matter most in practice. Every other EVM formula either depends on them or refines them. The critical insight is that CPI tends to be stable after the 20% completion mark – meaning the CPI you measure one-fifth of the way through a project is likely to stay within 0.10 of your final CPI. This is not a theory. Research published in the Project Management Journal confirms that CPI stabilises after approximately 20% project completion (Christensen, 1999 – still the canonical reference in PMI literature). That stability makes CPI the most actionable early indicator you have.

One nuance teams frequently miss: SPI loses predictive power as a project nears completion. Because SPI uses EV relative to PV, and PV eventually reaches BAC, SPI will converge toward 1.0 at project end regardless of whether the project delivered on time. For near-complete projects, use absolute Schedule Variance (SV) in days rather than SPI as a ratio.

For project management KPIs beyond EVM, CPI and SPI pair most usefully with resource utilisation rate, defect escape rate, and cycle time to give a complete picture of project execution health.

How Do You Use EAC and TCPI to Forecast Project Completion?

EAC answers how much the project will cost – TCPI answers whether hitting the budget is still realistic.

EAC answers the question every sponsor asks: “How much is this project going to cost?” The standard formula – EAC = BAC ÷ CPI – assumes current inefficiency continues at the same rate to project end. That is usually the most realistic assumption after the 20% mark.

TCPI is the less-discussed but arguably more useful companion. It answers: “What efficiency do we need to achieve from today forward to hit our budget?” A TCPI above 1.1 is a structural warning sign – it means the team would need to become significantly more efficient than they have been, which almost never happens without a scope reduction or rebaseline.

Worked Example

This example shows the EVM system working as designed: CPI of 0.80 triggers EAC, EAC reveals a $125k overrun, and TCPI of 1.20 immediately tells the project manager that hoping for recovery is not a plan. The decision – rebaseline, reduce scope, or escalate – has to be made now. See additional KPI examples by department for how financial performance metrics pair with project indicators across business units.

Profit.co surfaces CPI, SPI, TCPI, and EAC automatically on the portfolio dashboard at every review cycle – no manual data entry required. When TCPI rises above 1.1, the platform flags the programme for governance review before the next status meeting.

How Should EVM Metrics Connect to Your Strategic OKRs?

The structural blind spot between project performance and strategic goals – and how to close it.

This is where most organisations have a structural blind spot. EVM lives in the project management layer. OKRs live in the strategy layer. They run on separate cadences, in separate tools, reviewed by separate teams – and the connection between “this project is failing” and “this key result is now at risk” is never made until the quarterly review, when it is too late.

The fix is to treat EVM thresholds as OKR confidence triggers. Here is a concrete framework:

Most project management tools that support EVM reporting calculate CPI and SPI only when the team manually maintains baseline data and updates actual cost records. The calculation is not automated – it depends entirely on data entry discipline. And none of them connect EVM thresholds to strategic goals. When CPI drops below 0.8, the project tool flags the project, but the OKR platform tracking the key result that project is funding has no idea. The two systems run in parallel and never converge.

Profit.co’s project portfolio management platform closes that gap: CPI and SPI are calculated automatically from live milestone completion data, and when cost efficiency drops below your defined threshold, the linked key result is flagged in the same view. Strategy leaders see the risk before it appears in the monthly project report.

This matters because most strategic initiatives fail not because of poor strategy design, but because execution problems go undetected until the quarterly review. EVM provides the execution signal. OKRs provide the strategic context. Connecting the two closes the gap between “project is struggling” and “strategy leader knows about it.”

The OKR University covers how to structure key results so they can absorb project health signals – including how to write outcome-based key results that reflect delivery progress, not just effort.

Why Do Teams Track EVM Without Ever Acting on It?

Three structural reasons EVM adoption is higher than EVM action – and what changes each one.

EVM adoption is higher than EVM action. Teams collect the numbers, report the numbers, and then continue without changing course. The reasons are structural, not motivational.

1. Why Does Monthly EVM Reporting Miss the Intervention Window?

Monthly EVM reporting is standard. But CPI after the 20% completion mark is already predictive – every week you delay acting on a CPI of 0.82 is another week of compounding cost inefficiency. Teams that review EVM weekly and flag deviations above 0.05 catch problems while corrective action is still viable.

2. Why Do Teams Fail to Act When CPI Drops Below Threshold?

A CPI of 0.79 means nothing if nobody has pre-agreed what happens when CPI drops below 0.8. Escalation, rebaseline, scope reduction – these decisions should be codified in advance, not debated after the fact. Without a decision protocol, EVM data becomes reporting artefact rather than management input.

3. How Does the Separation Between PM Tools and OKR Platforms Create Strategic Blind Spots?

When EVM lives in the project management tool and OKRs live in a separate platform, nobody sees the connection between a failing project and an endangered key result. Strategy leaders set confidence scores based on conversations, not data. Project managers report to PMOs, not to strategy teams. The information that should bridge both layers never does.

The pattern is consistent across industries: teams have EVM data, but no pre-agreed protocol for what to do when a threshold is breached. That gap – between measurement and action – is where project overruns live. Use Profit.co’s ROI Calculator to quantify how much project overrun costs your organisation annually, and what connecting EVM to OKR confidence scoring would recover.