Managing a $2B Infrastructure Dispute Timeline

Construction disputes in the Middle East operate at a scale and complexity that few other categories of litigation can match. The projects are enormous — highways spanning hundreds of kilometres through desert terrain, tunnels bored beneath cities expanding at breakneck pace, airports designed to handle tens of millions of passengers. The contracts are commensurately complex, governed by bespoke amendments to FIDIC conditions, with multiple layers of subcontracting, joint ventures, and government oversight. When these projects go wrong — as they inevitably do, given the technical challenges, the extreme climate, and the compressed timelines — the resulting disputes can involve dozens of parties, thousands of documents, and claims measured in the hundreds of millions or even billions of dollars.

The dispute that brought a prominent regional law firm to Juristic was precisely this kind of case. A $2 billion highway and tunnel project — connecting two rapidly growing cities across terrain that included desert, mountains, and a major river crossing — had fallen behind schedule by nearly two years. The main contractor, a joint venture between a European construction group and a local partner, alleged that the delays were caused by the employer's failure to provide access to key sections of the route, design changes imposed mid-construction, and interference by government authorities that disrupted the planned sequence of works. The employer counterclaimed, alleging that the contractor's own mismanagement and subcontractor failures were the true cause of delay.

The disputes team engaged by the contractor comprised eight lawyers — three partners and five associates — supported by a claims consultant and two paralegals. The team was experienced in Middle Eastern construction arbitration, but the scale of this matter exceeded anything they had previously handled. The factual record was vast: five years of project execution had generated site diaries for every section of the route, variation orders numbering in the hundreds, payment certificates, delay notices, extension-of-time claims, correspondence between the contractor and the engineer, correspondence between the engineer and the employer, internal project reports, photographs documenting progress and defects, and minutes from weekly and monthly project meetings.

The document volume was estimated at over 40,000 individual files. The chronology — the backbone of any delay and disruption claim — needed to trace not just what happened and when, but who knew what at each point in time. In construction arbitration, the question of knowledge is often decisive: did the employer know that its design changes would cause critical-path delay? Did the engineer certify extensions of time promptly, or did delays in certification compound the contractor's cash-flow difficulties? Did the subcontractors notify the main contractor of the problems they were encountering, and did the main contractor act on those notifications?

Under the team's traditional approach, building this chronology would have been a monumental undertaking. Past practice involved assigning junior associates to read through document bundles — organised by category and date range — and extract key events into a master Excel spreadsheet. The spreadsheet would then be reviewed and enriched by more senior lawyers, who would add legal context, flag inconsistencies, and identify gaps in the factual record. On previous matters of this scale, the chronology phase alone had taken four to five months and consumed the full-time attention of three to four associates.

The lead partner was not willing to accept that timeline. The arbitration was proceeding under institutional rules with a fixed procedural calendar, and the first memorial was due in eight months. Four to five months on the chronology would leave barely enough time for the legal analysis, quantum assessment, and memorial drafting that would follow. The partner had heard about Juristic Timeline from a colleague who had used it on a London-seated arbitration and decided to evaluate it for this matter.

The evaluation was pragmatic rather than theoretical. The team uploaded a subset of the document set — roughly 5,000 files covering the first year of project execution — and used Timeline to build a chronology for that period. The results were encouraging: events could be plotted on a visual timeline, tagged by party, filtered by category, and linked directly to source documents. The associates who worked on the pilot were enthusiastic, noting that the visual representation of events made it far easier to spot patterns and gaps than the traditional spreadsheet approach.

The full migration followed. Over a three-week period, the team uploaded the complete document set and began building the five-year chronology in Timeline. Events were tagged along multiple dimensions: by party (employer, contractor, engineer, each of the seven subcontractors, government authorities), by claim head (delay, disruption, variation, defect, payment), and by project phase (mobilisation, earthworks, tunnelling, road construction, commissioning). Each event was linked to its source document — or, in many cases, multiple source documents — and witnesses were tagged against the events they could speak to.

The multi-layered tagging system proved to be Timeline's most powerful feature for this type of dispute. The team could filter the chronology to tell different stories depending on the argument being developed. To demonstrate the employer's knowledge of delays, they filtered for all events involving the employer and tagged as delay-related — producing a focused narrative that showed the employer receiving delay notifications, acknowledging access problems, and yet failing to grant extensions of time. To assess a particular subcontractor's performance, they filtered for that subcontractor's events alongside the relevant section of the route, revealing a pattern of late mobilisation and resource shortages that the main contractor had flagged repeatedly in site meeting minutes.

The ability to zoom into specific time periods was equally valuable. Construction disputes often hinge on what happened during particular windows — the period between a variation instruction and the resulting delay, or the gap between a payment application and its certification. Timeline allowed the team to isolate these windows with precision, examining every event that occurred within the relevant period and tracing the causal chain from instruction to impact. This granular analysis, which would have been extremely difficult to conduct in a spreadsheet, became almost intuitive in Timeline's visual interface.

Witness preparation was transformed. In traditional practice, preparing a witness for a construction arbitration involves walking them through the relevant documents — often hundreds of pages — to help them recall events and confirm their account. With Timeline, the team could show each witness the chronology filtered to include only the events they were involved in, displayed on a visual timeline with links to the underlying documents. Witnesses found it far easier to orient themselves in the factual narrative and to recall details that they might otherwise have forgotten. One project manager, who had been involved in the earthworks phase, identified two critical delay events during his preparation session that the team had not previously included in the chronology — events that proved material to the contractor's extension-of-time claim.

The hearing itself was where Timeline delivered its most dramatic impact. The arbitration was conducted before a three-member tribunal, with hearings held over four weeks in a neutral venue. The team had prepared a Timeline presentation that could be projected during oral submissions, allowing counsel to navigate the five-year chronology in real time. When the tribunal asked a question about a specific period — 'What was happening on the tunnel section between March and June of the third year?' — counsel could zoom into that period within seconds, displaying every relevant event with links to source documents. When opposing counsel made a factual assertion that contradicted the chronology, the team was able to pull up the relevant entries and source documents in real time, rebutting the assertion on the spot.

The tribunal chair — a retired judge with decades of experience in construction disputes — commented during the hearing that the contractor's factual presentation was 'the most organised factual case I have encountered in construction arbitration.' The compliment was directed at the team's preparation, but the partners acknowledged privately that Timeline was the foundation on which that preparation was built.

The quantitative impact was substantial. The lead partner estimated that the team saved approximately four months of preparation time compared to the traditional spreadsheet-based approach. This time saving was not merely a matter of efficiency — it allowed the team to invest more in legal analysis and memorial drafting, resulting in submissions that the partners believed were of a higher quality than they could have achieved under the compressed timeline that traditional chronology methods would have imposed.

The qualitative impact was perhaps even more significant. Several junior associates who worked on the matter described Timeline as a tool that made them better lawyers — not just more efficient ones. The visual representation of the dispute's factual narrative forced them to understand the case at a depth that spreadsheet-based chronologies never achieved. They could see the patterns, the gaps, the contradictions, and the causal chains in a way that rows and columns simply did not allow. One associate noted: 'For the first time, I felt like I truly understood the story of this project — not just the legal arguments, but what actually happened on the ground, month by month, event by event.'

The matter is ongoing as of this writing, with the tribunal's award expected in the coming months. Regardless of the outcome, the firm's disputes practice has adopted Timeline as its standard chronology tool for all construction and infrastructure matters. The lead partner, who has practiced Middle Eastern construction arbitration for over twenty years, describes the adoption as 'the most significant change in how we prepare cases since I began practice. We are not going back to spreadsheets. That chapter is closed.'