Society of Construction Law Delay & Disruption Protocol, India (2026): How Tribunals Assess Delay Analyses, EOT and LD Claims

The scl delay disruption protocol india question has become one of the most practically important themes in Indian construction arbitration as the sector heads into 2026, with tribunals increasingly expected to scrutinise how delay is proven, apportioned and quantified. The Society of Construction Law Delay and Disruption Protocol (the “SCL Protocol”) offers a disciplined methodological framework for extension of time (EOT) entitlement, concurrency and disruption, yet it is not law in India, it operates as persuasive professional guidance that tribunals may adopt, modify or decline.

This guide explains how Indian arbitral tribunals and courts receive SCL-style delay analyses, what evidence standards they expect, and how counsel can deploy critical path method (CPM), time impact analysis (TIA) and forensic window techniques to build or defend EOT and liquidated damages (LD) claims. It is written for in-house counsel, EPC contractors, developers and claims consultants who need a jurisdiction-specific roadmap rather than a generic international summary.

Who this is for and what you get: this is a practitioner guide for in-house counsel, EPC contractors, developers and claims consultants who must prepare or defend EOT and LD claims in India. It explains how to deploy SCL Protocol methods before Indian tribunals and delivers a practical checklist plus the evidentiary expectations tribunals apply in practice.

Quick summary, what the SCL Delay & Disruption Protocol is and why it matters in India

The SCL Protocol is a guidance document published by the Society of Construction Law that sets out recommended principles and techniques for analysing delay and disruption on construction projects. First issued in 2002 and substantially revised in a later edition, it addresses how to assess entitlement to extensions of time, how to treat concurrent delay, and how disruption to productivity should be evaluated and valued. Crucially for anyone researching the scl delay disruption protocol india position, the document is methodological guidance, it does not have the force of statute or binding precedent in India. Indian tribunals treat it as a persuasive aid to reasoning, particularly where contracts are silent on the delay analysis method to be applied.

The growing visibility of the Society of Construction Law India, reflected in its 2026 activity including the launch of a Council for Women in Construction Law & Arbitration, has reinforced practitioner familiarity with Protocol concepts. This institutional momentum means arbitrators sitting in Indian-seated construction disputes are more likely than ever to expect parties to articulate their delay case by reference to a recognised methodology. For claims teams, understanding the scl delay disruption protocol india landscape is therefore no longer optional, it shapes how credibly a delay narrative will land.

What the Protocol covers

• Entitlement principles. The core tests for when a contractor is entitled to an extension of time and how causation between an employer-risk event and critical delay should be established.
• Delay analysis techniques. Recognised methods including as-planned versus as-built, impacted as-planned, time impact analysis, time slice and as-planned versus as-built windows analysis.
• Concurrent delay. Guidance on identifying true concurrency and the consequences for time and money.
• Disruption. How loss of productivity, distinct from delay, should be identified and measured.
• Records and float. The central importance of contemporaneous records, programme updates and the ownership of float.

How Indian tribunals view protocols and guidance documents

Indian arbitral practice draws heavily on the framework set by the Arbitration and Conciliation Act, 1996, under which tribunals enjoy wide discretion over procedure and the admissibility, relevance and weight of evidence. Section 19 of that Act provides that a tribunal is not bound by the Code of Civil Procedure or the Indian Evidence Act, and this flexibility extends to how it receives expert delay methodology. The SCL Protocol itself is explicit that it is not a contract document and should not be applied mechanically; Indian tribunals adopt a similar stance, treating it as a lens through which to test the logic and rigour of an expert’s analysis rather than as a rule to be enforced.

The practical consequence is that a party invoking the scl delay disruption protocol india framework must still demonstrate that the chosen method fits the facts, the records and the contract.

Legal and procedural framework in India for delay, EOT and LD claims

Construction delay disputes in India sit at the intersection of contract law and arbitration procedure. The contractual bargain, whether a bespoke EPC agreement or a FIDIC-based form, defines the entitlement to time and the mechanism for liquidated damages. The Arbitration and Conciliation Act, 1996 governs the procedural environment in which these entitlements are tested, including the tribunal’s power to appoint experts, determine evidentiary matters and make a reasoned award. Indian courts have consistently emphasised that tribunals are the masters of the facts, and appellate intervention on findings of delay and quantum is narrow, which raises the stakes on getting the evidence right at first instance.

Contractual LD clauses must be read against established principles of Indian contract law. Under Section 74 of the Indian Contract Act, 1872, where a contract stipulates a sum payable on breach, the party complaining of breach is entitled to reasonable compensation not exceeding the amount so named, a stipulated sum therefore operates broadly as a ceiling on recovery, and the claimant is generally required to show that loss was in fact suffered, save where proof of actual loss is difficult or impossible. Public policy considerations under Section 34 of the Act also bear on enforcement, so an award that fails to reason through the delay analysis coherently risks challenge.

Comparative guidance under the UNCITRAL Model Law on International Commercial Arbitration, on which the Indian statute is based, reinforces the tribunal’s broad authority over evidence and expert input.

Arbitration versus court, admissibility of expert delay analysis

Expert delay evidence is often more effective in arbitration than in court litigation because arbitral tribunals have the freedom and often the technical fluency to engage with CPM and forensic analysis in detail. In an Indian-seated arbitration, the tribunal can direct the exchange of expert reports, order meetings of experts to narrow issues and, increasingly, adopt concurrent expert evidence (so-called “hot-tubbing”). When presenting a scl delay disruption protocol india analysis, the expert’s independence, the transparency of assumptions and the auditability of the underlying programme data all determine the weight the tribunal attaches to the opinion.

Notice, contemporaneous records and proof standards

Indian tribunals place significant weight on contemporaneous records. Programme updates, site diaries, minutes of progress meetings, delay notices and correspondence form the backbone of a defensible claim. Many standard-form contracts, including FIDIC forms widely used in India, make the service of timely notice a condition of EOT entitlement. A delay analysis built on a reconstructed, after-the-event narrative, unsupported by records created at the time, is routinely treated as less reliable. The SCL Protocol’s emphasis on records therefore aligns closely with what Indian tribunals already demand.

Core delay analysis methods under the SCL Protocol, and how tribunals treat them

The heart of any scl delay disruption protocol india exercise is the choice and defensible execution of a delay analysis method. The Protocol recognises several techniques, each with distinct data requirements and evidential profiles. No single method is universally “correct”; the right choice depends on the quality of the baseline programme, the availability of updates and records, the timing of the analysis relative to the events, and the contract. Indian tribunals expect the expert to justify the method selected and to explain why alternatives were rejected.

CPM (critical path), what tribunals expect

The critical path method underpins most credible delay analyses. It identifies the sequence of activities that drives the project completion date and assesses how particular events affected that path. Indian tribunals engaging with a CPM analysis typically look for a sound, contemporaneously agreed baseline programme, properly constructed logic links, transparent treatment of float, and regular updates that reflect actual progress. A CPM presented without a validated baseline, or one in which the logic has been retrospectively altered to produce a favourable result, invites rejection.

• Baseline. A baseline programme that was agreed or at least demonstrably used to manage the works.
• Logic. Activity dependencies that reflect the real construction sequence, free of artificial constraints.
• Float. A clear statement of how float is owned and consumed, consistent with the contract and the Protocol.
• Updates. Progress updates that capture actual start and finish dates, used to re-baseline critical path shifts over time.

Time Impact Analysis (TIA), use and common tribunal criticisms

Time impact analysis is a prospective, modelled technique that inserts delay events into a contemporaneous programme to project their likely effect on completion. The Protocol identifies TIA as well suited to assessing entitlement close to the time an event occurs, where contemporaneous programme updates exist. Its strength is that it mirrors how the parties would have viewed the impact at the time; its weakness is that it is model-driven and can diverge from what actually happened. Indian tribunals have been willing to accept TIA where the underlying programme is robust, but they are alert to criticisms that the method relies on hypothetical logic, can be manipulated through the choice of fragnet, and may overstate impact if actual mitigation is ignored.

A TIA that is not reconciled against the as-built record is particularly vulnerable.

As-built versus as-planned and forensic window analysis

Where contemporaneous updates are poor but good as-built records survive, retrospective methods come into their own. The as-planned versus as-built comparison and windows (or time-slice) analysis break the project into periods and examine how the critical path actually moved within each window. These techniques are fact-driven and, because they test what genuinely occurred, tribunals often find them persuasive. The trade-off is that they are data-hungry and labour-intensive, and the selection of windows must be principled rather than opportunistic. A well-executed forensic window analysis that is transparent about its windows and reconciled to the as-built record tends to carry significant weight in a scl delay disruption protocol india dispute.

Concurrent delay, methodological approaches

Concurrent delay, where an employer-risk event and a contractor-risk event each independently cause critical delay in the same period, is among the most contested issues. The Protocol distinguishes true concurrency from sequential delays that merely overlap. The practical approaches tribunals encounter include a “net effect” assessment of what actually drove completion, apportionment between the parties, and the position under which a contractor may recover time but not prolongation costs where its own concurrent delay would have caused the same critical delay. Indian tribunals tend to resolve concurrency on the facts and the contract wording, assessing net criticality rather than applying a rigid rule, which is why the underlying delay analysis must be capable of isolating each cause.

Table 1: Comparison of CPM/TIA, As-Planned vs As-Built and Forensic Window analyses under the SCL Protocol for India tribunals, method selection, data requirements and evidential expectations.

Practical steps to preparing SCL-style delay evidence for Indian tribunals

Preparing a defensible scl delay disruption protocol india analysis is as much about process discipline as it is about method. The strongest claims are assembled methodically, from contract review through to the final expert report and demonstratives. The following stepwise approach reflects what tribunals reward and what they penalise.

1. Contract review and baseline selection. Identify the EOT and LD clauses, notice requirements and any contractually specified programme or method, then fix the baseline against which delay will be measured.
2. Collate contemporaneous notices and records. Gather delay notices, programme updates, site diaries, progress minutes and correspondence to establish the factual spine.
3. Data cleansing and validation. Test the baseline and updates for logic errors, open-ended activities and constraints that distort the critical path.
4. Build a forensically defensible CPM. Model delay events using the method best suited to the records, documenting every assumption.
5. Document assumptions and sensitivity testing. Show the effect of alternative assumptions so the tribunal can see the robustness of the conclusion.
6. Draft the expert report with a clear methodology section. State the method, why it was chosen, its limitations and the data relied upon.
7. Prepare for joint experts and hot-tubbing. Anticipate the opposing expert’s critique and narrow the issues in a joint statement.
8. Produce demonstrative timelines and index the bundle. Make the delay story visually and documentarily easy for the tribunal to follow.

Notices, contemporaneous records and document preservation

Document preservation should begin the moment a delay event is foreseeable. In many Indian construction disputes, otherwise meritorious EOT claims fail because the contractor did not serve notice in the form and time the contract required, or because programme updates were not maintained. A disciplined records regime, preserving native programme files, not just printouts, allows an expert to rebuild and audit the critical path, which materially strengthens a scl delay disruption protocol india presentation.

For expert reports: clarity on methodology, assumptions and limitations

The Protocol stresses transparency, and so do tribunals. An expert report should set out the method in plain terms, declare every material assumption, acknowledge the limitations of the data, and explain why competing methods were not adopted. Reports that read as advocacy rather than independent analysis are discounted. Candour about limitations, counter-intuitively, increases credibility and the weight the tribunal attaches to the opinion.

Entitlement to EOT, common tribunal approaches and sample evidence package

Establishing entitlement to an extension of time requires more than showing that the project finished late. The contractor must demonstrate an event that falls within the EOT provisions, that the event caused critical delay to completion, that the notice and procedural requirements were met, and that reasonable steps to mitigate were taken. Indian tribunals test each of these elements against the contract and the records. A persuasive EOT package typically includes the executed contract and programme, the delay notices, contemporaneous programme updates, the expert delay report, correspondence evidencing the event and its effect, and mitigation records.

Quantifying EOT versus assessing LDs

It is essential to separate the time analysis (how many days of excusable delay) from the money analysis (prolongation cost or LD exposure). Establishing EOT entitlement extends the completion date and, to that extent, defeats or reduces the employer’s LD claim for the excused period. But EOT does not automatically carry prolongation costs, the contractor must separately prove loss and that the delay was compensable under the contract. Keeping these strands distinct avoids the common error of conflating time relief with cost recovery.

FIDIC-form contracts: clause crosswalk

FIDIC forms are widely used on Indian infrastructure and EPC projects, and their EOT and LD machinery is highly relevant to any scl delay disruption protocol india analysis. FIDIC conditions generally require the contractor to give notice of a claim within a defined period and to maintain contemporary records, with entitlement to an extension assessed by the engineer. Delay damages are addressed through a separate liquidated-damages mechanism. Because the FIDIC regime makes notice and records pre-conditions, the delay analysis and the contractual compliance narrative must be developed together, a technically flawless CPM is of limited value if the claim was never validly notified.

Practitioners should always check the specific edition and the particular conditions, as the precise notice periods and procedures vary between FIDIC forms and are frequently amended in the particular conditions.

Liquidated damages (LDs), mitigation and set-offs, tribunal practice

Liquidated damages in Indian construction are governed by contract and by established principles under Section 74 of the Indian Contract Act, 1872, which caps recovery at the stipulated sum and generally requires proof of loss suffered, subject to the courts’ recognition that proof may sometimes be impractical. When a contractor presents a credible SCL-style analysis showing excusable delay, the tribunal must reduce or extinguish LDs for the excused period. Where delay is partly excusable and partly the contractor’s responsibility, the tribunal apportions LD exposure according to the periods of critical delay attributable to each party. Mitigation is also relevant: a contractor who failed to take reasonable steps to recover time may find its EOT narrowed and its LD exposure preserved.

Concurrent delay and apportionment models

Concurrency frequently decides the LD outcome. Where an employer-risk event and a contractor-risk event both critically delay completion in the same window, tribunals typically either assess the net effect on completion or apportion responsibility. A common practical result is that the contractor obtains time relief, defeating LDs for the concurrent period, but is denied prolongation costs because its own delay would independently have caused the same critical delay. The decisive factor is net criticality, which only a rigorous delay analysis can establish. For example, if an employer’s late access and the contractor’s labour shortage each delay the same critical activity by thirty days, the tribunal must determine whether either alone would have driven completion and allocate LDs accordingly.

Practical tips for defending LD claims with SCL analyses

• Lead with the as-built critical path so the tribunal sees what actually drove completion.
• Isolate each delay event and test it independently to expose or rebut concurrency.
• Reconcile any prospective model against the as-built record to pre-empt criticism.
• Document mitigation efforts to protect both time and cost positions.
• Tie every day of claimed EOT to the LD reduction it produces, period by period.

Evidence checklist and model timeline

A well-ordered evidence bundle lets the tribunal follow the delay story without friction. The essential components are:

• Executed contract, special conditions and agreed baseline programme.
• All delay and claim notices with proof of service dates.
• Contemporaneous programme updates in native file format.
• Site diaries, progress minutes and relevant correspondence.
• The expert delay report, appendices and the expert’s curriculum vitae.
• Demonstrative timelines showing each window and critical-path shift.

Illustrative six-point timeline: (1) baseline agreed; (2) first delay event and notice served; (3) programme update capturing impact; (4) concurrent contractor delay identified; (5) mitigation measures recorded; (6) as-built completion reconciled to the critical path.

Practical pitfalls, tribunal red flags and how to avoid them

Several recurring mistakes undermine otherwise strong claims. The most damaging is the absence of a validated baseline, which deprives the entire analysis of a reference point. Others include retrospectively altering programme logic to improve an outcome, failing to disclose assumptions, and relying on reconstructed narratives unsupported by contemporaneous records. Tribunals also react poorly to experts who stray into advocacy, and to delay models that are never reconciled against what actually happened on site. The remedy in each case is discipline: fix the baseline early, preserve native programme files, document assumptions openly, maintain contemporaneous notices, and present the expert evidence as genuinely independent.

These habits are the difference between a scl delay disruption protocol india analysis that persuades and one that is discounted.

Conclusion, pragmatic next steps for counsel and claims teams

The scl delay disruption protocol india framework is best understood as a set of disciplined tools that Indian tribunals treat as persuasive rather than binding. Counsel and claims teams should adopt the Protocol’s methodology early, not at the dispute stage, by preserving native CPM files, maintaining contemporaneous notices and programme updates, and selecting a delay method that fits the records and the contract. Where resources allow, commissioning an independent expert at the outset and preparing for joint-expert engagement will materially improve outcomes. Executed well, a rigorous SCL-style analysis is the most effective route to securing EOT entitlement and to defending against or reducing liquidated damages in Indian construction arbitration.

For market context and local counsel, see our overview of Construction Lawyers India (overview), and watch for our forthcoming deep dives on CPM versus TIA Arbitration India and Concurrent Delay in India.

Sources

1. Arbitration and Conciliation Act, 1996 (India), India Code
2. Indian Contract Act, 1872 (India), India Code
3. UNCITRAL, Model Law on International Commercial Arbitration
4. Supreme Court of India, Judgments repository
5. Society of Construction Law (UK), Delay & Disruption Protocol
6. Society of Construction Law India
7. FIDIC, Official site (contract clause references)