FIDIC Sub-Clause 1.3: How to Serve a Notice That Actually Counts
The notice went out on day 19 of a 28-day window — nine days to spare, the right clause cited, the awareness date correct. Then the Engineer's reply arrives: it was never received, because it was emailed to the Resident Engineer's personal inbox instead of the address named in the Contract Data. A claim that should have been safe is now arguing about whether it was served at all. Sub-Clause 1.3 is the clause that decides that argument — and the one almost nobody reads until this happens to them.
What Sub-Clause 1.3 Actually Governs
Sub-Clause 1.3 — "Communications" under the FIDIC 1999 Red Book, "Notices and Other Communications" under FIDIC 2017 — fixes how every notice, approval, certificate, consent, instruction, or determination under the contract has to be given for it to count: the form it must take, the method it may travel by, and the address it has to reach.
What it does not do is tell you who should receive a particular notice. That is decided by the specific clause giving rise to it — Sub-Clause 20.1 (1999) or 20.2 (2017) names the Engineer as the recipient of most Contractor's claims, Sub-Clause 15.2 names the Contractor as the recipient of an Employer's termination notice, and so on. Sub-Clause 1.3 only decides whether the way you reached that recipient was valid.
That distinction matters because 1.3 reads like boilerplate and rarely gets argued on a smooth project. It becomes the first thing an opposing party reaches for to defeat a notice without touching its merits — attacking the envelope instead of the letter, because that is the cheaper fight to win.
Key Takeaway: Sub-Clause 1.3 governs the form, method, and address for every communication under the contract. It does not name who should receive a given notice — that comes from the clause that created the obligation to notify in the first place.
Form: What Turns a Letter Into a "Notice"
The first requirement is the most overlooked: a communication has to be identifiable as what it is meant to be. An email that mentions a delay in passing, inside a longer thread about something else, is correspondence — not automatically a Notice, however clearly the problem is described.
The safer habit: state plainly that it is a Notice, name the Sub-Clause it is given under, and keep it as its own message rather than a paragraph in an unrelated thread. A short, labelled block at the top does more work than a well-written closing paragraph ever will:
Nothing in that heading block argues the claim. It just removes any question about what the document is and which clause it is served under — the things Sub-Clause 1.3 cares about before anyone reaches the merits.
Key Takeaway: Label it. A communication that doesn't say it is a Notice and doesn't name the Sub-Clause invites the argument that it was never a formal Notice — regardless of how clearly it describes the problem.
Method: Why Email Isn't Automatically Enough
Sub-Clause 1.3 permits a short list of methods — hand delivery against receipt, mail, courier, or an agreed electronic system — but only the ones actually named for that recipient count. Under FIDIC 1999 those sit in the Appendix to Tender; under 2017 they sit in the Contract Data, which can also name a Common Data Environment the parties have agreed to use.
The practical trap: most teams communicate entirely by email on contracts where the Appendix to Tender or Contract Data was never updated to name email as an agreed method. Everyone treats it as obviously fine because it works for everything else — until a notice's validity is disputed, at which point "we've always done it this way" is not what the clause asks for. What it asks for is the agreed method, or written confirmation from the recipient accepting one.
Whichever of ChatNotice's notice types you draft — weather delay, variation claim, unforeseen conditions, or any other — the app gets the clause reference and content right, but the Sub-Clause 1.3 method and address are a separate, contract-specific check no drafting tool can confirm for you.
Key Takeaway: Email only satisfies Sub-Clause 1.3 if it is a method actually named for that recipient in the Contract Data or Appendix to Tender, or later agreed in writing — not merely because it is the method everyone happens to use.
Address: The Right Words Can Still Land in the Wrong Inbox
Sub-Clause 1.3 requires delivery to the address stated for the recipient's communications — not merely to someone who works for the right company. A notice sent to a named individual's personal inbox, rather than the address the contract actually states, carries the same vulnerability as one sent by the wrong method: flawless content, disputable delivery.
There is one built-in escape: if the recipient has given notice of a different address, communications are thereafter validly sent there instead. That update has to come from the recipient, in writing — not assumed by the sender because an individual happens to reply from a different account.
This is a narrower question than the one covered in who should receive a delay letter — Engineer or Employer. Sub-Clause 1.3 assumes you already know the correct recipient, and asks only whether the address and channel you used to reach them is the one the contract actually names.
Key Takeaway: "The right company" is not "the stated address." Send to the address named in the Contract Data or Appendix to Tender, and treat a different address as valid only once the recipient has confirmed it in writing.
FIDIC 1999 vs 2017: What Changed
The FIDIC 1999 wording is comparatively light — written communications, by hand, mail, courier, or an agreed electronic system, to a stated address. It never spells out that a communication has to announce itself as a Notice, which left room for exactly the dispute this guide opened with: was that email a Notice, or just an update?
The FIDIC 2017 Second Edition closes that gap. A communication intended to operate as a Notice now has to be identified as a Notice and state the Sub-Clause or other provision it is given under — turning the labelling habit this guide recommends into something closer to a contractual requirement. The 2017 edition is also more explicit about electronic transmission, including the option to name a Common Data Environment in the Contract Data as the agreed channel.
The reason is well documented in FIDIC commentary and the case law around notice validity generally: 1999-style disputes often turned on whether an informal communication satisfied a formal requirement, and 2017 removes that argument by making the formality explicit up front.
Key Takeaway: FIDIC 2017 requires a Notice to identify itself as a Notice and cite the Sub-Clause it is given under — a more prescriptive version of a requirement FIDIC 1999 leaves open to argument.
How This Interacts With the 28-Day Clock
Sub-Clause 1.3 does not create or move any deadline — the 28-day period for a notice of claim comes from Sub-Clause 20.1 or 20.2, and the 28-day rule runs exactly the same way regardless of how the notice is served. What 1.3 decides is whether a communication sent within that window counts as having been given at all — and that is the sting in the tail: a notice failing on form, method, or address can be treated as never served, which has the same practical result as missing the deadline outright, except it was entirely avoidable and often only surfaces months later.
Key Takeaway: A notice served on day 5 that fails Sub-Clause 1.3 is, in practical effect, no better off than a notice served on day 35. Being early protects nothing if the delivery itself is disputable.
Common Sub-Clause 1.3 Mistakes
- Treating a general email as a Notice. Mentioning a delay in an unrelated thread, with no label and no clause reference, invites the argument it was never a formal Notice.
- Using an unnamed electronic method. Email feels universal; the clause only cares whether it was actually named for that recipient.
- Sending to a person instead of the stated address. The right company with the wrong inbox is still the wrong address under the clause.
- Assuming an address changed informally. A different reply-from account is not the recipient formally notifying a new address.
- Addressing the wrong party for the clause relied on. Sub-Clause 1.3 won't rescue a notice sent to the Employer when the specific clause names the Engineer, or vice versa.
- No record the valid method was used. Hand delivery and courier generate proof automatically; a named electronic system should still be logged with a timestamp.
Key Takeaway: Every mistake on this list is a form failure, not a merits failure — which is why they are so avoidable and so costly. Check the Contract Data's named method and address before the notice goes out, not after it is challenged.
Frequently Asked Questions
Does an email count as a valid FIDIC notice?
Only if email is one of the methods actually named for that recipient under Sub-Clause 1.3 — either stated in the Contract Data (FIDIC 2017) or the Appendix to Tender (FIDIC 1999) as an agreed electronic transmission system, or later confirmed in writing by the recipient. Many older FIDIC contracts were never updated to name email even though every day-to-day communication on the project runs through it. If email was never named or agreed, sending the notice only by email leaves it open to challenge, however clearly it was written.
What happens if a notice is sent to the wrong address or person?
It can be treated as never validly given, regardless of its content or timing. Sub-Clause 1.3 requires delivery to the address stated for the recipient's communications, not merely to someone at the right company. A notice correctly drafted and sent nine days before a 28-day deadline but delivered to a personal inbox instead of the stated address can be disputed on exactly that basis — the clock keeps running because, as far as the contract is concerned, nothing was served.
What changed for notices under the FIDIC 2017 edition?
FIDIC 2017 tightens Sub-Clause 1.3 considerably compared with 1999. A communication that is meant to be a Notice now has to be identified as a Notice and state the Sub-Clause or other provision it is given under, closing off the argument that a general letter or email mentioning a problem should count as the formal notice. The 2017 edition is also more explicit about electronic transmission systems and a Common Data Environment, where the Contract Data names one.
Does Sub-Clause 1.3 change the 28-day notice deadline?
No, Sub-Clause 1.3 does not set or move any deadline itself — the 28-day period for a notice of claim comes from Sub-Clause 20.1 (1999) or 20.2 (2017). What 1.3 does is decide whether a communication sent within that period counts as having been given at all. A notice that misses 1.3's form, method, or address requirements can be treated as not served, which has the same practical effect as missing the deadline outright.
Can a bespoke contract change the Sub-Clause 1.3 requirements?
Yes. Sub-Clause 1.3 is a default procedural mechanism, and the Contract Data or Appendix to Tender — and any Particular Conditions amending the clause itself — can name different addresses, add or remove permitted methods, or impose extra formality such as a required subject line or reference number. Always check the project's actual Contract Data first; the standard FIDIC wording only applies to the extent it has not been amended.
Authoritative Sources
This guide reflects the FIDIC Conditions of Contract and established construction-law authority:
- FIDIC Conditions of Contract — the official contract suite published by the International Federation of Consulting Engineers, which sets out the Sub-Clause 1.3 communications procedure referenced throughout this guide.
- Obrascon Huarte Lain SA v HM Attorney General for Gibraltar — the leading authority on when a communication under a FIDIC contract is validly treated as a notice of claim.
About the Author
Muhammad M. Jiwani is a Project Director with 15 years' experience on major infrastructure and energy projects administered under FIDIC contracts. He writes from first-hand experience serving notices and managing contractual claims on live projects.