Liquidated Damages Calculator

Liquidated damages are a sum the contract fixes in advance as compensation for delay attributable to you. The buyer does not invoice it. It is deducted, from a running account bill, from the security deposit, or from the final bill.

Four things decide the number, and all four sit in the contract rather than in the tender notice:

• The rate. Usually a percentage, occasionally a fixed amount per period.
• The period the rate attaches to. Per day, per week or per month, and very often "or part thereof".
• The base the percentage applies to. Contract value, the value of the delayed portion only, or the value of unexecuted work. Many clauses say excluding taxes and duties.
• The cap. Usually a percentage of contract value, and worth finding before anything else.

Rates and caps vary between departments, between works, supply and service contracts, and between two tenders from the same buyer, so all four are inputs here, read off your own conditions. The clause is usually split across documents: the general conditions carry the mechanism, the special conditions overwrite the rate, and the schedule carries the completion period. None of it appears in a portal listing. The public feeds do not carry estimated value, EMD or eligibility criteria, and the LD clause sits deeper still. See how to read a tender document.

The calculation is arithmetic once the clause is read. Eight steps:

1. Take the contractual completion date, as extended by any extension of time actually granted.
2. Count the delay from that date to actual completion, or to today if the work is still running.
3. Convert the delay into the contract's unit. Where the clause says "or part thereof", round up. Eight days on a weekly rate is two weeks, not one.
4. Identify the base, and whether taxes are excluded.
5. LD for one period = rate x base.
6. Gross LD = LD for one period x number of periods.
7. Cap in rupees = cap percentage x contract value.
8. LD payable = the lower of gross LD and the cap.

One more line is worth computing at the same time, because it is the one that changes decisions:

Periods to reach the cap = cap percentage divided by the rate percentage, rounded up.

That gives the point at which the cap bites. Before it, each further period of delay costs you the full periodic amount. After it, the LD line stops growing. Knowing that number at the start of a slippage tells you what recovery is worth.

Nothing you type here leaves your browser. The calculation runs on your own device.

Almost every disputed LD figure comes from one of these, not from the multiplication.

Rounding part periods down. A clause reading "per week or part thereof" means a single day into a new week costs a whole week. On a daily rate this hardly matters. On a weekly or monthly rate it is the largest single source of error.

Using the wrong base. Supply contracts frequently apply the rate to the value of the delayed items only, not to the whole order. Works contracts more often apply it to the full contract value, and some apply it to the value of work not completed. These give answers that differ by an order of magnitude on the same delay.

Including taxes. Where the clause says the contract price excluding taxes and duties, the base is the pre-tax figure.

Counting from the original completion date after an extension has been granted, or counting from the extended date when the extension was granted with LD reserved. Read the sanction letter, not the clause.

Missing sectional or milestone LDs. Where the contract sets intermediate milestones, a separate deduction can run against each, and the cap may apply per milestone or to the contract as a whole.

Treating a deduction already made as final. Departments often deduct provisionally while an extension application is pending.

The cap is a ceiling on one line of a much longer list. Reaching it does not mean the delay has stopped costing you.

Once gross LD crosses the cap, the marginal LD cost of another week is nil. That is a real fact and it is also a trap, because everything else that delay triggers is still live and most of it is worse than the deduction:

• Termination for default, and completion of the balance work at your risk and cost, with the excess recovered from you.
• Invocation of the [performance guarantee](/blog/performance-bank-guarantee-explained), which is cash and also your banking limits.
• [Retention](/blog/retention-money-in-government-contracts) held longer, because release runs from completion and the defect liability period runs after that.
• A late completion certificate. That certificate is the document you produce to prove similar work experience on the next bid, so a delayed contract quietly delays your eligibility for the next one. See completion certificate vs work order.
• In serious cases, [debarment](/blog/blacklisting-and-debarment), which costs more than any single contract is worth.

So read the cap as the maximum of the deduction, never as the maximum of the delay. On GeM the same logic runs through the incident record rather than through the LD line alone. See GeM caution money and penalties.

English law turns on whether a stipulated sum is a genuine pre-estimate of loss or a penalty, and a penalty is unenforceable. Indian law does not run that way, which is why LD material written for other jurisdictions can mislead you.

Section 74 of the Indian Contract Act 1872 provides that where a sum is named in the contract as payable on breach, the party complaining is entitled to receive reasonable compensation not exceeding the amount so named, whether or not actual damage or loss is proved.

Three practical consequences for a contractor:

• The named sum is a ceiling on compensation, not automatically the compensation. The contract cap and the legal cap point the same way.
• The label in your contract does not decide the question. Indian standard forms use "penalty", "compensation for delay" and "liquidated damages" fairly loosely, and the wording alone does not change the analysis.
• Any argument about quantum is an argument about reasonableness and evidence, run after the deduction has already been made from your bill.

That last point is the one that matters commercially. The department deducts at the contract rate first. Recovering it means showing the delay was excusable, which is a documents question, or that the sum was unreasonable, which is a long road. Plan on the first.

The rate is fixed by the contract. The date the delay is counted from is not, and that is where the money is.

An extension of time moves the contractual completion date forward, so the delay period shrinks and the LD with it. What preserves the claim is nearly always procedural:

• Apply in the form and within the time the contract requires, when the cause arises, not at the end of the job. A late application is the most common reason a good cause fails.
• Notify in writing at the time. Drawings awaited, site or front not handed over, a decision pending with the department, a change in scope. Each of these belongs in a dated letter, not in a meeting.
• Keep the hindrance register and site instruction record current, and reconcile it against the programme. Contemporaneous records are the whole case.
• Read the sanction when it comes. An extension granted without LD and an extension granted with LD reserved are different documents with the same title.

Where the department deducted provisionally and then granted the extension, ask in writing for the reversal, with the bill number and the arithmetic. It is not automatic.

Before award, this is a pricing question and it has a clean answer: LD exposure belongs in the risk line, weighted by an honest view of your delay probability, alongside guarantee cost and the payment cycle. A short completion period with a heavy rate is a reason to bid differently, or not at all. See how to price a government tender and the bid or no bid framework.

After award, in order: notify the cause in writing as it arises, apply for the extension, keep executing, and check every bill for what has been deducted and under which head. Deductions land at the wrong base often enough to be worth checking each time. See running account bills and the RA bill deductions calculator.

On the GST question, CBIC took the position in Circular No. 178/10/2022-GST that amounts recovered as compensation for breach, including liquidated damages for delay, are not consideration for a supply and so are not taxable. Contracts word the recovery differently, so put your own clause in front of your accountant. See TDS and GST on government contracts.

A wrong deduction is a contract dispute, resolved through the contract's dispute resolution clause, not the tender grievance route, which addresses the bidding process. A written representation setting out the clause, the dates and the arithmetic gets further than a general complaint.