Professional Documents
Culture Documents
Analysis of complex construction delay issues has always been contentious leading to disputes between the Parties
In order to overcome and facilitate settlement of disputes, experts agreed on a standard called the
SCL Delay and Disruption Protocol
The SCL Protocol was finalized in October 2002 after several years of deliberations and considerable debate and agreement between experts from different backgrounds
The objective of the SCL Protocol was to bring reasonableness and fairness into the delay assessment process and to eliminate widespread manipulation of complex delay issues
Referral to case law from jurisdictions from around the world was a further cause for concern. The Protocol aimed at (and was able to considerably) reduce or eliminate references to case law from complex and alien jurisdictions
The SCL Protocol tried to standardize the issues such that disputes would be reduced or eliminated
Hundreds of Contracts are ongoing in the UAE. Generally, these Contracts do not specifically define a standard system of dealing with contentious delay issues. This makes it even more imperative to adopt a Standard
It is recommended that;
should be adopted as a Standard and should be, where possible, incorporated in the Construction Contracts
www.eotprotocol.com
3.
Guidance Section 3
4.
Guidance Section 4
5.
Appendices Appendix A Definitions and glossary Appendix B Model specification clause Appendix C Model records clauses Appendix D Graphics illustrating points in this Protocol
The remaining slides of this lecture will review and discuss the basic Principles suggested and recommended by the
SCL Protocol
RULE NO. 1
If there is an Employers delay, which is beyond the Contractors control, and if this delay impacts the Completion Date of the Works,
RULE NO. 2
For the case of recovery of delay (or prolongation) costs incurred due to the Employer delays, the Contractor must be able to prove that there has been no other delay, which is in his own control, and which is equally (or partly) contributing for delaying the Time for Completion.
RULE NO. 3
Where Contractors Delay to Completion occurs concurrently with Employers Delay to Completion, the Contractors concurrent delay should NOT reduce any Extension of Time (EOT), which is due.
[Result of Rule No. 1 will not change and is irrespective of the result of Rule No. 2]
The foregoing Rules proposed by the SCL Protocol are meant to bring fairness and reasonableness into the delay assessment process. [The emphasis of the SCL Protocol is that no one Party should benefit from default of the other Party]
Core Principle No. 7 - Float as it relates to time Unless there is express provision to the contrary in the contract, where there is remaining float in the programme at the time of an Employer Risk Event, an EOT should only be granted to the extent that the Employer Delay is predicted to reduce to below zero the total float on the activity paths affected by the Employer Delay. Guidance Section 1.12.1 If as a result of an Employer Delay, the Contractor is prevented from completing the works by the Contractors planned completion date (being a date earlier than the contract completion date), the Contractor should in principle be entitled to be paid the costs directly caused by the Employer Delay, notwithstanding that there is no delay to the contract completion date (and therefore no entitlement to an EOT), provided also that at the time they enter into the contract, the Employer is aware of the Contractors intention to complete the works prior to the contract completion date, and that intention is realistic and achievable.
Guidance Section 1.4.12 Where there has been Employer Delay, this may prevent the Employer charging the Contractor with LDs for failure to achieve a contract completion date
Principles & Provisions of the SCL Protocol relevant to Figure 9 of Appendix D Slide 1/2
Guidance Section 1.4.1 Where Contractor Delay to Completion occurs concurrently with Employer Delay to Completion, the Contractors concurrent delay should not reduce any EOT due. Guidance Section 1.4.7 Where Employer Risk Events and Contractor Risk Events occur sequentially but have concurrent effects, here again any Contractor Delay should not reduce the amount of EOT due to the Contractor as a result of the Employer Delay. Concurrency (Appendix A Definations and Glossary) 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. The term concurrent delay is often used to describe the situation where two or more delay events arise at different times, but the effects of them are felt (in whole or in part) at the same time. To avoid confusion, this is more correctly termed the concurrent effect of sequential delay events.
Principles & Provisions of the SCL Protocol relevant to Figure 9 of Appendix D Slide 2/2
Core Principle No. 9 - Concurrent delay its effect on entitlement to extension of time Where Contractor Delay to Completion occurs or has effect concurrently with Employer Delay to Completion, the Contractors concurrent delay should not reduce any EOT due. Core Principle No. 14 - Link between extension of time and compensation Entitlement to an EOT does not automatically lead to entitlement to compensation (and vice versa). Core Principle No. 10 - Concurrent delay its effect on entitlement to compensation for prolongation If the Contractor incurs additional costs that are caused both by Employer Delay and concurrent Contractor Delay, then the Contractor should only recover compensation to the extent it is able to separately identify the additional costs caused by the Employer Delay from those caused by the Contractor Delay. If it would have incurred the additional costs in any event as a result of Contractor Delays, the Contractor will not be entitled to recover those additional costs.