Sohaib Wasif Calgary based career in project controls includes work on programs where schedule control was genuinely high-stakes. The Coastal Gas Link pipeline. Ontario Power Generation’s multi-billion dollar enterprise program. Rio Tinto’s mining capital portfolio. These are not programs where a two-week schedule slip is a minor administrative note. At that scale two weeks on the critical path is a significant financial and commercial event.
Schedule control and cost control are not separate problems. They’re the same problem expressed in different units. A schedule that’s running behind is accumulating overhead costs and losing productivity and potentially affecting the commercial position of contracts that have milestone-linked payments or performance obligations. Treating schedule management as a separate function from cost management is how you end up with controls reports that are internally inconsistent.
What Makes a Schedule Reliable
A schedule is reliable when its logic reflects how the work is actually going to be executed. When the durations are based on realistic productivity assumptions for the specific site conditions. When the resources required by the schedule are actually available in the quantities assumed. And when the schedule is being updated with actual progress data on a consistent basis rather than just having activities pushed back when they run late.
Most large project schedules start with reasonable integrity and then degrade during execution as the discipline of maintaining them comes under time pressure. Contractor updates arrive late or with poor logic. Out-of-sequence progress gets recorded without logic changes. The critical path shifts without anyone explicitly acknowledging that it has shifted. And the schedule stops being predictive.
The Critical Path Problem on Long Programs
On a multi-year program the critical path at the end of execution is often completely different from the critical path that was identified at the start. Acceleration on some activities and delays on others combined with scope changes and contractor sequencing decisions all alter the network logic as the program progresses. Sohaib Wasif Calgary background on programs that run multiple years means working through that dynamic and keeping the schedule analysis connected to execution reality throughout.
The practical implication is that critical path analysis has to be done on the current schedule as it actually exists rather than on what the schedule was supposed to look like at project sanction. A milestone date that looks achievable based on the original logic might not be achievable based on the current network if the critical path has shifted.
Schedule Recovery: What It Actually Requires
Schedule recovery is one of the most mishandled situations in project controls. The common response to a schedule that’s running behind is to add resources and declare that recovery is underway. But adding resources to a late project often makes it later because of the supervision and coordination overhead that comes with acceleration. Real schedule recovery requires identifying which specific activities on the critical path can be compressed and at what cost and with what quality implications.
Sohaib Wasif‘s work on TC Energy and OPG programs that faced real schedule pressure is the kind of experience that teaches what credible recovery planning actually looks like. A credible recovery plan has specific logic for how each compression will be achieved. It has identified resource commitments. It has a risk assessment for the activities that are being compressed. And it has contingency for the risks most likely to affect the recovery path.
Earned Schedule and Why Standard EVM Falls Short
Traditional earned value management measures schedule performance in cost terms through the schedule performance index. But this can be misleading especially in the later phases of a project when the remaining work has a different cost profile than the work that’s been completed. Earned schedule methodology fixes this by converting schedule performance into time units directly. It tells you not just whether you’re ahead or behind but by how much time.
I think this is an underused technique specifically because it produces a more honest picture of schedule performance than reading a schedule performance index off a standard EVM report. The honest picture is more useful even when it’s less comfortable.
FAQ
What is the critical path in project schedule management?
The critical path is the sequence of activities that determines the earliest possible completion date for the project. Any delay on a critical path activity directly delays the project completion unless compensating action is taken. Most large capital projects have multiple near-critical paths that can become the critical path if a key activity is delayed.
How does schedule compression work in practice?
Schedule compression involves either adding resources to an activity to reduce its duration which is called crashing or overlapping activities that would normally be done sequentially which is called fast-tracking. Both approaches have cost implications and quality risks. Crashing increases direct cost. Fast-tracking increases rework risk if the overlapping activities have information dependencies.
What is float in schedule management?
Float is the amount of time an activity can slip before it affects the project completion date. Activities on the critical path have zero float. Activities with positive float have some scheduling flexibility. Managing float on near-critical paths is important because an activity with small float that slips by more than its float amount becomes critical and can change the project completion date.
