Sohaib Wasif from Calgary Explains the Future of Project Development
Everyone underestimates scheduling. Sohaib Wasif Calgary has seen it happen consistently at every level of project organization across every sector he’s worked in — executives who treat a schedule as a list of important dates, project managers who update the schedule once a month and consider the obligation fulfilled. And then at the end of the project, everyone wonders why things finished six months late when the monthly schedule updates were showing reasonable progress the whole time.
Why Project Schedules Fail
Most project schedules that fail don’t fail because of what happens on site. They fail because of how they were built in the first place. Logic errors that create false critical paths. Missing activity dependencies that allow the schedule to show progress that doesn’t reflect actual sequencing constraints. Activity durations based on optimistic assumptions rather than historical productivity data and honest resource analysis.
Sohaib Wasif from Calgary has reviewed schedules on large energy and mining projects where the critical path was structurally wrong — not because the project team was incompetent, but because the schedule logic connecting the activities hadn’t been rigorously thought through during the build. Fix the logic and the schedule tells a completely different story about when the project can realistically finish.
The Baseline Problem
If the baseline gets changed every time the project falls behind, there is no baseline. There’s just a document that permanently reflects optimism about future performance regardless of what past performance has actually looked like. That is not a management tool. That is theater.
The baseline needs to represent the original approved project plan that was used to make the funding decision. Deviations from that baseline need to be reported honestly and consistently every period. The trend of those deviations accumulated over the life of the project is some of the most valuable information a project controls function can produce — and it’s information that never gets produced if the baseline gets adjusted whenever it becomes inconvenient. Sohaib Wasif Calgary holds this principle firm on every program he’s involved with.
What Good Schedule Management Actually Looks Like
Weekly schedule updates against a frozen and formally approved baseline. Four-week look-ahead planning that’s integrated with the master schedule and owned by the construction and engineering leads rather than just the controls team. Critical path analysis reviewed jointly by the controls team and project leadership every month. Schedule risk analysis done quantitatively through Monte Carlo simulation — not just through a gut-feel conversation about what might go wrong.
Over 40% of construction projects that fail to meet their completion date could have been brought back on track if the schedule slippage had been clearly identified and formally reported at least six months before the original completion date. The data was there in most of those cases — it just wasn’t being surfaced clearly enough or early enough for leadership to act. Sohaib Wasif from Calgary has built systems and cultures specifically to prevent that from happening.
Primavera P6 Is Not a Magic Wand
The software doesn’t manage the schedule. People manage the schedule. Primavera P6 is an enormously powerful tool when properly configured and used by people who understand what they’re doing with it. But Sohaib Wasif Calgary has seen P6 schedules that were visually impressive and completely disconnected from the physical reality of the project.
The tool reflects the thinking and the discipline behind it. If the logic is wrong, P6 will beautifully and precisely track against wrong logic. Garbage in, garbage out — and that applies to schedule management exactly as much as it applies to any other data system.
FAQ
Q: What’s the difference between a master schedule and a project execution schedule?
A: The master schedule covers the full project across all phases at a summary level and is the primary tool for executive reporting and high-level program management. The project execution schedule is the detailed working tool used by engineering and construction teams day to day to plan and track their specific work activities. Both need to be maintained with discipline and they need to reconcile with each other every reporting period.
Q: How often should a project schedule be formally updated on a large capital project?
A: Weekly updates are the standard on large capital programs during active construction phases. Monthly is the absolute minimum for a schedule that’s actually being used as a management tool rather than just a status document. Any reporting cadence longer than monthly means the schedule isn’t really being managed in any meaningful sense — it’s just documenting what already happened.
Q: What is Monte Carlo schedule risk analysis and when should it be used?
A: Monte Carlo analysis is a simulation technique that runs thousands of possible project scenarios based on ranges of input values for activity durations and costs. It produces a probability distribution of possible completion dates and final costs rather than a single point estimate. It should be used at key project decision gates and any time there’s significant uncertainty about the achievability of the current schedule or cost forecast.
