Budget Variance Calculator
Calculate budget variance as a percentage by comparing actual spending against planned budget. Use it for project cost control, financial reporting, and identifying overrun risk early enough to take corrective action.
Last updated: May 2026
Compare with similar
About this calculator
The calculator returns budget variance as a percentage of planned budget. The formula is: Budget Variance (%) = ((Actual Spent − Planned Budget) / Planned Budget) × 100. Variables: Planned Budget is the originally approved budget for the period or project; Actual Spent is cumulative actual expenditure to date. Edge cases: positive variance indicates overrun (spending more than planned); negative variance indicates underrun (spending less than planned). Variance alone is not diagnostic without context — a project that is 50% complete but has spent 75% of budget has a 50% positive variance, but the more important number is the projected total at completion (EAC — Estimate At Completion), which may show 150% spending if the current trend continues. Modern earned-value management (EVM) provides a richer framework: Cost Performance Index (CPI) = Earned Value / Actual Cost, where CPI > 1 means good cost performance, CPI < 1 means overrun. EVM also tracks Schedule Performance Index (SPI) for time. Industry guidance: variance under 5% is normal noise (no action needed); 5–10% deserves a check-in (verify cause is understood, project is on track); 10–20% triggers serious management attention (root cause analysis, recovery plan, possibly stakeholder communication); >20% requires escalation, scope/timeline renegotiation, or stop-and-reassess. Healthy projects forecast continuously, not just compare to original budget; the original budget often reflects early-stage assumptions that should be revised as work progresses.
How to use
Example 1 — Project running slightly over. Planned budget $150,000, actual spent to date $162,000. Step 1: variance = (162,000 − 150,000) / 150,000 × 100 = 12,000 / 150,000 × 100 = 8%. Verify ✓. An 8% positive variance is meaningful but not yet critical — warrants management attention and root-cause analysis, but does not necessarily require escalation if the project is approaching completion and the overrun is well-understood (e.g., scope additions, vendor cost changes). Example 2 — Project significantly underspending. Planned budget $400,000, actual spent $290,000 at 70% completion. Step 1: variance = (290,000 − 400,000) / 400,000 × 100 = −110,000 / 400,000 × 100 = −27.5%. Verify ✓. A 27.5% underrun looks great superficially, but the more important question is WHY: (a) Team is more efficient than planned (good), (b) Scope was cut without rebaseline (review needed), (c) Work is delayed and spending will catch up (concerning — late spending often comes with overruns), (d) Original budget was padded with hidden reserve (rebaseline at lower number). Negative variance always requires the same investigation as positive variance.
Frequently asked questions
What does the variance percentage actually tell me?
It tells you the percentage by which actual spending differs from planned — but NOT whether the project is healthy. Variance is a snapshot at a moment in time; what matters is the projected variance at project completion (EAC vs BAC). A project at 50% completion with 8% positive variance may project to 16% over at completion if the trend continues. A project at 95% completion with 12% positive variance may finish nearly on-budget because remaining spend is small. Pair variance with: (1) Percent complete — variance early in a project is less alarming than the same variance late; (2) Trend over time — improving or worsening; (3) Earned value metrics (CPI, SPI) — variance alone doesn't capture work completed; (4) Root cause — scope additions, vendor changes, productivity issues all need different responses. Treat variance as a leading indicator that triggers investigation, not as a stand-alone judgment about project health.
What is the difference between variance and earned value analysis?
Budget variance compares actual spending to plan — but treats all spending as equivalent, which can be misleading. A project that spent 50% of budget might have completed 70% of work (good) or 30% of work (bad). Earned Value Management (EVM) distinguishes these by tracking three metrics: Planned Value (PV — work that should have been done by now per the schedule), Earned Value (EV — work actually completed, measured in budget-equivalent dollars), and Actual Cost (AC — actual spending). Then: Cost Variance (CV) = EV − AC (negative is bad); Schedule Variance (SV) = EV − PV (negative is bad); Cost Performance Index (CPI) = EV / AC (>1 is good); Schedule Performance Index (SPI) = EV / PV (>1 is good). Estimate At Completion (EAC) = Budget At Completion / CPI gives projected total cost if current performance continues. EVM is the standard framework for government, defense, aerospace, and large construction projects; it requires more measurement discipline than simple variance but gives much earlier and more accurate warning of trouble. Simple variance treats spending = progress, which is often wrong.
What are the most common mistakes when interpreting budget variance?
The biggest is treating variance as a leading indicator without considering progress — if spending pace mirrors work pace, variance is normal; if spending outpaces work, variance is warning of overrun. The second is comparing actual to ORIGINAL budget after scope changes — when scope is added or changed, the comparison baseline should also change (rebaseline) to maintain meaningful variance tracking. Many projects show 'overruns' that are actually scope additions never re-baselined. The third is not tracking variance over time; a single snapshot is much less informative than trends — is variance growing or shrinking? Is the rate of growth accelerating? The fourth is failing to investigate negative variance (underspending); it often indicates delays or scope reduction that will catch up later, not genuine efficiency. The fifth is reporting variance without action — variance metrics are useful only if they trigger investigation and corrective action when needed; tracking that no one acts on is busywork. The sixth is using variance alone for performance evaluation; it doesn't capture quality, scope completed, or downstream value created.
When should I NOT use budget variance as the primary metric?
Skip variance as the primary metric for projects with significant scope evolution — agile, R&D, exploratory projects where scope inherently changes during execution; variance against original budget becomes meaningless. Use earned-value metrics or velocity-based forecasting instead. Avoid variance for very early-stage projects where the baseline budget is itself highly uncertain; small percentage variances on uncertain baselines are noise. Do not use it for fixed-price contracts where the budget is locked but actual cost flows to the contractor; the relevant variance is at the contractor's level, not the buyer's. Skip variance for highly stochastic projects (research with binary outcomes — drug development, exploration drilling) where the relevant metric is decision quality at each stage gate, not cumulative spend. Do not rely on variance alone for senior stakeholder communication; pair with forecasted completion cost (EAC), scope status, schedule, and risk indicators for a complete picture.
How early can budget variance predict project overrun?
Cost Performance Index (CPI), the EVM equivalent of variance, has been shown by extensive research (DoD studies, Christensen 1994, Lipke 2003) to be a remarkably reliable predictor: once a project is 15–20% complete, the final CPI typically stays within 10% of the CPI at 20% complete. This means EAC projections from early stage are surprisingly accurate, contrary to optimism that the team 'will catch up.' Simple budget variance has similar predictive power if interpreted correctly: a project 20% complete that has spent 25% of budget is on track for 25% overrun at completion if the trend continues. This is why mature project management acts on negative cost performance early — by mid-project, recovery requires either large scope cuts or stakeholder communication about overrun. Studies show that 'we'll catch up' rarely materializes; most projects that are 20% over budget at midpoint finish at 20%+ over. Early action (descope, replan, escalate) when CPI < 0.95 typically delivers much better outcomes than waiting and hoping.