The Cost Consultant

📌 FIDIC Red Book 2017 | Sub-Clause 1.6 — Contract Agreement

Contract Agreement — What Every Contractor & Employer Must Know

Sub-Clause 1.6 of the FIDIC Red Book (2017) is one of the most critical provisions at the start of any construction project. It governs when and how the formal Contract Agreement must be signed between the Employer and the Contractor.

📝 The Rule: "The Parties shall sign a Contract Agreement within 35 days after the Contractor receives the Letter of Acceptance — unless they agree otherwise."

Here's what every contract professional needs to know 👇

⏰ 35-Day Deadline — Signing must happen within 35 days of receiving the Letter of Acceptance.

📄 Prescribed Form — The Agreement must be based on the form annexed to the Particular Conditions (Special Provisions).

💰 Stamp Duty Costs — All stamp duties and similar legal charges imposed by law are borne by the Employer.

👥 JV Requirement — If the Contractor is a Joint Venture, the authorised representative of EACH member must sign the Contract Agreement.

⚠️ Pro Tip: If lengthy tender negotiations took place, explicitly record the Accepted Contract Amount, Base Date and/or Commencement Date in the Agreement. Where local law makes formal signing MANDATORY, remove the words "unless they agree otherwise" from the clause.

Failing to execute the Contract Agreement on time can create legal uncertainty about the enforceability of contract terms. Don't overlook this administrative step — it's the foundation of your project's legal framework. ✅

🏗️ Mastering FIDIC 2017 Red Book:
1.5 Priority of Documents
In complex construction projects, it is common to find discrepancies between drawings and specifications. Sub-Clause 1.5 [Priority of Documents] provides the ultimate roadmap for resolving these conflicts and ensuring all project participants are on the same page.

⚖️ The Hierarchy of Documents
The FIDIC Red Book 2017 establishes a clear sequence of priority. If a conflict, ambiguity, or discrepancy is found, the documents rule in this order:

a) The Contract Agreement.
b) The Letter of Acceptance.
c) The Letter of Tender.
d) Particular Conditions Part A – Contract Data.
e) Particular Conditions Part B – Special Provisions.
f) The General Conditions.
g) The Specification.
h) The Drawings.
i) The Schedules.
j) The JV Undertaking (if the Contractor is a Joint Venture).
k) Any other documents forming part of the Contract.

🧩 What does "Mutually Explanatory" mean?

The Clause states that all Contract documents are to be "taken as mutually explanatory of one another". This means the Contract should be read as a single, cohesive unit where the various parts complement each other rather than being viewed in isolation. The priority list only acts as a "tie-breaker" when the documents are in direct conflict and cannot be reconciled through a unified reading.

🛠️ The Procedure for Resolving Conflicts

If you find a discrepancy, you cannot simply choose the document that favors your position. The Red Book mandates a specific process:

• Prompt Notification: The Party who finds an ambiguity must promptly give a Notice to the Engineer describing the issue.

• Engineer’s Role: After receiving Notice, or if the Engineer finds a discrepancy themselves, the Engineer must issue a clarification or instruction to resolve it.

• Right to Claim: A Party can raise a Claim under Sub-Clause 20.1(c) for the rectification of an ambiguity or discrepancy found in the documents.

💡 Key Insights for Contract Management

• Tender Clarity: It is recommended that tender documents explicitly state that Contract Data (Part A) takes precedence over Special Provisions (Part B), which in turn take precedence over the General Conditions.
• Internal Specification Priority: If your Specification consists of multiple volumes, you may want to amend sub-paragraph (g) to define an internal order of precedence between those specific documents.
• Governing Law: If Parties choose not to set a fixed hierarchy, priority may be determined by governing law, with the Engineer retaining authority to issue instructions to resolve the conflict.

Understanding the priority of documents is essential for effective risk management and avoiding costly disputes on-site!

🏗️ Mastering FIDIC 2017 Red Book:

📘 FIDIC 2017 Red Book | Sub-Clause 1.4 – Law and Language
Sub-Clause 1.4 lays down the fundamental legal and linguistic framework of the Contract. It eliminates uncertainty by clearly identifying which law governs the Contract and which language prevails in all contractual documents and communications—an essential safeguard for enforceability, consistency, and effective contract administration.

This Sub-Clause is structured around three key pillars:

1️⃣ Governing Law

Primary Rule: The Contract shall be governed by the law of the country or jurisdiction expressly stated in the Contract Data.

Default Rule: Where no governing law is stated, the applicable law shall be the law of the Country in which the Site is located and the Permanent Works are executed.

Legal Limitation: The governing law applies to the exclusion of conflict of laws rules, preventing indirect reference to another legal system and closing potential legal loopholes.

2️⃣ Ruling Language

Definitive Version: The ruling language is that stated in the Contract Data. If none is stated, it defaults to the language in which the Conditions of Contract are written.

Precedence: Where Contract documents are issued in more than one language, the version in the ruling language shall prevail in the event of any inconsistency—an essential principle supporting the Priority of Documents under Sub-Clause 1.5.

3️⃣ Language for Communications

Standard for Interaction: All Notices and other communications (as defined under Sub-Clause 1.3) shall be issued in the language stated in the Contract Data.

Default Setting: If no language is specified, communications shall be in the ruling language of the Contract.

Personnel Requirement: The importance of this obligation is reinforced by requiring the Engineer, the Contractor’s Representative, and Key Personnel to be fluent in the designated language to ensure effective management, coordination, and safety.

🔍 The Bottom Line
Sub-Clause 1.4 defines the “rules of the game” by fixing the legal jurisdiction and the authoritative language of the Project. Without these clear parameters, projects risk deadlock—where disputes arise not from technical issues, but from disagreements over which law applies or which wording is legally binding.

A small clause with major contractual consequences.

.4

Shout out to my newest followers! Excited to have you onboard! Thusitha Sandun, Asantha Jeevanath, Zamudika Amarawansha