One of the most significant structural changes in the FIDIC 2017 suite is the formalisation of the Engineer’s role in resolving disagreements between the Employer and Contractor before they escalate into formal disputes. Under Sub-Clause 3.7 of the 2017 Red, Yellow, and Silver Books, the Engineer is now required to follow a two-stage process — first attempting to facilitate an agreed settlement, and then, if agreement is not reached, issuing a formal Determination. This structured mechanism replaces the relatively brief Sub-Clause 3.5 of the 1999 editions and reflects a deliberate policy decision by FIDIC to embed dispute prevention into the contractual administration framework. Understanding how this process works — and where it can go wrong — is essential for every Engineer, Contractor, and Employer working on FIDIC projects.
The 2017 reforms were driven, in part, by the widespread criticism that the 1999 editions allowed Engineers to act as de facto Employer agents while nominally occupying a neutral role. In many projects, particularly in the Middle East and Southeast Asia, the Engineer’s determinations under Sub-Clause 3.5 of 1999 were seen as rubber-stamping the Employer’s position, leaving Contractors with no practical remedy short of formal dispute proceedings. The 2017 editions attempt to address this by strengthening procedural safeguards, imposing strict timeframes, and requiring the Engineer to consult and endeavour to reach agreement before making any determination.
This article examines the mechanics of Sub-Clause 3.7 in detail, contrasts it with the 1999 approach under Sub-Clause 3.5, and offers practical guidance for all parties on how to navigate this critical process.
The 1999 Baseline: Sub-Clause 3.5 and Its Limitations
Under the FIDIC 1999 editions (Red Book MDB Harmonised, Yellow Book, and Silver Book), Sub-Clause 3.5 imposed a relatively simple obligation: whenever the Contract required the Engineer to agree or determine any matter, the Engineer was required to consult with each Party in an endeavour to reach agreement, and if agreement was not achieved, to make a fair determination in accordance with the Contract.
The provision was brief and procedurally thin. It did not prescribe a specific timeframe for the consultation phase. It did not require the Engineer to separately notify the parties that consultation had failed before issuing a determination. And critically, it contained no mechanism to compel either party to engage genuinely in the consultation process. The result was that in many projects the “consultation” was perfunctory — a letter was sent to both parties and a determination issued shortly thereafter. Whether the Engineer had genuinely endeavoured to reach agreement was largely uncheckable.
The 1999 editions also left unresolved the question of what happened if the Engineer failed to issue a determination at all, or issued it outside any applicable timeframe. In the absence of a deemed rejection provision, delayed or absent determinations created procedural deadlock, particularly where the Contractor’s entitlement to proceed with a Notice of Dissatisfaction and then to the Dispute Adjudication Board (DAB) depended on first receiving the Engineer’s determination.
The 2017 Reforms: Sub-Clause 3.7 in Detail
Sub-Clause 3.7 of the FIDIC 2017 editions represents a substantial expansion and codification of the Engineer’s agreement and determination role. The provision operates in two distinct stages with mandatory timeframes attached to each.
Stage 1: The Agreement Phase (Sub-Clause 3.7.1)
When any matter requires the Engineer to agree or determine under the 2017 Contract, Sub-Clause 3.7.1 requires the Engineer to consult with both parties with the goal of reaching agreement. This consultation must be conducted within a defined Time for Agreement, which is 42 days from the date the matter is referred to the Engineer (or such other period as the Parties may agree).
Critically, the Engineer is expressly required during this stage to act neutrally between the Employer and Contractor. This is reinforced by the broader obligations in Sub-Clause 3.7 that the Engineer shall not act as agent for either party when performing the agreement and determination function. The obligation of neutrality is now explicitly contractual, not merely aspirational.
The Engineer may meet with each party separately or jointly. Good practice involves early disclosure of each party’s position to the other to facilitate genuine dialogue, though the Contract does not prescribe the consultation methodology in detail. The Engineer should document all consultation steps carefully in the event that the determination is later challenged.
If agreement is reached within the 42-day period, the Engineer records it in writing and it becomes binding on both parties under Sub-Clause 3.7.4. Neither party may subsequently raise a claim or dispute in relation to the agreed matter.
Stage 2: The Determination Phase (Sub-Clause 3.7.2)
If no agreement is reached within the Time for Agreement, the Engineer must issue a fair Determination within a further 42 days — that is, within 42 days after the expiry of the Time for Agreement. The total process therefore has a maximum duration of 84 days from referral, subject to the parties agreeing otherwise.
The Determination must be fair, must be in accordance with the Contract, and must set out the Engineer’s reasoning. The requirement to provide reasons is an important improvement over the 1999 approach — reasoned determinations are more transparent, easier to scrutinise, and support the DAB process if the matter is subsequently escalated.
Under Sub-Clause 3.7.3, if the Engineer fails to issue a Determination within the prescribed 84-day period, either party may treat the failure as a deemed rejection and proceed directly to the DAAB. This deemed rejection provision closes the procedural gap that bedevilled the 1999 editions and prevents the Engineer from frustrating the dispute resolution ladder through inaction.
Sub-Clause 3.7.4: Effect and Finality
Under Sub-Clause 3.7.4, both a recorded agreement and a Determination issued under Sub-Clause 3.7 are immediately binding on both parties, who shall promptly give effect to them. A party who wishes to challenge a Determination must give a Notice of Dissatisfaction (NOD) within 28 days of receiving the Determination. If no NOD is given within that period, the Determination becomes final and binding — a critical provision that can foreclose a party’s right to pursue the matter further if the deadline is missed.
The NOD triggers the right to refer the matter to the DAAB under Sub-Clause 21.4. The Determination remains binding pending the DAAB’s decision, meaning the obligated party must comply with it even while it is being challenged — a “pay now, argue later” principle consistent with the broader FIDIC dispute resolution philosophy.
The Engineer’s Neutrality: An Ongoing Tension
The explicit neutrality obligation in Sub-Clause 3.7 sits in some tension with the reality that the Engineer is appointed and paid by the Employer. Under Sub-Clause 3.1, the Engineer acts for the Employer in carrying out its general duties under the Contract — including issuing instructions, granting extensions of time, certifying payment, and administering the Works. It is only in the specific context of Sub-Clause 3.7 that the Engineer is required to act neutrally.
This dual role — Employer’s agent for most purposes, neutral adjudicator for Sub-Clause 3.7 matters — creates an inherent structural tension. Contractors frequently argue that Engineers cannot genuinely be neutral because their commercial relationship with the Employer creates at least a perception of bias. Employers, for their part, may regard the Engineer’s neutral determination function as an encroachment on Employer authority.
In practice, the neutrality obligation is enforceable at the DAAB stage. If a Contractor can demonstrate that the Engineer’s Determination was not genuinely “fair” — for example, because the Engineer adopted the Employer’s position wholesale without independent analysis, or failed to properly consider the Contractor’s submissions — the DAAB may substitute a different determination. Arbitral tribunals have also been prepared to scrutinise the Engineer’s neutrality as part of broader cost and time award proceedings.
From a project governance perspective, the best outcomes arise when the Engineer genuinely engages in structured consultation under Sub-Clause 3.7.1, requests and reviews detailed supporting submissions from both parties, and produces determinations that are demonstrably fact-based and independently reasoned.
Practical Application: Common Scenarios
Extension of Time Claims
Sub-Clause 8.5 of the FIDIC 2017 Red and Yellow Books requires the Engineer to determine any extension of time entitlement under Sub-Clause 3.7. When a Contractor submits a claim for EOT under Sub-Clause 20.2, the Engineer must first attempt to reach agreement with both parties on the quantum and basis of any extension, and then, if agreement fails, issue a determination. This means the Contractor’s EOT claim cannot simply be rejected by the Engineer without going through the Sub-Clause 3.7 process — an important procedural protection.
Additional Cost Claims
Similarly, claims for additional cost under Clause 20 are routed through Sub-Clause 3.7. Where a Contractor claims additional cost arising from Employer Risks, variations, unforeseeable conditions, or other Contractual entitlements, the Engineer must engage in the agreement and determination process. The 84-day outer limit provides a degree of certainty about when a Contractor can escalate to the DAAB if the Engineer is unresponsive or issues an adverse determination.
Notices of Dissatisfaction
One of the most critical procedural risks for both parties arises from the 28-day NOD deadline under Sub-Clause 3.7.4. A Determination that is not challenged within 28 days becomes final and binding — including where the Contractor has been awarded less time or cost than claimed. Failure to issue a timely NOD has been treated by arbitral tribunals as a waiver of the right to challenge the Determination, even where the underlying merits of the claim are strong.
Both Employers and Contractors should maintain active monitoring systems to track the dates of all Determinations and trigger immediate review by their legal or claims advisors upon receipt. The 28-day clock runs from receipt of the Determination, not from the date of issue — parties should note this distinction when administering international projects across different time zones.
Comparison with the 1999 Edition: Key Differences
The differences between Sub-Clause 3.5 (1999) and Sub-Clause 3.7 (2017) can be summarised as follows. First, the 2017 edition introduces a mandatory two-stage process with defined timeframes, whereas the 1999 edition contained no prescribed timetable for the consultation phase. Second, the 2017 edition expressly requires the Engineer to act neutrally during the agreement and determination process, a requirement that was implicit at best under 1999. Third, the 2017 edition introduces a deemed rejection mechanism for cases where the Engineer fails to act within the prescribed time, closing a significant procedural gap. Fourth, the 2017 edition requires the Engineer to give reasons for any Determination, improving transparency and accountability. Fifth, the 2017 edition makes clear that both agreements and Determinations are immediately binding on both parties pending any NOD and DAAB referral.
In aggregate, these changes represent a material strengthening of the procedural framework, though they also impose greater administrative burden on the Engineer and require both parties to be more alert to procedural deadlines.
Guidance for Contractors
Contractors should treat Sub-Clause 3.7 as an opportunity rather than merely a procedural hurdle. The agreement phase under Sub-Clause 3.7.1 provides a genuine forum for negotiated resolution — a well-presented, thoroughly evidenced submission during the consultation phase can result in a commercially acceptable agreed outcome without the cost and delay of DAAB proceedings.
Contractors should also ensure that all claim submissions are complete and detailed before referral to the Engineer, since the Engineer’s Determination will be based on the record before them. Incomplete submissions may result in adverse determinations that are then difficult to challenge at the DAAB. And as noted above, monitoring the 28-day NOD deadline is critical — claims teams should have a diarised review process for every Determination received.
Guidance for Employers
Employers should ensure that the Engineer is genuinely independent in carrying out the Sub-Clause 3.7 function and should resist any temptation to direct or influence the Engineer’s Determinations. Determinations that are perceived as biased toward the Employer are more likely to be overturned at the DAAB, and a pattern of adverse DAAB decisions can damage the Employer’s negotiating position significantly.
Employers should also be aware that the deemed rejection mechanism under Sub-Clause 3.7.3 means that Engineer inaction is no longer a viable strategy for managing contentious claims. If the Engineer fails to determine within 84 days, the Contractor gains an unqualified right to go to the DAAB — and the Employer loses the benefit of the Engineer’s structured analysis. Timely Engineer determinations, even if commercially adverse to the Employer in the short term, are generally preferable to allowing matters to escalate unresolved.
Guidance for Engineers
Engineers administering FIDIC 2017 contracts bear a heightened obligation of procedural rigour under Sub-Clause 3.7. An Engineer who fails to observe the prescribed timeframes, fails to document genuine consultation efforts, or issues a Determination without adequate reasoning runs the risk of the Determination being set aside at the DAAB — and potentially faces professional liability exposure if the deficient determination causes loss to either party.
Engineers should adopt a structured process for Sub-Clause 3.7 matters: acknowledge referral in writing, issue a consultation timetable to both parties, request detailed submissions with supporting documentation, hold consultation meetings where appropriate, and document all steps. If the 42-day agreement period is genuinely insufficient for complex matters, both parties’ agreement to extend the period should be obtained in writing before the deadline expires, not retrospectively.
Conclusion: A More Robust Framework, But Not Without Risk
The Sub-Clause 3.7 mechanism in the FIDIC 2017 editions represents a genuine improvement over the 1999 approach. The combination of prescribed timeframes, explicit neutrality obligations, reasoned Determinations, and a deemed rejection safety valve creates a more transparent and accountable framework for resolving disagreements at the project level. When the process works as intended, it can resolve disputes faster and at lower cost than formal adjudication or arbitration.
However, the mechanism introduces new procedural risks — particularly the 28-day NOD deadline and the binding effect of agreed and determined outcomes. Parties who are not alive to these deadlines risk losing rights they would otherwise have. And the structural tension between the Engineer’s dual roles as Employer’s agent and neutral determiner has not been fully resolved, meaning that the quality and integrity of Sub-Clause 3.7 outcomes will continue to depend, in large part, on the professional standards of the individual Engineer administering the contract.
For all parties, the message is clear: Sub-Clause 3.7 demands active engagement, rigorous documentation, and careful deadline management. In a well-administered FIDIC project, it can be one of the most effective tools for keeping disputes proportionate and projects on track.
This article is published for general information purposes and does not constitute legal advice. Construction law is a specialist field and parties to FIDIC contracts should seek professional legal advice in relation to their specific circumstances. CMGuide Pty Ltd provides construction claims, contract management, and contractual advisory services. For more information, visit cmguide.com.au.