What Is Budget Variance?
Budget variance is the difference between the amount you planned to spend and the amount you actually spent. It is one of the most fundamental project management metrics, used across industries to measure financial performance against plan.
The formula is: Budget Variance = Budgeted Amount - Actual Amount
A positive result means you are under budget (favorable). A negative result means you are over budget (unfavorable). To express the variance as a percentage:
Budget Variance (%) = (Budgeted Amount - Actual Amount) / Budgeted Amount x 100
A construction firm budgets $2,000,000 for a commercial build-out. Actual costs come in at $2,140,000. The budget variance is $2,000,000 - $2,140,000 = -$140,000, or -7%. This is an unfavorable variance that would trigger a review under most project governance frameworks.
Budget Variance Benchmarks
Acceptable budget variance depends on industry, project type, and organizational standards. PMI's PMBOK Guide recommends setting variance thresholds during project planning and defining specific responses for each level.
Budget Variance Thresholds
| Variance Range | Status | Interpretation | Recommended Action |
|---|---|---|---|
| 0% to +5% | Favorable | Under budget, within normal range. | Continue monitoring. Verify scope is being delivered. |
| -1% to -5% | Acceptable | Slight overrun, within tolerance. | Investigate root cause. Document in status report. |
| -5% to -10% | Warning | Meaningful overrun requiring attention. | Conduct variance analysis. Present corrective plan to sponsor. |
| -10% to -20% | Critical | Significant overrun threatening project viability. | Escalate to steering committee. Implement cost recovery plan. |
| Below -20% | Severe | Major overrun. Project may need restructuring. | Formal review. Consider scope reduction or project pause. |
| Above +10% | Review | Significantly under budget. | Verify quality and scope. Check for deferred costs. |
Typical Budget Overruns by Industry
| Industry | Average Cost Overrun | Projects On Budget |
|---|---|---|
| IT / Software Development | 45% | 31% |
| Construction | 16% | 39% |
| Manufacturing | 12% | 47% |
| Government / Public Sector | 27% | 28% |
| Healthcare | 18% | 36% |
Source: PMI Learning Library. Industry averages vary by project size, complexity, and methodology.
How to Calculate Budget Variance
Budget variance calculation requires two inputs: the approved budget and the actual cost. Both should cover the same scope and time period.
Dollar Variance = Budgeted Amount - Actual Amount
Percentage Variance = (Budgeted Amount - Actual Amount) / Budgeted Amount x 100
Worked example: A software development project has a total approved budget of $750,000. After six months, the team has spent $412,000 against a planned spend of $380,000 for the same period.
- Dollar Variance = $380,000 - $412,000 = -$32,000 (unfavorable)
- Percentage Variance = (-$32,000 / $380,000) x 100 = -8.4%
- Status: Warning zone. Investigate root cause and present corrective plan.
When calculating variance, always compare the planned spend for work completed (not total project budget) against actual spend for the same work. Comparing actual-to-date against the total project budget understates the problem because you are comparing partial spend to the full plan.
Types of Budget Variance
Budget variance can be broken into components to pinpoint where overruns originate. The two primary types are rate variance and quantity variance.
Rate Variance (Price Variance) measures the difference between the planned cost per unit and the actual cost per unit. If you budgeted $150/hour for a senior developer but the actual rate is $175/hour, the rate variance is -$25/hour unfavorable.
Quantity Variance (Usage Variance) measures the difference between planned quantity and actual quantity consumed. If you budgeted 200 developer hours but the work took 260 hours, the quantity variance is 60 hours unfavorable.
| Variance Type | Formula | What It Reveals |
|---|---|---|
| Rate (Price) Variance | (Budgeted Rate - Actual Rate) x Actual Quantity | Were inputs more or less expensive than planned? |
| Quantity (Usage) Variance | (Budgeted Quantity - Actual Quantity) x Budgeted Rate | Did you use more or fewer inputs than planned? |
| Total Budget Variance | Rate Variance + Quantity Variance | Combined financial impact of price and usage differences. |
Example: A marketing agency budgets a campaign at 100 hours x $120/hour = $12,000. Actual results are 115 hours x $130/hour = $14,950.
- Rate Variance = ($120 - $130) x 115 = -$1,150 (unfavorable)
- Quantity Variance = (100 - 115) x $120 = -$1,800 (unfavorable)
- Total Variance = -$1,150 + (-$1,800) = -$2,950 (unfavorable, 24.6% over budget)
The quantity variance is larger, which tells the project manager that the bigger problem is scope or productivity, not pricing.
Why Budget Variance Matters
Budget variance is a leading indicator of project health. A project that consistently runs 3-5% over budget each month will not self-correct. Without intervention, those small overruns compound into a major problem by project close.
It provides early warning. Tracking variance monthly lets you spot trends before they become crises. A project showing 2% unfavorable variance in month one and 4% in month two is accelerating in the wrong direction. Catching this at month two gives the team time to adjust. Catching it at month eight does not.
It drives accountability. When project teams know that variance is reviewed monthly, spending discipline improves. PMI research indicates that organizations with formal variance tracking processes complete 28% more projects within budget compared to organizations without structured cost monitoring.
It informs future estimates. Historical variance data makes future budgets more accurate. If your IT projects consistently overrun by 15-20%, you can build that into risk reserves rather than being surprised each time. A construction firm that tracks variance by project type can produce estimates with plus or minus 5% accuracy after 20 completed projects.
It protects margin. For service businesses, budget variance directly impacts profitability. A consulting engagement budgeted at $200,000 that comes in at $230,000 has consumed margin that cannot be recovered. Tracking variance at the work-package level lets managers move resources before the overrun becomes a write-off.
How to Reduce Budget Overruns
Most budget overruns are preventable. The strategies below target the most common root causes identified in PMI research.
1. Improve initial estimates with historical data. The top cause of budget overruns is inaccurate estimates. Use data from past projects, not optimistic guesses. If your last five software projects averaged 35% over their initial estimates, your estimation process has a consistent bias. Adjust by applying a correction factor or using three-point estimation (optimistic, most likely, pessimistic).
2. Include contingency reserves. PMBOK recommends including a contingency reserve of 5-15% for identified risks and a management reserve of 5-10% for unknown risks. A $500,000 project should carry $25,000-$75,000 in contingency and $25,000-$50,000 in management reserve. Projects without reserves have no buffer when surprises occur.
3. Control scope creep with a change management process. Scope creep is the second leading cause of cost overruns. Every scope change should go through a formal change request that includes cost impact analysis. A "small" feature addition that costs $5,000 seems harmless, but ten such additions over a project add $50,000 to the budget.
4. Track variance at the work-package level. Total project variance can mask problems. A project that is 0% over budget overall might have one work package at +20% and another at -20%. The overrun is real, it is just being hidden by savings elsewhere. When those savings run out, the overrun surfaces with less time to fix it.
5. Conduct monthly earned value analysis. Budget variance alone tells you about spending. Earned value analysis tells you about spending relative to work completed. A project can be under budget simply because it is behind schedule and has not spent money on work it should have started. Pair budget variance with CPI and SPI for the full picture.
6. Renegotiate vendor contracts early. If a major vendor's costs are trending above contract rates, address it immediately. Waiting until the project is 80% complete gives you no negotiating power. At 20% complete, you can rebid the work, adjust scope, or negotiate volume discounts.
This calculator provides estimates for informational purposes only. It does not constitute financial or project management advice. Actual budget variance depends on your specific project conditions, contracts, and organizational standards. Consult your project controls or finance team for precise measurements.