Your Baseline Is Broken.
How to Approach The Recovery Schedule When Regional Conflict Has Rewritten Your Project Reality
There is a specific kind of meeting that project directors across the GCC are having more frequently in 2026. The baseline schedule is on the screen. The current progress data is also on the screen. The gap between the two has grown to the point where it can no longer be managed through float, resequencing, or optimistic reporting. The programme is in distress. And the question on the table is no longer how to recover lost time on paper, but whether the team has the analytical rigour, contractual standing, and strategic clarity to build a recovery schedule that will actually hold.
The ongoing conflict between the United States, Israel, and Iran has introduced a category of disruption that most GCC project baselines were not written to absorb. Supply chains passing through or near contested maritime corridors have fractured. Specialist subcontractors from Europe and North America have demobilised or slowed mobilisation citing force majeure. Material lead times for steel fabrication, mechanical equipment, and specialist electrical components have extended by weeks and, in some cases, months. Labour access assumptions built into programmes eighteen months ago no longer reflect the operational reality on the ground.
In that context, recovery scheduling has become one of the most consequential disciplines in GCC project management. Not because delays are new, but because the scale, simultaneity, and contractual complexity of the current disruption demands a level of analytical and strategic sophistication that routine schedule updates were never designed to provide.
A recovery schedule built on the same assumptions that broke the baseline is not a recovery. It is a postponement of the same conversation, with higher stakes and less time.
Recovery scheduling is widely misunderstood, and that misunderstanding becomes most damaging precisely when the pressure to produce a recovery schedule is highest. In many organisations, the instruction to prepare a recovery schedule is interpreted as a request to compress the remaining programme until it shows an acceptable completion date. Activities get squeezed. Logic gets overridden. Resource assumptions become aspirational rather than realistic. The resulting document satisfies a governance requirement while solving nothing.
The MDPI peer-reviewed analysis of construction delay analysis techniques, reviewing decades of academic literature and industry practice, identifies the core failure mode in construction schedule recovery as the disconnect between the delay analysis that precedes a recovery schedule and the schedule logic that governs it. Organisations that treat recovery scheduling as a presentation exercise rather than an analytical one consistently produce programmes that fail again, at which point the contractual and commercial consequences become substantially harder to manage.
In a conflict-disrupted environment, the analytical prerequisites for a credible recovery schedule are more demanding than in routine delay situations. The disruption is not a single, bounded event with a known end date. It is an evolving operational environment with multiple simultaneous causes of delay, some of which are ongoing, some of which have cascading secondary effects, and some of which have not yet fully materialised. A recovery schedule that does not account for this dynamic nature is structurally compromised from the moment it is submitted.
Three analytical foundations are non-negotiable before a recovery schedule can be credibly constructed in the current GCC environment. First, a thorough and forensically documented delay analysis must establish what has actually happened to the programme, cause by cause, period by period, with contractual notices and contemporaneous records to support each position. Second, a realistic forward-looking risk assessment must identify which disruptions are ongoing, which have been resolved, and which are reasonably foreseeable given the current conflict trajectory. Third, the recovery measures proposed must be grounded in actual resource availability, actual procurement lead times, and actual site productivity rates, not theoretical acceleration factors applied to satisfy a target date.
One of the most costly errors GCC project teams make in conflict-related delay situations is treating the recovery schedule as a purely operational document. It is not. A recovery schedule submitted in a distressed programme context is simultaneously a contractual instrument, a commercial statement, and in many cases, the foundation of a future claim or defence against a claim. How it is constructed, what it concedes, what it reserves, and how it characterises the causes of delay all carry legal and financial implications that extend well beyond the project controls function.
Under FIDIC forms, which remain the dominant contract structure across GCC infrastructure and energy programmes, the Engineer’s determination of time and cost entitlement following a delay event depends substantially on the contemporaneous record and the reasonableness of the recovery measures proposed. A recovery schedule that accepts full programme responsibility for delays caused by conflict-related supply chain failure, without reserving the contractor’s entitlement under force majeure or change of law provisions, can inadvertently close off legitimate cost recovery claims. Equally, a recovery schedule that proposes acceleration measures without securing the client’s instruction and agreement on additional cost creates a risk of uncompensated acceleration that has destroyed contractor margins on programmes across the region.
The recovery schedule must therefore be prepared in close coordination between the planning function, the contract management team, and legal advisors where the stakes warrant it. The document needs to do several things simultaneously: demonstrate a credible path to completion, protect existing contractual entitlements, and avoid inadvertently conceding positions that have not been formally agreed.
The most expensive recovery schedule is the one prepared in isolation by the planning team, submitted without commercial review, and used six months later as evidence against the party that produced it.
McKinsey’s analysis of capital project schedule acceleration, drawing on projects across infrastructure, energy, and heavy industry, is direct on the sequencing question: schedule fundamentals must be addressed before recovery measures are applied. As the McKinsey article on controlling capital project duration and cost notes, teams that attempt to accelerate a programme built on a flawed or disconnected schedule simply compound the underlying dysfunction. The correct sequence is to stabilise the schedule logic first, then apply recovery measures against a reliable foundation.
In the GCC context of 2026, this means working through a specific sequence of actions before the recovery schedule is formally produced:
Several characteristics of the current disruption environment create particular complications for GCC recovery scheduling that deserve direct attention.
The first is the multiplicity of concurrent delay causes. Most delay analysis methodologies were designed for programmes where disruptions occur in relative sequence and can be isolated for analysis. The current environment has produced simultaneous disruptions across supply chain, labour, regulatory, and site access domains. Establishing a clear, auditable causal chain for each delay impact requires more rigorous analytical discipline than a conventional recovery schedule process. The forensic delay analysis must precede the recovery programme, not be produced alongside it under time pressure.
The second is the ongoing and unresolved nature of the conflict. A recovery schedule prepared in March 2026 cannot assume that the supply chain conditions of March 2026 will persist unchanged through to completion. The programme must be tested against scenarios in which the conflict escalates, the Strait of Hormuz faces further restriction, or additional sanctions affect material availability. Recovery schedules that have no scenario modelling built into their foundations are brittle documents that will require revision the moment the conflict conditions change again.
The third is the relationship between the recovery schedule and the contractor’s ongoing entitlement to extensions of time and additional cost. In a prolonged conflict-related disruption, the contractor’s entitlement is not a single historical claim but a rolling commercial position that must be managed in real time. Recovery scheduling must be integrated with active contract administration, not treated as a separate planning exercise that the commercial team picks up afterwards.
A recovery schedule that will withstand scrutiny from the Engineer, the client, a dispute resolution panel, or a future arbitration tribunal shares several characteristics that distinguish it from the governance-satisfying documents most distressed programmes produce.
It is grounded in forensic analysis, not assertion. Every day of delay claimed has a cause that is documented, dated, and supported by contemporaneous records. The analysis methodology is disclosed and defensible under recognised standards.
It is realistic about resources. Every acceleration measure proposed is supported by evidence of resource availability. Labour productivity assumptions are based on current site performance data, not historical benchmarks from a pre-conflict market.
It is honest about risk. The programme includes quantified contingency against ongoing and foreseeable conflict-related disruption. It does not model a path to completion that assumes the current risk environment resolves within a timeframe that cannot be justified.
It is commercially aligned. The recovery schedule is prepared and reviewed with full awareness of the contractual positions it supports or undermines. Entitlements are reserved, obligations are clearly defined, and the document is produced as part of an integrated contract management and planning process.
This is the standard that Kairos’s insight on Construction Schedule Management: The Art and Science of Recovery Schedule Construction addresses in practical terms: recovery scheduling as a diagnostic tool, a negotiation instrument, and a forecasting engine, rather than a revised Gantt chart produced to satisfy a steering committee. In a conflict-disrupted environment, that distinction carries a commercial value that is difficult to overstate.
The GCC’s distressed programmes of 2026 will test project organisations in ways that go well beyond their technical scheduling capability. The quality of their forensic analysis, the discipline of their contemporaneous records, the integration of their planning and contract management functions, and the honesty of their resource assumptions will all determine whether their recovery schedules actually deliver recovery, or simply defer the same conversation to a more expensive and contentious forum.
The organisations that approach recovery scheduling in the current environment with genuine rigour, contractual awareness, and realistic forward-looking modelling will not only improve their probability of programme recovery. They will protect their commercial positions, preserve client relationships, and build the kind of institutional capability that makes the next disruption, and there will be a next disruption, substantially less damaging.
The current conflict has not created the vulnerabilities it is exposing. It has simply made them impossible to ignore.
Work With Kairos
Kairos is a Dubai-registered, digital-first project management consultancy with over 20 years of frontline delivery experience across the GCC and beyond. Our Project Control Solutions and Contract Management Solutions are built for exactly the environment you are operating in now: complex, disrupted, and commercially high-stakes. If your programme is in distress, or if you want to ensure it does not reach that point, we can help. Contact the Kairos team to arrange a discovery workshop, or have a look at our recovery scheduling and project controls capability.