FIDIC Arbitration: Concurrent Delay, Variations and Forensic Schedule Analysis

Short answer: A FIDIC delay claim is not proved by showing that a project finished late. The claimant must connect a contractual event to critical-path delay, satisfy notice and records requirements, distinguish employer risk from contractor risk and prove the time and cost consequences. When an employer-caused event overlaps a contractor delay, the tribunal must decide what the contract says about concurrency, which delay actually affected completion and whether the contractor can recover time, money or both. A credible forensic schedule analysis can answer those questions; an attractive colour-coded programme cannot.

In a UAE-seated FIDIC arbitration, the contract’s Particular Conditions, governing law, dispute-board history and selected institutional rules matter as much as the General Conditions. DIAC Rules 2022 give the tribunal control over evidence and expert work. Federal Arbitration Law permits expert assistance, witness evidence by modern communications and court assistance with evidence. The FIDIC 2017 Red Book also emphasises clearer notices, equal claims procedures, dispute avoidance and project records, while leaving important concurrency treatment to the contract’s Special Provisions.

This article explains how to analyse concurrent delay, variations, extensions of time, disruption and prolongation costs, how to choose a forensic schedule method and how to present the case in UAE arbitration. It is written for employers, contractors, engineers, consultants, project managers, quantum experts and counsel; it is not a substitute for advice on a live FIDIC dispute.

Contents

1. Start with the FIDIC contract architecture
2. Claims, notices and the Engineer’s determination
3. What is concurrent delay?
4. Time entitlement and cost entitlement are separate
5. Variations and their effect on time
6. Forensic schedule analysis methods
7. Records, updates and critical-path proof
8. DIAC arbitration, evidence and experts
9. Prolongation, disruption and quantum
10. Worked scenarios
11. Practical checklist
12. Frequently asked questions

1. Start with the FIDIC contract architecture

Which FIDIC edition and which Particular Conditions?

“FIDIC contract” is not a complete answer. The legal analysis changes between the 1999 and 2017 editions, the Red, Yellow and Silver Books, the Particular Conditions, Employer’s Requirements, technical schedules and amendments negotiated for the project. Identify the edition, contract data, Special Provisions, governing law, dispute-board mechanism, arbitration clause and order of precedence before analysing the programme.

FIDIC’s official materials describe the 2017 Red Book as providing greater detail on notices and communications, separate treatment of employer and contractor claims, dispute-avoidance mechanisms and stronger quality and verification procedures. The Particular Conditions remain essential: FIDIC itself notes that project-specific information and special procedures should be placed there, with legal and engineering advice used to avoid ambiguity.

Map the time and claims machinery

Build a clause map showing:

• Time for Completion, programme and update obligations;
• extension-of-time events and the contractor’s notice requirements;
• Employer-risk events, Exceptional Events and relief for authorities or utilities;
• variations, valuation rules and any limits on omissions or additions;
• Engineer instructions, determinations, consultation and dispute escalation;
• concurrency wording in the Special Provisions;
• delay damages, acceleration and suspension provisions;
• record-keeping, contemporary records and access to site data; and
• DAAB/DAB, mediation and arbitration jurisdiction, seat and rules.

A tribunal will not treat a programming convention as a contractual entitlement. A critical-path analysis can show impact, but the contract determines whether that impact gives an extension, additional payment, both or neither.

2. Claims, notices and the Engineer’s determination

Notice is part of the entitlement analysis

FIDIC claims clauses are designed to identify delay and cost while the project is still developing. The contractor should give a notice of a potential claim within the contractual period, identify the event and preserve the right to submit particulars. The employer or Engineer should respond under the agreed procedure rather than leaving the issue until final completion.

Late notice can become a jurisdictional, contractual-bar or evidential issue. The result depends on the edition, Particular Conditions, governing law, wording of the notice clause and conduct of the parties. An employer that knew of the event may still argue that the contract made notice a condition; a contractor may argue waiver, prevention, estoppel or that the notice requirement was not triggered. Do not assume one universal FIDIC answer.

Contemporary records and continuing delay

A continuing event may require an initial notice followed by regular updates as the effect becomes clearer. The claim should distinguish the date of the event, the date of impact, the period of critical delay and the date when mitigation or a new event changed the analysis.

At minimum, preserve daily reports, instructions, RFIs, submittal logs, inspection requests, access records, labour and plant returns, delivery records, weather data, photographs, progress measurements, meeting minutes, updated programmes, payment certificates and correspondence about mitigation. A narrative written years later is rarely as persuasive as a contemporaneous record that identifies the affected activity and expected consequence.

Engineer’s determination is evidence, not the end of the case

The Engineer may make a determination or assessment under the FIDIC mechanism. The tribunal will examine the contract, facts and evidence independently unless the parties agreed a binding effect. The Engineer’s reasoning can be important, especially if it records contemporaneous acceptance of an event, but a tribunal may correct an unsupported methodology or a determination made without the required consultation.

3. What is concurrent delay?

Concurrent delay generally describes two delay events operating during the same period, one attributable to the employer or another risk accepted by the employer and one attributable to the contractor, with each capable of affecting completion. The phrase is not self-defining. The tribunal must consider causation, criticality, timing, contractual responsibility and the relevant concurrency rule.

True concurrency versus sequential delay

Suppose a contractor is already six weeks late because it failed to mobilise labour. The employer then issues a late design instruction that would have delayed completion by four weeks if the contractor had been on programme. The events overlap in time, but the employer may argue that the design instruction did not extend the actual completion date because the contractor’s prior delay consumed the available float. Conversely, if the design instruction affected the only remaining critical path and pushed the forecast completion beyond the contractor delay, the contractor may establish an extension for the incremental period.

Concurrency is not automatically a 50/50 split

Some contracts or governing laws support a “time but no money” approach, apportionment, prevention principles or a more event-specific analysis. Others provide a negotiated concurrency clause. The tribunal should not divide delay or damages evenly simply because two causes are present. It should apply the agreed wording and explain the causal connection between each event and each head of relief.

FIDIC and Special Provisions

FIDIC’s official commentary on the 2017 edition notes that Sub-Clause 8.5 refers to concurrency and leaves the assessment to the rules and procedures stated in the Special Provisions. That is a drafting signal: concurrency should be addressed expressly at contract stage. The parties should define the relevant period, criticality test, entitlement to time, entitlement to cost and preferred schedule methodology rather than rely on a short label.

4. Time entitlement and cost entitlement are separate

Extension of time

An extension-of-time claim asks whether an event delayed contractual completion and whether the contractor is entitled to move the Time for Completion. The analysis focuses on the accepted programme, critical path, logic, available float, actual progress, mitigation and the effect of competing events.

Prolongation cost

Prolongation cost asks a different question: did the event cause additional time-related cost, and is that cost recoverable under the contract? A contractor may obtain time but no cost under a concurrency clause, or obtain cost only for the period and resources caused by an employer event. Site overheads, head-office overheads, financing, supervision, plant, accommodation, insurance and escalation require separate proof.

Disruption

Disruption is loss of productivity or inefficiency, not simply delayed completion. A variation may force resequencing, out-of-hours work, stacking of trades, repeated mobilisation or loss of planned learning. A contractor should identify the baseline productivity assumption, the change in working conditions, the affected activities and a reliable causal method. A global claim that compares tender labour to final labour without linking the difference to specific events is vulnerable.

Acceleration

Acceleration may be instructed, constructive or voluntary. The claimant must prove the original completion risk, the instruction or conduct requiring acceleration, the measures taken, the cost incurred and the absence of an alternative explanation such as contractor inefficiency. A programme showing recovery is not itself proof that the employer authorised or caused the acceleration.

5. Variations and their effect on time

Identify the variation and its instruction path

Every variation analysis should connect the scope change to an instruction, drawing revision, site direction, request for quotation, Engineer determination or other contractual mechanism. Record the date, description, affected quantities, changed sequence, resources and valuation basis. A contractor should not quietly perform additional work and then assume entitlement to time and money without complying with the claims procedure.

Three different time effects

Omission and replacement work

FIDIC variation powers are not unlimited. An omission may be challenged if it removes work to be performed by another contractor or changes the fundamental bargain, depending on the edition and Particular Conditions. A variation analysis should examine the scope, pricing rules, valuation, procurement consequences and whether the Engineer acted within authority.

Variation notices and schedule updates

Do not wait for the final account to explain a variation’s time effect. Submit a contemporaneous impact assessment, identify assumptions and update it as design information develops. If the variation is not sufficiently defined, state what is known, what is uncertain and what records will be maintained to quantify the effect.

6. Forensic schedule analysis methods

No single method is automatically correct. The tribunal should choose a method that fits the available records, contract, project complexity, reliability of the baseline and timing of the analysis. The expert should explain why the chosen method is suitable and what limitations affect the conclusion.

Choose the method after testing the records

An expert should not select a preferred method because it produces the most favourable result. First test the baseline, updates, logic, actual progress records, calendars, constraints, resource data and change log. If the baseline is not contemporaneous or the updates contain unexplained logic changes, a windows analysis may require reconstruction or a different approach.

Critical path is dynamic

The critical path can change as work progresses. A path that was critical at tender may not be critical after a resequencing, acceleration effort or design change. A tribunal should be cautious about a static baseline path used to explain the whole project. Analyse the status date immediately before and after each event, then test whether the event actually moved the forecast or actual completion.

Float and ownership

Float is not automatically owned by the contractor or employer. The contract and programme methodology may address float, but the expert should explain whether the event consumed total float, free float, a time risk allowance or an unallocated contingency. A delay to a non-critical activity may become critical later; a delay to a critical activity may be absorbed by available float.

7. Records, updates and critical-path proof

Programme quality checklist

• baseline approved or at least submitted with a clear status date;
• logic ties, calendars, constraints and activity codes are consistent;
• updates show actual starts, actual finishes, remaining duration and forecast logic;
• progress data is supported by daily reports, quantities, inspections and payment records;
• changed logic is documented rather than silently overwritten;
• critical-path and near-critical activities are identified for each status date;
• variations and delay events are coded consistently across the programme;
• mitigation, recovery, acceleration and resequencing are recorded; and
• the expert can trace each conclusion to a source record.

Do not hide the bad update

Deleting or overwriting a programme can damage credibility. Preserve the original native file, PDF export, transmittal email and schedule calculation report. If an update was defective, explain the defect and reconstruct the analysis transparently. A tribunal is more likely to trust an expert who identifies limitations than one who presents a perfect retrospective programme with no source history.

Contemporaneous analysis versus retrospective opinion

A contemporaneous analysis prepared when the project was live may be strong evidence of what the parties understood at the time, but it is not automatically correct. A retrospective analysis may benefit from complete project data, but it risks hindsight. Use both where available: compare what the team believed then with what the records show now and explain the reasons for any difference.

8. DIAC arbitration, evidence and experts

DIAC Article 25 places the burden of proving facts on the party relying on them. The tribunal determines evidence rules, the timing and format of exchange, admissibility, relevance, materiality and weight. It may order production of documents, exhibits, information or property in a party’s possession or control and may require inspection or testing by the tribunal, a tribunal-appointed expert or another party.

DIAC Article 28 permits the tribunal to appoint independent experts on specific issues, communicate the terms of appointment, require relevant information or documents for inspection, and give parties an opportunity to comment on the report. A delay expert should therefore have a defined scope, access protocol, source-data schedule and a clear method for resolving disagreements about the programme model.

Federal Arbitration Law Article 34 similarly permits tribunal-appointed experts to seek information, documents, goods or property for inspection and requires the expert report to be shared with the parties. Article 35 permits witness and expert testimony by modern communications. Article 36 allows court assistance in taking evidence where tribunal powers need judicial support.

Present the schedule model as evidence

Do not leave the tribunal with an unexplained computer model. Provide a concise methodology statement, model assumptions, programme versions, event matrix, critical-path extracts, sensitivity tests and a list of excluded or uncertain records. Demonstrate how the model changes if a disputed event is removed, shifted or treated as concurrent.

Cross-examination themes

• Was the baseline accepted, realistic and contractually required?
• Were updates prepared contemporaneously or reconstructed for the arbitration?
• Did the expert use actual progress or only planned dates?
• How were changed logic, constraints, calendars and out-of-sequence work treated?
• How did the expert distinguish employer delay, contractor delay and neutral events?
• Was the same delay counted in both time and disruption calculations?
• Were mitigation and acceleration assumed without proof?
• What evidence supports the claimed critical path and completion date?

9. Prolongation, disruption and quantum

Time-related costs

Prolongation costs should be tied to the compensable period established by the schedule analysis. Separate site overheads, supervision, staff, accommodation, equipment, security, insurance, financing and head-office allocations. Explain whether each cost was actually incurred, already included in another claim or caused by a concurrent contractor event.

Measured mile and productivity evidence

For disruption, a measured-mile comparison may compare productivity in an unaffected period or area with productivity during the affected work. The expert should show comparability of crews, work type, access, design maturity, weather, learning curve, quantities and supervision. A simple “planned hours versus actual hours” calculation is not enough if the plan was unrealistic.

Global claims

A global claim aggregates multiple employer events and asks for a total loss without allocating each cost to each cause. It may be accepted in limited circumstances where causation cannot reasonably be separated, but it is risky where contractor delay, subcontractor default, market conditions or defective records provide alternative explanations. Build a cause-and-effect matrix and explain why allocation is impossible or disproportionate.

Delay damages and mitigation

Delay damages or liquidated damages require a correct contractual completion date after valid extensions. An employer should not apply damages without considering accepted or proven EOT entitlement. A contractor should document mitigation, but mitigation does not automatically waive the original delay claim. The tribunal should analyse what reasonable measures were available, their cost and whether they reduced the critical delay.

10. Worked scenarios

11. Practical checklist for FIDIC arbitration

• Confirm the FIDIC edition, book, Particular Conditions, governing law, seat and arbitration rules.
• Build a clause matrix for notices, EOT, variations, records, concurrency, delay damages, acceleration and dispute escalation.
• Preserve every native programme, update, schedule report, transmittal, instruction and data date.
• Maintain a live event register showing cause, responsible risk, affected activity, notice, mitigation and current forecast.
• Separate direct delay, disruption, acceleration and prolongation rather than combining them without explanation.
• Test whether the baseline was accepted, contractually compliant and realistically resourced.
• Analyse the critical path at each relevant status date, not only at tender and completion.
• Identify concurrent contractor, employer, neutral and subcontractor events and avoid double counting.
• Agree the forensic methodology early or explain why the selected method fits the available records.
• Give the delay and quantum experts the same event chronology and document index.
• Use DIAC evidence and expert provisions to obtain targeted documents, inspections and reasoned expert reports.
• Preserve notice, Engineer determination, DAAB/DAB, settlement and arbitration deadlines separately.
• Present a sensitivity analysis showing how the result changes if disputed events are treated as concurrent or non-critical.
• Ask the tribunal for a reasoned determination of the contractual concurrency rule before modelling damages.

12. Frequently asked questions

Does concurrent delay automatically defeat an extension of time?

No. The answer depends on the FIDIC edition, Particular Conditions, governing law and the proven critical-path effect. Some contracts grant time but restrict cost; others provide an apportionment or a specific concurrency rule. The tribunal must apply the contract rather than assume a universal rule.

Is an employer variation automatically an extension-of-time event?

Not automatically. The variation must be authorised, within the contract’s scope and shown to affect completion or another contractual milestone. A variation that is absorbed by float or does not affect the critical path may change price without changing the Time for Completion.

Which forensic schedule method is best?

There is no universal winner. Windows analysis is often persuasive where reliable updates exist; time-impact analysis is useful for contemporaneous assessment; impacted as-planned can help where actual data is limited; and as-built but-for analysis may assist retrospective disputes. The expert should justify the method against the records and contract.

Can a contractor recover cost while also being in delay?

Possibly, but the contractor must prove that the employer event caused the compensable cost and that the contract does not bar or limit recovery during concurrency. A contractor’s culpable delay may reduce, overlap with or defeat particular heads of cost even where an employer event gives time relief.

What if the programme was never approved?

An unapproved programme is not automatically irrelevant, but its evidential weight depends on the contract and conduct. Use contemporaneous updates, accepted schedules, progress records, payment evidence and witness testimony to establish the planned sequence and actual critical path.

Can a tribunal appoint its own delay expert?

Yes, subject to the applicable law and rules. DIAC Article 28 and Federal Arbitration Law Article 34 allow tribunal-appointed experts, require defined tasks and provide parties an opportunity to comment on the report. The tribunal should avoid delegating the legal interpretation of the contract to the expert.

What is the difference between delay and disruption?

Delay concerns time to completion or a milestone. Disruption concerns reduced productivity or inefficiency, which may occur without extending completion. A claim should prove each separately and avoid counting the same labour, plant or overhead loss twice.

Does a DAAB/DAB decision end the dispute?

It depends on the FIDIC edition, contract wording, notice of dissatisfaction and subsequent arbitration procedure. A party must preserve the contractual deadline for challenging or referring the decision. The board’s decision may remain binding on an interim basis even while the underlying merits are arbitrated.

Conclusion

FIDIC delay arbitration is won or lost in the interface between contract wording, project records and schedule logic. Concurrent delay is not a slogan, a 50/50 compromise or a reason to ignore the critical path. Variations must be tied to instructions, notices, programme effects and measured cost. A forensic schedule analysis must show what the project plan was, how it changed, which event controlled completion and why the claimed relief follows under the contract.

HZ Legal Consultancy advises employers, contractors, consultants and project teams on FIDIC claims, EOT and variation strategy, DAAB/DAB referrals, DIAC arbitration, forensic schedule evidence, disruption and prolongation quantum. Early records and a defensible programme usually matter more than a sophisticated model prepared after the project has ended.

Official sources

• FIDIC Construction Contract 2nd Edition (2017 Red Book), including official notes on notices, claims, dispute avoidance and Particular Conditions.
• FIDIC official article on time under the 2017 Contract, including concurrency and programme records.
• DIAC Arbitration Rules 2022, especially Articles 25 and 28.
• Official UAE Ministry PDF of Federal Law No. 6 of 2018 on Arbitration, including Articles 23 and 33–36.
• Federal Law No. 6 of 2018 on the UAE Legislation platform.

Disclaimer: This article is for general information only and reflects the official materials reviewed on 29 October 2026. It is not legal advice, does not create a lawyer–client relationship and may not address the edition, Particular Conditions, governing law, records or procedural history of a particular FIDIC project. Obtain UAE-qualified legal and delay-expert advice before serving a claim notice, accepting a determination or commencing arbitration.