Construction Claims
The SCL Protocol, in Practice · Part 1 of 24
What the SCL Protocol Is Actually Trying to Solve
The SCL Delay and Disruption Protocol is a shared rulebook for how to have the delay conversation well — not a verdict on how it ends. It is not law, not a contract, and it decides no one's entitlement. Used from day one, it stops most disputes before they start.
The SCL Delay and Disruption Protocol is a best-practice guide for handling delay and disruption on construction projects. It exists to stop the same arguments happening on every job — by promoting clear programmes, good records, prompt assessment and consistent methodology. It is not law, it is not a contract, and it does not decide who is entitled to what. Think of it as a shared rulebook for how to have the conversation, not a verdict on how it ends.
The construction-site version
Picture a progress meeting that has gone sideways. The Contractor says the job is late because of the Employer’s late drawings. The Employer says no — it’s late because the Contractor was short of labour for two months. Both point at the same 90-day slip and both are certain they’re right. Nobody has an agreed baseline, the programme hasn’t been updated since month three, and the site records are three different spreadsheets that don’t reconcile.
The Protocol doesn’t walk into that room and announce a winner. What it does is describe the disciplined way both parties should have been working, so the argument never got this bad — an accepted baseline, regular updates, contemporaneous records, and delay assessed close to the event rather than reconstructed eighteen months later from memory. Follow it from day one and most of that meeting simply doesn’t happen.
The technical bit
The Protocol is a document published by the Society of Construction Law (UK). The current version is the 2nd Edition, February 2017, which superseded the 1st Edition (2002) and its Rider 1. It is built in a few clear layers:
Two of the 2nd Edition’s headline shifts tell you what the drafters were worried about. First, they elevated contemporaneous assessment to a Core Principle — deal with the time impact of events as the work proceeds, don’t “wait and see.” Second, they dropped the previous edition’s preference for one particular analysis method when the analysis is done long after the event, and instead set out a menu of methods with the factors for choosing between them. Both changes point the same direction: outcomes are decided by records and timing, not by clever technique applied late.
How three roles should read it
Your job is the layer the Protocol keeps coming back to: a properly prepared, logic-linked baseline that is genuinely owned and regularly updated. Everything downstream is only as good as that programme. If your baseline is unaccepted, your updates are sporadic and your logic is held together with hard constraints, you have removed the very tool the Protocol assumes you are using.
The Protocol is a framework you can lean on, not a trump card you can play. "The SCL Protocol says…" is not an argument that wins on its own. What wins is showing that the contract’s requirements were met, that the events are evidenced, and that the effect on completion is demonstrated. The Protocol helps you organise that story consistently; it does not substitute for it.
The Protocol rewards early, boring discipline and punishes the "we’ll sort it out at the end" instinct. The cheapest delay claim to run is the one where the records already exist because someone kept them at the time. That is a management decision you make at month one, not month thirty.
The trap
Treating the Protocol as if it were the contract or the law. It is neither. It is unusual for a contract to actually incorporate the Protocol, and unless it does, the Protocol doesn’t bind anyone — it informs how reasonable professionals, and sometimes tribunals, approach these questions.
The parties dispute a variation’s effect on completion. The Contractor’s consultant produces a slick analysis captioned “prepared in accordance with the SCL Protocol.” The other side’s expert produces a different result — also “in accordance with the SCL Protocol.” Both can be true. The Protocol accommodates more than one legitimate method, and the caption doesn’t validate the inputs. What actually decides it is which analysis rests on an accepted baseline, reliable progress records and a defensible link between the event and the critical path. The label is not the evidence.
What the Protocol says — and doesn’t
It sets out recommended good practice for determining extensions of time and compensation for delay and disruption, organised as 22 Core Principles with supporting guidance. It expressly presents itself as guidance, and recognises that transparency of programme and methodology is central to both preventing and resolving disputes.
What it does not say:
- That following the Protocol guarantees an EOT or any particular outcome.
- That it overrides the contract, the governing law, or the facts.
- That it has the force of law — it is rarely incorporated into contracts.
- That there is a single “correct” delay-analysis method for after-the-event analysis.
”Our analysis follows the SCL Protocol, so our entitlement is established.”
The Protocol is guidance on how to approach the question. Entitlement is established by the contract, the facts, the evidence and the applicable law — not by a compliance label.
The Protocol’s foundations are things that live on the planner’s screen: an accepted, logic-linked baseline; sensible data-date discipline on updates; minimal hard constraints; and a programme that reacts dynamically to change. If constraints are freezing your logic so the schedule can’t respond to progress, you’ve disabled the exact behaviour the Protocol relies on.
Evidence check
The guidance to Core Principle 1 frames records in six categories (listed in Appendix B). In practice that means, among others: the accepted baseline and its updates; progress and site records; resource and labour allocation records; cost records; correspondence, instructions, RFIs and minutes; and the contract and tender documents. What is actually relevant always depends on the facts and the contract — but “we didn’t keep it” is not a position you want to argue from.
Rishi’s takeaway
- The Protocol is a shared method for having the delay conversation well — not a ruling on who wins it.
- Its power is preventive: records and timely assessment kept from day one are worth more than any late analysis.
- ”In accordance with the SCL Protocol” is a description, not proof — interrogate the inputs.
- Always read the Protocol against the contract; the contract wins where they differ.
The Protocol tells you how to argue well. The contract, the facts and the evidence decide who’s right.
References — Society of Construction Law, Delay and Disruption Protocol, 2nd Edition, February 2017: Introduction and structure; Core Principle 1 (programme and records); Core Principle 4 (contemporaneous analysis); guidance to Core Principle 11 (analysis time-distant from the delay event); Appendix B (record categories). The Protocol has no force of law unless incorporated into a contract. Educational commentary; not legal advice.
Common questions
Is the SCL Delay and Disruption Protocol legally binding?
No. The Protocol is guidance, not law — it is not a contract and does not decide entitlement. It is rarely incorporated into contracts, and where it is not, it binds no one; it simply informs how reasonable professionals and tribunals approach delay and disruption.
What changed in the 2nd Edition of the SCL Protocol?
The 2nd Edition (2017) elevated contemporaneous assessment to a Core Principle — deal with the time impact of events as work proceeds rather than waiting and seeing — and replaced the previous preference for one after-the-event analysis method with a menu of methods and the factors for choosing between them.
Does the SCL Protocol decide who is entitled to an extension of time?
No. Entitlement is established by the contract, the facts, the evidence and the applicable law. A report captioned as prepared in accordance with the SCL Protocol is a description, not proof; the Protocol only offers a consistent way to approach the question.
How is the SCL Protocol structured?
It comprises 22 Core Principles, Guidance Parts A (concepts), B (guidance on each principle) and C (other financial heads of claim), plus Appendix A (definitions) and Appendix B (record categories).
Does the SCL Protocol recommend a single delay-analysis method?
No. For analysis carried out long after the event it sets out a menu of recognised methods and the factors for selecting between them, rather than endorsing one correct method.
Related