UK: FIDIC Notice Requirements: When To Give Notice Of Entitlement

Last Updated: 25 July 2014
Article by David Robertson


Under the FIDIC Yellow Book Conditions, a contractor must give notice of a delaying event within 28 days or risk losing its entitlement to an extension of time. This reflects standard practice for international EPC contracts. A properly drafted 'notice condition precedent' will be enforceable (under English law) and can have dramatic consequences for a contractor – in some circumstances leaving the contractor liable for delay liquidated damages even where the project owner is responsible for the delay.

Under the relevant notice clauses in the FIDIC Yellow Book Conditions, notice must be given within 28 days of any event the result of which is that the date for completion 'is or will be delayed'.

This has traditionally been understood to place the burden on a contractor to notify not only an event which has an immediate and measurable impact on the completion date, but also one which will, at some time in the future, have such an impact.

A recent English High Court case has offered an alternative interpretation of this notice obligation which is more accommodating to contractors and may permit a valid notice to be served at a later date than previously thought.

Legal advisers to both contractors and owners should take note; the former to take full advantage of an approach which reduces the risk of losing an entitlement and the latter to consider drafting amendments to clarify the intention that notice must be given at the earliest possible stage.

The case

The English High Court (Technology & Construction Court) judgment, Obrascon Huarte Lain SA v Her Majesty's attorney General for Gibraltar [2014] EWHC 1028 (TCC), decided a dispute concerning a road and tunnel project in Gibraltar. The dispute arose under a contract based on the FIDIC Conditions of Contract for Plant and Design-Build (known as the Yellow Book).

The primary issues were allocation of ground conditions risk and the lawfulness of the termination of the contract. However, Mr Justice Akenhead also expressed an interesting view on the interpretation of the notice requirements contained in Clauses 20.1 (Contractor's claims) and 8.4 (Extension of time for completion) of the FIDIC Conditions of Contract.

FIDIC notice requirements – a condition precedent

Clause 20.1 of FIDIC Yellow Book provides as follows:

"If the Contractor considers himself to be entitled to any extension of the Time for Completion and/or any additional payment ... the Contractor shall give notice to the Engineer, describing the event or circumstances giving rise to the claim. The Notice shall be given as soon as practicable, and not later than 28 days after the Contractor became aware, or should have become aware, of the event or circumstance.

If the Contractor fails to give notice of a claim within such period of 28 days, the Time for Completion shall not be extended, the Contractor shall not be entitled to additional payment, and the Employer shall be discharged from all liability in connection with the claim."

Clause 20.1, which is identical in the FIDIC EPC/Turnkey Contracts (Silver Book), is a well drafted 'condition precedent' clause. This means that (under English law, at least) a failure to give the required notice will result in the Contractor losing its entitlement to an extension of time and/or additional payment in respect of an otherwise valid claim.

It should be noted that the law in some jurisdictions will limit the effectiveness of notice conditions precedent, the Arabic Civil Codes in the Gulf Region, for example.

Clause 8.4 of the FIDIC Yellow Book (again identical to the Silver Book) outlines when an entitlement to an extension of time arises as follows:

"The Contractor shall be entitled ... to an extension of Time for Completion if and to the extent that completion ... is or will be delayed by any of the following causes:"

Clause 8.4 then lists the events which entitle the Contractor to an extension of time.

'Is or will be delayed' – notify now or in the future?

Clause 8.4 defines when, for the purposes of Clause 20.1, the Contractor could 'consider himself entitled to an extension of time' and, therefore, when the 28 day window for notice starts running. The trigger is where completion 'is or will be delayed' by one of the listed events.

Similar formulations of this language are commonly found in international EPC contracts. For example:

"The Contractor must without undue delay give notice ... of all ... events ... affecting or likely to affect the progress of the Works such that the achievement of the Guaranteed Completion Date for the Plant will or is likely to be delayed."
[Extracted from the EPC contract for a project financed process plant in the Middle East.]

Language linking a notice obligation to both the occurrence of an event having an immediate impact, and also to one which 'will' or 'is likely to' have an impact, was introduced into EPC contracts to offer greater protection to an owner's interests.

Earlier EPC contracts only required that notice be given of events 'which caused a delay'. This caused difficulties where project owners wished to make the giving of notice within a fixed (and short) time period a pre-condition to any entitlement. For example, where it was not immediately clear to the contractor whether a particular event would cause a delay or not, or where an event had no immediate impact, but caused a delay to a future activity which may not have been critical at the time of the original event.

Problematic situations like this led to interpretative difficulties which left some conditions precedent unenforceable or construed against the owners on the basis that the notice obligation was uncertain.

Language of the type used in Clause 8.4 of the FIDIC Conditions was thought to eliminate this problem by requiring a contractor to give notice of both actual and potential delay events. This has placed an additional burden on contractors to consider whether notice is required even where an event does not immediately impact activities which are on the critical path at the time of its occurrence.

The decision

In the case cited above, Akenhead J noted that the contractor's entitlement to an extension of time can arise when the completion date 'is or will be delayed' by a particular event. He concluded that the extension of time can be claimed either when it is clear that there will be delay (a prospective delay), or when the delay has been at least started to be incurred (a retrospective delay).

In reaching this conclusion, Akenhead J noted that the wording of Clause 8.4 does not say that notice is to be given when completion 'is or will be delayed, whichever is the earliest'; the absence of this express requirement leaving it open to the contractor to notify at either point.

Given the serious effect of vitiating a party's contractual right to claim, Akenhead J considered that the clause should be strictly construed against the owner.

An illustration

Let's briefly consider the implications of this interpretation by reference to a scenario where a variation is instructed to a part of the works which is programmed to fall on the critical path, but which at that time of the instruction, has not been commenced.

On the interpretation offered in this case, the contractor's obligation to notify is triggered either at the point of the instruction when it is known that the event 'will' cause a delay, or at the later point when work commences on the variation and delay 'is' being caused.

In the absence of clear language requiring the contractor to give notice at the earlier of these two points, Akenhead J decided that the contractor can, in effect, choose which point to treat as the trigger.

Key point to take away

Akenhead J either did not consider that the requirement in Clause 20.1 that notice be given 'as soon as practicable' altered this interpretation, or was not directed to consider this point.  However, these words are, arguably, insufficiently express to detract from his interpretative approach.

It remains good practice for contractors to serve notices at the earliest possible date to avoid the risk of losing an entitlement and there are good commercial reasons for a project owner to require this.  However, this interpretation may provide greater flexibility to contractors to retrospectively notify events the impact of which was not fully understood at the time.

Legal advisers for owners, on the other hand, may wish to consider amending such clauses in the future to clarify that the notice condition is triggered by the earlier of the dates on which delay is caused or will or is likely to be caused.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.