UK: The SCL Delay And Disruption Protocol: A Second Edition

Last Updated: 11 July 2017
Article by Jeremy Glover

The Society of Construction Law's (SCL) Delay and Disruption Protocol was first published in 2002. The intention was to provide a scheme whereby delay could be better controlled and managed during the construction process. The SCL has always said that, overall, the Protocol aims to set out and be consistent with good practice (rather than best practice). Although the Protocol has no force of law (unless it is adopted into a contract, which is a very rare occurrence), it is often used as a benchmark for how to approach delay analysis. Following the publication of an intermediary update, known as Rider 1, on 1 July 2015, in February 2017 the Second Edition of the Protocol was released.1 There were eight specific terms of reference:

  1. whether the expressed preference should remain for time-impact analysis as a programming methodology where the effects of delay events are known;
  2. the menu and descriptions of delay methodologies for after the event analysis;
  3. whether the Protocol should identify case law (UK and international) that has referenced the Protocol;
  4. record keeping;
  5. global claims and concurrent delay;
  6. approach to consideration of claims (prolongation/disruption – time and money) during currency of project;
  7. model clauses; and
  8. disruption.

The Second Edition helpfully builds on the guidance provided in the Frist Edition and Rider 1. We set out below one to two of the key elements.

Forms of delay analysis

The Second Edition of the Protocol makes it clear that prompt, indeed contemporary, evaluation is to be preferred. There is a new Core Principle 4 which notes as follows:

"4 Do not 'wait and see' regarding impact of delay events (contemporary analysis)

The parties should attempt as far as possible to deal with the time impacts of Employer Risk Events as the work proceeds (both in terms of EOT and compensation). Applications for an EOT should be made and dealt with as close in time as possible to the delay event that gives rise to the application..."

If this is not possible, the Protocol also considers the most appropriate form of delay analysis after the event. Here, the original Protocol recommended that one particular form of delay analysis, namely the time-impact form of delay analysis methodology, be used wherever the circumstances permitted, "both for prospective and (where the necessary information is available) retrospective delay analysis". This was not universally supported and was one of the main reasons for the review of the existing Protocol. One particular issue with the time-impact analysis can be its reliance upon theoretical modelling and not the actual sequence of events. At the same time, the original Protocol made no mention of the "windows" form of delay analysis which has certainly become one of the most used forms of delay analysis, arguably because it is considered to be one of the most reliable.

This omission has now been rectified and under the Second Edition of the Protocol, no one form of delay analysis is preferred, where that analysis is carried out some time after the delay event or its effect. Instead the Second Edition of the Protocol sets out the factors that need to be taken into account in selecting the most appropriate form of delay analysis as well as providing a helpful explanation of many of the delay analysis methodologies currently in common use. It begins with the prudent comment that:

"Irrespective of which method of delay analysis is deployed, there is an overriding objective of ensuring that the conclusions derived from that analysis are sound from a common sense perspective."

The Protocol then lists a number of criteria which should help determine the choice of the appropriate method of delay analysis. These include: the Contract terms, the circumstances of the project, the nature of the relevant or causative events, the claim or dispute, the value of the project, the time available and the available project records as well as the need to ensure that a proportionate approach is taken. There is an emphasis on what actually happened and a recognition that a theoretical delay analysis which is divorced from the facts and common sense can be unhelpful in ascertaining whether in fact the relevant delay event caused critical delay to the completion date and the amount of that delay. The key to establishing the critical path to completion is often the practical analysis of the relevant facts including production and/or resource data, not what the software says.

Concurrent delay

The 2016 pre-release version of the FIDIC Yellow Book included at sub-clause 8.5 the following new provision:

"If a delay caused by a matter which is the Employer's responsibility is concurrent with a delay caused by a matter which is the Contractor's responsibility, the Contractor's entitlement to EOT shall be assessed in accordance with the rules and procedures stated in the Particular Conditions (if not stated, as appropriate taking due regard of all relevant circumstances)."

The SCL say that the approach to concurrent delay in the original Protocol has been amended in the Second Edition to reflect recent case law. The Second Edition defines concurrent delay in this way:

"True concurrent delay is the occurrence of two or more delay events at the same time, one an Employer Risk Event, the other a Contractor Risk Event, and the effects of which are felt at the same time. For concurrent delay to exist, each of the Employer Risk Event and the Contractor Risk Event must be an effective cause of Delay to Completion (i.e. the delays must both affect the critical path). Where Contractor Delay to Completion occurs or has an effect concurrently with Employer Delay to Completion, the Contractor's concurrent delay should not reduce any EOT due."

Where concurrent delay occurs, then any Contractor Delay should not reduce the amount of an extension of time that may be due to the Contractor as a result of the Employer Delay. The Second Edition of the Protocol recognises that true concurrency is rare,2 and this definition is clearly based on the English approach where concurrency is said to arise only where there are events that are equally causative of critical delay. In other words, if one of the events was the dominant cause of delay, then the other would not be truly concurrent because it would not be an effective cause of delay.

When discussing contemporary delay analysis, the Second Edition of the Protocol also notes that, where Employer Risk Events and Contractor Risk Events occur sequentially but have concurrent effects, the delay analysis should determine whether there is concurrent delay and, if so, whether an extension of time is due for the period of that concurrency.

The Second Edition of the Protocol gives the following example. A Contractor Risk Event will result in five weeks' Contractor Delay to Completion, delaying the contract completion date from 21 January to 25 February. Independently and a few weeks later, a variation is instructed on behalf of the Employer which, in the absence of the preceding Contractor Delay to Completion, would result in Employer Delay to Completion from 1 February to 14 February. The Protocol takes the position that the Employer Delay will not result in the works being completed later than would otherwise have been the case because the works were already going to be delayed by a greater period because of the Contractor Delay to Completion. The only effective cause of the Delay to Completion is the Contractor Risk Event.

The approach to notices

We have previously discussed in IQ the importance of complying with project notice procedures and time bars. This is, unsurprisingly, endorsed by Rider 1 which stresses that:

"The parties and the CA should comply with the contractual procedural requirements relating to notices, particulars, substantiation and assessment in relation to delay events..."

This will become ever more important under the new FIDIC Forms which have an increased emphasis on time limits for notices and the provision of further particulars.

Global claims

The Second Edition says this of global claims:

"The not uncommon practice of contractors making composite or global claims without attempting to substantiate cause and effect is discouraged by the Protocol, despite an apparent trend for the courts to take a more lenient approach when considering global claims."

Again, the reference to courts really means "English Courts". The Second Edition continues that Contractors should be aware that there is a risk that a global claim will fail entirely if any material part of the global loss can be shown to have been caused by a factor or factors for which the Employer bears no responsibility. The Contractor must try to provide adequate records to enable the Engineer or other adjudicator to establish a causal link between the Employer's Risk Event and any resultant costs or delay.


This further confirms the importance of maintaining records. The new FIDIC Form will impose a greater burden on all parties. Both the Employer and Contractor must keep such contemporary records as may be necessary to substantiate a Claim. Sub-clause 20.2 notes that:

"'contemporary records' means records that are prepared or generated at the same time, or immediately after, the event or circumstance giving rise to the Claim."

Appendix B of the Protocol lists record types relevant to delay and disruption. Further, Core Principle 1 of the Second Edition notes that:

"Contracting parties should reach a clear agreement on the type of records to be kept and allocate the necessary resources to meet that agreement."

Under the new FIDIC Form, the Engineer may monitor the record keeping and/or instruct the Contractor to keep additional contemporary records. Here the Protocol provides guidelines on the keeping of records and advises that in order to avoid disputes, where practicable, records should be signed by representatives of the Employer and Contractor. The Protocol recognises that there is a cost here (the benefit being that better records mean, in theory, fewer disputes) and specifically notes that:

"Good record keeping requires an investment of time and cost, and the commitment of staff resources by all project participants. It is therefore recommended that, prior to preparing the tender documents, the Employer considers its requirements of the Contractor in relation to record keeping and includes these within the tender documents."

Whether that becomes a standard feature, remains to be seen.


As noted above, the Second Edition of the Protocol has no legal effect unless it is specifically incorporated into a contract. It has also primarily been prepared from a common law perspective. Of course, its fundamental starting point, namely "that transparency of information and methodology is central to both dispute prevention and dispute resolution", is universal. Where, however, the Protocol continues to have value and an increasing influence is by providing guidance as to good (and even best) practice.


1. For further details, please go to the SCL website:

2. The example often given, and indeed given in the Protocol, is the commencement date, where, for example, the Employer fails to give access to the site, but the Contractor has no resources mobilised to carry out any work.

International Quarterly is produced quartely by Fenwick Elliott LLP, the leading specialist construction law firm in the UK, working with clients in the building, engineering and energy sectors throughout the world.

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.

Jeremy Glover
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.