Critical path analysis

The critical path is the sequence of activities with zero float (1) — the longest path through the network, which determines the minimum time to complete the project (1).

Float = LFT(end node) − duration − EST(start node) = 15 − 5 − 6 = 4 days (Knowledge 1, Application 2). Since the float is not zero (4 days), activity X is not on the critical path — it has spare time (Analysis 1).

CPA identifies MegaBuild's critical activities and the shortest possible completion time (Knowledge + Application). Knowing which activities have zero float — the groundworks and structural frame that must not slip — lets MegaBuild focus management attention and site resources on them, keeping the whole build on schedule and avoiding the costly penalties of overrunning a construction contract (Analysis).

CPA also reveals the float on non-critical trades and when each activity needs resources (Knowledge + Application). This lets MegaBuild phase labour, materials deliveries and plant to arrive just when needed (supporting JIT) and redeploy spare resources from trades with float to critical ones (Analysis). Sequencing site resources this precisely while protecting the critical path helps MegaBuild hit its handover date and control build costs and cash flow on a complex project (Analysis).

There is some justification for the manager's confidence. CPA gives RapidBuild a clear plan — the shortest completion time, the critical activities (such as groundworks or the structural frame) to prioritise, and the float available on non-critical trades elsewhere. By sequencing the critical path and phasing subcontractors, plant and materials deliveries to arrive when each activity needs them, RapidBuild is much more likely to finish on time than without any site scheduling, so CPA genuinely improves its chances.

However, believing CPA guarantees on-time completion is not justified. CPA is only a plan based on estimated activity durations — if RapidBuild's time estimates for each trade are wrong, the whole network, including which path is critical, is unreliable. More fundamentally, CPA plans but does not manage the build: unexpected events — a materials-supplier delay, bad weather halting site work, plant breakdown or a labour dispute — can disrupt activities regardless of the plan, causing delays CPA cannot prevent.

Whether the belief is justified therefore depends on how RapidBuild uses CPA and the accuracy of its estimates. CPA improves the likelihood of finishing on time and is a valuable planning tool, so the manager is right to value it. But it cannot guarantee the outcome — that depends on accurate duration estimates and, crucially, on active site management and contingency planning to respond to the unexpected. So the belief is partly justified (CPA helps a lot) but overstated (it guarantees nothing): RapidBuild should use CPA to plan and manage the site actively, rather than assume the plan alone ensures success.

For a large building project with many interdependent activities, CPA is well-suited — but its usefulness depends on the accuracy of TowerCo's estimates and how it manages the site alongside the plan.

Why CPA is useful here. With many interdependent activities — where the frame cannot start until groundworks finish, and fit-out cannot start until the frame is up — TowerCo needs to know the order, timing and dependencies between trades, exactly what a network diagram maps. CPA finds the shortest completion time, identifies the critical activities that must not slip, and reveals float on non-critical trades elsewhere, letting TowerCo prioritise, phase subcontractors and materials deliveries (JIT) and control cash flow. For a complex construction project where delay penalties are costly, this planning value is substantial — arguably CPA is most useful precisely for complex, interdependent projects like TowerCo's.

Its limitations. However, CPA relies on estimated activity durations, and for a large, complex build these estimates carry real uncertainty — if they are wrong, the critical path and completion time are unreliable. CPA is also only a plan: it cannot prevent unexpected disruptions (subcontractor delays, weather stopping site work, materials shortages, labour issues) common on big construction sites, and it says nothing about cost or quality, only time.

Judgement. On balance, CPA is highly useful for TowerCo — its complex, interdependent build is exactly the situation CPA is designed for, and the benefits of mapping trade dependencies, identifying critical activities and phasing site resources are significant. However, its usefulness depends on the accuracy of TowerCo's duration estimates and on TowerCo using CPA as a planning aid within active site management, not as a guarantee. TowerCo should build in contingency for the uncertainty and update the network as the build progresses and estimates firm up. So CPA is a valuable, arguably essential tool for a project of this complexity — provided TowerCo grounds it in realistic estimates and combines it with strong ongoing site management to handle the inevitable surprises.

CPA is a core project-planning tool, and Landmark relies on it — but as a plan built on estimated durations, its usefulness depends on estimate accuracy, the complexity of the development, and how Landmark manages the build alongside it.

Why CPA is useful. For a developer managing large construction projects, CPA provides real value. It maps every activity — groundworks, structural frame, services, fit-out — along with its order and dependencies, and calculates the shortest possible completion time. It identifies the critical activities (zero float) that Landmark must prioritise and monitor to avoid delaying handover of the whole development, and it reveals the float on non-critical trades, allowing site resources to be moved where needed. This lets Landmark phase labour, subcontractors, materials deliveries and cash for exactly when each activity requires them (supporting JIT and cash-flow management) and anticipate and manage potential bottlenecks on site. For complex, multi-activity developments, this structure and foresight are highly valuable — helping Landmark finish on time and control build costs.

Its limitations. However, CPA has clear weaknesses. It relies entirely on estimated activity durations; if these are inaccurate — likely on large, uncertain builds — the network, the critical path and the completion time are all unreliable. CPA is only a plan, not site management: it cannot prevent unexpected events (subcontractor failures, weather, strikes, design changes) that disrupt real projects, and a delay to a previously non-critical trade can shift the critical path. CPA also focuses solely on time, ignoring cost and quality, and complex developments produce complicated networks that are hard to construct and update.

What it depends on. How useful CPA is for Landmark depends on several factors. It depends on the accuracy of its duration estimates — reliable estimates make CPA powerful; poor ones make it misleading. It depends on project complexity — CPA is most valuable for large, interdependent developments (like Landmark's) and less needed for simple ones. It depends on how well Landmark monitors and updates the plan as the build unfolds and estimates firm up. And it depends on whether Landmark treats CPA as a planning aid within active site management or as a guarantee.

Conclusion. On balance, CPA is a highly useful, arguably essential planning tool for a developer like Landmark Developments, but it is not a guarantee of success. Its ability to map dependencies, find the shortest completion time, identify critical activities and phase site resources makes it genuinely valuable for the large, complex developments Landmark manages — so its reliance on CPA is well-placed. However, because CPA depends on uncertain estimates, covers only time, and plans rather than manages, Landmark should treat it as a framework to support decision-making, not a promise of on-time handover: it must ground the network in realistic estimates, build in contingency, update the plan as work progresses, and pair CPA with active site management to handle the inevitable disruptions. Used that way, CPA is one of the most useful tools available for complex project planning; relied on blindly as a guarantee, it can create false confidence. Its usefulness therefore depends less on the technique than on the accuracy of Landmark's estimates and the quality of its ongoing site management.