Engineering Knowledge Cards.
Confidence HighUpdated 2026-09-25

The contractual definition and form requirements of a Notice under FIDIC 2017 Red Book (1.1.56 + 1.3): formal compliance is constitutive - a non-compliant document is not a Notice

In FIDIC 2017 Red Book, Notice is a term of art: 1.1.56 defines "'Notice' means a written communication identified as a Notice and issued in accordance with Sub-Clause 1.3". Three cumulative elements: (1) in writing; (2) identified as a Notice; (3) issued per 1.3 (signed paper original or designated electronic system, copies to the other side). The logic runs "formal compliance makes it a Notice carrying contractual effect", not "effect first, certification later"; a document failing the elements is an ordinary communication and cannot trigger any mechanism conditioned on giving a Notice - claims (20.2.1: 28-day bar on additional payment) or NODs (1.1.57/3.7.5: the special Notice of Dissatisfaction within 28 days of determination, preconditioning arbitration under 21.4.4).

Applicable Codes

  • FIDIC Conditions of Contract for Construction (Red Book), 2nd ed. 2017 — Sub-Clause 1.1.56, 1.1.57, 1.3, 3.7.5, 20.1, 20.2.1, 20.2.4~20.2.7, 21.4.4
  • FIDIC Conditions of Contract for Plant and Design-Build (Yellow Book), 2017 — 索赔通知条款(同 28 天规则)

Topic Positioning

The contractual definition, constitutive elements, and effect logic of "Notice" in the FIDIC Conditions of Contract for Construction (Red Book), 2nd ed. 2017: what qualifies as a Notice, the consequences of non-compliant communications, and derivatives like the NOD - per the 2017 Red Book text, with the Yellow Book's claim-notice rules analogous, and comparable with GB/T 50500-2024 (both 28 days, different forfeiture).

Core Conclusions

  1. Notice is a term of art in 2017, not everyday "notification". Clause 1.1.56, original: "'Notice' means a written communication identified as a Notice and issued in accordance with Sub-Clause 1.3 [Notices and Other Communications]." Three elements: (1) written; (2) identified as a Notice (the document must itself declare that status); (3) issued per the 1.3 procedure.
  2. Direction of the logic: formal compliance is constitutive, not an "effect certification" - from the moment the elements are met the document is a Notice and automatically carries contractual effect (starting clocks, marking procedural nodes, triggering duties). There is no intermediate state "non-compliant but still a Notice": failing 1.3 makes it an ordinary communication (other communication), unable to start any mechanism conditioned on giving a Notice; conversely, compliance means automatic effect without further validation.
  3. Clause 1.3 requirements (Red Book 2017): (a) in writing, originals either (i) paper, signed by the Contractor's Representative, the Engineer, or the Employer's authorized representative, or (ii) electronic, generated from a system stated in the Contract Data (if not stated, a system acceptable to the Engineer) and transmitted from the electronic address uniquely assigned to each authorized representative (original quoted); (b) documents that are Notices must be "identified as a Notice"; other communications must identify their type and cite the clause under which they are issued; (c) copying: "When a Notice or NOD or certificate is issued by a Party or the Engineer, the paper and/or electronic original shall be sent to the intended recipient and a copy shall be sent to the Engineer or the other Party", and communications must not be unreasonably withheld or delayed. Ordinary correspondence also follows 1.3's writing/delivery rules without being upgraded to Notices.
  4. Derivative - NOD (Notice of Dissatisfaction): 1.1.57 defines it as the Notice a Party may give if dissatisfied with an Engineer's determination etc.; per 3.7.5 it must be given within 28 days of receiving the determination. The NOD is itself a Notice meeting 1.1.56 + 1.3 and is the gateway to escalation: except as provided in 3.7.5's last paragraph, 21.7, and 21.8, "neither Party shall be entitled to commence arbitration of a Dispute unless a NOD in respect of that Dispute has been given" (21.4.4).
  5. Typical consequence of failing notice duties (claims show "form = effect" best): 20.2.1 requires the Notice of Claim as soon as practicable and no later than 28 days after awareness; original: "If the claiming Party fails to give a Notice of Claim within this period of 28 days, the claiming Party shall not be entitled to any additional payment" (with loss of the corresponding EOT claim). Yellow Book 2017 goes further: no EOT, no additional payment, and the Employer discharged from all liability for the claim. Continuing claims (20.2.6) require monthly interim detailed claims with accumulated amounts, and contemporary records must be kept for the Engineer. In practice, "oral/WeChat remarks don't count; a late written notice forfeits outright" - the strictness flows from 1.1.56 + 1.3 plus the rigid 28-day claim clock.
  6. Version background: the 2017 foreword lists "greater detail and clarity on the requirements for notices and other communications" among the edition's main improvements - the definition and proceduralization of Notice is a hallmark of 2017.

Applicable Boundaries

  • Based on the 2017 Red Book text; Yellow Book 2017 claim-notice rules are structurally similar but numbering and wording follow each text. The 1999 and earlier editions differ (1.1.56/1.1.57 are 2017 definitions) - check the old text before citing.
  • The Contract Data and Particular Conditions may set the electronic system, addresses, and language - agreement prevails; this card states the general framework.
  • Two separate rule systems from China: GB/T 50500-2024 Section 8.11 (intention 28 days, report 28 days if silent; "may be deemed waived" / "may be deemed accepted" on non-reply) differs from FIDIC's "not entitled to any additional payment" hard bar - same number, different strength and default effects; do not mix in practice.
  • Oral exchanges or instant messages outside the 1.3 channel are not Notices and start no mechanism - though they may serve as contemporary records evidencing events and losses; substantive rights still require compliant notice procedure.

Further Reading

  • Red Book 2017 originals: 1.1.56 (Notice), 1.1.57 (NOD), 1.3 [Notices and Other Communications] (writing/signing/electronic originals/identification/copying/delivery), 3.7.3/3.7.5 (determination limits and the 28-day NOD window), 20.1, 20.2.1 (28 days), 20.2.4-20.2.7, 21.4.4 (NOD precondition); Yellow Book 2017 counterpart clauses.
  • Domestic comparison and evolution: GB/T 50500-2024 Section 8.11 (8.11.1-8.11.6); the shift from the repealed GB 50500-2013's "loss of claim right on late intention notice" to 2024's "may be deemed waived / handled per contract" - see dedicated cards.

Keywords

Cited By