What is the difference between cost variance and profit variance

TL;DR: Most articles on cost variance hand you the formula and move on. This one draws a precise line between cost variance and profit variance, two metrics IT project managers routinely conflate, and shows how each one changes a budget decision. You'll leave knowing which number to reach for first, and what it tells you that the other one can't.

What cost variance actually measures

Cost variance measures how much you've spent versus how much work you've actually completed, at any point during a project. It's a core metric in earned value analysis, not a simple budget-vs-actual comparison.

The cost variance formula is:

CV = Earned Value (EV) minus Actual Cost (AC)

Earned Value is the budgeted cost of work you've completed. Actual Cost is what you paid to complete it. If you've finished $40,000 worth of planned work but spent $50,000 doing it, your CV is -$10,000.

That negative number matters more than most teams realize. It doesn't mean you've blown your total budget at completion. It means your completed work cost more than planned, which is a different and more precise problem. A project can be under total budget but still carry a negative CV if early deliverables ran over.

Positive CV means you delivered work for less than budgeted. Negative CV means you overspent on completed scope. Zero means you're tracking exactly to plan, which is rare in practice.

This is where cost variance in project management diverges from how most people use "variance" in accounting. Accounting variance compares actuals to a fixed budget line. CV compares actuals to earned progress, which makes it a leading signal, not a lagging one. That distinction becomes critical when you're separating execution problems from financial performance issues, which the next section covers directly.

Cost variance vs profit variance: the key difference

Cost variance and profit variance both measure a gap between what you expected and what happened. That's where the similarity ends.

Cost variance is a project execution metric. It tells you whether the work completed so far cost more or less than planned, using the formula CV = Earned Value minus Actual Cost. A negative CV means you overspent on completed work. It says nothing about whether the project is profitable.

Profit variance is a financial performance metric. It compares actual profit against budgeted profit, typically broken into components like selling price variance, volume variance, and cost variance. It lives on your P&L, not your project tracker. You'd use it to explain quarterly results to a board, not to flag a scope creep problem mid-sprint.

The confusion happens because cost variance feeds into profit variance. If your project runs a CV of negative $15,000 for three consecutive reporting periods, that overspend eventually shows up as a compressed margin in your profit variance. But by the time it hits the P&L, the window to correct it has closed.

For IT company owners, the practical rule is this: cost variance in accounting and project management is your early warning system. Profit variance is the post-mortem. Understanding how earned value analysis works in project management gives you the framework to act on CV data before it becomes a profit problem. For the full financial picture, pair it with a profit and loss statement.

How cost variance affects your project budget

A negative cost variance doesn't stay isolated. It compounds.

When your actual costs run ahead of earned value, the cost variance formula (EV minus AC) gives you a number — but that number is also a signal about where your project budget is heading. Left uncorrected, a small negative CV in week three becomes a forecast problem by week eight.

The clearest downstream effect shows up in your Estimate at Completion (EAC). Most project managers calculate EAC by dividing budget at completion by the cost performance index. A CPI below 1.0 — which any negative CV produces — inflates that EAC figure. A project with a $200,000 BAC and a CPI of 0.85 now forecasts a final cost closer to $235,000. That gap has to go somewhere: absorbed margin, a change order conversation with the client, or both.

Client billing is the part most teams delay addressing. Fixed-price contracts mean the cost overrun hits your margin directly. Time-and-materials contracts require documented justification before you can pass costs through.

Earned value analysis gives you the framework to catch this early. Acting on CV data weekly — not monthly — is what keeps the forecast recoverable.

Main causes of cost variance in projects

Five root causes account for most of the cost variance problems IT and construction project managers actually deal with.

• Inaccurate initial estimates are the most common. When scope isn't fully defined before budgeting, the baseline cost figures are guesses dressed up as numbers. A 20% estimate error at project start compounds into a significant negative CV by week eight.

• Scope creep is the second. Uncontrolled additions to deliverables, features, or site work consume budget that was never allocated. In IT projects especially, "small" feature requests stack up fast. Earned value analysis surfaces this early by comparing earned value against actual cost before the overrun becomes unrecoverable.

• Resource rate changes catch teams off guard when contract labor costs, material prices, or subcontractor rates shift after the budget at completion was set. In construction projects, material price volatility alone can swing cost variance by tens of thousands of dollars mid-project.

• Schedule delays drive indirect cost variance in project management because fixed overhead, equipment rental, and staff time keep accumulating against a frozen budget.

• Poor time tracking and billing gaps create a different problem: the cost variance looks fine on paper until an invoice reconciliation reveals hours that were worked but never logged. This is where cost variance data and your profit and loss picture start to diverge in ways that hurt client billing accuracy.

How to analyze and interpret cost variance in five steps

Five steps turn a raw cost variance number into a decision you can act on.

1. Calculate CV using the earned value formula. CV = Earned Value (EV) minus Actual Cost (AC). EV is the budgeted value of work you've actually completed; AC is what you spent to complete it. A negative result means you've spent more than the work is worth at this point in the project. If your team completed $80,000 worth of planned work but spent $95,000 doing it, CV = -$15,000. For a deeper look at how EV fits into broader project health tracking, earned value analysis in project management covers the full framework.

2. Express CV as a percentage of EV. A raw dollar figure is hard to compare across projects of different sizes. Divide CV by EV and multiply by 100. That -$15,000 on an $80,000 EV becomes -18.75%, which is a signal most project sponsors will treat as urgent.

3. Place the number in context. A single negative CV reading may reflect a one-time spike, a delayed invoice batch, or a genuine scope problem. Compare this period's CV against the previous two or three reporting periods. A trend that's worsening is a different conversation than a variance that's stabilizing.

4. Identify the root cause before deciding on a response. The previous section covered the most common causes: scope creep, inaccurate estimates, resource rate changes, and rework. Match the pattern of your variance to one of those before you act. Responding to a rate problem with a scope freeze wastes time.

5. Update the forecast, not just the record. Once you know the cause, revise your estimate to complete and recalculate your Budget at Completion. A cost variance that goes unaddressed in the forecast silently inflates your projected profit. If you're reporting project financials alongside a profit and loss statement, an unreconciled CV will distort both documents.

The goal isn't a clean variance report. It's a corrected plan.

Where to track cost variance without a spreadsheet

Spreadsheets calculate cost variance once, at the moment you update them. By the time you open the file, the number is already stale.

A dedicated project tracking tool solves this by pulling actuals from your time logs, invoices, and resource allocations continuously. Cost variance in project management becomes a live signal rather than a weekly chore.

Taro's analytics dashboards surface CV automatically alongside schedule variance and budget burn rate. When a project drifts negative, Taro flags it as a risk alert before the gap compounds, so you can act on the cause rather than the symptom.

Pair that with earned value analysis and your Budget at Completion baseline, and you have a complete picture: what you planned to spend, what you earned, and where the gap opened. No manual formula required.

Frequently asked questions about cost variance

What is cost variance? Cost variance measures the difference between your budgeted cost of work performed and the actual cost spent. A negative result means you've overspent; a positive result means you're under budget.

What is the cost variance formula? CV = Earned Value (EV) minus Actual Cost (AC). For a deeper walkthrough of each input, see how to calculate cost variance in project management.

How is cost variance different from profit variance? Cost variance isolates one input: what you spent versus what you planned to spend. Profit variance measures the full outcome: actual profit minus budgeted profit. Profit variance splits further into selling price variance, sales volume variance, and cost variance itself. Cost variance is a component of profit variance, not a synonym for it.

What does a negative cost variance mean? Your project has consumed more budget than the work completed justifies. The further negative it runs, the harder recovery becomes without scope or resource changes.

Is cost variance only used in project management? No. Accounting teams use it to compare standard costs against actual production costs. The formula and interpretation are the same; the context differs.

Closing

Cost variance and profit variance measure different problems at different times. Cost variance is your real-time execution signal—it tells you whether completed work cost more or less than planned, and it's actionable before the project ends. Profit variance is the financial retrospective that appears on your P&L after the damage is done. The teams that move fastest are the ones acting on cost variance weekly, not monthly, because small overruns compound into forecast problems fast. Start by calculating CV for your active projects this week. What does that number tell you about resource allocation or scope creep you haven't addressed yet?

FAQ