Start free
November 10, 202615 min read

Budget vs. Actual in Construction: How to Track and Fix Variance

Cost manager comparing construction budget and actuals

Budget vs. actual in construction means comparing what you planned to spend on a job with what you have really spent, cost code by cost code, and acting on the gap while there is still work left to change. The gap is called variance. Spent less than planned for the work done is favorable, spent more is unfavorable, and the useful part is finding out why while the phase is still active.

This guide shows how the budget differs from an estimate, how to calculate variance, how to set up the comparison so it tells you something, and what to do when a job drifts.

Designflow-build
designflow-build.com
See Project Costs in One System
DesignFlow Build brings project management, accounting, and field operations together, helping contractors track costs without switching between spreadsheets and separate tools.
Explore the platform

TL;DR

Table of Contents

Budget, estimate and actual: what each one means

These three words get mixed up, and the mix-up quietly ruins reports.

The estimate is built during preconstruction. According to a Purdue University text on construction project cost control, the estimate serves as the yardstick against which actual cost performance is measured. The same text notes that an inaccurate budget is useless for measuring cost performance, so the comparison is only as good as the number you start with.

The budget is the plan for spending. The estimate says what the work should cost. The budget says what you are allowed to spend and when. In practice, once a contract is signed, the detailed estimate is converted into the project budget, with each line mapped to a cost code.

The actual is what has really been incurred: labor hours at real wage rates, materials invoiced, subcontractor billings, equipment and other job costs. The Carnegie Mellon construction management textbook describes this flow: the original estimate becomes a project budget, expenses are recorded in job cost accounts, and each account is compared with the original estimate in its category. Individual job cost accounts are the basic unit of cost control.

Two more terms show up on a good report:

What belongs in the budget

A construction budget has two broad halves. A Columbia University guide to capital project budgets lists hard costs (direct trade costs, general conditions, general contractor overhead and profit, contingencies, hazardous materials and FF&E) and soft costs (consultant fees, project management fees, legal costs, land or building acquisition and debt service). It puts overall project contingency typically in the 5 percent range.

An Institute of Internal Auditors chapter presentation from January 2022 reports that hard costs typically make up 70 to 75 percent of total project cost and soft costs 25 to 30 percent.

Hard costs, soft costs and typical contingency shares

If you are a contractor rather than an owner, your budget will usually center on hard costs: labor, materials, equipment, subcontractors and general conditions. Owner-side soft costs matter mainly when you work for an owner and need to understand their budget limits.

How to calculate budget vs. actual variance

The basic formula is simple. Variance is the difference between what you budgeted and what you actually spent. The Carnegie Mellon text defines it exactly that way and adds that items with unusually large overruns deserve particular managerial attention.

Write it consistently so everyone on the team reads it the same way:

Variance = Budget − Actual (positive means under budget, negative means over)

Some teams use Actual − Budget instead. Either works as long as the report labels it and every job uses the same sign.

The catch: spending is not progress

A raw comparison of budget to dollars spent can mislead. If you have spent 60 percent of a cost code’s budget, that is great news at 70 percent complete and a problem at 40 percent complete. That is why earned value matters.

The Los Angeles Bureau of Engineering’s control and variance analysis manual explains the principle: if earned value is greater than expended value, the project is ahead of its actual expenditures, and if earned value is significantly less than expended value, the project may be in trouble and might not finish within its budget. It also stresses reviewing work progress to make sure it moves at the same pace as expenditures.

A worked example

Say you are installing ductwork under a $200,000 labor and material budget for that cost code. Your field team reports the work is 50 percent complete, and you have spent $120,000.

Measure Calculation Result
Earned value (budgeted cost of work done) $200,000 × 50% $100,000
Actual cost From job cost ledger $120,000
Cost variance $100,000 − $120,000 −$20,000 (over)
Cost performance index $100,000 ÷ $120,000 0.83
Projected cost at completion $200,000 ÷ 0.83 About $240,000

A plain budget-versus-spent view would show $120,000 of $200,000 used, which sounds comfortable. The earned value view shows you are heading for roughly a $40,000 overrun if nothing changes. The projection is a trend, not a prophecy, but it is exactly the early warning you want while the remaining hours can still be changed.

Compare by cost code, not just by job

The job total is the least useful number on the report. A project can look on budget in aggregate while individual trades run well over and savings elsewhere cover the overage. That hides the problem until the schedule or the final invoices expose it.

So build the comparison around cost codes:

  1. Standardize your cost codes before the job starts, and map each one to your general ledger so job costs flow into the books without re-keying.
  2. Break the estimate into those codes so every estimate line has a home in the budget.
  3. Record actuals against the same codes: timecards, vendor invoices, subcontractor pay applications and equipment charges.
  4. Add committed costs from subcontracts and purchase orders.
  5. Report on each code: original budget, approved changes, revised budget, committed, actual, variance and forecast to complete.

With that structure, the report answers real questions. Is framing labor overrunning? Are finish materials costing more than the estimate assumed? Is one phase dragging the whole job? Without codes, a budget-versus-actual report is a scoreboard. With them, it is a control system.

If your chart of accounts and cost codes are a mess, start there. Our guides on building a construction chart of accounts around job costing and a 30 to 60 day plan for cost codes and GL mapping walk through it.

Why actual costs differ from the budget

Variance is a symptom. To fix it, you need the cause, and research is fairly consistent about where causes start.

The Carnegie Mellon text adds the shop-floor view: overruns may come from lower than expected productivity, higher wage rates, higher material costs or other factors.

Controllable and uncontrollable variance

Sort every variance into one of two buckets before you react. Labor productivity, rework and unapproved scope are things you can still influence. A material price spike usually is not. The first bucket calls for field action. The second calls for a change order conversation, a re-forecast or a pricing adjustment on future bids.

How often to review budget vs. actual

The answer depends on job size and how fast costs move, but monthly alone is too slow. By the time a month-end report lands, the hours that caused an overrun are already spent.

Our recommended rhythm for contractors:

A phase flagged in week one still has remaining hours you can change. A phase flagged at closeout has only a lesson. For more on this, see our posts on job cost variance for PMs and accountants and a live job cost dashboard that ends monthly surprises.

What to do when a job runs over

Finding the variance is half the work. The response is the other half. This sequence works on most jobs:

  1. Find the root cause first. Pull the cost breakdown by trade and compare it line by line with the original estimate. Do not average the problem away.
  2. Separate real overruns from timing. Check whether invoices posted early, progress is unreported or committed costs are missing.
  3. Adjust scope or schedule where it is actually possible. Resequencing, resourcing a crew differently or value engineering a remaining scope item can recover margin.
  4. Freeze unapproved changes. Every change gets priced and approved in writing.
  5. Move to weekly cost tracking for the rest of the project.
  6. Update the forecast at completion using earned value or simple percent complete, and carry the corrected number into your WIP schedule.
  7. Communicate early. If more funding will be needed, the Los Angeles manual says the project manager should raise it with the program manager and be ready to explain what will be required. On private work, the equivalent is an early conversation with the owner.

Contingency is not a substitute for control

Carrying more contingency does not by itself keep a job on budget. Research from the Construction Industry Institute data cited in a target value design study found an average spent-budget ratio of 0.986 across 168 healthcare projects not using target value design, with a range from 0.584 to 1.702. The worst project was about 70 percent over. The same paper reports that target value design projects carried an average 3.5 percent construction contingency against 7.9 percent for the others, yet were less likely to go over budget. The takeaway for any contractor: process and visibility protect margin better than padding.

Why spreadsheets break down

Most budget-versus-actual pain comes from the same place: the budget lives in one file, the actuals in an accounting system, field hours on paper or in texts, and committed costs in someone’s inbox. Somebody then stitches them together at month end. By the time you read the report, it describes the past.

The fixes are structural:

That is the idea behind our posts on reliable job costing in 90 days and real-time budget tracking for construction projects. If you run engineering work, our guide to managing engineering project budgets accurately applies the same logic to professional services.

Perspective

We built DesignFlow Build because contractors kept telling us the same story: the numbers they needed to manage a job were scattered across Excel, an accounting package and a project tool, and nobody trusted the result until the month was closed.

Our view is that budget versus actual should not be a monthly report at all. It should be a live view that sits on top of the same data your field and accounting teams already enter. When the estimate, the cost codes, the timecards, the commitments and the general ledger live in one system, variance stops being something you reconstruct and becomes something you watch.

That is why our platform combines project management, accounting and field operations, and why we designed it for self-implementation in 2 to 4 weeks, without an army of consultants. Our AI-driven project management is designed to predict risks and support resource allocation, so a drifting cost code reaches the project manager while there is still something to fix.

Start with clean cost codes, a realistic budget and a weekly habit. Then let the software carry the arithmetic.

Keith

See budget vs. actual live in one system

If you are tired of stitching reports together, DesignFlow Build brings job costing by cost code, general ledger, AR/AP, certified payroll, WIP, estimating and field operations into one construction ERP. There is a free tier that offers core features, so you can start without a big commitment.

Designflow-build

Paid plans scale by seat. Pro is $100 per month per office user, and Field seats are $25 per month per user. Your field crews can enter time and progress from our mobile field app, and you can compare plans on the pricing page. Check that page for the current details of each plan.

If you are also working on estimating and scheduling, our AI blueprint takeoff and construction scheduling software feed the same budget you track against. Not sure of a term? The construction software glossary covers the basics.

A simple weekly routine you can start now

You do not need new software to improve this tomorrow. Try this on your largest active job:

  1. Export the budget by cost code with approved changes.
  2. Add actuals to date and open commitments.
  3. Ask the field for percent complete on each code with meaningful dollars.
  4. Calculate earned value, variance and a projected final cost for each.
  5. Sort by the biggest unfavorable variance and talk to the project manager about the top three.
  6. Write down the cause and the action, then check it again next week.

Do this for a month and you will see which codes keep surprising you. Those are the codes where your estimates need better assumptions, your field reporting needs tighter habits or your change control needs teeth. Our construction company financial waste checklist can help you spot other leaks while you are at it.

FAQ

What is the difference between an estimated budget and actual cost?

The estimate is what the work should cost, built before construction. The budget is the spending plan derived from it. Actual cost is what you really incur during the job. The estimate becomes the yardstick, and actuals are compared to it as costs are collected.

How do you calculate budget vs. actual variance?

Subtract actual cost from budget, and say clearly which sign means over or under. For a more honest read, compare actual cost to earned value, which is the budgeted cost of the work completed. If earned value is lower than actual cost, you are spending faster than you are producing.

What should a construction budget vs. actual report include?

For each cost code: original budget, approved changes, revised budget, committed costs, actual costs, variance and forecast to complete. Include percent complete so spending can be read against progress.

How often should I compare budget vs. actual on a job?

Weekly on active cost codes is a strong habit, with a complete report each month. The reason is simple: a cost code flagged early still has hours left to correct. One flagged at closeout does not.

Why do construction projects go over budget?

Common causes include poor scope definition, inaccurate estimates, design problems, unclear specifications and uncontrolled changes. Productivity, wage rates and material prices also move actual costs away from the estimate.

Sources