TL;DR: Most articles on the cost variance formula stop at the math. This one shows IT company owners what the result actually means for budget decisions, how to read positive and negative variances without second-guessing yourself, and how to act on the number inside a project tracking tool rather than leaving it buried in a spreadsheet.
What cost variance means in plain terms
Cost variance measures the gap between what you planned to spend and what you actually spent to produce a given amount of work. A positive number means you came in under budget; a negative number means you overspent. That single signal tells a project manager or accountant whether a budget is holding or slipping before the damage compounds.
The formula appears in two distinct contexts. In earned value management, cost variance is calculated as Earned Value (EV) minus Actual Cost (AC), where EV is the budgeted value of work completed and AC is what you actually paid to complete it. A CV of negative $4,000 does not just mean you overspent by $4,000 — it means you got $4,000 less value than the money you spent should have produced. In accounting, the same concept uses a different lens: standard cost minus actual cost, where standard cost is the pre-set benchmark for producing one unit or completing one task.
Both versions answer the same question from different angles. The sections ahead cover how each formula is calculated step by step, including when to use one over the other.
The cost variance formula and its two versions
Two formulas carry the "cost variance" label, and they live in different disciplines.
Project management version (PMI/PMBOK):
CV = EV − AC
Earned Value (EV) is the budgeted cost of work you have actually completed. Actual Cost (AC) is what you spent to complete it. A negative result means you spent more than the work was worth at budget rates. A positive result means you came in under. If EV is $40,000 and AC is $44,000, your CV is −$4,000. You are over budget by that amount, not by a percentage guess. For a deeper look at how EV fits into the broader measurement system, earned value management formulas explained for IT project managers covers the full set.
Accounting version (CIMA/standard costing):
CV = Standard Cost − Actual Cost
Here, Standard Cost is the pre-set cost your finance team assigned to a unit of output. Actual Cost is what production or delivery really cost. The sign convention flips: a positive result is favorable (you spent less than standard), a negative result is adverse.
Which version applies to you? If you are tracking a project against a schedule and scope baseline, use EV minus AC. If you are reconciling a cost center or production run against a fixed rate card, use the accounting variant. The cost variance calculation is the same arithmetic; the inputs come from different systems.
How earned value analysis works in practice explains when to apply each metric during a project review.
How to calculate cost variance in 5 steps
Before you run the formula, you need four clean inputs. Skipping the prep step is where most cost variance calculations go wrong, not the math itself.
Lock down your planned budget for the period. Pull the budget baseline for the specific phase or sprint you are measuring, not the total project budget. If you are doing a mid-sprint check on a $120,000 fixed-price software build, and that sprint covers 25% of the scope, your planned value (PV) for the period is $30,000.
Calculate earned value (EV). EV is the budgeted cost of work actually completed. If your team finished 20% of the total project scope by mid-sprint, EV = 20% × $120,000 = $24,000. This number tells you what the completed work was supposed to cost, not what you paid for it.
Record actual cost (AC). Pull your real spend for the same period from your accounting system or time-tracking tool. If you paid $27,000 in labor and tools during that sprint window, AC = $27,000. Use the same time boundary as your EV calculation or the comparison is meaningless.
Apply the formula. Cost variance in project management follows the PMI definition from the PMBOK Guide: CV = EV minus AC. Using the numbers above: CV = $24,000 minus $27,000 = negative $5,000. A negative result means you spent more than the completed work was worth. A positive result means you came in under budget for that scope.
Interpret the number in context. A CV of negative $5,000 on a $120,000 project is a 4% overrun at mid-sprint. That is worth a conversation, not a crisis. To understand whether the trend is accelerating, calculate the cost performance index (CPI = EV ÷ AC). Here, CPI = $24,000 ÷ $27,000 = 0.89. Anything below 1.0 means every dollar you spend is returning less than a dollar of completed work. If CPI stays below 0.9 for two consecutive sprints, you have a structural budget problem, not a timing blip.
The five steps work the same way whether you are tracking a single sprint or a full delivery phase. The discipline is in keeping EV, AC, and your time window consistent. If those three inputs are clean, earned value analysis gives you an honest read on project health before the overrun becomes unrecoverable.
A worked example from an IT project
Your IT firm wins a fixed-price contract: build a client portal for $50,000 over ten weeks. At the five-week mark, you run a mid-sprint check-in using earned value management formulas.
Here are the three inputs you pull from your project tracker:
Budget at Completion (BAC): $50,000
Percent complete (actual work done): 40%
Actual Cost (AC): $24,000 spent so far
Step 1: Calculate Earned Value (EV) EV = BAC × % complete = $50,000 × 0.40 = $20,000
Step 2: Apply the cost variance formula CV = EV − AC = $20,000 − $24,000 = −$4,000
You've earned $20,000 worth of work but spent $24,000 to get there. The project is $4,000 over budget at the halfway point.
What this number tells you
A negative $4,000 CV at week five on a $50,000 project is a 8% budget variance. That's not catastrophic, but it compounds. If the same burn rate continues, you'll finish roughly $8,000 over the fixed-price ceiling, absorbing that loss directly.
This is where earned value analysis earns its place. The raw CV number tells you you're over budget. The Cost Performance Index (CPI = EV ÷ AC = 0.83) tells you you're getting 83 cents of value for every dollar spent, which sharpens the forecast conversation with your client.
Tracking these inputs in one place matters. A single source of truth for project financials means your CV calculation reflects real data, not a spreadsheet someone updated last Tuesday.
How to read the result and decide what to do
Once you calculate CV, the number tells you one of three things.
Negative CV means actual costs have outrun earned value. Your project is over budget. A CV of negative $4,000 on a $40,000 build is a 10% overrun — manageable if you catch it at sprint three, serious if you catch it at sprint eight. Check your cost performance index (CPI = EV ÷ AC) alongside it. A CPI below 0.8 usually means the overrun is structural, not a one-sprint anomaly, and warrants a scope or budget conversation with the client.
Zero CV means earned value equals actual cost. You're on budget. No action required beyond keeping the current pace.
Positive CV means you've completed more work than the money spent so far would predict. That's a good sign, but worth a quick check: confirm the team hasn't deferred testing or documentation to hit short-term numbers.
A simple decision tree for cost variance in project management:
CV is negative and CPI < 0.9: escalate, reforecast, and review scope
CV is negative and CPI between 0.9 and 1.0: monitor weekly, identify the specific tasks driving overspend
CV is zero: maintain course
CV is positive: verify work quality, then document what's working
The accounting variant of budget variance (standard cost minus actual cost) follows the same sign logic: negative means over standard, positive means under. Same interpretation, different input set.
Track cost variance inside your project tool
Recalculating CV by hand every sprint is where the number stops being useful. By the time you've pulled actuals from your accounting tool, matched them against logged hours, and checked task completion in a separate sheet, the data is already a week old.
Taro centralizes the three inputs that drive cost variance in project management: planned budget per task, actual time logged, and percent complete. From those, it calculates earned value and actual cost continuously, so your CV updates as work moves, not after you rebuild the spreadsheet.
For teams running earned value management across multiple projects, that live number changes how you respond. A CV of negative $4,000 on Tuesday is still recoverable. The same number discovered on Friday during a sprint review often isn't.
Taro also connects to downstream planning. If your CV signals an overrun, you can pull the budget at completion forward and revise the forecast before the client asks.
The math stays the same. The lag disappears.
Frequently asked questions
What is the cost variance formula? CV = Earned Value (EV) minus Actual Cost (AC). In accounting, the variant flips to Standard Cost minus Actual Cost. Both measure budget deviation; the project management version ties to earned value analysis, while the accounting version benchmarks production efficiency.
What does a negative cost variance mean? You spent more than the work is worth at that point. A CV of negative $4,000 means you're over budget by $4,000 relative to progress, not just total spend.
How often should you run the cost variance calculation? Every sprint or billing cycle. Weekly is better for fixed-price contracts.
Where do the inputs come from? Budget, logged time, and task completion data. Earned value management formulas explained covers how to source each one accurately.
Closing
The cost variance formula works only when you treat it as a living metric, not a one-time calculation. Most IT teams run CV once at project end and wonder why they didn't catch budget drift earlier. The real power emerges when you calculate it every sprint across all active projects—that's when spending patterns become visible before they compound into unrecoverable overruns. Taro's budget tracking and risk prediction features keep your CV numbers surfaced and actionable without the manual spreadsheet overhead, so your team stays on top of cost health as work happens, not after it's done.
FAQ
How do I calculate cost variance in project management?
Use CV = EV − AC, where EV is the budgeted value of completed work and AC is what you actually spent. Pull both numbers for the same time period, subtract, and interpret the sign: negative means over budget, positive means under.
What is the cost variance formula in accounting?
CV = Standard Cost − Actual Cost. Standard Cost is your pre-set rate per unit; Actual Cost is real production spend. Here, positive is favorable (under budget), negative is adverse (over budget)—opposite of the project management sign convention.
Can you provide an example of the cost variance formula?
On a $50,000 fixed-price portal build, at week five you've completed 40% of scope (EV = $20,000) but spent $24,000 (AC). CV = $20,000 − $24,000 = −$4,000. You're $4,000 over budget at the halfway point.
How does the cost variance formula help in budgeting?
CV tells you whether your actual spend is tracking your plan before overruns compound. A negative CV early signals you to adjust scope, timeline, or resource allocation to stay within the fixed-price ceiling.
What does a negative cost variance mean for my project?
Negative CV means you spent more than the completed work was worth at budget rates. It's a clear overrun signal. Pair it with Cost Performance Index (CPI = EV ÷ AC) to determine if the trend is structural or temporary.
What is the difference between cost variance and schedule variance?
Cost variance measures spend versus value (CV = EV − AC); schedule variance measures work progress versus time (SV = EV − PV). Both use Earned Value but compare it to different baselines—cost or schedule.
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
Megan Foster is a Legal Operations Specialist & Contract Workflow Advisor who focuses on the often-overlooked gap between a closed deal and a signed contract. With experience in legal ops and document automation, she writes about streamlining approvals, reducing signature delays, and building contract workflows that make clients feel confident from day one