What Does “Consequential Loss” Actually Mean?
If you’ve ever signed a contract, you’ve probably seen the phrase “the party shall not be liable for consequential loss.” It sounds technical, but the idea behind it is simple.
When someone breaks a contract, the loss they cause usually falls into two buckets:
- Direct loss – the loss that naturally and obviously flows from the breach. If a seller fails to deliver goods, the direct loss is the difference between what the buyer paid and what it now costs to buy the same goods elsewhere.
- Consequential (or indirect) loss – the loss that happens afterward, as a knock-on effect. For example, because the goods never arrived, the buyer lost a big resale deal, or a factory had to shut down for a week.
In plain words: direct loss is what breaks immediately; consequential loss is what breaks because the first thing broke.
Where Does This Term Come From?
In Indian law, this concept comes straight from the actual text of Section 73 of the Indian Contract Act, 1872:
“When a contract has been broken, the party who suffers by such breach is entitled to receive, from the party who has broken the contract, compensation for any loss or damage caused to him thereby, which naturally arose in the usual course of things from such breach, or which the parties knew, when they made the contract, to be likely to result from the breach of it. Such compensation is not given for any remote and indirect loss or damage sustained by reason of the breach. Explanation. – In estimating the loss or damage arising from a breach of contract, the means which existed of remedying the inconvenience caused by the non-performance of the contract must be taken into account.”
The Supreme Court has interpreted this section in several judgments. Two of them explain it clearly:
In Indian law, this concept is rooted in Section 73 of the Indian Contract Act, 1872, which deals with compensation for loss caused by breach of contract. The Supreme Court has interpreted Section 73 in several landmark judgments, and two of them explain the idea clearly:
Murlidhar Chiranjilal v. Harishchandra Dwarkadas (AIR 1962 SC 366): The parties entered into a contract for the sale of canvas. The seller failed to deliver the goods as agreed. The buyer claimed damages, arguing that the seller knew the goods were intended to be transported to Calcutta and that the buyer had consequently suffered a loss. The Supreme Court held: “Compensation under Section 73 is available for losses that naturally arise in the usual course of things from a breach of contract, and losses that the parties knew, at the time of entering into the contract, were likely to result from its breach.” The Court emphasized that remote and indirect losses cannot automatically be recovered, and it also recognized the injured party’s duty to mitigate its loss.
Karsandas H. Thacker v. Saran Engineering Co. Ltd. (AIR 1965 SC 1981): The buyer entered into a contract for purchasing scrap iron. He intended to resell it for export but did not communicate this particular purpose to the seller. When the seller failed to deliver the goods, the buyer claimed damages based on the loss suffered from the intended resale transaction. The Court held: “The buyer could not recover the additional loss because the seller was not aware of the intended export transaction when the contract was made.” The loss was considered too remote to be recoverable under Section 73.
Together, these cases establish the foreseeability principle: a party is only responsible for losses it could reasonably have foreseen when the contract was signed, not for every loss that eventually follows.
Why This Matters in a Contract
Without a clear understanding of consequential loss, parties can end up exposed to open-ended, unpredictable liability. Imagine a software vendor whose product has a small bug. If the client suffers a loss of millions in lost business because of that bug, should the vendor pay all of it, even for things it never imagined?
This is exactly why contracts include a “limitation of liability” or “exclusion of consequential loss” clause. Its purpose is to:
- Cap or exclude liability for indirect losses such as loss of profit, loss of business opportunity, loss of goodwill, or loss of data.
- Keep liability limited to the direct, foreseeable loss that naturally flows from a breach.
- Give both parties certainty about their maximum financial exposure before they sign.
Without such a clause, a party could technically be held liable for losses it never anticipated when agreeing to the deal – which can make contracts commercially risky, especially for service providers, vendors, and consultants.
How to Use This in a Contract
If you’re drafting or reviewing a contract, here’s how the concept of consequential loss is typically put to use:
- Add a limitation of liability clause. State clearly that neither party will be liable to the other for indirect, special, or consequential losses – and list examples (loss of profit, loss of revenue, loss of data, loss of goodwill).
- Define what counts as “direct loss.” Since Indian courts look at what the parties actually foresaw, spell out what losses are expected and recoverable (e.g., cost of replacement goods, repair costs).
- Disclose special purposes upfront. If one party has a specific plan (like reselling goods for export, as in the Karsandas case), it should communicate this clearly at the time of contracting – otherwise, any resulting loss may be considered too remote to claim.
- Set a liability cap. Many contracts add a monetary ceiling (e.g., “total liability shall not exceed the contract value”) so that even direct losses remain predictable.
- Keep a duty-to-mitigate clause. Courts expect the injured party to take reasonable steps to reduce its own loss – reflecting this in the contract avoids disputes later.
Here’s what an actual clause like this looks like in a commercial contract:
“Limitation of Liability. Notwithstanding anything contained in this Agreement, in no event shall either Party be liable to the other Party for any indirect, special, incidental, or consequential damages, including but not limited to loss of profit, loss of revenue, loss of business opportunity, or loss of goodwill, arising out of or in connection with this Agreement, whether in contract, tort or otherwise, even if such Party has been advised of the possibility of such damages. Each Party’s total aggregate liability arising out of or in connection with this Agreement shall not exceed the total fees paid or payable under this Agreement in the twelve (12) months preceding the event giving rise to the claim.”
Notice how the clause does three things at once: it excludes indirect/consequential losses by name, it caps total liability at a fixed amount, and it applies to both parties equally , so no one is left over-exposed.
A well-drafted clause protects both sides: it gives the breaching party predictability, and it gives the injured party clarity on what it can realistically claim.
Watch the Full Breakdown
Reading about these judgments is one thing, hearing them broken down case by case makes the foreseeability principle click much faster. Check out the video attached to this post for a quick, visual walkthrough of both judgments discussed above. Here’s what it covers:
