Clause 3.7 – FIDIC Yellow Book 1999 vs 2017 Explained

Table of Contents

84 / 100 SEO Score

Views in the last 30 days: 100

Estimated read time: 28 minute(s)

🔍 Comparative Clause Analysis: Clause 3.5 (1999) vs Clause 3.7 (2017)Determinations


📒 FIDIC 2017
📘 FIDIC 1999

📒 Purpose of Clause 3.7 – FIDIC 2017

Clause 3.7 helps resolve disagreements or claims by encouraging mutual agreement first. If that fails, the Engineer acts as a neutral party to make a fair decision—quickly and clearly.

  • ⚖️ Engineer must act neutrally (explicit requirement).
  • 🕒 Time-bound: 42 days for agreement or determination.
  • 📭 Deemed rejection if no response is issued in time.
  • 📌 Notice of Dissatisfaction (NOD) within 28 days to challenge.

This clause ensures efficient internal resolution of claims or matters and prevents disputes from stalling progress. It builds fairness and trust by requiring Engineers to act as unbiased intermediaries.

📘 Purpose of Clause 3.5 – FIDIC 1999 (Old 3.7)

The Engineer consults both parties to resolve a disagreement. If they can’t agree, the Engineer makes a decision. It’s functional—but informal and open-ended.

  • ⛔ No timeframes for resolution.
  • ⚠️ No formal requirement for Engineer neutrality.
  • 🌀 No structure for challenging or correcting determinations.

Without structure or deadlines, disputes could linger. Clause 3.5 left too much to the Engineer’s discretion, which sometimes caused delays, inconsistencies, or biased decisions.

🔹 FIDIC 1999 – Clause 3.5: Determinations

The Engineer was required to:

  • 🗣️ Consult with both Parties to seek agreement
  • ⚖️ If no agreement: make a “fair determination” in line with the Contract

📋 Key Characteristics:

  • ⏳ No specific deadlines
  • 📑 No procedural steps for consultation
  • 📝 No formatting requirements for determinations
  • 🧑‍⚖️ Neutrality was assumed but not explicit
📌 Bottom Line:
Vague but flexible. Gave Engineers discretion—but that often felt skewed toward Employers.

🧠 Contractors often questioned neutrality since the Engineer was appointed and paid by the Employer.

🔸 FIDIC 2017 – Clause 3.7: Agreement or Determination

The new version introduced a structured, fairer process:

  • 🤝 First step: Encourage agreement through consultation
  • 📋 Introduced procedural timelines and steps
  • ⚖️ Engineer must act neutrally between the Parties
💼 A New Ethos:
“The Engineer shall act neutrally between the Parties and shall not be deemed to act for the Employer.”

✅ FIDIC finally codifies the idea of Engineer neutrality—giving more confidence to Contractors.

🔎 This isn’t just rewording—it’s a shift from flexible discretion to structured fairness.

📑 Clause 3.7 – FIDIC 1999 vs 2017

Purpose: Resolves disagreements between parties through Engineer-facilitated agreement or determination.

Feature 📘 1999 Yellow Book 📒 2017 Yellow Book
Engineer’s Neutrality Not required to act neutrally Must act neutrally
Consultation First? Optional Mandatory
Time Limit for Action ❌ None ✅ 42 days
Deemed Rejection/Dispute Not addressed ✅ Built-in default rejection
Effect of Determination Binding unless disputed Binding unless corrected or NOD filed
Correction of Errors ❌ Not addressed ✅ Allowed (14 days)
Partial Dissatisfaction ❌ Not possible ✅ Partial NODs allowed
💡 Best Practice Tip:
Use the 2017 structure as a blueprint when tailoring Particular Conditions under the 1999 edition.

🔸 FIDIC 2017 – Clause 3.7: Agreement or Determination

Fast forward to 2017, and we get a totally revamped version: Clause 3.7, titled Agreement or Determination. It’s not just a rewording — it’s a philosophical shift in how FIDIC wants parties to handle claims and disagreements.

Here’s the evolution:

💼 A New Ethos: Neutrality and Dialogue

“When carrying out his/her duties under this Sub-Clause, the Engineer shall act neutrally between the Parties and shall not be deemed to act for the Employer.”​

This is big. It’s the first time FIDIC explicitly codifies the Engineer’s neutrality. This helps Contractors trust the process more and shifts the Engineer's role closer to that of a quasi-adjudicator.

🔁 Structured Two-Phase Process (FIDIC 2017 Clause 3.7)

1️⃣ Consultation Phase (Sub-Clause 3.7.1)

🕒 Timeline: 42 days (or as agreed)
  • The Engineer must actively facilitate discussion.
  • Parties aim to reach consensus.
If successful:
Notice of the Parties’ Agreement is signed & issued.

2️⃣ Determination Phase (Sub-Clause 3.7.2)

If no agreement in time limit:
  • The Engineer makes a fair, detailed determination.
  • Must include: reasons, supporting data, and formal notice format.
If not resolved:
Determination is binding (unless challenged by a NOD).
Why it matters: This dual-phase structure gives space for consensus before any authoritative decision—making it a powerful dispute-avoidance tool in practice.

❓ Why Was This Upgrade Necessary?

📍 Real-world construction is conflict-heavy.
Delays, scope creep, and blurred responsibilities create frequent disagreements. The 1999 model left too much to Engineer discretion, lacking structure and safeguards.
The 2017 upgrade brings real change:
  • Time discipline (42-day cycles)
  • 🧐 Procedural transparency (clear steps & documentation)
  • ⚠️ Consequences if the Engineer doesn’t act in time
For example:
“If the Engineer does not give the Notice of determination within the relevant time limit... in the case of a Claim, the Engineer shall be deemed to have given a determination rejecting the Claim.”

🔔 Silence isn’t golden—it now counts as a rejection!

🌐 How Clause 3.7 Ties Into the Bigger Contract Picture

Where is it triggered?
  • 1.9 (Errors in Employer’s Requirements)
  • 4.7.3 (Rectification measures)
  • 13.3.1, 14.4, 15.6, and more
  • All Claims under Clause 20 (Claims & Disputes)
🚦 Metaphor: If Clause 3.5 (1999) was a “procedural stop,”
Clause 3.7 (2017) is a checkpoint with a proper tollbooth.

You can’t move forward unless you’ve engaged in the process correctly!

2️⃣ Breakdown of Clause 3.7 – Agreement or Determination (FIDIC 2017)

🔹
Sub-Clause 3.7.1 – Consultation to Reach Agreement
  • Engineer promptly starts consultation between Parties
  • Engages both Parties (together or separately)
  • Keeps written record of consultations (unless agreed otherwise)
  • 🕰️ Timeline: 42 days (unless otherwise agreed)
  • If agreement is reached: Engineer issues a Notice of the Parties’ Agreement (signed by both)
  • If not: Move to Sub-Clause 3.7.2
👉 This phase is proactive: encourage consensus and prevent disputes from snowballing.
🧑‍⚖️
Sub-Clause 3.7.2 – Engineer’s Determination
  • Engineer makes a fair determination based on the Contract, facts, and circumstances
  • Issues a formal Notice of the Engineer’s Determination
  • Notice must include detailed reasons, supporting particulars, and evidence
This stage is about transparency and fairness—not just making a call.
⏱️
Sub-Clause 3.7.3 – Time Limits
  • Consultation period: 42 days from trigger point
  • Determination period: If no agreement, Engineer has another 42 days to issue determination
  • Trigger points vary by clause (e.g., start with notice/claim for Clause 20)
  • If Engineer fails to respond:
    • For Claims: deemed rejected
    • Other matters: becomes a Dispute, eligible for DAAB referral
🚨 Clause 3.7 ensures nothing sits in limbo!
📜
Sub-Clause 3.7.4 – Effect of Agreement/Determination
  • Becomes binding unless challenged under Clause 21 or corrected for clerical errors (within 14 days)
  • Engineer must issue a revised notice within 7 days of discovering/correcting error
  • If money is involved, Contractor includes it in next Statement, Engineer in next Payment Certificate
➡️ Ensures determinations actually impact the project, not just paperwork.
📮
Sub-Clause 3.7.5 – Dissatisfaction with Engineer’s Determination
  • If dissatisfied, Party may issue Notice of Dissatisfaction (NOD) within 28 days (from determination, correction, or deemed rejection)
  • Partial NODs allowed — you can dispute part, accept the rest
  • If no NOD in time: determination is final and binding
  • If a Party ignores a final determination: other can go straight to arbitration (Clause 21.6), skipping DAAB
📌 Final “safety valve”: Partial NOD = only disputed part goes to DAAB; rest is binding.
✅ In Summary: Clause 3.7 is a well-oiled machine: it opens doors to dispute, but only in a structured, time-bound way.
🤝 Try to agree. 🧑‍⚖️ If not, Engineer decides. ⏱️ Timelines keep it moving. 📜 Outcomes must be reasoned and shared.

3️⃣ Key Interpretations & Implications of Clause 3.7 (FIDIC 2017)

⚖️ The Engineer’s Role: From Agent to Arbitrator-Lite
  • Must act neutrally—no longer an Employer’s “agent”.
  • Neutrality is required in tone, behavior, and documentation.
✅ Implication: Engineer becomes a trusted referee, not just a process manager.
📤 Notice of Dissatisfaction (NOD): Your Ticket to Dispute
  • Challenge the Engineer’s decision by issuing a clearly-labeled NOD within 28 days.
  • Partial dissatisfaction allowed: only challenge what you dispute; rest is binding.
✅ Implication: Flexible and fair—no “all or nothing.”
🚨 Finality and Enforceability
  • If not challenged in 28 days, the determination is final and binding.
  • Clerical errors can be corrected within 14 days (revised notice in 7 days).
  • If a Party ignores a final determination: other Party can proceed directly to arbitration—no DAAB required.
⚠️ Implication: Compliance is mandatory; ignore it, and you risk fast-tracked arbitration.
⏱️ Timelines: 42-Day & 28-Day Rhythm
  • 42 days to reach agreement or determine.
  • 28 days for NOD if dissatisfied.
  • If the Engineer misses the timeline: Claims are deemed rejected, others go to DAAB without NOD.
🚨 Implication: Issues can’t be ignored; the clock keeps ticking for all Parties.
🔁 When Determinations Involve Money
  • Contractor must include determined amount in next Statement.
  • Engineer must include in next Payment Certificate.
✅ Implication: Determinations are real—they drive cash flow, not just paperwork.
🧠 Practical Takeaways
Engineers
Document thoroughly, remain neutral, act promptly.
Contractors/Employers
Track timelines carefully—missing a day may lose you leverage.
Project Managers
Build Clause 3.7 deadlines into project control systems (use shared calendars, alerts, dashboards).
Lawyers/Advisors
Train your teams on compliant NODs—poor formatting can sink a dispute.

4️⃣ Cross-Referencing with Other Clauses: How Clause 3.7 Powers the Contract

🧩 Where does Clause 3.7 get triggered?
  • 1.9 – Errors in Employer’s Requirements
  • 4.7.3 – Rectification measures, delay and/or Cost
  • 10.2 – Taking Over of Parts of the Works
  • 11.2 – Cost of Remedying Defects
  • 13.3.1 – Variation by Instruction
  • 13.5 – Daywork
  • 14.4 – Schedule of Payments
  • 14.5 – Plant and Materials Intended for the Works
  • 14.6.3 – Modification of Interim Payment Certificates
  • 15.3 – Valuation after Contractor’s Default Termination
  • 15.6 – Valuation after Employer’s Convenience Termination
  • 18.5 – Optional Termination due to Exceptional Events
📌 Each clause defines its “date of commencement” for the 42-day consultation/determination clock under Sub-Clause 3.7.3.
💰 Impact on Payment & Cash Flow
When Clause 3.7 leads to a financial outcome:
– Contractor must include it in the next Statement (Clause 14.3)
– Engineer must include it in the next Payment Certificate (14.6.3)
💸 These are not just words—they drive real project cash flow.
🛠️ Clause 20 – Claims
  • Every Claim (time, money, or relief) triggers Clause 3.7 when a full Claim is submitted.
  • Engineer starts with consultation (3.7.1); if unresolved, issues a determination (3.7.2)—all within set timeframes.
  • Failing to act? For Claims: deemed rejected. For others: eligible for DAAB, no NOD needed.
⚖️ Clause 21 – Disputes & DAAB
  • Disagree? Party must serve a NOD (3.7.5) within 28 days.
  • This opens the door to DAAB (21.4) or, if Engineer never decides, skips straight ahead.
🧠 Clause 3.7 is a “first stop”
  • Formal dispute is only possible after the 3.7 process.
  • Prevents unnecessary escalation and keeps the project moving.

🧠 Final Reflections: Why Cross-References Matter

Understanding the full web of references to Clause 3.7 is more than trivia — it’s essential to managing risk, time, and money on a FIDIC project.

✅ If you know when Clause 3.7 is triggered, you can:

  • 🕒 Start your stopwatch on the 42-day cycle,
  • 📎 Prepare your documentation and arguments,
  • 📤 Anticipate the need for a NOD,
  • ⚖️ Avoid procedural missteps that can derail a Claim or delay resolution.

📋 Clause 3.7 Decision Log Template

Auto-compute 42→42 windows & 28-day NOD, with overdue alerts and CSV tools.
OK Due Soon (≤ 7 days) Overdue Agreement window: +42 days from consultation start • Determination window: next +42 days • NOD: +28 days from determination (or deemed rejection for Claims).
Ref. No. Triggering Clause Matter/Claim Description 3.7.1 Consultation Start Date Agreement Reached? (Y/N) 3.7.2 Determination Due Date Date Determination Issued NOD Deadline (28 Days After) NOD Issued? (Y/N) Disputed Elements
(if partial)
Final Outcome Notes/Follow-Up
001 13.3.1 Variation Instruction – Additional Pipework 10-Feb-2025 N 24-Mar-2025 22-Mar-2025 19-Apr-2025 Y Valuation only DAAB Ref. 02 Contractor disagreed with $ valuation
002 20.2.4 Claim for EOT due to late access 15-Jan-2025 Y N/A N/A N/A N/A Agreed – 10 days EOT Signed agreement notice issued
003 14.6.3 Correction to Payment Certificate #8 01-Mar-2025 N 12-Apr-2025 Not Issued N/A N/A Entire matter Dispute Initiated Engineer missed deadline – matter escalated
🛠 How to Use It:
  • Triggering Clause: From Sub-Clauses like 1.9, 4.7.3, 13.3.1, 20.2.4, etc.
  • Consultation Start Date: Date the Engineer formally initiated 3.7.1 consultation.
  • Determination Due Date: 42 days after consultation (or as required).
  • NOD Deadline: 28 days after determination is issued or deemed rejected.
  • Final Outcome: Note whether the issue was agreed, bound, escalated to DAAB, or moved to arbitration.
Copied!
FIDIC 2017 — Clause 3.7

Clause 3.7 Decision Log — Project, Planner & Report

Consultation (e.g., 42d) → Determination (e.g., 42d) → NOD (28d). Add project details, track rows, export calendar & generate a detailed HTML report.

28-day NOD Deemed paths Severability

🏷️ Project Details

🧰 Standard Windows & Options

📊 Live KPIs

next deadline
days left
⚠️
rows due ≤3d

KPIs update from the rows below and your preset windows.

🗂️ Decision Log Rows

📚 Quick Reference — Keys

KeyMeaningNotes
Consultation deadlineTrigger + Consultation days3.7.1
Determination dueConsultation deadline + Determination days3.7.2
Deemed eventMissed determination deadlineClaim → deemed rejection; Other Matters → dispute (3.7.3)
NOD deadlineNOD start + NOD days3.7.5

📋 A. Cross-Reference Matrix – Where Clause 3.7 Applies

Sub-Clause Title Triggers 3.7? Time Commencement Button
1.9Errors in the Employer’s RequirementsYesYes
4.7.3Rectification Measures, Delay and/or CostYesYes
10.2Taking Over of Parts of the WorksYesYes
11.2Cost of Remedying DefectsYesYes
13.3.1Variation by InstructionYesYes
13.5DayworkYesYes
14.4Schedule of PaymentsYesYes
14.5Plant and Materials Intended for the WorksYesYes
14.6.3Correction/Modification of Interim Payment CertificatesYesYes
15.3Valuation after Termination for Contractor’s DefaultYesYes
15.6Valuation after Employer’s Convenience TerminationYesYes
18.5Optional Termination (Exceptional Events)YesYes
20.2.5Claims: Agreement or Determination after full submissionYes (Claim-based triggers)Yes

🧩 What-If Scenarios: Putting Clause 3.7 into Action

❓ What if only part of the Engineer’s determination is disputed?
The dissatisfied Party must issue a Notice of Dissatisfaction (NOD), clearly identifying the specific part(s) they disagree with. The rest of the determination becomes final and binding.
🧠 Implication: This streamlines the process—only disputed parts go to the DAAB, and the rest is enforced immediately.
❓ What if the Engineer doesn’t issue a determination within the 42-day deadline?
For Claims under Clause 20: The Claim is deemed rejected.
For other matters: The issue is treated as a Dispute and can go to the DAAB without a NOD.
✅ No silence games! Engineer inaction moves the process forward, not backward.
❓ What happens if a Party fails to issue a Notice of Dissatisfaction (NOD) within 28 days?
The determination becomes final and binding on both Parties, enforceable and reflected in future Payments (Clause 14.6.3). No DAAB or arbitration is possible for that issue.
⏰ Missing the NOD window is like missing your exit—you can’t turn back.
❓ Can a Party challenge a “deemed rejection” of a Claim?
Yes. If the Engineer doesn’t respond in time, the Claim is deemed rejected. The dissatisfied Party can treat it as a Dispute and go straight to the DAAB under Clause 21.4—no NOD needed.
📌 Contractor isn’t penalized for Engineer silence—the contract guarantees escalation routes.
❓ What if a Party refuses to comply with a final and binding determination?
The other Party can go straight to arbitration under Clause 21.6. No DAAB or NOD required—as long as the determination is final and binding.
🚨 “Final” means enforceable. If compliance is ignored, litigation is the next stop.
❓ What if the NOD itself is flawed?
A NOD that lacks the correct label, reasons, or is filed late may not qualify under Sub-Clause 3.7.5. This could block the route to DAAB/arbitration, and the determination stands.
💡 Pro tip: Always format NODs exactly as required—clarity, timing, and purpose matter!
🧠 Closing Thoughts:
Track the 42-day Engineer window and 28-day NOD deadline like project milestones.
Don’t sit on your rights—delay can shut the door on your claims. Engineer silence triggers escalation, not stalling.
🚀 Use automated alerts in your contract system to avoid missed deadlines!

🛠 Suggestions for Clarity & Improvement: Making Clause 3.7 Even Stronger

📌 A. “Neutrality” of the Engineer – Define It Operationally
🎯 Current Gap: “Act neutrally” is philosophically admirable but contractually vague.
  • Does the Engineer have to disclose conflicts?
  • Avoid ex parte (one-sided) communications?
  • Maintain separate records of engagement?
🛠 Suggested Improvement:
“The Engineer shall act neutrally between the Parties, meaning the Engineer shall not have any undisclosed financial, professional, or personal interests in either Party and shall not engage in unilateral communication during any part of the Clause 3.7 process unless explicitly agreed by both Parties.”
The Engineer shall act neutrally between the Parties.
The Engineer shall act neutrally between the Parties, meaning the Engineer shall not have any undisclosed financial, professional, or personal interests in either Party and shall not engage in unilateral communication during any part of the Clause 3.7 process unless explicitly agreed by both Parties.
Impact: This tweak makes “neutrality” measurable and enforceable—building trust, reducing disputes, and protecting both Parties.

📎 B. Format and Consistency of Notices – Standardize Them

FIDIC requires strict notice titles:
– Determinations must be labeled “Notice of the Engineer’s Determination”.
– NODs must say “Notice of Dissatisfaction with the Engineer’s Determination”.
🎯 Current Challenge: Notices are often inconsistently labeled or lack clear reasons in real projects—risking invalidity.
🛠 Suggested Format Template for a NOD:
Subject: Notice of Dissatisfaction with the Engineer’s Determination Date of Determination: [Insert date] Reasons for Dissatisfaction: - [Clearly outline issue #1] - [Clearly outline issue #2] (add more as needed) Relevant Contract Clauses: - [Insert Clause numbers]
Impact: Using this template ensures notices are valid, reasoned, and preserve your dispute rights—no more lost cases due to bad formatting!

📊 C. Time Limits – Reinforce Them with Built-In Prompts

⏱ The Essentials:
– Engineer: 42 days to issue a determination
– Parties: 28 days to submit a NOD
Missing these windows can make or break a dispute.
🎯 Current Risk: Deadlines are missed—especially during holidays, shutdowns, or staff changes—leading to lost rights or leverage.
Time limits apply, but reminders are not required. Missed deadlines can go unnoticed.
“The Engineer shall notify both Parties, no less than 7 days before the expiration of each applicable time limit under this Sub-Clause, of the pending deadline.”
Impact: Adds transparency and ensures deadlines don’t catch anyone by surprise. A simple prompt can save a Party’s right to dispute.

📂 D. Clarify “Partial Dissatisfaction” – Add Practical Examples

🎯 Current Gap: “Partial dissatisfaction” is buried in the contract, making severability hard to apply in real cases.
🧾 Practical Example:
The Engineer determines the Contractor is entitled to a 10-day extension and $20,000.
The Contractor agrees with the 10 days, but disputes the amount.
✅ What happens?
The Contractor issues a NOD only for the $20,000 — and the 10 days becomes binding on both Parties.
NODs can be issued, but severability isn’t spelled out.
“Where a Party is dissatisfied with only part of the determination, the NOD shall identify which portion is disputed. The undisputed portion shall be deemed severable and shall become final and binding.”
Impact: This addition removes ambiguity, speeds up project elements that are not in dispute, and ensures fair, efficient progress for both Parties.

📑 Suggested Modified Wording (Sub-Clause 3.7.5)

See how a clearer, enforceable revision compares to the original language.
If either Party is dissatisfied with the determination of the Engineer (or a deemed determination or a corrected determination) under Sub-Clause 3.7, then the dissatisfied Party shall give a Notice of Dissatisfaction to the other Party, with a copy to the Engineer, within 28 days after receiving the determination (or corrected determination) or after the time for the Engineer to give the determination has expired. The Notice of Dissatisfaction shall state that it is a Notice of Dissatisfaction with the Engineer’s Determination and shall set out the matter in dispute and the reason(s) for dissatisfaction.
If either Party is dissatisfied with the Engineer’s determination (or a deemed rejection or corrected determination), it shall issue a written notice clearly titled “Notice of Dissatisfaction with the Engineer’s Determination” within 28 days of the relevant trigger date. This notice shall: • Specify whether the dissatisfaction is partial or total, • Clearly identify the disputed element(s) of the determination, • Provide the contractual and factual grounds for dissatisfaction, • Be sent to the other Party and copied to the Engineer. If no such notice is issued within the applicable time limit, the determination shall become final and binding, and enforceable under Sub-Clause 21.7.
Key upgrade: The revised wording removes ambiguity about partial NODs, strengthens enforceability, and improves clarity for all Parties.

✅ Clause 3.7 Practical Checklists (FIDIC Yellow Book 2017)

1. Engineer’s Checklist – Agreement or Determination (3.7.1 & 3.7.2)
StepAction RequiredReference
1Identify trigger clause (e.g., 1.9, 13.3.1, or a Claim)3.7 opening
2Notify both Parties of intent to consult3.7.1
3Begin consultation process within required timeframe3.7.1
4Issue written record of consultation (unless waived)3.7.1
5If agreement is reached, issue Notice of Agreement3.7.1
6If no agreement, issue Notice of Determination within 42 days3.7.2
7Include title, reasoning, and supporting documents3.7.2
8Serve Notice to both Parties formally and simultaneously3.7.2
2. Party Checklist – Responding to Determination (3.7.5)
StepAction RequiredReference
1Record date of receiving Engineer’s Determination3.7.2
2Review determination for satisfaction or disagreement3.7.5
3Draft “Notice of Dissatisfaction with the Engineer’s Determination”3.7.5
4Include reasons and indicate whether dissatisfaction is partial or total3.7.5
5Submit NOD within 28 days to other Party and Engineer3.7.5
6Retain proof of delivery for contractual recordBest Practice
3. Deemed Rejection or Dispute Escalation Checklist
StepAction RequiredTrigger Clause
1Monitor if Engineer failed to determine within 42 days3.7.3
2For Claims: Treat as deemed rejected3.7.3(c)
3For other matters: Treat as Dispute (NOD not needed)3.7.3(a)-(b)
4Decide whether to refer to DAAB under Clause 21.4Clause 21.4
5Prepare dispute file and chronology of 3.7 eventsBest Practice
4. Final & Binding Determination Enforcement Checklist
StepAction RequiredReference
1Confirm no NOD was issued within 28 days3.7.5
2Mark the determination as final and binding3.7.5
3Reflect determination value in next Statement (Contractor)14.3
4Include it in next Interim Payment Certificate (Engineer)14.6.3
5If one Party fails to comply, consider direct arbitration21.6 / 21.7

✉️ Sample Letters – Clause 3.7 (FIDIC Yellow Book 2017)

Fill once → inject everywhere • Copy / Download / Email • Inline editor • Standalone view
3.7.1 Agreement 3.7.2 Determination 3.7.5 NOD (28 days) 3.7.3 Deemed rejection
Placeholders like [Insert Date], [Engineer’s Name], [Employer Name], etc. will be auto-filled.
1. Engineer’s Notice of the Parties’ Agreement (3.7.1)
Tip: attach scanned acknowledgement if you use signature lines.
Subject: Notice of Agreement Between the Parties – Clause 3.7.1  
Date: [Insert Date]  
Project: [Insert Project Name and Contract Number]  
To: [Employer Name] / [Contractor Name]

Dear [Party Name],

Pursuant to Sub-Clause 3.7.1 of the Contract, I confirm that the Parties have reached agreement on the matter referenced below:

Matter: [e.g., EOT for Event XYZ / Evaluation of Variation under Clause 13.3.1]  
Agreed Outcome: [Summarize agreement terms, e.g., 12-day extension, or USD 45,000 payment]  
Date of Agreement: [Insert Date]

This agreement is now binding in accordance with the provisions of the Contract. Please sign below to acknowledge receipt and acceptance.

Yours sincerely,  
[Engineer’s Name]  
[Engineer’s Title]

Acknowledged by Contractor: _____________________  
Acknowledged by Employer: _____________________
2. Engineer’s Notice of Determination (3.7.2)
Remember to attach reasoning & evidence index.
Subject: Notice of the Engineer’s Determination – Clause 3.7.2  
Date: [Insert Date]  
Project: [Insert Project Name and Contract Number]  
To: [Employer and Contractor]

Dear Sirs,

In accordance with Sub-Clause 3.7.2 of the Contract, and following the consultation period under Sub-Clause 3.7.1, I hereby issue my determination regarding the following matter:

Reference: [e.g., Contractor’s Claim dated DD/MM/YYYY]  
Background: [Summarize facts and reference clauses invoked]  
Determination:

Entitlement: [Yes/No]  
Extension of Time: [e.g., 10 calendar days granted]  
Payment: [e.g., USD 20,000 payable under Clause 14.6]  
Reasoning:  
[Provide brief explanation of how determination was made — contractual basis, supporting documentation, etc.]

Please note that under Sub-Clause 3.7.5, either Party may issue a Notice of Dissatisfaction within 28 days of receipt of this Notice should they wish to challenge this determination.

Yours faithfully,  
[Engineer’s Name]  
[Engineer’s Firm]
3. Contractor’s Notice of Dissatisfaction (NOD) – 3.7.5
Switch “Contractor” to “Employer” as needed—either Party may issue NOD.
Subject: Notice of Dissatisfaction with the Engineer’s Determination – Clause 3.7.5  
Date: [Insert Date]  
To: [Employer Name], cc: [Engineer Name]

Dear Sirs,

This is a Notice of Dissatisfaction with the Engineer’s Determination, issued in accordance with Sub-Clause 3.7.5 of the Contract.

Reference: Engineer’s Determination dated [Insert Date]  
Matter: [e.g., Claim for Extension of Time related to XYZ Event]

Grounds for Dissatisfaction:

The Engineer has failed to account for delays attributable to [Event].  
The monetary entitlement assessed does not reflect actual incurred costs supported by submitted records.  
This notice is issued within the 28-day time limit. We consider this matter a Dispute and intend to proceed under Sub-Clause 21.4.

Yours sincerely,  
[Party Representative Name]  
[Position / Company Name]
4. Notification of Deemed Rejection – Engineer’s Inaction (3.7.3)
Use when a Claim determination is not issued within the 42+42 limit.
Subject: Notification of Deemed Rejection under Sub-Clause 3.7.3  
Date: [Insert Date]  
To: [Engineer Name], cc: [Employer Name]

Dear [Engineer],

We refer to our fully detailed Claim dated [Insert Date], submitted in accordance with Sub-Clause 20.2.4. As of today, we note that the Engineer has not issued a determination within the time limit set out under Sub-Clause 3.7.3.

In accordance with the Contract, the Claim is therefore deemed rejected, and the matter shall now be treated as a Dispute under Sub-Clause 21.4.

We reserve our right to refer the matter to the Dispute Avoidance/Adjudication Board without further notice.

Yours sincerely,  
[Party Representative Name]  
[Title / Company]
Copied!

🧾 Clause 3.7 Cheat Sheet – Agreement or Determination (FIDIC Yellow Book 2017)

42-day agreement window → 42-day determination window → 28-day NOD • Engineer acts neutrally
3.7.1 Consultation 3.7.2 Determination 3.7.3 Time limits 3.7.4 Corrections (14/7) 3.7.5 NOD 28 days DAAB (21.4)
View:
Claim path (toggle for Matter path)
🔁 Standard Process Flow
StepActionClause ReferenceTimeline
1️⃣ Matter or Claim arises (referred to the Engineer under 3.7) 3.7(a) list / Clause 20
2️⃣ Engineer consults Parties to reach agreement 3.7.1 Up to 42 days to reach agreement (from referral)
3️⃣ If agreement is reached → Engineer issues Notice of Parties’ Agreement 3.7.1 / 3.7.3 Within the same 42 days
4️⃣ If no agreement → Engineer issues Determination 3.7.2 / 3.7.3 Within next 42 days (after the agreement window)
⏱️ Key Deadlines
EventDeadlineConsequence of Miss
Consultation duration 42 days Proceed to determination window
Engineer’s determination 42 days (after consultation window) Claim → deemed rejection
Notice of Dissatisfaction (NOD) 28 days from receipt (or deemed) of determination Determination becomes final & binding
Typo/Clerical/Arith. error correction 14 days to report → Engineer has 7 days to issue corrected notice Beyond that, original stands (unless revised via Clause 21)
Tip: After a valid NOD, referral to DAAB must be made within 42 days of the NOD, or the NOD lapses.
🚨 What-If Triggers & Remedies
ScenarioOutcomeClause
Engineer fails to determine a Claim in time Claim is deemed rejected 3.7.3
Engineer fails to determine a non-Claim matter in time Becomes a Dispute → DAAB (21.4) 3.7.3
NOD is not issued in time Determination becomes final & binding 3.7.5
Only part of the determination is disputed Disputed part may go to DAAB; balance remains binding 3.7.5
Party ignores binding determination Other Party may proceed to enforcement/arbitration 21.6 / 21.7
NOD is defective (e.g., vague, late) May be invalid → determination stands 3.7.5

Use the switch above to highlight Claim vs Matter outcomes.

📌 NOD Must-Haves (Sub-Clause 3.7.5)
  • ✅ Clearly titled: “Notice of Dissatisfaction with the Engineer’s Determination”
  • ✅ Includes specific reasons for dissatisfaction
  • ✅ Issued within 28 days to both the other Party and the Engineer
  • ✅ Can be partial, but must clearly state the disputed parts
🧮 NOD Deadline Calculator
Enter the determination date/time to compute the final NOD deadline (+28 days) and a suggested reminder.
Copied!

Educational content; tailor to Particular Conditions. Not legal advice.


Suggested Redline of Clause 3.7 – Agreement or Determination (FIDIC 2017)

Neutrality clarified • Clearer Notices • Practical time-keeping & severability
3.7.1 Consultation 3.7.2 Determination 3.7.3 Time Limits 3.7.5 28-day NOD
Tip: Your suggested pre-expiry reminder (−7 days) helps avoid accidental lapses—see Calculator.
📍 Sub-Clause 3.7.1 – Consultation to Reach Agreement No change
Unchanged (already clear and functional).
📍 Sub-Clause 3.7.2 – Engineer’s Determination
Suggested Add-on at the end:
The Engineer shall ensure the Determination includes:
  • A clear title: “Notice of the Engineer’s Determination”
  • Reasoned analysis,
  • Supporting contract references and factual evidence.
📍 Sub-Clause 3.7.3 – Time Limits
Suggested addition at the end:
To support compliance, the Engineer shall notify both Parties no less than 7 days before the expiration of any time limit under this Sub-Clause, including consultation and determination periods.
📍 Sub-Clause 3.7.4 – Effect of Agreement or Determination
Suggested addition:
Where only part of a matter or Claim is agreed or determined, the binding effect shall apply only to the agreed or undisputed portion, provided that the Notice of Dissatisfaction (if any) clearly identifies the disputed element(s). Any uncontested elements shall be treated as severable and final.
📍 Sub-Clause 3.7.5 – Dissatisfaction with Engineer’s Determination
Toggle
BeforeRedlined
Original: If either Party is dissatisfied with the determination of the Engineer, or with a deemed rejection or a corrected determination, then the dissatisfied Party shall give a Notice of Dissatisfaction setting out the matter in dispute and the reason(s) for dissatisfaction. The Notice of Dissatisfaction shall be given to the other Party, with a copy to the Engineer, within 28 days after receiving the determination, or the corrected determination, or the expiry of the time limit stated in Sub-Clause 3.7.3, as applicable. If the dissatisfied Party fails to give the Notice of Dissatisfaction within such period of 28 days, then the determination shall become final and binding.
✍️ Optional Addition to Sub-Clause 3.7 Preamble
To clarify neutrality and procedural transparency, consider this enhancement:
When performing duties under this Sub-Clause, the Engineer shall act neutrally, meaning:
  • Avoiding any actual or perceived conflict of interest,
  • Disclosing any prior engagements or relationships that could impair impartiality,
  • Ensuring equal opportunity for both Parties to present facts or arguments during consultation.
💡 Bonus: Cross-Reference Notes
  • Refer to Sub-Clause 20.2.5 for Claim-based triggers.
  • Refer to Sub-Clause 21.6 for enforcement of final determinations.
Enter the determination date/time to compute:
• Final NOD deadline (e.g., +28 days)
• Suggested reminder (e.g., −7 days)
📄 Quick Draft – NOD Template (click to expand)
Subject: Notice of Dissatisfaction with the Engineer’s Determination

Contract: [Project / Contract No.]
Reference: Sub-Clause 3.7 (FIDIC 2017)

We refer to the Engineer’s determination dated [date] regarding [matter/Claim]. We are dissatisfied with the determination for the following reasons:

1) Scope of dissatisfaction: [Partial / Total]
2) Disputed element(s): [List items]
3) Contractual basis: [Sub-Clauses, e.g., 3.7.2, 3.7.3, etc.]
4) Factual basis: [Key facts, evidence]

This notice is issued within 28 days of receipt/deemed issuance. A copy is being provided to the Engineer and to the other Party in accordance with the Contract.

Signed:
[Name, Position]
[Party]
Date: [____]

Severability tip: If only part is disputed, explicitly list what is not disputed; that portion becomes final and binding.

Copied!

This educational widget illustrates drafting options you may tailor to your Particular Conditions. It is not legal advice.

Leave a Comment

Scroll to Top