Riyadh, Saudi ArabiaCR 7038223082
Sun - Thu, 9:00 - 18:00info@vendorloc.com
Calculate your BIM feeBIM feeالعربية

PMO and project controls

Extension of time: what the SCL Protocol says about float, concurrent delay and records

Published: 6 min readPrepared by the VendorLoc technical team

Service page: PMO and project controls

From delay event to extension of time1Delay eventnotice under thecontract2Critical pathdoes it delaycompletion?3Floatis any total floatleft?4Time and costtwo linkedsubmissions5Recordsmade at the time,facts only
From delay event to extension of time1Delay eventnotice under the contract2Critical pathdoes it delay completion?3Floatis any total float left?4Time and costtwo linked submissions5Recordsmade at the time, facts only

When a delay hits a project, the first argument is nearly always about time: is the contractor entitled to an extension of time (EOT), and for how many days? The Society of Construction Law (SCL) Delay and Disruption Protocol, 2nd edition (February 2017), is one of the most cited references on that question. This article sets out what it says on float, concurrent delay and records, and what a project controls team can do with it.

This is a guide for project controls and contract teams, not legal advice. The Protocol is guidance. Your contract and its governing law decide entitlement, and Particular Conditions often change the position.

What the Protocol is, and what it is not

The Protocol is built on 22 Core Principles, with guidance on each in Part B and a list of typical project records in Appendix B. The 2nd edition was a partial review of the 2002 first edition. Its drafters state that it should continue to focus on the UK construction market and English law, and that it is not meant to be incorporated into a contract as a contract document.

That matters on Saudi projects. Most are built on FIDIC-based forms with amended Particular Conditions. Treat the Protocol as a benchmark of good practice that a tribunal or an employer's consultant may recognise, and check every point against the contract you signed.

Why an EOT matters

Core Principle 2 gives the purpose. For the contractor, an EOT removes liability for delay damages (usually liquidated damages) for the period before the extended completion date, and allows the works to be reprogrammed. For the employer, it sets a new completion date and stops time for completion becoming "at large", which also lets the employer plan its own activities.

Do not wait and see

Core Principle 3 says the parties and the contract administrator should follow the contract's procedural requirements for notices, particulars, substantiation and assessment. Core Principle 4 adds that delay events should be dealt with as the work proceeds. Applications for an EOT should be made, and assessed, as close in time to the delay event as possible, and a "wait and see" approach is discouraged. The 2nd edition raised contemporaneous assessment to a Core Principle, which the 1st edition did not do.

A contractor can be entitled to an EOT only for events or causes of delay for which the employer has taken the risk, and only where they affect the critical path (Core Principles 4 and 5). If the full effect of an event cannot yet be predicted, Core Principle 7 says the contract administrator should grant an EOT for the effect that can be predicted, then review it at intervals and increase it if appropriate. It should not be reduced unless the contract expressly allows that.

Float

Core Principle 8 starts from the point that float shows how critical an activity is, and that when float is used up, the completion date is usually affected. Unless the contract says otherwise, where total float remains when an employer risk event occurs, an EOT should only be granted to the extent the event is predicted to take total float on the affected critical path below zero. In plain terms: a delay that is absorbed by float does not extend the completion date.

Core Principle 9 adds that float is far easier to identify when there is a properly prepared and regularly updated programme. The wording "unless there is express provision to the contrary" is important. If your contract says who may use float, or how it is shared, the contract wins over the Protocol.

Concurrent delay

Core Principle 10 defines true concurrent delay as two or more delay events occurring at the same time, one an employer risk event and the other a contractor risk event, with their effects felt at the same time. Both must be an effective cause of delay to completion, meaning both must affect the critical path. Where that is the case, the contractor's concurrent delay should not reduce the EOT due.

Time and money are treated differently. Core Principle 12 says entitlement to an EOT does not automatically give entitlement to compensation. Under Core Principle 14, where the delays are concurrent, the contractor recovers prolongation costs only if it can separate the additional costs caused by the employer's delay from those caused by its own. The drafters changed the concurrent-delay approach in the 2nd edition to reflect recent case law, so older summaries of the Protocol may be out of date on this point.

Records

Core Principle 1 asks the parties to agree the type of records to be kept, to allocate resources to keep them, and for the contractor to prepare, and the contract administrator to accept, a proper programme. That programme should then be updated for actual progress, variations, changes of logic, methods and sequences, mitigation or acceleration measures and any EOTs granted.

Part B and Appendix B add detail:

  • Records must be produced contemporaneously as the work progresses, not afterwards.
  • Appendix B groups typical records into six categories: programme, progress, resource, costs, correspondence and administration, and contract and tender documents.
  • Progress, resource and cost records should set out facts only, with no opinions, and where practicable be signed by both the contractor and the contract administrator.
  • Records should be electronic and searchable. Apart from emails, the Protocol suggests searchable PDF in a document management system, with emails, programmes and spreadsheets that contain formulae kept in native format.

Choosing a delay analysis method

The 1st edition preferred time impact analysis where the effects of delay events were known. For analysis done a long time after the event, the 2nd edition no longer names a preferred method. It lists the factors to weigh when selecting one and gives an overview of the methods in common use. Core Principle 11 notes that where an EOT is assessed after completion, or long after the event, a prospective analysis may no longer be appropriate.

A routine for the project controls team

The points below are our working practice, built on the principles above. They are not quotations from the Protocol.

  • Agree the records on day one. Name who produces, checks and stores each category, and how often.
  • Keep the accepted programme alive. Update it every period with actual progress, logic changes and a short narrative, so float and the critical path can be read at any date.
  • Tie every delay event to a notice. Keep one register that links the event, the notice date, the programme effect and the status of the EOT request.
  • Check float and critical path before submitting. An application that ignores remaining float will be answered with it.
  • Submit time and cost separately. The EOT and the compensation claim have different tests, so prepare them as two linked documents.
  • Review the EOT as the impact unfolds. Where the effect is not yet clear, ask for what is predictable now and update it.

If you want a records plan, a programme health check or an EOT assessment set up on your project, our PMO and project controls team can start from your contract and latest programme.

Sources

  1. Society of Construction Law, Delay and Disruption Protocol, 2nd edition (February 2017)