Earned Value Management (EVM) — Complete Guide for Project Managers

Have you ever been in a project meeting where someone confidently says “we’re on track” — only to discover three months later that you’re 40% over budget and two months behind schedule? The deliverables looked done. The team was busy. The status reports said green. But something was fundamentally wrong with how performance was being measured.

This is precisely the problem that Earned Value Management (EVM) was designed to solve. EVM integrates scope, schedule, and cost into a single, coherent performance framework — giving project managers an objective, data-driven picture of where the project really stands.

In this guide you will find:

• What EVM is and why it matters for project managers
• The three foundational metrics: PV, EV, and AC
• Performance indexes (SPI and CPI) with a worked example
• Variance analysis: understanding CV and SV
• Forecasting formulas: EAC, ETC, and TCPI
• A step-by-step guide to implementing EVM on real projects
• How EVM applies in agile and hybrid environments
• The most common EVM mistakes — and how to avoid them
• A complete quick-reference formulas table

1. WHAT IS EARNED VALUE MANAGEMENT

Straight to the point

Earned Value Management is a project performance measurement methodology that integrates three critical dimensions — scope, schedule, and cost — into a unified framework. Rather than reporting cost and schedule separately (which often masks true project health), EVM ties cost performance directly to the work actually completed.

The core idea is simple but powerful: how much work was planned to be done, how much was actually done, and how much did it cost to do it? From these three questions, EVM generates a comprehensive set of metrics, indexes, and forecasts that tell the full story of project performance.

EVM originated in the United States Department of Defense in the 1960s as a cost and schedule control system for major defense contracts. Over the following decades it was adopted by industries ranging from construction and aerospace to IT and pharmaceuticals. Today, EVM is recognized in PMI’s PMBOK Guide, ISO 21508, and is a core competency for the PMP certification.

Why EVM is different from traditional reporting

Traditional project reporting typically answers two separate questions:

• “Are we on schedule?” — comparing planned vs. actual timelines
• “Are we on budget?” — comparing planned vs. actual costs

The problem is that these questions can give misleading answers. Imagine a project that has spent exactly what was budgeted at the midpoint. Sounds on track, right? But what if only 30% of the planned work has been completed? The project has spent 50% of its budget to deliver 30% of its scope — a serious performance problem that traditional budget tracking completely misses.

EVM catches this by introducing a third variable: the value of the work actually completed. This transforms performance reporting from a two-dimensional comparison into a three-dimensional analysis.

2. THE THREE KEY METRICS: PV, EV, AND AC

Every EVM analysis is built on three foundational metrics. Understanding these precisely is essential before moving to more advanced formulas.

Planned Value (PV)

Planned Value is the authorized budget assigned to the scheduled work — the amount of work that should have been completed by a given point in time, expressed in cost terms.

PV answers the question: “How much work did we plan to complete by now?”

PV is derived directly from the project’s cost baseline. At any given status date, PV equals the cumulative budgeted cost of all work scheduled to be completed up to that date. At project completion, PV equals the total Budget at Completion (BAC).

Key point: PV is time-dependent. It changes as you move through the project schedule.

Earned Value (EV)

Earned Value is the measure of work actually performed, expressed in terms of the authorized budget for that work.

EV answers the question: “How much work did we actually complete — and what was that work supposed to cost?”

EV is calculated by multiplying the percentage of work completed by the total budget (BAC) for that work package. This is the metric that makes EVM unique: it converts physical progress into monetary terms, making it directly comparable to cost data.

Key point: EV is the “currency” of EVM. It is the bridge between scope completion and cost performance.

Actual Cost (AC)

Actual Cost is the realized cost incurred for the work performed during a specific time period.

AC answers the question: “How much have we actually spent to complete the work done so far?”

AC includes all costs that have been incurred — labor, materials, equipment, overhead — to accomplish the work represented by EV.

Key point: AC is only meaningful when compared to EV. Spending $500,000 tells you nothing by itself. Knowing you spent $500,000 to complete work that should have cost $400,000 tells you everything.

Worked Example: The Software Dashboard Project

To make these concepts concrete, let us work through a consistent example that we will build on throughout this guide.

Project: Software Dashboard Development
Total Budget (BAC): $200,000
Planned Duration: 10 months
Status Date: End of Month 5

Project breakdown (simplified):

• Module A — Requirements & Design: $40,000 (months 1–2)
• Module B — Backend Development: $60,000 (months 2–5)
• Module C — Frontend Development: $50,000 (months 3–6)
• Module D — Testing & QA: $30,000 (months 6–8)
• Module E — Deployment & Training: $20,000 (months 9–10)

At Month 5:

• Module A: 100% complete (on schedule)
• Module B: 100% complete (on schedule)
• Module C: 60% complete (planned: 80%)
• Modules D & E: not started (on schedule)

Calculating PV at Month 5:
Modules A and B should be 100% complete: $40,000 + $60,000 = $100,000
Module C should be 80% complete: 0.80 × $50,000 = $40,000
PV = $140,000

Calculating EV at Month 5:
Module A: 100% × $40,000 = $40,000
Module B: 100% × $60,000 = $60,000
Module C: 60% × $50,000 = $30,000
EV = $130,000

Actual Cost (AC) at Month 5:
The project has actually spent: AC = $148,000

Now we have our three key numbers: PV = $140,000 | EV = $130,000 | AC = $148,000

3. PERFORMANCE INDEXES: SPI AND CPI

With PV, EV, and AC established, we can calculate performance indexes — dimensionless ratios that instantly communicate how efficiently the project is using time and money.

Schedule Performance Index (SPI)

Formula: SPI = EV / PV

SPI measures schedule efficiency: for every unit of time scheduled, how much work is actually getting done?

Worked Example:
SPI = EV / PV = $130,000 / $140,000 = 0.93

An SPI of 0.93 means the project is getting $0.93 of work done for every $1.00 of work that was scheduled. The project is 7% behind schedule in terms of work completion.

Cost Performance Index (CPI)

Formula: CPI = EV / AC

CPI measures cost efficiency: for every dollar spent, how much value (work) is being generated?

Worked Example:
CPI = EV / AC = $130,000 / $148,000 = 0.878

A CPI of 0.878 means the project is getting only $0.878 of value for every $1.00 spent. The project is over budget by approximately 12%.

Why CPI matters more than raw spend: Without EVM, the project looks like it is spending on track ($148K vs $140K planned — only 5.7% over). But when we compare spend to work actually accomplished, the picture is much worse: the project has spent $148K to complete work worth only $130K. That is a $18,000 efficiency gap that will compound over the remaining five months.

Combined SPI/CPI Analysis

Looking at both indexes together gives a richer picture:

Our dashboard project falls in the bottom-left quadrant: SPI 0.93 (behind schedule) and CPI 0.878 (over budget). This requires immediate investigation and corrective action.

4. VARIANCE ANALYSIS: SV AND CV

While indexes are great for quick health checks, variance figures tell you the absolute dollar (or time) gap between plan and reality. They are essential for communicating with stakeholders who think in budget terms rather than ratios.

Schedule Variance (SV)

Formula: SV = EV − PV

SV expresses schedule performance in monetary terms — specifically, the dollar value of work that is ahead of or behind the schedule.

• SV = 0: On schedule
• SV > 0 (positive): Ahead of schedule
• SV < 0 (negative): Behind schedule

Worked Example:
SV = EV − PV = $130,000 − $140,000 = −$10,000

The project is behind schedule by $10,000 worth of work. In practical terms: at current performance rates, about $10,000 of planned work has not been completed yet.

Important limitation: SV always converges to zero at project completion (because EV will eventually equal BAC = PV at completion), even if the project finished late. This means SV is not a reliable indicator of schedule performance in the final phases of a project. For late-phase schedule analysis, use SPI or time-based metrics.

Cost Variance (CV)

Formula: CV = EV − AC

CV expresses cost performance in dollar terms — the difference between what work was budgeted to cost and what it actually cost.

• CV = 0: On budget
• CV > 0 (positive): Under budget
• CV < 0 (negative): Over budget

Worked Example:
CV = EV − AC = $130,000 − $148,000 = −$18,000

The project has overspent by $18,000 relative to the work completed. This is the clearest signal that costs are running higher than planned.

Variance at Completion (VAC)

Formula: VAC = BAC − EAC

VAC projects the total cost variance at project completion. A negative VAC indicates the project is expected to finish over budget. We will cover EAC in the next section, but note that VAC connects variance analysis to forecasting.

5. FORECASTING: EAC, ETC, AND TCPI

One of EVM’s most powerful capabilities is forecasting — using current performance data to predict where the project will end up. This transforms EVM from a rear-view mirror into a forward-looking management tool.

Estimate at Completion (EAC)

EAC is the expected total cost of completing the project based on current performance. There are three main formulas, each based on different assumptions about future performance:

EAC Formula 1: Future work performed at current CPI (most common)
EAC = BAC / CPI

Use this when: current cost efficiency is expected to continue for the remainder of the project.

EAC Formula 2: Future work performed at planned rate
EAC = AC + (BAC − EV)

Use this when: the current variance was a one-time event and future work will be performed at the original budgeted rate.

EAC Formula 3: Future work at a new estimate
EAC = AC + ETC

Use this when: the original estimate is fundamentally flawed and a new bottom-up estimate is prepared for remaining work.

EAC Formula 4: Composite (using both CPI and SPI)
EAC = AC + [(BAC − EV) / (CPI × SPI)]

Use this when: both cost and schedule performance are expected to influence future outcomes (common in schedule-constrained projects with resource cost implications).

Worked Examples:

EAC₁ = BAC / CPI = $200,000 / 0.878 = $227,800 (if current inefficiency continues)
EAC₂ = AC + (BAC − EV) = $148,000 + ($200,000 − $130,000) = $218,000 (if future work is at planned rate)
EAC₄ = $148,000 + [($200,000 − $130,000) / (0.878 × 0.93)] = $148,000 + [$70,000 / 0.817] = $148,000 + $85,678 = $233,678

The range of $218,000 to $233,678 represents the realistic cost envelope for project completion, compared to the original $200,000 budget.

Estimate to Complete (ETC)

ETC = EAC − AC

ETC is the expected cost to complete the remaining work — the amount you still need to spend from today to project close.

Worked Example (using EAC₁):
ETC = EAC − AC = $227,800 − $148,000 = $79,800

This tells management: you have already spent $148,000 and you need approximately $79,800 more to complete the project. Compare this to the $52,000 originally remaining in the budget ($200,000 − $148,000) and the magnitude of the problem becomes clear.

To-Complete Performance Index (TCPI)

Formula: TCPI = (BAC − EV) / (BAC − AC)

TCPI is perhaps the most revealing EVM metric for forecasting. It tells you the cost efficiency you need to achieve on all remaining work to meet the original budget target.

Alternatively, to meet EAC instead of BAC:
TCPI = (BAC − EV) / (EAC − AC)

Worked Example (to meet original BAC):
TCPI = (BAC − EV) / (BAC − AC) = ($200,000 − $130,000) / ($200,000 − $148,000) = $70,000 / $52,000 = 1.346

A TCPI of 1.346 means the team would need to perform at 34.6% better cost efficiency than originally planned for the rest of the project to come in on budget. Given the current CPI of 0.878, this represents an extremely aggressive — and likely unrealistic — recovery target.

Practical rule of thumb: When TCPI to BAC exceeds 1.10, the original budget is effectively unachievable. The project manager should update the EAC, communicate the revised forecast, and focus TCPI calculations on meeting EAC instead of BAC.

TCPI to meet EAC₁:
TCPI = ($200,000 − $130,000) / ($227,800 − $148,000) = $70,000 / $79,800 = 0.877

This makes sense: to meet EAC₁, the project needs to continue performing at approximately its current CPI of 0.878 — which is exactly what EAC₁ assumes.

6. HOW TO APPLY EVM STEP BY STEP

Understanding EVM formulas is one thing. Implementing EVM on a real project is another. Here is a practical implementation guide.

Step 1 — Establish the Performance Measurement Baseline (PMB)

Before EVM can work, you need a reliable baseline that integrates scope, schedule, and cost. This means:

• A complete Work Breakdown Structure (WBS) that accounts for 100% of project scope
• A schedule that assigns time-phased work to each WBS element
• A cost baseline that assigns budgets to each work package
• A defined control account structure — the level at which EVM will be measured

The PMB is the foundation of everything. If your baseline is incomplete, unrealistic, or not formally approved, EVM metrics will produce misleading results.

Step 2 — Define Earning Rules for Each Work Package

An “earning rule” (or “earned value technique”) defines how EV is calculated for each work package as work progresses. Common techniques include:

• Percent complete: EV = % complete × Budget. Flexible but requires objective measurement.
• 0/100: EV = 0 until complete, then 100% of budget. Best for short tasks.
• 50/50: EV = 50% of budget when started, 100% when complete. Simple but less precise.
• Milestones with weighted values: EV credited at predefined milestone completion. Good for deliverable-based work.
• Apportioned effort: EV is a fixed ratio of another work package’s EV. For support activities.

Choose earning rules before the project starts and document them in the EVM plan. Changing earning rules mid-project distorts trend data.

Step 3 — Collect Performance Data at Regular Intervals

EVM requires disciplined data collection. Establish a regular reporting cadence (weekly or bi-weekly for most projects) and collect:

• Actual costs incurred (from accounting/timesheets)
• Physical progress for each work package (from team leads)
• Any changes to scope or schedule (from the change control log)

The quality of your EVM analysis is only as good as the accuracy of your progress reporting. Invest time in training team leads to report progress objectively, not optimistically.

Step 4 — Calculate EVM Metrics and Populate Dashboards

With PV, EV, and AC for each reporting period, calculate:

• SPI, CPI for performance trends
• SV, CV for absolute variances
• EAC, ETC for forecasting
• TCPI to assess recovery feasibility

Plot cumulative S-curves showing PV, EV, and AC over time. The visual gap between these curves is one of the most powerful communication tools available to a project manager.

Step 5 — Analyze Trends, Not Just Snapshots

A single period’s CPI or SPI can be distorted by unusual events. The real value of EVM comes from trend analysis:

• Is CPI improving, stable, or declining?
• Is the gap between EV and PV widening or closing?
• Are EAC forecasts trending up or stabilizing?

Research by Christensen (1999) found that CPI rarely improves significantly after the 20% completion point. If your project shows a CPI below 1.0 at the 20% milestone, treat it as a serious early warning signal.

Step 6 — Take Corrective Action and Update the Baseline if Needed

EVM is a tool for management, not just measurement. When variances exceed predefined thresholds (e.g., CPI below 0.9 or SPI below 0.85), initiate formal corrective action:

• Identify root causes of variance (scope creep, resource issues, estimation errors)
• Develop a recovery plan with specific actions and owners
• Update forecasts (EAC, ETC) to reflect the recovery plan
• If the original baseline is no longer achievable, establish a revised baseline through formal change control

Step 7 — Report to Stakeholders with Context

EVM numbers without context create anxiety. Always report EVM results with:

• A clear explanation of what the numbers mean in plain language
• The root causes of any significant variances
• The corrective actions in place and their expected impact
• The range of EAC forecasts (not just one number)

7. EVM IN AGILE AND HYBRID ENVIRONMENTS

Traditional EVM was designed for predictive, plan-driven projects with stable scope. Applying it in agile and hybrid environments requires adaptation — but the core principles remain valid and valuable.

EVM in Agile Projects

In agile environments, scope is defined as a backlog of user stories with story point estimates. EVM can be adapted as follows:

PV in agile: The cumulative story points (or business value) scheduled for completion by the current sprint, expressed in monetary terms using the project’s cost-per-story-point rate.

EV in agile: The cumulative story points actually completed and accepted (meeting the Definition of Done), expressed in monetary terms. Only stories meeting the Definition of Done earn value — partially complete stories earn zero.

AC in agile: Total cost incurred (sprint team costs, infrastructure, etc.) through the current sprint.

Agile EVM in practice:

• Velocity tracks story completion rate — the agile equivalent of SPI
• Burn-down and burn-up charts are visual EVM tools, though less rigorous
• CPI can still be calculated and used to forecast total cost
• EAC = AC + (Remaining story points × cost-per-story-point / CPI)

The key adaptation is that in agile, scope evolves. This means the baseline (PV) may be re-baselined at each release planning session, which requires care to maintain meaningful trend data.

EVM in Hybrid Projects

Hybrid projects that combine predictive phases (e.g., requirements, design, deployment) with agile sprints (e.g., development iterations) can apply EVM at the phase level:

• Predictive phases use traditional EVM with time-phased work packages
• Agile phases use story-point-based EVM with sprint-level reporting
• An integration layer aggregates both into a single project-level EVM dashboard

The integration challenge is ensuring that agile velocity data and traditional schedule data feed into a coherent EAC. This typically requires a master schedule that maps sprint deliverables to phase milestones.

EVM and SAFe (Scaled Agile Framework)

At the Program Increment (PI) level, SAFe naturally supports EVM. PI Planning establishes the planned work (PV), feature completion tracks EV, and actual team costs track AC. Many organizations implementing SAFe find that PI-level EVM provides the governance visibility that senior stakeholders require while preserving agile delivery autonomy at the team level.

8. COMMON EVM MISTAKES — AND HOW TO AVOID THEM

EVM is powerful but frequently misapplied. These are the most common mistakes practitioners make.

Mistake 1 — No baseline, no EVM

Why it happens: Teams start collecting AC and estimating progress without a formal, approved, integrated baseline. Without a valid PV baseline, EV calculations are meaningless and all downstream metrics are unreliable.

How to avoid it: Before collecting any EVM data, verify that you have an approved Performance Measurement Baseline that covers 100% of project scope. If the baseline is not yet approved, delay EVM reporting or report with an explicit caveat.

Mistake 2 — Optimistic progress reporting

Why it happens: Team members report 90% complete on tasks that are actually 50% complete, often to avoid negative attention or because they genuinely believe they are nearly done (the “90% complete” phenomenon). This inflates EV and hides real performance problems.

How to avoid it: Use objective earning rules (0/100, milestones, or measurable deliverables) rather than subjective percent-complete estimates wherever possible. Train teams to understand that honest reporting is more valuable than optimistic reporting.

Mistake 3 — Confusing AC with budget consumption

Why it happens: Project managers report “budget consumption” (how much of the budget has been spent) as a performance metric, without relating it to work accomplished. This is AC-only reporting — not EVM.

How to avoid it: Always report AC alongside EV. The ratio (CPI) is the performance indicator, not AC alone. Budget consumption tracking has its place, but it is not a substitute for EVM.

Mistake 4 — Using EVM only for compliance, not management

Why it happens: EVM is required by contract or by PMO policy, so the team generates the reports but nobody uses them for decisions. Metrics are calculated, filed, and ignored.

How to avoid it: Ensure that EVM reporting feeds directly into management decision-making. Set threshold triggers (e.g., CPI drops below 0.9) that automatically generate a required management response. EVM data should be visible on project dashboards, discussed in steering committee meetings, and used to justify resource adjustments.

Mistake 5 — Applying EVM at too granular a level

Why it happens: Teams create control accounts at the task level, generating hundreds of EVM data points. The volume of data becomes unmanageable, and the important signals get lost in noise.

How to avoid it: Apply EVM at the control account level — typically 2–3 levels below the WBS root, representing meaningful chunks of work (e.g., major deliverables or sub-phases). For a $5M project, you might have 15–25 control accounts. For a $50M project, 30–60 is typical.

Mistake 6 — Ignoring TCPI

Why it happens: TCPI is less intuitive than CPI and SPI, so it is often omitted from EVM reports. This means project managers miss the most powerful reality-check tool in the EVM toolkit.

How to avoid it: Always calculate TCPI to BAC as part of your standard EVM report. If it exceeds 1.10 at any point, explicitly communicate to management that the original budget is at risk and that the current EAC should replace the BAC as the target.

9. QUICK-REFERENCE FORMULAS TABLE

CONCLUSION

Earned Value Management is one of the most rigorous and powerful tools in the project manager’s toolkit. By integrating scope, schedule, and cost into a single measurement framework, EVM replaces the dangerous illusion of “on track” with an objective, data-driven picture of project health.

The three essential takeaways for practice:

• EVM requires a solid baseline. Without an approved, integrated Performance Measurement Baseline, all EVM metrics are meaningless. Invest the time to build a credible PMB before the project begins.
• CPI is your most important early warning signal. Research consistently shows that CPI stabilizes early in the project lifecycle. If your CPI drops below 0.9 by the 20% completion point, treat it as a serious project-level risk, not a variance to be explained away.
• EVM is for management, not compliance. The value of EVM is realized only when its outputs drive decisions. Integrate EVM metrics into steering committee agendas, resource allocation reviews, and change control processes.

The project manager who masters EVM does not just track projects — they predict the future with evidence. They walk into sponsor meetings not with optimism but with data. They make corrective decisions weeks before problems become crises. And when they say “the project is on track,” everyone in the room can trust that claim.

This Earned Value Management guide covers everything you need to know. See all PMBOK 8 articles in the Complete Index

Call to Action:

References

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Eighth Edition. Newtown Square, Pennsylvania, USA: Project Management Institute, 2025.

PMBOK Guide 8: The New Era of Value-Based Project Management. Available at: https://projectmanagement.com.br/pmbok-guide-8/

Disclaimer

This article is an independent educational interpretation of the PMBOK® Guide – Eighth Edition, developed for informational purposes by ProjectManagement.com.br. It does not reproduce or redistribute proprietary PMI content. All trademarks, including PMI, PMBOK, and Project Management Institute, are the property of the Project Management Institute, Inc. For access to the complete and official content, purchase the guide from Amazon or download it for free at https://www.pmi.org/standards/pmbok if you are a PMI member.