Construction software needs construction knowledge

Why Most EOT Claims Fail

In my experience on FIDIC Red Book contracts in Bahrain and the wider GCC, the majority of EOT claims that get disputed or rejected share one common weakness: they describe the delay but don't prove causation. The Engineer needs a clear, unbroken chain from the Employer risk event to the critical path impact on the Completion Date. If that chain has any gaps, the claim is vulnerable.

FIDIC Sub-Clause 20.1 is strict on timing: the Contractor must give notice of a claim within 28 days of becoming aware of the event. Missing this window doesn't automatically kill the claim, but it significantly weakens your position and gives the Engineer grounds to reduce the extension. On every project I manage, we track potential delay events from day one.

The Five Elements Every EOT Claim Must Have

• Contractual entitlement: Identify the specific Sub-Clause that gives you the right to an extension: 8.4(b) for Employer-caused delays, 8.4(e) for unforeseeable conditions, 19.1 for Force Majeure events. Never build a claim on implied entitlement.
• The delay event, precisely defined: State the exact date the event started, the date you gave notice, and the date the event ended or was resolved. Attach the correspondence chain as annexures.
• Critical path proof: Run your TIA in Primavera P6. The baseline programme matters here: if you don't have an Engineer-accepted baseline, your impacted programme is automatically suspect. Show exactly which activities were delayed, how they sit on the critical path, and the resulting float consumption.
• Contemporaneous records: Daily reports, site diaries, RFI logs, drawing issue registers, and inspection request (IR) logs. These are your evidence. If it isn't in writing at the time, it didn't happen as far as the contract is concerned.
• Quantum: Under FIDIC, EOT and cost claims are linked but submitted separately. The extension claim should focus on time; a concurrent Section 20.1 cost claim handles the financial impact. Don't mix them in a way that lets the Engineer reject the whole submission on a technical ground.

The Most Common Mistakes I See

• Claiming concurrent delays from Employer and Contractor causes in the same period without separating them: this opens the door to apportionment arguments that reduce your entitlement.
• Narrative-heavy, evidence-light submissions. Three pages of complaint and two pages of P6 screenshots is not a claim. Reverse that ratio.
• Failing to reserve the right to claim additional cost when submitting the time extension. Under FIDIC 1999, if you don't reserve rights properly, you may be deemed to have settled for time alone.

One Final Piece of Advice

Treat your EOT claim as a legal document from the moment you start writing it. Every sentence should be something you're prepared to defend in a Dispute Adjudication Board (DAB) hearing. If you write it with that standard in mind, you'll naturally produce a submission the Engineer finds difficult to dismiss.

What TIA Is Actually Measuring

Time Impact Analysis works by inserting a delay fragment (a fragnet) into the accepted programme at the point in time when the delay event occurred, then measuring the resulting push to the critical path and the Completion Date. Done correctly, it answers the question: if this specific event had not occurred, when would the project have completed?

The critical word is "accepted." Under MoW Bahrain CoC 2009 and FIDIC Red Book, the baseline programme must be formally accepted by the Engineer before it can anchor a TIA. On a recent Capital Waterfront project I worked on, we had 20 delay events to analyse, and the strength of each analysis traced directly back to the acceptance status of our baseline.

What P6 Can Prove

• Critical path status at the time of the delay: P6 shows whether the activity impacted by the delay was on the critical or near-critical path at the data date of the delay event. This is fundamental: delaying a non-critical activity with 45 days of float doesn't move the Completion Date.
• Float consumption: If the delay event consumed all available float on an activity chain, pushing subsequent activities onto the critical path, this is visible and auditable in P6.
• Impacted vs. as-built: By comparing the impacted programme against actual progress, you can isolate which delays are attributable to Employer risks and which reflect Contractor performance. This separation is critical when concurrent delays are alleged.

What P6 Cannot Prove (And Where Claims Fall Apart)

• It can't prove causation without contemporaneous records. P6 can show that a delay started on a particular date, but the Engineer will ask: "How do I know this was caused by the Employer's late drawing issue and not by your own resource shortage?" The answer lives in your RFI log, drawing transmittal register, and daily reports, not in P6.
• It can't repair a compromised baseline. If your baseline was submitted late, never formally accepted, or significantly revised without the Engineer's knowledge, your TIA is building on sand. I've seen technically brilliant analyses dismissed because the baseline couldn't be defended.
• It can't resolve concurrent delay disputes automatically. When both Employer and Contractor delays overlap, P6 will show the combined impact, but determining the respective entitlements requires legal and contractual analysis, not just scheduling software.

The Baseline Problem in GCC Contracts

MoW Bahrain CoC 2009 Clause 14 requires the Contractor to submit a programme within 14 days of award. In practice, a formally accepted baseline is rare on smaller projects. If you're in this situation, build your case using the as-planned programme alongside progress meeting minutes where the Engineer acknowledged your schedule. Tacit acceptance, consistently documented, is defensible.

What Sub-Clause 4.21 Actually Says

FIDIC Red Book 1999, Sub-Clause 4.21 requires the Contractor to submit monthly progress reports to the Engineer. The clause specifies the minimum required content: charts and detailed descriptions of progress, photographs, details of Contractor's personnel and Equipment on Site, quality assurance documentation, safety statistics, comparisons of actual and planned progress, and details of any events which may jeopardise completion.

The clause does not impose an obligation on the Contractor to resubmit a report simply because the Employer or Engineer requests it, unless there is a specific provision elsewhere in the Contract requiring resubmission after comments.

The Resubmission Question

On a recent project in Bahrain, we received a formal instruction requiring us to resubmit a monthly progress report that had already been submitted in full compliance with Sub-Clause 4.21. The instruction cited "inadequate information", but the items cited were not within the scope of Sub-Clause 4.21's required content.

Our position, set out in formal correspondence, was straightforward: the Contractor's obligation under Sub-Clause 4.21 is to submit a report meeting the specified minimum content requirements, monthly. We had done so. The clause does not create a parallel obligation to resubmit in response to review comments, nor does it give the Engineer power to reject a progress report. This is distinct from documents requiring approval, such as the programme under Sub-Clause 8.3, or method statements, where a review and resubmission cycle is explicitly provided for in the contract.

When You Should Resubmit

There are circumstances where resubmission is the sensible commercial decision even when it isn't strictly required:

• If the alleged deficiency relates to content that genuinely affects the Engineer's ability to assess progress or make decisions affecting payment.
• If you are in an active claim period and the progress report forms part of the contemporaneous record supporting your EOT, in which case accuracy matters more than the principle.
• If resubmission costs you nothing and refusing it damages the relationship at a critical project stage.

How to Respond Without Escalating

The response we used acknowledged the Engineer's comments, confirmed that the submitted report was compliant with Sub-Clause 4.21, noted that we would endeavour to include the additional information in the following month's report as a matter of good practice, and reserved all rights under the contract. This keeps the relationship professional while clearly establishing on record that we do not accept the resubmission instruction as a contractual obligation.

Keeping that on record matters: it prevents the same argument resurfacing in a later dispute and establishes a consistent interpretation of the contract's obligations.

Design-Construction Overlap: The Real Risk

On many GCC projects, especially mixed-use towers and government infrastructure, the design is not fully complete at the time of contract award. This is normal. What isn't normal, but happens constantly, is proceeding without a formal mechanism to track the issuance of Engineer's Instructions (EIs) and their impact on the programme.

The moment the Contractor proceeds on an area without an approved EI, two things happen simultaneously: the work becomes a potential variation dispute, and the clock starts running on a delay event that may never make it into an EOT claim because it wasn't formally noticed at the time.

What I Do Differently Now

• EI tracking register from day one. Every outstanding instruction gets logged with the date requested, the activity it gates, the planned start date, and the float available. When float reaches zero, a formal notification goes to the Engineer the same day.
• Constructive acceleration notices. If the Engineer doesn't issue an EI and the team proceeds to avoid site stoppage, we issue a constructive acceleration letter under Sub-Clause 8.5. This establishes that we are accelerating under protest and at the Employer's cost, not accepting a delay voluntarily.
• Progress meeting minutes as contemporaneous records. At every weekly progress meeting, the outstanding EI register is tabled and the minutes record the status. This creates an unbroken chain of evidence for any future EOT submission.

The Cost of Saying Nothing

The instinct on site is to keep the peace: avoid confrontational letters, proceed with what you can, flag it later. This instinct costs contractors millions across the GCC every year. By the time "later" arrives, there are no contemporaneous records, the delay has been absorbed into concurrent contractor issues, and the Engineer has grounds to reject the claim on multiple fronts.

Issuing a formal notice is not escalation. It is your contractual obligation, and doing it professionally (factual, dated, referenced to the specific clause) is simply good contract administration.

The Excel Problem

Excel is a brilliant tool. I still use it every day. But for generating S-curves on live projects, where the data changes weekly and you need a report-ready output fast, it has three problems. First, the chart formatting is inconsistent across machines and Excel versions, which matters when your report goes to a client with different Office settings. Second, combining Planned, Actual, Earned Value, and Forecast lines in a single clean chart with a proper data table underneath requires more setup time than most site teams can afford mid-project. Third, and most practically: not everyone on the team has a properly configured Excel template.

What the S-Curve Tool Does

The S-Curve Generator on Planix Engineering was built to solve exactly these problems. You enter your period-by-period percentages for Planned, Actual, Earned, and Forecast. The tool generates the cumulative curves automatically, overlays them on a single chart, appends a formatted data table, and lets you download the whole thing as a single image, ready to drop into any progress report.

• No Excel installation required: runs entirely in the browser.
• Four curve types: Planned, Actual, Earned Value, and Forecast.
• Auto-generated data table below the chart: no separate formatting needed.
• Single-image download: the chart and table together, as one file.

The Broader Principle

The best planning tools are ones that get out of your way. They take the mechanical work (the chart formatting, the data calculations, the layout) and handle it so you can focus on the analysis and the narrative that goes alongside it. That's the principle behind everything on Planix Engineering: tools built by someone who uses them, for people who use them on real projects.

FIDIC Sub-Clause 19.1: The Four Criteria

FIDIC Red Book 1999 defines Force Majeure as an exceptional event or circumstance that is beyond a Party's control, which the Party could not reasonably have provided against before entering into the Contract, which having arisen the Party could not reasonably have avoided or overcome, and which is not substantially attributable to the other Party.

All four criteria must be met simultaneously. This is where most disputed FM notifications collapse: the event may be beyond the Contractor's control, but it was foreseeable, or avoidable with reasonable precautions, or partially self-caused.

What I've Seen Work and What Hasn't

• War risk surcharges and JWC area declarations: Where a project's marine supply chain passes through a JWC-designated war risk area, documented rate increases from P&I clubs and hull insurers constitute verifiable FM cost impacts. We used primary source JWC/BIMCO data to support a recent claim. This category typically holds up well because the evidence is from independent, authoritative sources.
• COVID-19 supply chain disruption: Worked on contracts where notice was given promptly and the disruption was specific and documented: particular materials, specific delivery routes, verifiable port shutdowns. Failed where it was used as a catch-all explanation for general programme slippage.
• Regulatory delays by government authorities: Interesting area under FIDIC. If the authority is an Employer-related entity, the FM route may be weaker than a direct Employer delay claim under Sub-Clause 8.4. The correct route depends on how the contract defines "Employer's Personnel" and the relationship between the approval authority and the Employer.

The Documentation Standard

FM claims require the same rigour as any other FIDIC claim, arguably more, because the threshold for what qualifies is higher. Primary source evidence matters: insurance circulars, government authority notices, published index data, official port closure notices. Second-hand references or news articles are not sufficient to anchor a FM claim that will withstand scrutiny in a DAB or arbitration.

What Concurrent Delay Actually Means

Concurrent delay occurs when both an Employer-risk event and a Contractor-risk event are delaying the same critical path activity during the same period. Under English law (which governs most FIDIC contracts in the GCC), the dominant approach is that where there is true concurrency, the Contractor is entitled to an extension of time but not to delay damages, because the Contractor's own delay prevented them from using that time productively.

The key word is "true" concurrency. In practice, the Employer's team often argues concurrent delay where the delays are actually sequential, or where the Contractor delay is on a non-critical path while the Employer delay is critical. Learning to distinguish these is core to defending your EOT position.

How I Approach Concurrent Delay Allegations

• Establish the critical path status of each alleged delay independently. If the Contractor's delay is on a path with positive float while the Employer's event is on the critical path, there is no true concurrency: the Contractor's issue didn't delay the project, only the Employer's did.
• Use as-built data to show sequence, not just overlap. Two delays that overlap in calendar time are not necessarily concurrent if one started before the other and the second only affected activities after the first was resolved. Timeline evidence matters here.
• Document Contractor mitigation efforts during the Employer delay period. If the Contractor resequenced work, deployed additional resources, or accelerated other activities while the Employer's delay was ongoing, this rebuts the argument that Contractor culpability was contemporaneous and critical.

Practical Advice for Active Projects

The best protection against concurrent delay arguments is not built at claim stage: it's built during the project. Track your own programme performance at the activity level, weekly. If your own activities are slipping, record the cause in the daily report. When you have an Employer delay event, issue a notice the same week and include a clear statement that the Contractor's own works are proceeding as planned on all other critical path activities. This contemporaneous segregation of causes is far more powerful than any retrospective analysis.

The Setup

On a live project in Bahrain, we received a debit note from a subcontractor for tower crane hire charges covering a period we considered to be outside the agreed scope and timeline. The subcontractor's position was that crane utilisation had extended due to Employer-caused programme delays, a position that, while understandable, ignored several critical facts about their own performance during the same period.

Our exposure if we simply paid or ignored the debit was significant. But the instinct on many projects is to avoid the formal correspondence and try to resolve it over a phone call. That instinct is commercially dangerous.

The Six-Point Response

We issued a formal response letter within five days of receiving the debit note. The letter made six specific points:

1. The contractual basis on which the debit was calculated was identified and challenged with reference to the specific subcontract clause it purported to rely on.
2. The subcontractor's own programme performance during the disputed period was set out, with reference to site records and daily reports showing their contribution to delay.
3. The agreed crane hire rate was restated from the subcontract and compared against the rate the debit note applied.
4. Our concurrent entitlement to backcharge the subcontractor for delay-related costs during the same period was reserved and quantified preliminarily.
5. The debit note was formally rejected pending satisfactory justification of the amounts claimed.
6. A without-prejudice meeting was proposed to resolve the matter commercially before escalation.

Why the Letter Mattered

The response worked not because it was aggressive, but because it was specific. It showed we had read the subcontract, we had the records, and we had a counter-position that was grounded in the contract and the facts. Subcontractors, and their commercial teams, respond very differently to a formal, evidenced response than they do to an informal objection or silence.

More importantly, the letter created a record. If the dispute had escalated, we had a documented rejection with stated grounds, issued promptly. That prevents the retrospective argument that we accepted the charges by not responding.