This article was first published in the December 2025 issue of Construction Week Middle East. 

A perspective on why linear projects demand a different lens 

Rail programmes in the Middle East are entering a new phase. What was once a collection of isolated transport corridors is becoming a regional network that spans borders, climates and delivery cultures. These schemes stretch for hundreds of kilometres. They cross land planned for future cities, desert zones with restricted access, utility corridors under heavy protection, and areas where approvals travel through long, multi-layered channels. 

Delays are inevitable. What matters is how they are understood. Here lies the problem. Much of the industry still leans on delay analysis tools developed for vertical construction or compact infrastructure sites. Tools that assume the work is static. Tools that presume a fixed path. On a long rail alignment, this view rarely holds. 

It is time to rethink the way we assess delay on linear programmes, not to replace existing methods, but to recognise the reality of how railways are built. 

The gap between schedules and the ground 

Many schedules still treat a railway as a single, uninterrupted chain of logic. This creates the impression that if something slips at one end, the entire line stalls. Anyone who has delivered a railway knows this is not how linear projects progress in practice. 

Crews move. Resources shift. Contractors adapt to circumstances on the ground. Teams jump forward to the next accessible chainage while waiting for design, utilities or permits. The alignment becomes a set of moving parts, not a single sequence. 

Traditional “Critical Path Method (CPM)” struggles with this. It shows theoretical criticality, not operational criticality. Activities appear critical because of their place in the logic, not because of their impact on what crews could or could not do at a specific point along the alignment. 

The result is predictable: disputes over logic, arguments over float, and narratives that do not reflect the reality of the project. 

Why linear projects require a spatial viewpoint 

Time and sequence matter but so does location. Without a spatial lens, a delay analysis for a railway risks becoming detached from how construction actually unfolded. 

Time–Chainage, when used properly, changes the conversation. It allows teams to see where crews advanced, where they were forced to pause, and why certain stretches became bottlenecks. It exposes gaps in work-front availability, often long before they appear in a CPM output. It also helps distinguish between localised problems and systemic ones. 

This spatial perspective does not replace CPM. It contextualises it. A delay that appears critical on the programme may have been absorbed by working elsewhere. Another that looks minor may have blocked multiple trades because of where it occurred and the nature of the works that followed. 

Linear projects behave differently. Our delay methodologies should acknowledge that. 

Understanding how sequences evolve, not how they were planned 

Baseline programmes serve an important purpose. They tell us how teams intended to build the railway. However, the more linear and dispersed a project becomes, the more likely it is that reality diverges from intention. 

An As-Planned versus As-Built (APvAB) comparison reveals this shift. It shows when crews abandoned the planned logic because a predecessor was not ready, or because access opened earlier in another zone. It shows where trades were unable to start because the alignment had not progressed to the handover condition they required. In a region where authority approvals, NOCs and third-party readiness vary significantly from kilometre to kilometre, this understanding is essential. 

The point is not to point fingers at deviations. It is to understand what truly controlled progress. 

Why the Middle East’s rail ambitions need a more mature analytical approach 

The region’s next generation of rail programmes is larger, more complex and more interdependent than anything delivered here before. Stakeholders span multiple countries. Utility owners have wide mandates and tight constraints. Many areas carry heritage, environmental or security sensitivities. And unlike mature rail nations, much of the supply chain is still scaling up to meet the volume. 

Delays in this environment rarely emerge from a single cause. They arise from the interaction of access, permissions, approvals, weather, logistics and resource availability. Understanding these interactions requires a methodology that reflects the linear nature of the works. 

A combined Time–Chainage and APvAB approach does exactly that. One shows how the alignment moved. The other shows how the sequence changed. Together they reveal what genuinely drove criticality. 

This approach is not new globally but in the Middle East, where linear rail programmes are growing in both scale and ambition, it is becoming essential. 

Towards more robust, defensible delay narratives 

A stronger analytical foundation does more than resolve disputes. It improves design management. It strengthens risk forecasting. It exposes systemic approval challenges and it helps delivery teams adapt programmes before issues escalate. 

Most importantly, it brings clarity. Rail projects succeed when everyone can see how work is flowing along the alignment and why. A delay analysis that reflects this reality is far more valuable than one that simply follows the logic of a programme. 

If the region is to deliver its rail ambitions at the pace expected, then the industry must evolve the way it interprets delay. Not with new jargon or fashionable tools, but with an approach grounded in the actual behaviour of linear construction.