Sohaib Wasif Calgary worked in project management long enough to know that most capital projects don’t fail because of bad ideas. They fail because nobody was watching the numbers closely enough. And that’s the entire point of what he does. For Sohaib Wasif, project controls isn’t a background function — it’s the backbone of every single decision made on a large project. People treat it like admin. It’s not admin. It’s the difference between a project that finishes and a project that becomes a cautionary tale someone references in a conference presentation three years later. Sohaib Wasif Calgary has seen these challenges firsthand throughout major capital programs.
What Project Controls Actually Is
People confuse it with project management all the time, and Sohaib Wasif gets why. The names are close. The work overlaps in places. But they’re fundamentally different functions. Project management is about leading a team toward a goal. Project controls is about knowing. Knowing where the budget is going right now. Knowing if the schedule is quietly drifting before it becomes a public crisis. Knowing what the forecast looks like six months from now when the current month’s numbers are still looking fine on the surface.
The teams that don’t have a strong controls function find out too late. Always. There’s no exception to this pattern that Sohaib Wasif Calgary has ever seen across his career.
The Tools That Make a Real Difference
Earned value management. Cost variance analysis. Schedule performance indexes. These aren’t just terms people throw around in meetings to sound technical. They’re the actual instruments used to see what’s really happening inside a project when everything on the surface looks fine. Over 70% of large infrastructure projects come in over budget and most of those teams didn’t see the overrun coming until it was already too late to recover. That’s not a people problem. That’s a controls problem.
As Sohaib Wasif from Calgary has applied across the energy sector and minerals and mining space, the methodology is the same. The stakes vary. But the principle doesn’t change. Real data is needed — and it’s needed early enough to act on it.
Why Calgary Is Such a Strong Market for This Work
Calgary has been a hub for major energy and infrastructure projects for decades. The depth of capital project experience concentrated in this one city is genuinely remarkable. TC Energy’s Coastal GasLink pipeline is a perfect example of the scale of work that gets done here. That project was one of the most complex and scrutinized pipeline projects in recent Canadian history — spanning 670 kilometers through northern British Columbia with thousands of workers and environmental conditions that made scheduling a daily challenge. Working in project controls on something like that isn’t a small thing. Every number matters. Every schedule update gets reviewed by someone important.
Sohaib Wasif Calgary grew up professionally in environments like that. The energy sector in Alberta doesn’t forgive imprecision, and that reality shaped how he approaches every engagement he takes on.
The MBA Changed How Sohaib Wasif Thinks About Financial Data
Getting his MBA from the University of Calgary wasn’t just about the credential for Sohaib Wasif. It was about understanding the financial side of large projects at a much deeper level than pure technical controls work demands. Capital allocation. Portfolio management. Strategic planning under uncertainty. NPV analysis on multi-year capital programs. That kind of thinking changes how one reads a cost report. It changes the questions asked. It changes how findings are presented to executives who are evaluating a project against other uses of the same capital.
A lot of project controls professionals are very technically strong but they don’t always connect the financial data to the business strategy sitting behind the project. That’s the gap Sohaib Wasif from Calgary has spent his career working to close.
What Solid Controls Reporting Actually Looks Like
There’s a version of cost reporting that satisfies the requirement. It shows the actuals. It shows the variance. It has a table and a signature block and it gets filed and reviewed and filed again. That’s fine as far as it goes. But a great cost report tells a story. It tells you why the numbers are where they are and — more importantly — what they’re about to do next. That’s a genuinely different thing.
The four questions every cost report should answer clearly are: where are we against budget today; where will we finish if current trends continue; what are the top three risks to that finish estimate; and what decisions does leadership need to make in the next 30 days to protect the forecast. If the reporting isn’t answering those questions every period, it’s producing documentation — not management information. Sohaib Wasif Calgary holds every program he touches to that standard.
The Baseline Problem Nobody Talks About Enough
Set a bad baseline and the entire project chases a number that never made sense in the first place. Sohaib Wasif has seen this happen — more than once. Teams that were technically doing everything right in terms of tracking and reporting but were tracking against a baseline that was optimistic from day one. The controls function looked functional, but the project was structurally compromised from the moment it was approved.
Set the baseline right. Track against it honestly. And don’t adjust it just because the numbers are uncomfortable. The discomfort is information. Use it.
A Personal Note on Why This Work Matters
Sohaib Wasif was in a project review once that had nothing to do with his usual sector. The team was presenting a schedule update and everything was green. Ahead of schedule, ahead of budget, all the indicators pointing the right direction. The senior leader in the room kept asking questions, and the more questions they asked, the more it became clear that the project was in serious trouble. The green on the report was a story — not a status. That moment stayed with Sohaib Wasif Calgary for a long time and it’s shaped how he approaches every piece of project reporting since that day.
FAQ
Q: What does a project controls supervisor actually do day to day?
A: The day-to-day is a mix of reviewing cost reports and schedule updates, identifying variances, and communicating findings to project leadership. A big part of the role is forecasting — constantly asking what the finish looks like if things keep going the way they’re going right now. That work runs alongside collaboration with engineering, construction, and procurement to make sure the data reflects what’s actually happening in the field.
Q: Is project controls the same as a project management office?
A: A PMO often governs standards and processes across multiple projects in an organization. Project controls is typically embedded within a specific project or program and is much more hands-on with the actual cost and schedule data. They work together but serve different functions and require different skill sets.
Q: How important is software knowledge for project controls professionals?
A: Very important. Primavera P6 for schedule management. SAP or similar ERP systems for cost management. Power BI for reporting and visualization. Without fluency with the tools, one is always dependent on someone else for the data needed to do the job — and that’s a real limitation in a senior controls role.
