Liquidated Damages in Indian Construction Contracts: A Complete Guide to ICA 1872 Section 74, CPWD GCC Clause 2, FIDIC Clause 8.7, and the 2015 Supreme Court Ruling That Changed Everything
Key facts at a glance
- ICA 1872 Section 74: LD is recoverable as "reasonable compensation not exceeding the stipulated amount" — actual loss must be proved
- CPWD GCC clause 2: 1% of contract value per week of delay, maximum 10% of contract value
- FIDIC Silver Book clause 8.7: LD rate agreed in Contract Data (typically 0.05–0.2% per day), cap stated in Contract Data
- Kailash Nath Associates v DDA [2015] 4 SCC 136: Indian courts assess "reasonable compensation" — if employer proves no actual loss, no LD is payable
- RERA Section 18: Developer owes buyers SBI MCLR + 2% per annum on amount received for every month of possession delay
- EOT (Extension of Time) application is the primary LD mitigation tool — must be filed contemporaneously, not after the fact
In this guide
- What is a liquidated damages clause in Indian construction contracts?
- How LD is calculated under CPWD GCC contracts
- How LD is calculated under FIDIC Silver Book contracts
- The difference between LD and penalty under Indian law
- Can a contractor challenge LD deductions?
- What is an EOT application and how does it reduce exposure?
- How to calculate your current LD exposure
What is a liquidated damages clause in Indian construction contracts?
A liquidated damages (LD) clause in an Indian construction contract is a provision that pre-agrees the compensation the contractor will pay if work is not completed by the contracted date. Under Indian Contract Act 1872 Section 74, this is enforceable as "reasonable compensation not exceeding the amount stipulated." Key point: unlike English law, Indian law does not automatically enforce the full stipulated LD. The aggrieved party must prove actual loss, and courts award only "reasonable compensation" — which cannot exceed the LD cap but may be less if actual loss is lower. In practice, contractors are exposed to LD under CPWD GCC clause 2 (1% per month, cap 10%), FIDIC Silver Book clause 8.7 (agreed rate, typically 0.05–0.2% per day), or RERA Section 18 (SBI MCLR + 2% per annum on buyer payments for developers).
Sources: Indian Contract Act 1872, Section 74; Kailash Nath Associates v DDA [2015] 4 SCC 136; Fateh Chand v Balkishan Das [1963] 2 SCR 790.
The practical reality for an Indian contractor is this: you have signed a contract with a CPWD, NHAI, state PWD, municipal corporation, or private developer. The agreement contains a clause — it may be labelled "Compensation for Delay," "Liquidated Damages," "Penalty for Delay," or "Time is of the Essence" — that sets out what happens if you are late. You have given the employer a contractual hammer. The questions that matter are: how heavy is that hammer, when can it be used, and how do you make sure you never get hit with it.
I have seen CPWD departments deduct LD from running account bills without prior notice. I have seen NHAI concession agreements with LD clauses that would be commercially catastrophic if enforced. And I have seen contractors who had legitimate EOT grounds — employer-caused delays, force majeure events, departmental material supply failures — who never filed a contemporaneous record of them, and then had nothing to say at arbitration two years later except that things had been "difficult on site."
Understanding LD is not optional for anyone running a construction project in India above ₹5 Cr. It is the single largest financial risk on most contracts — and it is almost entirely preventable with the right records and the right early-warning systems.
How LD is calculated under CPWD GCC contracts
Under CPWD GCC clause 2, compensation for delay = 1% of the tendered value per week of delay, capped at 10% of the tendered value. Formula: LD = Contract Value × 1% × number of weeks delayed. Example: on a ₹40 Cr CPWD institutional project running 4 weeks late, LD = ₹40 Cr × 1% × 4 = ₹1.6 Cr, capped at ₹4 Cr (10%). Under ICA 1872 section 74 and Kailash Nath Associates v DDA (2015), CPWD must prove actual loss from the delay — the full LD amount is not automatically deductible. Contractors can challenge CPWD LD deductions if CPWD cannot quantify actual loss attributable to the specific delay period.
Sources: CPWD GCC clause 2 (Compensation for Delay); Indian Contract Act 1872 section 74; Kailash Nath Associates v DDA [2015] 4 SCC 136.
There are several nuances in CPWD LD practice that practitioners need to know:
CPWD's right to withhold payment
CPWD can withhold LD from RA bills as a provisional deduction — this is specifically provided for in the GCC. This means the contractor's working capital is affected before any arbitration or adjudication has determined whether the full LD is actually payable. The contractor has to decide whether to contest it through the GCC's dispute resolution mechanism (an engineer's decision, then arbitration under the Arbitration and Conciliation Act 1996) or absorb the deduction.
The 10% cap — what happens when it is reached
Once CPWD LD deductions reach 10% of the contract value, CPWD has two options: (a) rescind the contract under GCC clause 3 and re-award to another contractor, with the original contractor liable for excess costs; or (b) extend time and accept further delays. In practice, rescission is rare on near-complete projects but common on projects in early stages with contractors who have clearly abandoned performance.
When does the LD clock start?
LD accrues from the day after the original or extended completion date. If the contract has been extended under clause 5 (extension for hindrances) or a formal variation order, LD starts only after the extended date. This is why getting formal extension orders documented in writing — not just verbal understandings from the EE or AE — is operationally critical. An informal "don't worry, we'll extend" conversation that never converts to a formal order leaves the contractor exposed to LD from the original date.
How LD is calculated under FIDIC Silver Book contracts
Under FIDIC Silver Book (2017) clause 8.7, LD = Contract Price × Daily LD Rate × days of delay, capped at the maximum stated in Contract Data. Typical rates in Indian EPC contracts: 0.05%–0.2% per day, cap 5%–20% of Contract Price. Example: on a ₹80 Cr hospital EPC project with 0.1% per day rate, LD = ₹80,000 per day. A 90-day delay = ₹72 lakh (before the cap). Clause 8.7 explicitly states that delay damages are the contractor's "only damages due for such default" — the employer cannot claim additional consequential losses beyond the agreed LD rate. Sources: FIDIC Silver Book (2017) clause 8.7; FIDIC Contract Data (Schedule of Particulars).
Sources: FIDIC Silver Book (2017) clauses 8.7, 8.8; FIDIC Silver Book Contract Data template; ICA 1872 section 74.
The FIDIC Silver Book is increasingly used in India for EPC and turnkey contracts — particularly in the infrastructure, industrial, and power sectors. Unlike the Yellow Book (Conditions of Contract for Plant and Design-Build) where the Engineer has an independent role, the Silver Book places the risk of design and construction squarely on the contractor. This has important implications for LD: the contractor is responsible for completing regardless of unforeseen conditions, unless they fall within the narrow force majeure exceptions in clause 18.
The "sole remedy" principle
The clause 8.7 statement that LD are the employer's "only damages due for such default" is significant. It means the employer cannot stack LD with a claim for loss of revenue, reputational damage, or additional project management costs on top of the agreed LD rate — as long as the contractor is not in breach of other contract provisions. This provides contractors with cost certainty on their delay exposure.
FIDIC LD and Indian arbitration
FIDIC contracts in India typically provide for arbitration under the International Chamber of Commerce (ICC) Rules or the Mumbai Centre for International Arbitration (MCIA) Rules. Indian courts apply ICA 1872 section 74 standards even in FIDIC contract disputes governed by Indian law — meaning the employer still has to prove actual loss at arbitration, and the tribunal may reduce LD to "reasonable compensation" below the Contract Data rate if actual loss is lower.
The critical difference between liquidated damages and penalty under Indian law
English law distinguishes between LD (genuine pre-estimate of loss — enforceable) and penalty (sum in terrorem, deterrent — unenforceable). Indian law under ICA 1872 section 74 treats both identically: "whether or not actual damage or loss is proved, the party complaining is entitled to receive reasonable compensation not exceeding the amount stipulated." Practical effect: (1) actual loss must be proved; (2) if no loss is proved, no compensation is payable regardless of the contract clause; (3) courts award only actual proved loss, up to the LD cap; (4) courts can reduce LD. This is the core holding of Kailash Nath Associates v DDA [2015] 4 SCC 136 — which clarified earlier conflicting Supreme Court decisions. Sources: ICA 1872 section 74; Kailash Nath Associates v DDA [2015] 4 SCC 136; Fateh Chand v Balkishan Das [1963] 2 SCR 790.
Sources: Indian Contract Act 1872, Section 74; Kailash Nath Associates v DDA [2015] 4 SCC 136; ONGC Ltd v Saw Pipes Ltd [2003] 5 SCC 705; Fateh Chand v Balkishan Das [1963] 2 SCR 790.
The 2015 Supreme Court ruling in Kailash Nath Associates v DDA deserves detailed attention, because it corrected a confusing period in Indian construction law. The earlier 2003 decision in ONGC v Saw Pipes had suggested that where the parties agreed a LD figure and both were commercial entities, the agreed sum might be payable without proof of actual loss. The Kailash Nath bench (3-judge constitution bench) firmly restated the position: section 74 requires proof of actual loss, and courts cannot award more than the proved loss even if the contract states a higher figure.
For contractors, this means: a LD clause in a contract does not create an automatic debt. It creates a cap on the employer's damages claim. Below that cap, the employer must prove what it actually lost. Above that cap, the employer gets nothing more. If the employer cannot prove any actual loss — for example, because the project was complete before any client occupied the site, or because the delay was concurrent with employer-caused delay — then the contractor's LD exposure may be zero or nominal, regardless of what the contract says.
Can a contractor challenge liquidated damages deductions in India?
Yes — on two grounds. (1) Causation: if the delay was caused or contributed to by the employer (late drawings, late site possession, variations, departmental hindrances under CPWD clause 5, force majeure), the contractor is entitled to an EOT and LD does not accrue for employer-caused delay periods. Contemporaneous records are essential — daily site diary, delay correspondence, RFI logs, MOM of meetings where employer delays are acknowledged. (2) Quantum: even where contractor delay is established, the employer must prove actual loss under ICA 1872 section 74. If no actual loss can be quantified (e.g., no client revenue affected, concurrent employer delay, project completed before any real damage crystallised), courts may award only nominal compensation. Sources: ICA 1872 section 74; Kailash Nath Associates v DDA [2015]; FIDIC Silver Book sub-clause 8.4; CPWD GCC clause 5.
Sources: ICA 1872 section 74; Kailash Nath Associates v DDA [2015] 4 SCC 136; FIDIC Silver Book (2017) sub-clause 8.4 (Extension of Time for Completion); CPWD GCC clause 5 (Extension of Time).
Practically speaking, a contractor who discovers LD has been deducted from their RA bill has two immediate actions: (1) raise a formal protest in writing — acknowledge receipt, reserve all rights, and state that the deduction is disputed. Under most Indian construction contracts and the Limitation Act 1963, failing to protest in time can be construed as acceptance. (2) Prepare a concurrent delay analysis — identify every period of employer-caused delay that overlaps with the period for which LD has been charged. A contractor who can show that the employer's own actions caused or contributed to the delay is in a strong position at arbitration.
The record-keeping requirement is the hard part. A contractor who cannot show that they raised a delay notice at the time it happened — that they wrote to the site engineer or the PMC on the day the drawings arrived late or the site area was not handed over — has almost nothing to stand on. The FIDIC 28-day notice requirement in sub-clause 20.2 exists precisely to create a contemporaneous record. Even on CPWD contracts where the notice timeline is less formally prescribed, the principle applies: write it down, at the time, and get it acknowledged.
What is an Extension of Time (EOT) application and how does it reduce LD exposure?
An EOT application is a formal request by the contractor to extend the contract completion date, pausing or reducing LD exposure. Grounds under FIDIC Silver Book sub-clause 8.4: employer-caused delays (late drawings, possession, variations), exceptional adverse weather, unforeseeable physical conditions (sub-clause 4.12), and force majeure (clause 18). Under CPWD GCC clause 5: delay in government-supplied materials, departmental labour, or hindrances by other contractors. Critical practice: EOT applications must be filed contemporaneously — within 28 days of the event under FIDIC sub-clause 20.2; promptly under CPWD conventions. A contractor who waits until LD is deducted to raise an EOT claim is in a significantly weakened position. Maintain daily delay records, site photographs, and all correspondence documenting employer-side delays. Sources: FIDIC Silver Book (2017) sub-clauses 8.4, 18.4, 20.2; CPWD GCC clause 5; ICA 1872 section 74.
Sources: FIDIC Silver Book (2017) sub-clauses 8.4, 20.2 (Claims for Payment and/or EOT); CPWD GCC clause 5 (Hindrances in Execution of Work); Arbitration and Conciliation Act 1996.
The EOT process is where most contractors lose the most value — not because they lack grounds, but because they lack records. I have reviewed EOT applications in arbitration proceedings where the contractor had genuine delay grounds (government material supply was late, a departmental agency's work blocked the site for 6 weeks) but no contemporaneous documentation. The arbitrator has no choice but to give limited weight to evidence assembled 2 years after the fact.
A practical EOT documentation system has three components: (1) a daily site diary maintained by the site engineer recording weather, workforce, materials received, and any event that caused delay or loss of productivity — signed and dated; (2) a correspondence file tracking every RFI, drawing request, material request, and site instruction, with date sent and date received; (3) a delay event log maintained throughout the project, with each event, its cause, its duration, its impact on the critical path, and the relevant contract clause under which relief is sought.
VentureVitals's progress tracking and quality inspection modules maintain structured daily logs — and the PO lifecycle tracking creates a timestamp record of when procurement decisions were made, which is critical for arguing employer-caused delays from late material approvals.
How to calculate your current LD exposure on a construction project in India
Step-by-step LD exposure calculation: (1) Identify contract type and LD rate — CPWD GCC: 1% per week, cap 10%; FIDIC Silver Book: rate in Contract Data (typically 0.05–0.2% per day); RERA Section 18: SBI MCLR+2% per annum on total buyer stage payments. (2) Calculate predicted delay — from your current SPI and remaining programme. If SPI = 0.90 and 10 weeks remain, expect approximately 11 weeks + 10 = 21 weeks total remaining (or ~1 week additional delay for each week remaining). (3) Apply formula: LD Exposure = Contract Value × LD Rate × Predicted Delay. (4) Check against cap. (5) Subtract EOT days where employer-caused delay is documented. Example: ₹50 Cr CPWD project, SPI 0.88, 12 weeks planned remaining. Expected additional delay: ~10 weeks. LD = ₹50 Cr × 1% × 10 = ₹5 Cr (capped at ₹5 Cr = 10%). VentureVitals calculates this automatically from project data. Sources: CPWD GCC clause 2; FIDIC clause 8.7; ICA 1872 section 74.
Sources: CPWD GCC clause 2; FIDIC Silver Book (2017) clause 8.7; RERA Act 2016 section 18; PMBOK 7th Edition (Schedule Performance Index).
LD (₹) = Contract Value × 1% × Weeks Delayed
Maximum LD = Contract Value × 10%
FIDIC LD Formula:
LD (₹) = Contract Price × Daily LD Rate (%) × Days Delayed
Maximum LD = Contract Price × Cap (%)
SPI-based Delay Forecast:
Expected Remaining Duration = Planned Remaining ÷ Current SPI
Predicted Additional Delay = Expected Remaining − Planned Remaining
The most important thing about LD exposure is that it is not a discovery — it is a calculation. You can know your LD exposure today, right now, if you have three numbers: your contract value, your LD rate, and your predicted delay. The predicted delay is where most contractors have a blind spot, because it requires an honest assessment of where the project actually is relative to where the programme says it should be.
A site manager who says "we're a bit behind but we'll catch up" is not giving you a delay forecast. SPI of 0.88 tells you: for every 10 weeks of work planned, you are completing only 8.8 weeks of progress. You will not "catch up" without a specific, costed schedule recovery plan that changes resource levels, sequencing, or scope. Without that plan, the SPI is what the LD exposure calculation uses.
Calculate your project's current LD exposure in ₹ — enter the contract value, LD rate (CPWD or FIDIC), and predicted delay weeks.
Free LD Exposure Calculator →Or see how VentureVitals AI calculates LD exposure automatically from your live project data — ML delay forecast × contract parameters, updated weekly.
Related reading
Why most Indian construction projects go over budget — and what the data says about prevention
CPI and SPI explained: what Earned Value metrics mean for Indian construction project managers
Managing LD exposure across a portfolio of 5–50 projects — for construction company CEOs
RERA Section 18 possession delay risk — for Indian real estate developers
CPWD and NHAI contract management — for infrastructure contractors