When a project budget blows up, the story is rarely a single bad decision. It is a hundred reasonable ones that nobody added up. A contractor extended a week here, a software license renewed there, a vendor invoice came in higher than the estimate. Each was approved by someone with the authority to approve it. None of them, individually, looked like a problem. Together they put the project 18 percent over, and the PMO found out at quarter end.
Controlling portfolio spend is mostly about closing that visibility gap. The schedule gets watched obsessively. The money, and specifically the money that has been committed but not yet invoiced, often does not.
Key takeaways
- Track committed cost, not just actuals. A signed purchase order is real money even before the invoice arrives.
- Tie every commitment back to a project and a budget line so overruns surface early.
- Match approval thresholds to risk, so small spend moves fast and large spend gets real scrutiny.
Committed cost is the number that hides
Most budget tracking watches actuals: money that has been invoiced and paid. But by the time a cost is an actual, it is history. The number that lets you steer is committed cost, the spend you have already agreed to through purchase orders, contracts, and approved work, even though the invoice has not landed. A project can look on budget on actuals while carrying a stack of commitments that will push it well over once they clear.
The fix is to track commitments the moment they are made, not when they are paid. Every purchase order against a project should reduce the remaining budget immediately, so the picture reflects what you have actually obligated.
Tie every commitment to a project and a line
Spend control breaks down when purchases float free of the plan. A budget overrun is easy to catch when every purchase order is coded to a specific project and budget line and someone reconciles commitments against the plan on a regular cadence. It is nearly impossible to catch when procurement happens in a separate system that the PMO only sees at month end.
This is also where approval discipline matters. Purchase orders need a clear approval path, with thresholds matched to risk: small, routine spend should move quickly, while anything large enough to dent a budget should get real scrutiny before it becomes a commitment. Teams managing high purchase-order volume across many projects often run this through dedicated purchase order management software so that every commitment is captured, routed for approval, and visible against the budget rather than living in a chain of email approvals. The principle holds regardless of tooling: a commitment you cannot see is a commitment you cannot control.
Reconcile on a cadence, inside governance
Budget control is not a year-end audit. It belongs in the same rhythm as the rest of portfolio steering. Pulling committed cost against plan into the regular portfolio governance review means overruns surface while there is still time to do something: renegotiate, reprioritize, or pause downstream spend. Wait for the formal financial close and the only option left is to explain the variance.
Budget and capacity are the same conversation
Money and people are two views of the same constraint. A project that needs more budget usually needs more of a scarce skill too, and both signals should land in the same place. When you review whether a project still deserves funding, review whether it still deserves capacity, using the same lens described in resource and capacity planning. Steering a portfolio means steering both, together, rather than discovering the budget problem and the staffing problem in separate meetings a month apart.