A budget report built only on actual spend tells you where you’ve been. Committed cost tells you where you’re going.
How Projects Go Overbudget Without a Single Bad Decision
By Atif Rehman,
Every project has three numbers that matter: what was budgeted, what has been committed, and what has actually been spent. Most reporting only shows two of them.
That missing number, committed cost, is the difference between a project that looks healthy and a project that is healthy. Understanding why requires understanding what a commitment actually is.
The Three Numbers, Defined
Budget is what you planned to spend. Straightforward, and rarely the source of confusion.
Actual cost is what has been invoiced and posted. Also straightforward. This is the number every finance report leads with, because it’s the easiest to verify.
Committed cost is what you have already agreed to spend, whether or not an invoice has arrived. A signed purchase order. An awarded subcontract. A confirmed order for a long-lead item. The obligation exists the moment the agreement is made, not the moment the supplier bills for it.
Most project reporting compares budget to actual and stops there. That comparison answers “how much have we spent.” It does not answer the more important question: “how much can we still afford to commit?”
Why the Gap Exists
The reason committed cost gets missed isn’t carelessness. It’s timing.
A steel package can be committed in month two and not invoiced until month six. An MEP subcontract is often awarded before design coordination is even finished. On a fast-track UAE project running multiple packages in parallel, months of commitments can accumulate before anyone consolidates them into a single view.
Individually, none of these are alarming. A PO here, a subcontract there. But consolidated, they represent real money the project no longer has, whether the accounts reflect it yet or not.
A Short Diagnostic
Before reading further, test your own reporting against this checklist. If you can’t answer these with confidence today, the blind spot already exists on your projects.
- Can you see committed cost, not just actual cost, on a live project report right now
- Does a purchase order check against remaining budget before it’s issued, or only after
- Are long-lead items tracked against both schedule and remaining cash
- Do procurement, project management, and finance work from the same live budget figure
- Would an unbudgeted commitment get flagged automatically or only discovered at month-end
Most contractors answer “no” to at least two or three of these. That’s not a criticism. It’s simply where reactive, spreadsheet-driven procurement naturally lands.
The Principle: Visibility at the Point of Commitment
The instinct when budgets slip is to add controls. More sign-offs, more layers of approval, more reviews. This usually makes the problem worse, not better, because it adds friction without adding information.
The actual fix is simpler and less bureaucratic: give the person about to make a commitment the same information finance already has, at the moment they’re making it.
That means:
Every purchase order is checked against remaining budget before issue, not after Committed, invoiced, and remaining values sit side by side, by package and cost code Unbudgeted commitments trigger approval automatically, not at month-end review Long-lead procurement is planned against schedule and cash flow together, not treated as procurement’s problem alone One live number is shared across procurement, project management, and finance, instead of three reconciled spreadsheets
None of this slows procurement down. It moves the moment of truth earlier, from “we found out at month-end” to “we knew before we signed.”
Where This Breaks Down in Practice
The blind spot rarely causes damage while a project is going smoothly. It causes damage the moment something changes: a price increase, an added scope, a delayed variation approval, and there’s no room left to absorb it.
By then, the commitment is already locked in. There’s no renegotiating a signed PO because the budget turned out tighter than expected. What’s left is to eat the overrun, or dispute it, and neither is a comfortable position mid-project.
It’s also where internal trust erodes. Project managers get blindsided by numbers finance was quietly carrying. Finance gets blindsided by commitments the site made without flagging them. Nobody did anything wrong. They simply weren’t looking at the same numbers.
A Closing Principle
A budget report built only on actual spend tells you where you’ve been. Committed cost tells you where you’re going. Most overruns aren’t the result of one bad decision. They’re the accumulation of small commitments nobody consolidated until the budget was already spoken for.
