How Enterprise Capital Programs Go Over Budget, and Where the Money Actually Leaks

Most capital overruns are not discovered. They're revealed.

The money left weeks or months before anyone reported it. A commitment was made that nobody tracked, a change was approved verbally and priced later, contingency was drawn down without anyone watching the rate. Then the monthly report catches up, the number moves, and a meeting gets scheduled to discuss what happened.

By then the question isn't what happened. It's what else is already gone that hasn't surfaced yet.

This piece is about the specific places capital money leaks during execution, and what closes each one. Not about estimating, which is a separate failure with separate causes.

Two different failures that both look like an overrun

Worth separating these, because they need different fixes and organizations routinely apply the wrong one.

The estimate was wrong. The project was never going to cost what the capital request said. Research on this is well established: optimism bias and strategic misrepresentation produce systematically low estimates, with documented average overruns around 45% on rail, 34% on bridges and tunnels and 20% on roads.

The estimate was reasonable and the money leaked anyway. Scope grew without anyone deciding it should. Commitments accumulated faster than they were tracked. Contingency disappeared into a hundred small approvals. Nobody saw the aggregate until it was reported.

The second one is what this article covers. It's the more common failure on institutional and corporate programs, and it's the more fixable one, because it's an information problem rather than a judgment problem.

The three-number problem

Almost every leak in this article traces back to the same structural gap.

Any capital project has three numbers running at once.

• Budget is what you approved. Stable, reported, well understood.
• Spent is what's been invoiced and paid. Also well understood, because accounting produces it.
• Committed is what you've contractually obligated but haven't been invoiced for yet. Executed subcontracts, purchase orders, approved change orders, long-lead equipment. The work hasn't happened, the invoice hasn't arrived, and the money is already gone.

Most organizations track budget and spent. Committed is the one that's frequently approximate, updated monthly, or living in a different system from the budget it consumes.

That gap is where exposure hides. A project can be forty percent spent and ninety percent committed, and if you're only watching spend, it looks like there's room. There isn't. You're just early in the invoicing cycle.

If you fix nothing else, fix this. Real-time committed cost against budget is the single most useful number in capital cost control and the one most frequently unavailable when someone asks.

Where the money actually leaks

• Commitment creep

What happens. Subcontracts get executed, purchase orders issued, equipment ordered. Each is authorized. None individually alarming. The cumulative committed position drifts past what the budget supports, and nobody sees it because commitments are tracked per contract rather than aggregated against the budget line they consume.

The fix. Commitments post against budget lines as they're executed, not at month-end. Anyone approving a commitment should see the remaining uncommitted balance on that line before signing, not after.

• Change orders approved before they're priced

What happens. Work has to proceed, so it's authorized verbally or by directive with pricing to follow. Reasonable in the moment and sometimes contractually correct. The problem is that unpriced authorized work is real exposure that doesn't appear in any number until it's negotiated, which can be months.

The fix. Track authorized-but-unpriced work as a distinct category with an estimated value attached, visible alongside committed costs. It's an estimate, and an estimate in the report beats a zero in the report.

• The cumulative change order blind spot

What happens. Change orders get evaluated individually. Each one is justified. Research from Dodge Data & Analytics puts change orders at roughly 10% of total contract value on average, with some projects reaching 25%. Large, complex projects average over eleven change orders. When each is approved on its own merits and nobody watches the running total against contingency, the aggregate arrives as a surprise.

The fix. Every change order approval shows cumulative change order value as a percentage of original contract and remaining contingency. Approvers should never be looking at one change in isolation.

• Contingency drawn down without a burn rate

What happens. Contingency gets used, appropriately, throughout the project. What's rarely tracked is the rate relative to completion. A project sixty percent complete with seventy-five percent of contingency consumed is in trouble, and that's visible in month five if anyone computes it. Usually nobody does until it's exhausted.

The fix. Report contingency remaining against percent complete as a standing metric, not contingency remaining in dollars. The ratio is the signal.

• Scope creep that never becomes a change order

What happens. The owner asks for something during a site walk. It's small. The contractor absorbs it or handles it informally. Ten of those, and the project has grown without a single change order documenting it. The cost surfaces later as a claim, a schedule impact, or a contractor whose margin has eroded and who becomes adversarial about everything else.

The fix. A rule that owner-requested changes go through the process regardless of size, with a fast lane for small ones. The goal isn't bureaucracy, it's that the aggregate is visible. Ten informal accommodations are invisible; ten small change orders are a pattern.

• Allowances and provisional sums treated as firm

What happens. The budget carries an allowance for something not yet defined. It's a placeholder. It gets reported alongside firm numbers in the same column, and after a few months everyone treats it as a real figure. Then the actual scope is defined and the allowance was low.

The fix. Allowances flagged distinctly in reporting, with the date they're expected to convert to firm pricing. An unconverted allowance late in a project is a risk item, not a budget line.

• Soft costs outside the tracked budget

What happens. The construction contract gets tracked rigorously. Design fees, permits, owner's rep fees, FF&E, IT and low voltage, commissioning, moving costs and internal labor either sit in a different system or aren't tracked with the same discipline. The construction number stays green and the capital project overruns.

The fix. The tracked budget is the approved capital budget, not the construction contract. If soft costs live elsewhere, they're a leak by definition, because nobody is watching them against the total.

• Escalation assumed away

What happens. A multi-year program prices in year one and doesn't model material and labor escalation across the program duration. Each project appears fine at approval. The later ones come in high and it reads as an execution failure rather than an indexing one.

The fix. Explicit escalation assumptions in multi-year program budgets, revisited annually. If a project is being priced against a three-year-old basis, that should be visible to whoever approves it.

• Funding source misattribution

What happens. A program draws on multiple sources, bonds, grants, general funds, donations, each with different eligibility and reporting rules. Spend gets charged to whichever source has room rather than the one that should carry it. Discovered at audit, and the remedy is expensive.

The fix. Source attribution at the point of commitment, not reconciled afterward. This is a system requirement rather than a discipline requirement, because manual attribution reliably drifts.

• Forecast at completion that never moves

What happens. Cost-to-complete is a forecast, and forecasts have authors. A project manager who reports a rising estimate at completion invites scrutiny, so the number often stays flat until it can't. The overrun was foreseeable for months and only became reportable at the end.

The fix. This is cultural more than procedural. Organizations where revising a forecast upward early is treated as good practice get earlier warning than organizations where it's treated as failure. Tracking forecast accuracy by project, rather than by person, helps separate the signal from the blame.

• Portfolio-level blind spots

What happens. Every project reports within tolerance. The program is over. This happens when each project holds a small variance that's individually acceptable and collectively significant, or when contingency is held at project level with no view of aggregate exposure.

The fix. Roll up variance and contingency position across the portfolio as a standing report. A program manager should be able to see total exposure without opening fifteen projects.

How it accumulates

Individually these look minor. Here's roughly how they compound on a project that never had a single dramatic problem.

A $40 million build. Approved budget includes $3 million contingency, about 7.5%.

Month four: three change orders totaling $180,000. All justified, all approved. Nobody notes that contingency is now at 94% with the project 15% complete.

Month seven: a design clarification adds scope worth perhaps $90,000. It's handled as a clarification rather than a change order because it's small and the contractor absorbs part of it. It doesn't appear anywhere.

Month nine: long-lead equipment is committed at $2.1 million against a budget line carrying $1.9 million. The purchase order is approved by someone who can see the PO but not the remaining balance on that line. The $200,000 variance won't be visible until invoices arrive in month fourteen.

Month eleven: an allowance for specialty finishes, carried at $400,000 since the original estimate, converts to a real number at $610,000.

Month thirteen: the owner's rep flags that FF&E, tracked in a separate system by a different department, is running roughly $250,000 above plan. Nobody had been reporting it against the capital budget.

Month fourteen: the PM revises estimate at completion for the first time in five months. The forecast moves $1.4 million.

Nothing here was mismanagement. Every individual decision was defensible. The project is now roughly $2.7 million over on a $3 million contingency, and the first time anyone saw it as a single number was month fourteen, when four of the five contributing items were already irreversible.

The pattern matters more than the arithmetic. Leaks don't arrive as one event, they surface as one event.

Your contract type decides which leaks you're exposed to

The eleven above aren't universal. Contract structure determines which ones are even possible, and reading your overrun pattern against your contract type tells you where the real problem sits.

• Lump sum. The contractor carries execution cost risk, so productivity losses and means-and-methods problems are theirs. Your exposure concentrates almost entirely in change orders and scope disputes, because that's the only mechanism through which cost reaches you. If you're seeing heavy change order volume driven by design gaps, the actual failure happened earlier: documents weren't complete enough at bid. That's a procurement timing problem, not a project management one, and no amount of change order discipline fixes it after the fact.
• Guaranteed maximum price. You see actual costs, which is genuine visibility, and you're protected above the cap. The exposure is in how the GMP got set. A GMP established at 60% design carries assumptions about the remaining 40%, and the gap between those assumptions and the final documents is where the money goes. Allowances, contingency drawdown and scope clarifications are the leak points to watch here, not change order volume.
• Cost-plus. You carry cost risk directly and you have the most visibility of any structure. Every leak in this article is available to you, which sounds bad and isn't necessarily: the costs are visible as they occur rather than arriving as a negotiated change. The risk is weak controls, since there's no contractual ceiling doing the work for you.
• Unit price. Exposure concentrates in quantity variance. The rates are fixed; how much you need isn't. Common on heavy civil, where the leak looks like a quantity overrun rather than a cost overrun.
• Design-build. Single point of responsibility reduces design-gap changes substantially, since the party that designed it is the party building it. Owner-driven scope changes still flow through normally. The tradeoff is less visibility into how the price was composed.

The practical use: if your change orders cluster in a category your contract type shouldn't be producing, the cause is upstream of the project. Design gaps under lump sum point at document completeness. Allowance conversions under GMP point at when the price was locked. Quantity overruns under unit price point at the estimate basis. Each one is a different fix, and treating them all as change order management wastes the signal.

Why it stays invisible so long

Three structural reasons, and they compound.

1. Reporting lag. If cost data is compiled monthly and the close takes two weeks, leadership is routinely looking at a picture that's six weeks old. On a fast-moving project that's several commitments and a handful of change orders ago. Decisions get made against a number that was accurate in a meaningful sense and is no longer true.
2. Reconciliation gaps. The project system and the accounting system disagree, and someone reconciles them periodically. Between reconciliations, two numbers exist and people use whichever one they can reach. The discrepancy is usually discovered rather than monitored.
3. Aggregation is manual. Portfolio position requires someone to assemble it. Because it's work, it happens on a schedule rather than continuously, which means the aggregate view is always the least current view, despite being the one executives rely on.

None of these are anyone's fault, which is part of the problem. They're properties of how the information moves, and they persist through personnel changes and good intentions alike.

Early warning signals

Before the number moves, a few things tend to shift. These are worth watching precisely because they're visible when the budget still looks fine.

• Contingency burning faster than the schedule. The single best leading indicator. Contingency consumed as a percentage should track roughly with percent complete. When it runs ahead by a meaningful margin, that gap almost never closes on its own.
• RFI volume rising in a specific scope area. A cluster of RFIs around one system or trade usually means the documents were unclear there, and unclear documents produce change orders with a lag of a month or two.
• Change orders shifting from field conditions to design gaps. Field conditions are normal and roughly random. A pattern of design-related changes suggests the documents weren't complete at bid, which means more are coming.
• Forecast at completion that hasn't moved in several reporting cycles. On an active project, a perfectly stable EAC is more suspicious than a moving one. Either nothing is changing, which is unlikely, or the forecast isn't being genuinely reassessed.
• Growing gap between committed and spent. If committed is accelerating away from spent, invoices are coming that the current spend picture doesn't reflect.
• Approval velocity slowing. When change orders and submittals start taking longer to get through, it usually means someone has become cautious, and that caution normally precedes bad news rather than following it.
• Unconverted allowances late in the project. Every allowance still carrying a placeholder value past the halfway mark is unpriced risk sitting in the budget looking like a firm number.
• The project manager stops volunteering information. Not a metric, and the most reliable signal on this list. People who are confident report proactively. People who are worried report when asked.

What to do when you're already over

Prevention advice is less useful when the number has already moved. A few things that work better than others.

• Establish the real position before deciding anything. The instinct is to act immediately. The more valuable first step is a complete picture: all commitments including unpriced authorized work, converted and unconverted allowances, soft costs, and a genuinely reassessed estimate at completion. Most recovery efforts start from a number that's still incomplete, which means the second surprise arrives a month later and costs more credibility than the first.
• Separate what's committed from what's still discretionary. Money already obligated is not a lever. The recoverable amount is always smaller than the overrun, and knowing that number quickly prevents plans built on savings that aren't available.
• Report the full expected position, not the current one. Revising a forecast twice is far worse than revising it once by more. If your best estimate is that the final number is 8% over, report 8% now rather than 5% now and 3% later.
• Look at scope before quality. Value engineering that reduces specification quality tends to generate operating cost for decades on an asset you keep. Deferring or removing scope is usually the better trade, and it's reversible later if funding appears.
• Fix the reporting gap immediately, even mid-crisis. Whatever prevented you from seeing this early will prevent you from seeing the next one. The temptation is to deal with the overrun first and the process afterward, and the process improvement rarely happens afterward.
• Document what caused it while people remember. Six months on, the explanation will have smoothed into something less useful. A contemporaneous account of which leaks contributed and by how much is the most valuable thing an overrun can produce, because it's the input to not repeating it.

What good cost control actually looks like

Not more approvals. More visibility, earlier, with fewer people assembling it.

Committed costs post in real time against the budget line they consume. Anyone with approval authority sees remaining balance before committing, not after.

Contingency is reported as a ratio against completion, so the burn rate is visible rather than the balance.

Change orders show cumulative position at every approval. The tracked budget is the full capital budget including soft costs, not the construction contract.

Funding source attribution happens at commitment. Portfolio exposure is a view, not a monthly exercise.

And forecasts get revised when the person closest to the work believes they should be, without that being a career event.

Most of that is achievable without new software, through discipline and reporting design. The parts that genuinely require systems are the real-time ones, because manual processes can't produce current data no matter how disciplined the people are.

Who should be seeing what

Reporting design matters as much as reporting frequency, and most programs send the same report to everyone.

The project manager needs line-item detail: committed against budget by cost code, open change orders, unpriced authorized work, contingency position. Continuous, not monthly.

The program manager needs comparability: variance and contingency position across every project, with the outliers surfaced. They shouldn't be reading fifteen project reports to find the two that matter.

Finance needs the committed position and the forecast, by funding source, with enough lead time to manage cash. Their question is when money leaves, not what it bought.

The executive or board needs three things: current forecast against approved budget, the direction it's moving, and what would have to be true for it to move again. Detail below that level generates questions that consume the meeting without improving the decision.

The common failure is giving executives project-level detail, which produces scrutiny of individual line items while the portfolio position goes undiscussed.

The visibility question

Every leak in this article is ultimately about latency: the gap between when money leaves and when someone with authority sees it.

That framing is more useful than treating overruns as a control problem. Controls exist in most organizations. Approval thresholds, sign-off matrices, contingency policies. The controls fire on information, and if the information arrives six weeks late, the control fires six weeks late.

So the question worth asking about your own program isn't whether you have cost controls. It's how long it takes for a commitment made on a jobsite on Tuesday to appear in a number the CFO can see, and whether the answer is hours or a month.

Where INGENIOUS.BUILD fits

The leaks described here are mostly information latency, and that's what INGENIOUS.BUILD is built to remove on the owner side.

Budgets, contracts, commitments, change orders, invoices and pay applications run in one system, so committed cost posts against the budget line it consumes as it happens rather than at reconciliation. Funding source tracking attributes spend by source at the point of commitment. Capital planning connects to live project financials, so portfolio forecasts reflect actual position rather than the assumptions at approval. And portfolio views are a filter rather than an assembly job.

It isn't an accounting system and it doesn't replace your GL. What it does is close the gap between the project where money is committed and the report where someone sees it.

Book a demo to see what real-time committed cost against budget looks like across a portfolio.

The eleven leaks, in one place

For reference, since there are a lot of them:

1. Commitment creep — obligations accumulate past what the budget supports, tracked per contract rather than against budget lines
2. Unpriced authorized work — changes approved before pricing, invisible in reporting until negotiated
3. Cumulative change order blindness — each approved on its own merits, aggregate never shown
4. Contingency without a burn rate — balance tracked, rate against completion not
5. Scope creep below the change order threshold — informal accommodations that never aggregate
6. Allowances treated as firm — placeholders reported alongside real numbers
7. Soft costs outside the tracked budget — design, permits, FF&E, IT, commissioning, internal labor
8. Escalation assumed away — multi-year programs priced against a stale basis
9. Funding source misattribution — spend charged to the wrong source, found at audit
10. Forecast at completion that doesn't move — cultural reluctance to revise upward early
11. Portfolio blind spots — every project within tolerance, program over

Most programs have three or four of these running at once. Very few have none.

The short version

Capital overruns get treated as events. They're usually accumulations that became visible.

The money leaks through commitments nobody aggregated, changes approved before pricing, contingency consumed without a burn rate, soft costs outside the tracked budget, and forecasts that stayed flat longer than they should have. None of those are dramatic. All of them are quiet, and quiet is why they work.

The counter isn't tighter approval. It's shorter latency between the commitment and the number.

FAQ

Why do capital projects go over budget?

Two distinct causes. Estimates can be systematically low due to optimism bias and strategic misrepresentation. Separately, money leaks during execution through untracked commitments, unpriced change orders, contingency drawn down without monitoring, scope creep that never becomes a change order, soft costs outside the tracked budget, and forecasts revised too late.

What is commitment creep in construction?

The gradual accumulation of contractual obligations, meaning subcontracts, purchase orders and approved change orders, beyond what the budget supports. It's invisible when commitments are tracked per contract rather than aggregated against the budget lines they consume, and it hides because the work hasn't been invoiced yet.

What's the difference between committed and spent costs?

Spent is what's been invoiced and paid. Committed is what you're contractually obligated to pay but haven't been invoiced for yet. A project can be 40% spent and 90% committed, which looks like available budget if you're only tracking spend.

How should contingency be tracked on a capital project?

As a ratio against percent complete rather than as a remaining dollar balance. A project 60% complete with 75% of contingency consumed is in trouble, and that's visible months before the contingency runs out if anyone computes the rate.

Why do change orders cause budget overruns even when each one is justified?

Because they're evaluated individually. Change orders average roughly 10% of contract value and can reach 25%, with large projects averaging over eleven. When approvers never see the cumulative position against remaining contingency, the aggregate arrives as a surprise.

What costs get left out of tracked construction budgets?

Design fees, permits, owner's representative fees, FF&E, IT and low voltage, commissioning, moving costs and internal labor. When only the construction contract is tracked rigorously, the construction number can look healthy while the capital project overruns.

How long should it take for a cost commitment to appear in reporting?

The useful test is how long between a commitment made in the field and a number an executive can see. Monthly compilation with a two-week close means leadership routinely views data six weeks old, which is several commitments and multiple change orders behind reality.

What is the best way to control capital program costs?

Reduce latency rather than adding approvals. Post commitments against budget in real time, show cumulative change order position at every approval, report contingency as a burn rate, track the full capital budget including soft costs, attribute funding sources at commitment, and make portfolio exposure a live view rather than a monthly assembly.

What are the early warning signs a capital project will go over budget?

Contingency burning faster than percent complete, RFI volume clustering in one scope area, change orders shifting from field conditions toward design gaps, a forecast at completion that hasn't moved in several cycles, a growing gap between committed and spent, slowing approval velocity, and allowances still unconverted late in the project.

What should you do when a capital project is already over budget?

Establish the complete position before acting, including unpriced authorized work and soft costs. Separate committed money from what's still discretionary, since only the latter is recoverable. Report the full expected overrun once rather than revising twice. Prefer deferring scope over reducing quality on an asset you'll operate for decades. And fix the reporting gap immediately, because it won't get fixed afterward.

Who should receive capital project cost reporting?

Project managers need continuous line-item detail. Program managers need comparability across projects with outliers surfaced. Finance needs committed position and forecast by funding source. Executives need forecast against approved budget, its direction, and what would change it. Sending everyone the same report usually means executives scrutinize line items while portfolio position goes undiscussed.

Does contract type affect which budget overruns you're exposed to?

Substantially. Under lump sum, exposure concentrates in change orders, so heavy design-gap changes point at incomplete documents at bid. Under GMP, exposure sits in how the price was set, making allowances and contingency drawdown the signals to watch. Cost-plus exposes you to everything but with maximum visibility. Reading your overrun pattern against your contract type identifies where the real failure occurred.