Views in the last 30 days: 63
Estimated read time: 7 minute(s)
📘 Breakdown of Clause 3.4 – Replacement of the Engineer
FIDIC Yellow Book 1999 – Clause 3.4
“If the Employer intends to replace the Engineer, the Employer shall, not less than 42 days before the intended date of replacement, give notice to the Contractor of the name, address and relevant experience of the intended replacement. The Employer shall not replace the Engineer with a person against whom the Contractor raises reasonable objection by notice to the Employer, with supporting particulars.”
- Minimum 42-day notice required.
- Notice must include: Name, Address, Experience.
- Contractor can object, but must provide solid reasoning.
FIDIC Yellow Book 2017 – Clause 3.4
The core intent remains, but refinements ensure tighter alignment with other clauses. Notice and objection rights are preserved — with formal notice under Clause 1.3 and explicit reference to fairness and competency.
- Still uses 42-day advance notice and formal communication protocols.
- Objection window clearly limited to 14 days.
- Temporary appointments allowed in emergencies.
| Step | 1999 – Clause 3.4 | 2017 – Clause 3.6 | Practical Effect |
|---|---|---|---|
| 1️⃣ | Employer issues notice ≥ 42 days before change, naming the new Engineer. | Same 42 days notice, but includes address and relevant experience. | Early disclosure lets Contractor run quick due-diligence. |
| 2️⃣ | Contractor may object “with supporting particulars”. | Contractor must object within 14 days or deemed to accept. | Tighter timeline → faster staffing decisions. |
| 3️⃣ | Employer must not appoint someone to whom Contractor raises reasonable objection. | Same prohibition on unreasonable appointments. | Keeps Engineer neutral & competent. |
| 4️⃣ | — | If Engineer cannot act (e.g., illness), temporary Engineer may be appointed immediately. | Prevents project delays in emergencies. |
🔍 Key Interpretations and Implications
✅ Right to Object: The Contractor’s ability to object safeguards against unqualified or biased appointments—ensuring the Engineer remains a neutral, competent authority under the contract.
❌ But Not a Veto: The objection must be based on reasonable grounds and documented with supporting details. It’s a shield, not a sword—no absolute power to reject at will.
📒 Clarified in 2017: FIDIC’s 2017 edition preserves the same right but frames it more clearly using formal notice protocols (Clause 1.3). This reflects FIDIC’s “Golden Principle” of fair and transparent risk allocation.
⚠️ Risks of Poor Replacement: An unsuitable Engineer could stall quality checks, certifications, and create dispute bottlenecks. Abrupt or politically influenced changes can undermine project momentum and trust.
🧭 Cross-Referencing Clause 3.4 – The Contract Web
🔗 Clause 3.1 – Engineer’s Duties and Authority
Clause 3.1 defines the Engineer as the backbone of contract administration—issuing instructions, certifying payments, and making determinations. Replacing them mid-project isn’t just a name change—it’s a major role shift.
Can the Contractor trust the replacement? Will they respect the project’s history? Clause 3.4 gives the Contractor a voice—for good reason.
🔗 Clause 3.2 – Delegation by the Engineer
Under Clause 3.2, Engineers delegate duties to assistants. When a new Engineer comes in, existing delegations may shift or vanish—impacting site workflows.
A new assistant could challenge protocols that were accepted for months—altering compliance interpretation on the fly.
🔗 Clause 3.5 / 3.7 – Determinations
The Engineer’s quasi-judicial role under Clause 3.5 (1999) or Clause 3.7 (2017) is vital to resolving claims. A new Engineer might reopen past determinations—without full context.
This is why Clause 3.4 insists on “reasonable objection”—to prevent disruption in dispute handling.
🔗 Clause 20 – Claims and Disputes (DAB/DAAB)
Clause 20 is the Contractor’s legal backup. If an Engineer is replaced improperly and mismanages claims, disputes escalate here.
“The new Engineer mishandled our EOT claim. We objected to the replacement. We’re now escalating to the DAAB.” — A common project scenario.
🔗 Clause 1.1.2.4 – Definition of the Engineer
The definition itself explicitly ties back to Clause 3.4. It ensures any replacement is procedurally valid—reinforcing the integrity of the Engineer’s role.
Even the dictionary section of FIDIC underlines how serious replacements are—it’s not just legal trivia.
✍️ Suggestions for Clarity and Improvement
🔍 A. Identifying Potential Ambiguities
- “Reasonable Objection” is undefined — What counts as reasonable?
- No standard for qualifications or language fluency.
- No provision for interim Engineer in case of sudden resignation.
- No mandatory consultation with the Contractor before decision.
💡 B. Practical Examples That Demand Better Wording
📌 Example 1: The Employer proposes a marine specialist for an MEP project. The Contractor objects—but “technical fit” isn’t defined.
📌 Example 2: The proposed Engineer has prior business with the Employer’s legal team. Without a stated policy, objections become subjective.
🔧 C. Suggested Wording – Golden Principles Compliant 🟢
Here’s a suggested Particular Conditions version of Clause 3.4, written to pass the FIDIC Golden Principles (GP1–GP5):
Sub-Clause 3.4 [Replacement of the Engineer] – Amended
If the Employer intends to replace the Engineer, the Employer shall, not less than 42 days before the intended date of replacement, give a Notice to the Contractor of the name, address, and relevant qualifications and experience of the proposed replacement.
The replacement Engineer shall:
(a) have not less than 15 years of relevant professional experience, with 5 in similar project environments;
(b) be fluent in the ruling language as defined in Sub-Clause 1.4;
(c) have had no direct commercial or advisory relationship with either Party in the past 3 years;
(d) meet the standards required in Sub-Clause 3.1.
The Contractor shall, within 14 days of receiving the Notice, submit a Notice of objection with reasonable grounds. These may include: lack of competence, conflict of interest, insufficient experience, or language barriers.
Failure to respond within 14 days shall be deemed acceptance.
If the Engineer resigns, is incapacitated, or dies, the Employer may appoint an interim Engineer for up to 30 days with immediate notice. The permanent process shall still follow this Sub-Clause.
No replacement shall take effect unless all conditions above are satisfied.💬 Why This Works: The GP Compliance Test ✅
| Element | FIDIC Golden Principle | Why It Passes |
|---|---|---|
| Minimum qualifications & neutrality | GP1, GP3 | Clarifies duties & preserves balance |
| Defined “reasonable objection” | GP2 | Removes ambiguity with objective triggers |
| Interim appointment provision | GP1, GP4 | Handles sudden exits without project freeze |
| 42-day notice retained | GP4 | Upholds the original tested timeline |
| Language fluency clause | GP1 | Ensures Engineer’s ability to interpret and act effectively |
✉️ Clause 3.4 / 3.6 Letter Scenarios – Sample Templates
📬 Scenario 1 – Employer’s 42-Day Notice of Proposed Replacement
[Employer’s Letterhead] Our Ref: _______ Date: ___ ______ 20__ To: [Contractor’s Name & Address] Contract: [Project title, Contract No.] Subject: Notice of Proposed Replacement of the Engineer under Clause 3.4 (1999) / 3.6 (2017) Dear Sirs, Pursuant to Clause 3.4 / 3.6, we hereby give you notice of our intention to replace the Engineer. 1. Proposed Engineer: [Full legal name] 2. Address for correspondence: [Postal & e-mail] 3. Relevant experience (summary CV enclosed): ▢ 4. Effective date of appointment: [dd mmm yyyy] (not earlier than 42 days from the date of this notice). Please review the above nomination and advise us of any reasonable objection within the period specified in the Contract. Yours faithfully, [Authorised signatory] for and on behalf of the Employer Attachments: CV, key project references, organisational chart (optional)
🛑 Scenario 2 – Contractor Objects (within 14 days – 2017)
[Contractor’s Letterhead] Our Ref: _______ Date: ___ ______ 20__ To: [Employer’s Name & Address] Contract: [Project title, Contract No.] Subject: Objection to Proposed Replacement of the Engineer – Clause 3.6 (2017) Dear Sirs, We refer to your letter dated [dd mmm yyyy] regarding the proposed appointment of [Name] as Engineer. Under Clause 3.6(b), we must raise our reasonable objection as follows: 1. Conflict of interest – Nominee currently engaged by [Company] advising the Employer 2. Lack of design-build experience – CV shows <5 years on comparable EPC projects 3. Pending arbitration – Nominee involved in [XYZ] Project with our group entity We respectfully request the nomination of an alternative Engineer in accordance with the Contract. Yours faithfully, [Authorised signatory] for and on behalf of the Contractor
✅ Scenario 3 – Contractor No-Objection / Acceptance
[Contractor’s Letterhead] Our Ref: _______ Date: ___ ______ 20__ To: [Employer’s Name & Address] Contract: [Project title, Contract No.] Subject: Acceptance of Proposed Replacement of the Engineer – Clause 3.4 / 3.6 Dear Sirs, We acknowledge receipt of your notice dated [dd mmm yyyy] naming [Name] as the proposed new Engineer. Having reviewed the submitted credentials, we raise no objection under Clause 3.4 (1999) / 3.6 (2017). Please confirm the effective hand-over date and arrange a briefing meeting on programme, variations, and determinations. Yours faithfully, [Authorised signatory] for and on behalf of the Contractor
🚨 Scenario 4 – Employer’s Emergency Temporary Appointment (2017 only)
[Employer’s Letterhead] Our Ref: _______ Date: ___ ______ 20__ To: [Contractor’s Name & Address] Contract: [Project title, Contract No.] Subject: Temporary Appointment of Engineer – Clause 3.6(d) (2017) Dear Sirs, We regret to inform you that the current Engineer, [Name], is no longer able to act due to [reason]. In accordance with Clause 3.6(d), we hereby appoint, on a temporary basis, [Interim Engineer’s Name] of [Company] to perform the Engineer’s duties with effect from today. Please cooperate fully with the Interim Engineer to prevent disruption to the Works. Yours faithfully, [Authorised signatory] for and on behalf of the Employer
⚖️ Scenario 5 – Contractor Cost / Time Claim for Non-Compliant Replacement
[Contractor’s Letterhead] Our Ref: _______ Date: ___ ______ 20__ To: [Employer’s Name & Address] Contract: [Project title, Contract No.] Subject: Notice of Claim – Breach of Clause 3.4 / 3.6 (Unnotified Replacement) Dear Sirs, We record that on [dd mmm yyyy], the Employer introduced [Name] as Engineer without prior notice required under Clause 3.4 (1999) / 3.6 (2017). This has disrupted progress meetings and delayed determinations under Clause 3.7. We therefore give Notice of Claim under Clause 20.1 (1999) / 20.2 (2017) for: - EOT of [x] days - Cost plus Profit estimated at [currency] [amount] Yours faithfully, [Authorised signatory] for and on behalf of the Contractor
🔑 Tips for Using These Templates
| Step | Key Check-Point | Reminder |
|---|---|---|
| 📌 1 | Quote the right clause and edition | Distinguish between 3.4 (1999) and 3.6 (2017) |
| 📌 2 | Track the notice dates | Use a tracker for the 14-day / 42-day windows |
| 📌 3 | Attach evidence to your objection | CVs, conflicts, programme impacts – be persuasive |
| 📌 4 | Mirror letters to all parties if needed | Send to Employer, Contractor, and Engineer |
🏗️ Employer — 42-Day Notice & Nomination Steps
| # | Action Item | Clause | Book | Timing / Period | ☐ |
|---|---|---|---|---|---|
| 1 | Draft formal notice naming the proposed Engineer | 3.4 / 3.6 (a) | 1999 / 2017 | ≥ 42 days before appointment | |
| 2 | Attach CV showing relevant design-build/EPC experience | 3.6 (a)(ii) | 2017 | With the notice | |
| 3 | State contact address, e-mail & phone of nominee | 3.6 (a)(iii) | 2017 | With the notice | |
| 4 | Copy the notice to the current Engineer (if still in post) | Good practice | Both | Immediately | |
| 5 | Note calendar reminder for end of objection window | 3.6 (b) | 2017 | Day 0 + 14 | |
| 6 | File proof-of-delivery to Contractor | Contract admin | Both | Day 0 |
🛠️ Contractor — Review & Objection Window
| # | Action Item | Clause | Book | Timing / Period | ☐ |
|---|---|---|---|---|---|
| 1 | Log date/time notice received | 1.3 (Notices) | Both | On receipt | |
| 2 | Circulate CV for internal conflict & competence review | 3.4 / 3.6 | Both | Within 3 days | |
| 3 | Consider external due-diligence check | Risk mgmt. | Both | Within 7 days | |
| 4 | Decide if grounds for “reasonable objection” exist | 3.4 / 3.6 (b) | Both | By Day 12 / promptly | |
| 5 | Draft objection letter with evidence (if needed) | 3.4 / 3.6 (b) | Both | By Day 14 (2017) | |
| 6 | If no objection, send acceptance & request hand-over | Same | Both | Before Day 14 | |
| 7 | Update claim tracker if notice non-compliant | 20.1 / 20.2 | Both | Ongoing |
⚡ Emergency / Temporary Engineer (2017-Only)
| # | Action Item | Clause | Timing | ☐ |
|---|---|---|---|---|
| 1 | Employer issues immediate notice for temporary Engineer | 3.6 (d) | Day 0 (event) | |
| 2 | Share credentials & contact of interim appointee | 3.6 (d) | Day 0 | |
| 3 | Inform Contractor that full nomination will follow | 3.6 (d) | With notice | |
| 4 | Keep separate audit trail for interim decisions | Best practice | Continuous | |
| 5 | Initiate 42-day nomination process for permanent Engineer | 3.6 (a–c) | Within 14 days | |
| 6 | Update programme/risk logs for disruption | PMO | Ongoing |
📊 Flowchart: Engineer Replacement Process under FIDIC 1999
Click to view full-size flowchart – visual summary of Clause 3.4 (FIDIC 1999)
- Start: Employer decides to replace the Engineer.
- Prepare Notice: Full details of replacement Engineer drafted.
- Issue 42-Day Notice: Sent to Contractor in advance.
- Contractor Decision Point: Review and raise objection if needed.
- Submit Objections: Contractor provides reasons + documentation.
- Employer Review: Objections assessed for merit.
- Outcome:
- ✔️ Valid objection → Select new Engineer
- ✔️ No objection or invalid → Proceed with original choice
- Engineer Appointed: Formal appointment confirmed.
- Duties Begin: New Engineer takes over.
- Project Continues: Progress resumes under new Engineer.
💡 Pro Tip: This flow is based on FIDIC 1999 Clause 3.4. For 2017 contracts, remember the 14-day objection deadline and provisions for temporary appointments under Clause 3.6(d).
📈 Sequence Diagram: Engineer Replacement Steps in FIDIC 1999
Click to view full-size sequence diagram — shows the communication & action chain in Clause 3.4 (1999)
- Employer Notifies Contractor of intention to replace Engineer (with full details).
- Contractor Receives Notice and begins assessing proposed Engineer.
- Contractor Raises Objections (if any), citing reasonable grounds.
- Employer Reviews the Contractor’s objections to assess validity.
- Employer Confirms or Revises the nomination based on objections.
- Employer Formally Appoints the new Engineer.
- New Engineer Assumes Role and initiates communication.
- Contractor Acknowledges and prepares to receive instructions.
- Engineer Issues Instructions to continue the project smoothly.
- Contractor Complies with instructions and resumes work.
- Engineer Reports progress to Employer regularly.
- Employer Reviews and gives feedback or directives.
- Engineer Relays Feedback back to the Contractor for execution.
💡 Tip: This sequence shows how the replacement affects **not just approval**, but ongoing communication and operational flow. It complements the flowchart overview by focusing on **message sequencing and response logic**.