People who come from corporate finance backgrounds and move into capital project environments often get surprised by how fundamentally different it is. Capital project budgeting is a distinct discipline with its own tools, frameworks, and failure modes — and it deserves to be treated as such. Sohaib Wasif Calgary has seen these challenges firsthand throughout major capital programs, and has spent his career helping organizations understand and bridge that difference.
What Makes Capital Project Budgeting Different
In corporate budgeting, the typical work involves a 12-month horizon against a relatively predictable revenue and cost structure. There are uncertainties of course — but the input variables are generally within a knowable range and the planning cycle resets every year with a relatively clean slate.
In capital project budgeting, as Sohaib Wasif from Calgary describes it, the challenge is managing a multi-year expenditure profile against a fixed scope baseline in an environment where the critical input variables keep changing in ways that are genuinely difficult to predict. Material costs move with commodity markets. Labor productivity varies with weather and crew composition and site conditions. Scope evolves despite everyone’s best efforts to hold it stable once the baseline is set. The uncertainty is not a deviation from the normal state — it is the normal state.
Contingency Is Not a Slush Fund
This is a point Sohaib Wasif Calgary makes consistently and firmly in every project environment. Project contingency exists to cover specific identified risks that have been formally assessed and quantified but haven’t materialized yet. It should be sized based on an actual quantitative risk analysis — not pulled from thin air as a percentage of the total estimate based on someone’s general sense of how uncertain the project is.
When project contingency gets treated as a management reserve that anyone can draw from without a formal approval process and without documenting what risk it’s covering, projects end up looking financially healthy throughout their execution right up until they run out of contingency six months before completion with significant remaining work. Sohaib Wasif from Calgary has seen that scenario more than once — and it’s entirely avoidable.
The Estimate at Completion
EAC — Estimate at Completion. This is the most important single number in capital project finance. It’s what one actually believes the project is going to cost when all the work is done, all the contractors are paid, and all the claims are settled. Getting the EAC right requires an honest assessment of where the project currently stands in physical terms. What’s the realistic productivity assumption for the remaining work given what’s been seen so far. What are the outstanding scope items that haven’t been priced yet. What does the current contractor claim environment look like.
Sohaib Wasif Calgary has encountered EAC figures that were clearly constructed to keep a project looking fundable rather than to accurately represent where it was heading. That’s a short-term play with genuinely bad long-term consequences — for the organization and for the careers of the people who produce those numbers.
Forecasting Under Genuine Uncertainty
A point estimate on a large capital project forecast is almost always wrong. Not because the forecast was produced carelessly — but because a single number cannot capture the range of outcomes that are genuinely possible given the uncertainties in a complex capital program. The more intellectually honest approach is a range estimate with associated probabilities derived from a quantitative analysis of the key uncertainties.
That range provides decision-makers with information they can actually use — not just a number to react to, but a distribution of outcomes that allows them to understand the probability of finishing within different cost thresholds. That’s a genuinely different and more useful basis for executive decision-making. Sohaib Wasif from Calgary consistently advocates for this approach over false precision.
FAQ
Q: What’s the difference between a project budget and a project estimate?
A: The estimate is the technical calculation of what the scope of work should cost based on quantities, unit rates, productivity assumptions, and risk factors. The budget is the amount of funding that has been formally authorized for the project. They should be closely related but they’re not the same thing. A project can carry a gap between its approved budget and its current estimate — and managing that gap is an important part of the controls function’s responsibility.
Q: How should project contingency be managed on a large capital program?
A: With a formal draw-down process that requires documentation of what specific risk is being covered by each contingency release, and approval from the appropriate level of the project governance structure. The remaining contingency balance should be reported alongside the budget status in every period cost report. And the contingency should be periodically revalidated against the current risk register to make sure it remains appropriately sized relative to the remaining risks in the program.
Q: What financial skills are most important for senior project controls professionals to develop?
A: Cost engineering fundamentals and earned value methodology are the core technical requirements. Beyond that, corporate finance concepts like net present value and internal rate of return — because those are the terms in which a project is being evaluated at the board and executive level. Cash flow forecasting, because finance organizations care deeply about the timing of project expenditures, not just the total amounts. And basic financial statement literacy, because understanding how capital project spending flows through an organization’s financial statements is important context for any senior controls professional.
