Cost Variance

Cost variance is the gap between what you planned to spend and what you actually spent — the simplest, most direct feedback a budget can give. In everyday budgeting, it is budgeted cost minus actual cost for a line item, a department, or a whole project. In earned value management (EVM), the discipline project managers use to track big programs, it has a precise form: cost variance equals earned value (the budgeted cost of the work actually completed) minus actual cost. Either way, the sign is what you read first. By common convention a favorable variance means you came in under budget and an unfavorable one means you went over, though teams differ on whether to write the over-run as a positive or negative number, so agree on the sign before you argue about the size.

Cost variance matters because it turns a budget from a wish into a control system. A plan that is never checked against reality is just a hope; a plan measured by its variance becomes a live signal. Track cost variance often enough and an overrun shows up while there is still time to renegotiate a supplier, cut scope, or re-plan — long before the final invoice makes the damage permanent. It also localizes the problem. A blended "we're over budget" tells you little, but cost variance broken out by task or cost category points straight at the line that is bleeding, which is where the fix has to happen. The number is only useful, though, if someone acts on it.

Cost variance has a twin in earned value management called schedule variance, and confusing them is a classic mistake. Cost variance compares the value of work done against what that work actually cost — it answers whether you are spending more or less than the work is worth. Schedule variance compares the value of work done against the value of work that was planned by now — it answers whether you are ahead of or behind the timeline. Cost variance is about money; schedule variance is about time. A project can be dead on budget yet badly behind schedule, or racing ahead of schedule while burning cash far faster than planned. Reading only one leaves half the picture dark.

The two together are more honest than either alone. Imagine a build that has completed exactly the work it should have by this date — schedule variance is zero — but has spent well over the earned value doing it, so cost variance is sharply unfavorable. The timeline looks fine while the budget is quietly failing, and a manager watching only the calendar would be blindsided at the end. Reverse it and a project can look expensive per week yet finish early and cheaply overall. Because cost variance and schedule variance can point in opposite directions, mature program tracking always shows both, usually alongside their index forms, so cost performance and timeline performance are judged on their own terms rather than blurred into a single reassuring or alarming number.

Use cost variance as an early-warning instrument, which means measuring it often and at the right grain. A variance calculated once, at the end, only confirms the damage; calculated weekly and broken out by task or cost category, it catches an overrun while it is small. Fix the sign convention and the baseline first — everyone must agree what budgeted means and whether favorable is positive — or the meetings dissolve into arguing about arithmetic. Pair it with schedule variance so you never mistake a timing problem for a cost problem, and investigate the causes behind a variance rather than just its size, because the same dollar overrun can come from a price rise, a scope change, or plain inefficiency, and each needs a different response.

The failures are watching cost variance too late to act, changing the baseline midstream so the variance loses meaning, and treating every unfavorable number as waste when some overruns reflect deliberate, sensible scope additions. A variance is a question, not a verdict — it tells you to look, not what you will find. Consider this a primer on the metric, not financial or accounting advice. Used well, cost variance keeps a budget honest and a project steerable, turning the plan into a running conversation with reality rather than a document filed away and compared to the outcome only when it is far too late to change anything.

Cost variance — actual cost measured against budgeted or earned cost — is the control signal that flags overruns, most precisely defined within earned value management as earned value minus actual cost.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where cost variance is a core concern: