TL;DR: Most EVM articles define the formulas and move on. This one shows IT company owners how earned value management works as a live budget control system, connecting each metric to a specific decision: when to reforecast, when to escalate, and when to cut scope. You'll leave with a framework you can apply to your next project this week.
What earned value management actually means
Earned value management (EVM) is a project control method that measures how much work you've actually completed against what you planned to spend and when you planned to finish it. Most teams track budget and schedule separately, which means you can be on budget but three weeks behind, or on schedule but burning through contingency fast. EVM collapses both signals into one, so you see the real picture at any point in the project.
The core idea is straightforward: every task in your project gets a dollar value assigned upfront. As work gets done, that value is "earned." Comparing earned value to actual costs tells you whether you're spending efficiently. Comparing it to planned value tells you whether you're on time. That's earned value analysis used in project management in its simplest form.
For EVM project budgeting, the practical benefit is early warning. A cost or schedule problem that's invisible in a status report shows up immediately in the numbers. The next section covers the six metrics that make this work.
Key metrics you need to run EVM
Six numbers drive every EVM conversation. Each one answers a specific question your budget review should be asking.
Planned Value (PV) is the authorized budget for work scheduled by a given date. Think of it as your baseline commitment: if you planned to complete 40% of a project by week six, PV is the dollar value of that 40%. You can visualize how PV builds over time by plotting your planned value over time on an S-curve.
Earned Value (EV) is the budget assigned to work actually completed. It answers "what did we get for what we spent?" not "how much did we spend?" That distinction matters because a team can burn through budget quickly while completing very little.
Actual Cost (AC) is straightforward: total spend to date. On its own, AC tells you nothing about whether that spend was efficient. It only becomes useful when you set it against EV.
Those three are your raw inputs. The next three are your decision signals.
Cost Performance Index (CPI) = EV ÷ AC. A CPI below 1.0 means you're spending more than the work is worth. A project running at CPI 0.85 is getting 85 cents of completed work for every dollar spent. The formulas behind each metric show how small CPI drops compound fast over a long project timeline.
Schedule Performance Index (SPI) = EV ÷ PV. Below 1.0 means you're behind. An SPI of 0.90 says you've completed 90% of the work you should have by now.
Estimate at Completion (EAC) projects total cost at finish, typically calculated as Budget at Completion ÷ CPI. It's the metric that turns today's performance data into a forward-looking budget number, which is where catching cost risk before it compounds becomes critical.
Treat these earned value management metrics as a decision system, not a reporting checklist. CPI and SPI tell you where you are. EAC tells you where you're headed.
How EVM differs from traditional project management
Traditional project management gives you two data points: what you planned and what you spent. EVM adds a third, what you actually accomplished, and that third number changes everything.
Here is how the two approaches compare across the dimensions that matter most for IT project budgeting:
Dimension | Status-report tracking | EVM |
|---|---|---|
Visibility | Progress is self-reported | Progress is tied to measurable work completed |
Timing of signals | Problems surface at milestones or budget exhaustion | CPI and SPI flag drift weekly, sometimes daily |
Budget control | Spending is tracked; value delivered is not | Actual Cost is always compared against Earned Value |
Forecast accuracy | Gut feel or simple burn rate | EAC uses real performance data to project final cost |
In practice, a team reporting "70% complete" on a status call might have spent 85% of the budget. EVM catches that gap immediately because the formulas behind each metric force you to quantify what was delivered, not just what was done.
Milestone-based tracking has the same blind spot. You know a phase closed; you do not know whether it closed efficiently. How earned value analysis works in practice shows why that distinction matters when a client asks for a revised budget estimate mid-project.
The shift from EVM vs traditional project management is not methodological preference. It is the difference between a lagging indicator and an early warning system.
How EVM helps you control project budgets
EVM project budgeting works because it replaces gut-feel status updates with a number that tells you, right now, whether your project is earning back the budget you've spent.
The key signal is the cost performance index (CPI): Earned Value divided by Actual Cost. A CPI below 1.0 means you're spending more than the work is worth. A CPI of 0.85 on a 40% complete infrastructure migration tells you the final cost will run roughly 18% over budget — before you've touched the remaining 60% of scope. That's the early warning traditional milestone tracking never gives you.
For client conversations, CPI gives you a defensible forecast rather than a revised estimate built on optimism. You can show how earned value analysis works in practice to a client and explain exactly why the number changed, not just that it did.
Corrective action also becomes specific. If CPI is slipping, you know whether to cut scope, add resource, or renegotiate the timeline — because the data separates cost variance from schedule variance. Pair that with catching cost risk before it compounds, and you're managing the budget forward, not explaining overruns after the fact.
How to implement EVM in your project in 5 steps
Implementing EVM starts before the first task is assigned. The groundwork you lay in week one determines whether your metrics mean anything in week eight.
Step 1: Set the performance measurement baseline (PMB)
Break your project into a work breakdown structure (WBS), assign a budget to each work package, and spread that budget across the schedule. This gives you your Planned Value (PV) curve. Plotting your planned value over time as an S-curve makes deviations visible at a glance. For an IT example: a 12-week software migration project with a $120,000 budget should have roughly $10,000 of PV scheduled per week, adjusted for when heavy lifting actually occurs.
Step 2: Measure Earned Value as work completes
At each reporting period, calculate how much of the authorized budget has been "earned" by completed work. If your migration is 40% complete, your Earned Value (EV) is $48,000, regardless of what you've spent. This separation of physical progress from spend is what makes EVM different from a simple budget tracker.
Step 3: Record Actual Cost
Pull your real spend for the same period from timesheets, invoices, and contractor bills. This is your Actual Cost (AC). No estimates. If AC is $55,000 when EV is $48,000, you already have a cost problem. The formulas behind each metric show exactly how to calculate each figure.
Step 4: Calculate CPI and SPI
Cost Performance Index (CPI) = EV / AC. Schedule Performance Index (SPI) = EV / PV. In the migration example: CPI = 48,000 / 55,000 = 0.87, meaning you're getting $0.87 of work for every dollar spent. SPI = 48,000 / 40,000 = 1.20, meaning you're ahead of schedule. Those two numbers together tell you the project is over budget but running fast, a specific diagnosis, not a vague "things are off." For a deeper look at how these feed decisions, see how earned value analysis works in practice.
Step 5: Revise the forecast and act
Use CPI to recalculate your Estimate at Completion (EAC): Budget at Completion / CPI. At 0.87, a $120,000 project now forecasts to $137,900. That number either triggers a scope conversation with the client or a resource reallocation internally. Either way, you're making a decision based on data, not instinct, before the budget is fully spent. For IT teams managing multiple concurrent projects, catching cost risk before it compounds at this stage is what separates recoverable overruns from write-offs.
Where to centralize your EVM data
Spreadsheets break down the moment you're running three or more projects simultaneously. Actuals live in one tab, task progress in another, and the performance measurement baseline in a third file someone updated two weeks ago. By the time you reconcile them, your CPI is stale and the forecast is guesswork.
A work management tool that connects time logs, task completion, and budget baselines in one place removes that lag. When you implement earned value management inside a connected system, how earned value analysis works in practice becomes visible in near real-time, not after a Friday afternoon data-merge. You spend less time assembling numbers and more time acting on them.
Common EVM mistakes and how to avoid them
Four mistakes show up repeatedly when IT teams first apply earned value management metrics to real projects.
Skipping the baseline: EVM project budgeting only works if your Performance Measurement Baseline is locked before work starts. Teams that adjust it mid-project are measuring against a moving target, which makes every metric meaningless.
Updating actuals too infrequently: Weekly at minimum. Monthly updates hide cost drift until it's too late to correct. The formulas behind each metric only produce useful signals when the inputs are current.
Ignoring SPI when CPI looks healthy: A CPI above 1.0 can mask a schedule slipping badly. Always read both together. How earned value analysis works in practice shows why treating them as a pair catches problems CPI alone won't surface.
Conflating EAC with the original budget: Estimate at Completion is a forecast, not a target. Treating them as the same number leads teams to stop corrective action too early.
Closing
Earned value management stops being theoretical the moment you tie it to real decisions: when to reforecast, when to escalate, and when to cut scope. The three core metrics—CPI, SPI, and EAC—turn your budget data into an early warning system that catches cost and schedule drift before they compound. The framework works because it forces you to measure what you actually delivered, not just what you spent or what you said you'd do. Start by building your performance measurement baseline this week: break your next project into work packages, assign budget to each one, and spread it across your schedule. Then log time and task completions as work moves forward. If you're managing this across a spreadsheet or manual exports, you're spending more time on the math than the decisions. Taro brings time logs, task completions, and budget baselines into one view, so your EVM metrics update in real time instead of living in a Friday afternoon export. Explore how Taro's project tracking features can turn your earned value data into actionable signals—start a free trial and see how your next project's budget picture changes when you have live CPI and SPI signals instead of waiting for status meetings.
FAQ
How does earned value management help with project budgeting?
EVM compares what you've actually completed against what you planned to spend and when you planned to finish, giving you one signal instead of two. A CPI below 1.0 tells you immediately whether you're on track financially, so you can reforecast or cut scope before overruns compound.
What are the key metrics used in earned value management?
Planned Value (PV) is your baseline budget by date; Earned Value (EV) is the budget assigned to completed work; Actual Cost (AC) is what you've spent. CPI (EV÷AC) and SPI (EV÷PV) flag drift; EAC projects your final cost using real performance data.
How does EVM differ from traditional project management methods?
Traditional tracking shows planned vs. spent. EVM adds a third signal: what you actually accomplished. This catches the gap between 70% reported complete and 85% budget burned, which milestone-based tracking misses entirely.
How do I implement earned value management in my project management framework?
Start by building your performance measurement baseline: break the project into work packages, assign budget to each, and spread it across the schedule. Then measure Earned Value as work completes, record Actual Cost from timesheets, and calculate CPI and SPI weekly.
What are the benefits of using earned value management in IT projects?
EVM replaces gut-feel status updates with early warning signals. You catch cost and schedule problems before they compound, give clients defensible forecasts instead of revised estimates, and make corrective action specific—cut scope, add resource, or renegotiate timeline with data backing each choice.
What is a good CPI score in earned value management?
A CPI of 1.0 or higher means you're earning at least a dollar of work for every dollar spent. Below 1.0 signals inefficiency; a CPI of 0.85 means your final cost will run roughly 18% over budget if performance holds steady.
Can you use EVM on agile or sprint-based projects?
Yes. Assign story points or budget to each user story, track Earned Value as stories move to done, and calculate CPI and SPI per sprint. The principle is the same: measure what you completed, not just what you did or spent.
Get tactical playbooks every Tueday
One email. 5-min read. Tactical reads for B2B operators who actually run the business.
Join 48,000+ B2B operators · Unsubscribe anytime
Elena Petrova is a Project Management Consultant & Agile Coach who has delivered complex multi-team projects for technology companies across Eastern Europe and the US. She writes about sprint design, team velocity, and the project discipline that consistently separates teams that ship on schedule from teams that are always one week away from done.